Profiles

Proposer Profiles

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use When

• Use this skill whenever proposal content needs the correct proposer identity, signatory, or voice.
• Load it when the user asks to write as a person, company, consortium, or client.

Do Not Use When

• The task is unrelated to proposal authorship or identity.
• A proposer profile has already been selected and does not change.

Required Inputs

Workflow

1. Determine who the proposal is being written for before drafting any section.
2. Load exactly one primary profile unless the engagement explicitly requires a consortium or joint venture.
3. Apply the selected profile to voice, signatory, experience framing, team composition, and branding.
4. Create or adapt a client profile if no existing file fits.
5. Re-check downstream sections for profile consistency before finalizing.

Stop condition: Stop when proposer identity, controlling framework, mandatory form, sector fit, current rule, or load-bearing evidence remains unresolved.

Recovery: Record the gap and owner, seek clarification or current evidence, and return only the separable proposal content that remains supportable.

Quality Standards

• Use one clear proposer identity across the proposal unless a multi-entity arrangement is explicit.
• Keep voice, credentials, and experience evidence aligned to the selected profile.
• Treat profile files as living records that can be updated after successful proposals.

Anti-Patterns

• Do not draft proposal content before resolving the proposer identity.
• Do not mix individual and company voices inside the same section unless the structure requires it.
• Do not reference Peter or Chwezi when ghostwriting for a client unless they are genuinely part of the team.
• Treating a neighbouring sector or framework as interchangeable. Fix: identify the controlling rule and primary outcome.
• Adding terminology without changing a delivery choice. Fix: link each term to method, risk, output, or evaluation criterion.
• Presenting an unverified current rule or statistic as settled. Fix: cite and date the source or mark it not assessed.
• Ignoring a missing mandatory input. Fix: stop the affected claim and assign an evidence owner.
• Letting sector or identity framing contradict methodology, staffing, schedule, or price. Fix: reconcile all affected sections before release.

Outputs

Evidence Produced

Capability Contract

This skill may read supplied profiles, solicitations, ToRs, approved references, and proposal drafts and may prepare routing guidance or draft content within the authorised workspace. Review is read-only by default. It must not invent credentials, certify compliance, submit a bid, accept terms, publish, disclose confidential information, or change source records without explicit authority.

Degraded Mode

If the solicitation, profile, current procurement source, sector evidence, network, or reviewer is unavailable, provide the narrowest useful qualified routing or draft. Mark the missing check not assessed, omit unsupported credentials, thresholds, dates, or compliance claims, and identify the evidence owner. An unassessed requirement is never a pass.

Decision Rules

Worked Example

A solicitation requires proposer identity, but one controlling input is missing. The proposal team applies this rule: Select one primary profile and document any consortium or sub-consultant relationship before drafting. It records the gap and owner, withholds the affected assurance, and proceeds only with content that can be verified. This avoids mixed voice, false credentials, or wrong signatory.

References

• Proposal skill router — orchestration, profile, reasoning, and release gates.

• Profile markdown files in this directory.
• Proposal-level orchestration.

Every proposal is written on behalf of a specific entity. The profile determines the voice, credentials, experience, and branding used throughout the document. Load exactly one profile before generating any proposal content.

How It Works

1. User specifies the proposer — "write this as Peter", "write this for Chwezi", "write this for [client name]"
2. Load the matching profile from this directory
3. Apply the profile to every section: voice, signatory, experience, team, references
4. If no profile exists for the specified proposer, copy client-template.md, fill it in with the user, and save it for future use

Available Profiles

Profile Selection Rules

What the Profile Controls

Combination Scenarios

Proposals sometimes involve multiple entities:

Individual Consultant + Associates

• Load peter-bamuhigire.md as primary profile
• List associates in team composition with their roles
• Voice remains first-person singular with "supported by" language

Company + Sub-Consultants

• Load chwezi-core-systems.md as primary profile
• Sub-consultants appear in team composition and association arrangements
• Voice remains first-person plural

Company as Lead + Peter as Named Expert

• Load the company profile as primary
• Peter appears in team composition with his CV
• Voice follows the company profile

JV or Consortium

• Load both company profiles
• Cover letter references the JV/consortium arrangement
• Voice: "The Consortium proposes…" or "The Joint Venture will…"
• Lead firm identified; each firm's role described

Writing for a Client

• Load the client's profile (or create one)
• Do not reference Peter Bamuhigire or Chwezi Core Systems unless the client is explicitly associating with you as a team member or sub-consultant
• You are the invisible proposal writer — the document speaks entirely in the client's voice

Keeping Profiles Current

After each successful proposal, update the profile with:

• New experience entries (project name, client, country, year, outcome)
• New team members or associates
• Updated qualifications or certifications
• New differentiators or branded frameworks

Profiles are living documents — they grow with every assignment.