The proposal structure that closed 8 of my last 10 freelance projects

Most freelance proposals read like a menu: here's what I do, here's the price, let me know. Then they wonder why the client "went with someone else."

A proposal isn't a price list - it's an argument that you understand the problem better than anyone else bidding. Here's the six-part structure I've used to close the large majority of my recent projects. Copy it.

1. Mirror the problem in their words

Open with their problem, described the way they described it - not your services. If the discovery call had them say "our checkout is losing us sales and we don't know why," the first line is about that, verbatim.

"You mentioned checkout drop-off is costing you roughly 20% of potential orders, and you haven't been able to pin down where it's happening."

This one move separates you from every freelancer who opens with "Thank you for the opportunity."

2. State the outcome, not the deliverable

Clients don't buy "a redesigned checkout flow." They buy "fewer abandoned carts." Lead with the result.

"The goal of this project is a checkout flow that recovers a meaningful share of those lost orders - measured, not guessed."

3. Scope - bounded and explicit

List exactly what's included, and (quietly powerful) what's not. Ambiguous scope is where projects die.

Included:

• Audit of the current 4-step flow
• Redesign to 2 steps
• A/B test setup
• One round of iteration on the losing variant

Not included:

• Backend/payment-gateway changes
• Ongoing maintenance (available separately)

4. Price with an anchor

Never show one number alone. Show a good/better option so the client is choosing between your options instead of whether to hire you at all.

• Option A - Checkout redesign + test: $X
• Option B - A + a 30-day optimization retainer: $Y

The mere presence of Option B makes Option A feel like the sensible, safe choice.

5. Proof, briefly

One relevant result. Not your life story.

"I did a similar checkout rebuild for [type of company] and cart completion went from 61% to 78% in six weeks."

If you have no case study yet, use the process as proof: "Here's exactly how I'll approach this," with a short numbered plan. Specificity reads as competence.

6. A CTA with a gentle deadline

End with the single next action and a soft reason to take it now.

"If you'd like to move forward, reply and I'll send the agreement today. I'm booking new projects for the week of the 21st, and I keep two slots open per cycle."

Real scarcity (your actual capacity), not fake urgency.

The whole thing fits on one page. Clients don't read ten-page proposals; they skim for "does this person get it" and "what's it cost." Nail parts 1, 2, and 4 and you're already ahead of most.

I ended up templating this into a Claude Code skill (/proposal) - I paste the job post or my call notes and it drafts the six parts in this structure so I'm editing instead of staring at a blank page. It's in a small pack of freelance skills; the invoice-generator one is free to try the format: https://agentia11.gumroad.com/l/qclmyx

But the structure above is the actual value - it works whether you write it by hand or not.