Client Proposal

What this does

Turns your notes from an exploratory call into a short, outcomes-first proposal - the client's problem in their own words, what'll be different when the work is done, how you'll get there, and exactly what's in and out. Pricing is left for you to complete. The draft goes out the same week the call happened, while the conversation is still warm.

What you give it

• Your notes from the exploratory call - rough is fine, pasted or attached
• Who the proposal is addressed to, and their role (optional - you'll be asked if it's unclear)
• Your standard phases or way of working, if you have one you want reflected (optional)
• Anything discussed on the call that must not appear in writing (optional)

How it does the work

1. Read the call notes fully before drafting.
2. Ask up to 3 short questions if essentials are missing - who signs this off, roughly how long the engagement runs, or whether anything from the call is off the record. Then proceed.
3. Find the client's problem in their own words. If the notes quote them, use the quote. If they don't, paraphrase closely and mark it [to confirm] so the user checks it sounds like the client before sending. The opening of a proposal that echoes the client's language wins; one that opens with the consultant's method loses.
4. Write the outcomes before the approach. Outcomes are what's different for the client afterwards - a decision made, a team aligned, a process that stops leaking time. Not deliverables, not activities.
5. Structure the approach as 2-4 named phases, each with a plain-words purpose and what the client sees at the end of it. Use the user's standard phases if provided; otherwise derive sensible ones from the notes.
6. Draft the inclusions and exclusions list. Exclusions matter as much as inclusions - they're what protect the engagement from scope creep. Pull likely exclusions from the notes (things mentioned but out of scope) and mark uncertain ones [to confirm].
7. Leave every commercial figure as [to complete] - the fee, payment terms, validity period. Never suggest a price, a rate or a discount.
8. Draft using the output layout. Two pages maximum - a proposal is an invitation to say yes, not a contract.
9. Do a client-readiness pass: warm but not gushing, confident but not salesy, zero jargon. Read it as the client would - does every section answer "what's in this for me?"
10. Show the draft, list the [to confirm] and [to complete] items in one place, and offer one revision pass.

Output layout

# Proposal - [Engagement name]

**Prepared for:** [Name, role, organisation]
**Prepared by:** [Your name / business name]
**Date:** [date]

## The problem
[The client's situation in their words, two or three sentences. What's hurting, what it's costing them, why now.]

## What'll be different
By the end of this engagement:
- [Outcome 1 - a change in their world, not a deliverable]
- [Outcome 2]
- [Outcome 3]

## How we'll get there
### Phase 1 - [Name]
[What happens and why, two or three sentences. What the client sees at the end of it.]

### Phase 2 - [Name]
[Same.]

### Phase 3 - [Name]
[Same, or remove if two phases.]

## What's included
- [Item]
- [Item]

## What's not included
- [Item]
- [Item] [to confirm]

## Investment
[to complete]

**Payment terms:** [to complete]
**This proposal is valid until:** [to complete]

## Next step
[One sentence - the single action that starts the work, e.g. reply to confirm and we'll book the kick-off.]

Rules

• Australian English with contractions - organise, prioritise, we'll, they've.
• Never invent scope, timelines, client quotes or figures. Gaps are [to confirm]; money is always [to complete].
• Benefits before features throughout. Every phase description says what the client gets, not just what the consultant does.
• The client's language beats the consultant's. Mirror their words for the problem; save methodology names for the appendix or leave them out.
• No pressure tactics - no fake urgency, no "limited availability" unless the user says it's true.
• Keep it to two pages. If it's longer, the approach section is doing too much.
• This skill drafts the proposal only. Contracts, terms of engagement and pricing strategy are the user's call.