Guides / Updated Mon 19 Oct 2026

How to write a freelance proposal a client can say yes to

What goes in, in what order, and how to price it so the client can decide without a call.

A client reads a proposal to answer three questions: what do I get, what does it cost, and when is it done. Everything else in the document exists to make those three answers believable. Write it in that order and most of the back-and-forth disappears.

Open with the figures, in one sentence

Put the price, the length and the delivery date at the top, before the letter: “€18,755 for four phases over 25 working days, delivered Fri 4 Dec.” A busy owner reading on a phone gets the whole deal in one line, and a manager it is forwarded to does not have to hunt for the total.

Write a short letter, not a pitch

Three short paragraphs: what you heard them say they need, what you are proposing in response, and what you need from them to start. Use their words for the problem. Leave out your process diagram and your agency history; they asked for a proposal, not a brochure.

Break the work into phases that run in order

Phases like Discovery, Design, Build and Launch give the work a shape the client can follow, and give every phase a start and an end date. Estimate each line in working days; the phases add up to the delivery date, skipping weekends, so the date is a consequence of the scope rather than a promise pulled from the air.

Price line by line

• One line per thing the client can recognise: “Storefront: Shopify build with 40 products, collections and checkout”, not “Development”.
• A fixed price, or a quantity times a rate when the amount is the point: “8 hours of support × €100”.
• A working-day estimate on every line, so the schedule is visible next to the money.
• Tax and deposit stated once, under the total, with the amounts worked out.

Give the client real choices

A single number asks for a yes or a no. A proposal with a design tier to pick and a couple of optional extras asks which, and the client who shaped the scope owns it. Show what each choice does to the total and the date before they make it.

How to set up options and tiers without turning the proposal into a menu

State the terms plainly

• When you get paid: for example 30% on acceptance, 40% at design sign-off, 30% at launch.
• How many rounds of changes each phase includes, and what further changes cost.
• When the work becomes theirs: usually once the final invoice is paid.
• How long the proposal stands before the prices need another look.

Make accepting one step, and say what it is

Ask for a typed name against one exact version, and record the date and what was accepted. Be honest about what that is: a record of acceptance, not a legal signature. If the work needs a signed contract, sign one alongside it; the proposal is still the clearest statement of what was agreed.

When the scope changes, revise; don’t rewrite

After a yes, changes happen. Keep the accepted version as it was and put the change in a new version, set against the old one line by line: what was added, what was removed, what it does to the total and the date. The client accepts the revision the same way they accepted the first one.

Before you send it

• Can someone who never spoke to you find the total, the delivery date and the deposit in five seconds?
• Does every line say what the client gets, in their words?
• Does every option show what it does to the money and the days?
• Is there exactly one way to say yes?