---
name: client-proposal-writer
description: "Writes a client proposal that restates their problem, shows competence without giving the method away, makes exclusions unmissable, and ends on a dated next step. Use when a consultant or agency has had a discovery call and must send a proposal that can be forwarded to the decision-maker without further explanation. Do not use for an agency project proposal built from a standard section list or a legal contract. Related topics: Business, Writing, Communication."
---

# Client Proposal Writer

Writes a client proposal that restates their problem, shows competence without giving the method away, makes exclusions unmissable, and ends on a dated next step.

## When to use

Use this skill when a consultant or agency has had a discovery call and must send a proposal that can be forwarded to the decision-maker without further explanation. Do not use it for an agency project proposal built from a standard section list or a legal contract.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Restate the client's problem in their own language, noting where it differs from the stated brief.
3. Describe the approach at the level of what will be done, leaving out how it is done.
4. Write the deliverables, timeline, and an exclusions section that cannot be missed.
5. Set out the price with its context and payment stages, with a tone matched to the competition and relationship.
6. End with a single next step and an expiry date, then check the document reads clearly to someone not on the call.

## Inputs

- **Who they are** (longer free text)
- **What they asked for** (longer free text)
- **What I think they actually need** (longer free text)
- **Who will read this** (longer free text)
- **Deliverables** (longer free text)
- **Timeline** (longer free text)
- **Explicitly not included** (longer free text)
- **Price and payment structure** (free text, e.g. "Total and deposit and stages")
- **Competition** (choose one: Sole supplier, A few others, Formal tender, No idea)
- **Relationship** (choose one: Cold, Warm intro, Existing client, They approached me)

## Output

A proposal in markdown with a problem restatement, approach, deliverables, timeline, a prominent exclusions section, priced investment, and a dated next step.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Client Proposal

Write this so it can be forwarded to someone who was not on the call and still make sense.

**The client**
- Who they are: {{Who they are}}
- What they asked for: {{What they asked for}}
- What I think they actually need: {{What I think they actually need}}
- Who will read this: {{Who will read this}}

**The work**
- Deliverables: {{Deliverables}}
- Timeline: {{Timeline}}
- Explicitly not included: {{Explicitly not included}}
- Price and payment structure: {{Price and payment structure}}

**The situation**
- Competition: {{Competition}}
- Relationship: {{Relationship}}

Open by restating their problem in their own language, so they know they were heard before they reach the number.

Show the approach at a level that demonstrates competence without handing over the method. There is a difference between what we will do and how we do it.

Make the exclusions unmissable, because that section prevents the argument in week six.

Adjust the tone to the competition and the relationship: a formal tender needs structure and compliance, a warm intro needs more narrative. Put the price in context rather than apologising for it, and end with a next step and a date the proposal expires.

## Pitfalls

- Describing the method in so much detail that the client can do the work without you.
- Burying the exclusions, which causes scope disputes mid-project.
- Apologising for the price instead of anchoring it to the value of the outcome.
