How to use it
- Restate the client's goal in their own words from your call notes.
- Describe the outcome — what's different for them when the work ships.
- List the scope as deliverables tied to that outcome, not tasks.
- Present 2–3 priced options so the client chooses which, not whether.
- Name the next step and make it one action.
- Add timeline, terms, and validity date — then send it while the call is still warm.
The skeleton
Copy this structure into your document tool of choice and fill the brackets. Every section earns its place; delete nothing until you've tried closing without it.
[PROJECT NAME] — proposal for [CLIENT] 1. WHERE YOU'RE HEADED [2–3 sentences restating the client's goal in their words. "You're launching X in Q4 and the current site undersells the product…"] 2. WHAT I'M PROPOSING [The outcome, not the activity. "A site that makes the product's value obvious in the first screen — built to ship before your launch date."] 3. THE WORK [3–6 deliverables, each tied to the outcome:] - [Deliverable] — [why it serves the goal] - [Deliverable] — [why it serves the goal] 4. OPTIONS Essential — $[X]: [tight core scope] Complete — $[Y]: [recommended; core + what protects it] ← most clients choose this Premium — $[Z]: [extended scope / more handled for them] All options include [revisions policy, file delivery, check-in cadence]. 5. WHEN YOU SAY YES [One step: "Reply 'Option B' and I'll send the agreement + kickoff invite the same day."] 6. DETAILS Timeline: [start → milestones → ship] Terms: [deposit]% to book, remainder [on milestones/at delivery]. This proposal is valid until [date].
Why options beat a single price
A single number invites yes/no; options invite which. Anchor with the premium tier, recommend the middle, and keep the essential tier genuinely useful — a decoy insults the client and they can tell. Deeper dive: the pricing-tiers guide below.
The two sentences that raise close rates
First, the goal restatement — clients decide you understood them before they read a single deliverable. Second, the validity date — not as fake urgency, but because open-ended proposals invite open-ended silence, and a date gives your follow-up a legitimate reason to exist.
Common questions
- How long should a freelance proposal be?
- One page of substance, two at most. Length signals uncertainty — the goal restated, the outcome, the scope, three options, and one next step fit comfortably on a page, and busy clients decide in the first half of it.
- Should I put the price in the proposal or discuss it first?
- Both: name a range on the call so the proposal never ambushes anyone, then present the precise options in the proposal where value frames them. A proposal whose price is a surprise is a proposal that gets 'we'll think about it.'
- How fast should I send a proposal after the call?
- Same day if you can, within 48 hours always. Time-to-proposal correlates strongly with closing — enthusiasm decays and other options appear. (This is exactly the gap North exists to close: notes in, sendable proposal out, while the call is still warm.)
Go deeper: read the full guide on the blog.