How to write a project proposal that wins work

A proposal is how you win the work — it’s the document that turns an interested prospect into a signed client. A quote is just a price; a proposal shows the client you understand their problem and can solve it, then gives the price. Get it right and you compete on value, not on being cheapest.

Proposal vs quote vs estimate

A quote is a firm price for a defined scope.
An estimate is an approximate price.
A proposal wraps the price in context: the problem, your approach, the outcome and why you. Use a proposal for bigger or competitive jobs; a quote for simple, well-defined ones.

What goes in a proposal

The client’s problem, in their words. Open by showing you get it. This is what separates a proposal from a price list.
Your proposed approach. How you’ll solve it — phases, method, what makes you the right choice.
Scope & deliverables. Exactly what they get — and, just as importantly, what’s not included (your defence against scope creep).
Timeline. Phases or milestones with rough dates.
Price. Ideally a fixed project price tied to value, not an hourly figure. Anchor it against the outcome, not your costs.
Why you. Brief, relevant proof — results, similar work, a short testimonial.
A clear next step. One obvious call to action: “Reply accept and I’ll send the contract.”

Structure it to get a yes

Lead with their outcome, not your bio. Clients care about their result first.
Offer options (good / better / best). Tiered pricing lets clients choose how much rather than whether — and often nudges them up.
Keep it skimmable. Headings, short paragraphs, one clear price.
Put a validity date on it. It creates gentle urgency and protects your pricing.

From proposal to paid

A proposal is the start of the money trail, not the end. Once it’s accepted:

Price it right first with the rate calculator and turn the scope into a clean quote;
Lock scope and payment terms into a contract;
Invoice on the agreed milestones — and follow up so it’s actually paid.