How to write a project proposal that wins the job
Most freelance proposals are structured backwards. They open with the freelancer's background, move through a list of deliverables, and arrive at a price on the last page, where it lands like a bill. The client reads it in reverse anyway — price first, then whatever it takes to justify it — and by the time they reach your credentials they have already decided.
A proposal is not a description of what you will do. It is an argument that the outcome is worth the money, written in the client's language, with the decision made as easy as possible. Here is the structure that does that.
Open with their goal, in their words
The first line of your proposal should be a sentence the client could have written themselves. Not "Proposal for website redesign" but "You want the new site live before the March trade show, with a checkout that stops losing people on mobile."
This does two things at once. It proves you listened, which is rarer than it should be. And it frames everything that follows as being about their deadline and their leaking checkout, rather than about your design process.
If you cannot write this sentence, you do not know enough to send a proposal yet. Go back and ask.
Restate the problem before the solution
Spend a short paragraph on what is going wrong now and what it costs. Use their numbers if they gave you any, their words if they did not.
This section feels redundant to write — they already know their problem. It is not redundant to read. It is the part that makes a price look small. A 4,000 proposal against "we need a new site" is expensive; the same proposal against "we lose roughly a third of mobile checkouts" is cheap, and nothing changed except that the reader was reminded.
Sell the outcome, not the hours
Clients do not buy deliverables. They buy the state of the world after the deliverables exist.
So write "a checkout that works on the phones your customers actually use" rather than "responsive templates, 5 pages, 2 revision rounds". List the deliverables too — you need them for scope — but put the outcome first and the inventory second. The inventory is how you protect yourself. The outcome is how you get hired.
Offer three options, not one
A single price is a yes/no decision, and the easiest answer to a yes/no question from a stranger is no. Three options change the question from "should I hire this person?" to "which of these should I pick?" — a much better question to be inside.
The structure that works:
| Option | What it is | Its job |
|---|---|---|
| Essential | The smallest thing that genuinely solves the problem | Makes the middle option look reasonable |
| Recommended | What you would actually choose in their position | The one you expect them to take |
| Complete | Everything, including the things they have not thought of | Anchors the price and occasionally sells |
Label the middle one "Recommended" explicitly, and say in one line why. Most clients take it. Some take Complete, which is a pleasant surprise. Almost nobody takes Essential — its job is to exist.
Every option needs a real price. "From 2,000" is not a price, it is an invitation to negotiate downward before the conversation has started. If you are not yet sure what your numbers should be, work them out first with our rate calculator and pricing guide.
Make the scope boringly specific
This is the least exciting section and the one that saves you the most money. For the chosen option, state exactly what is included: how many pages, how many revision rounds, what formats, what you need from them and by when.
Then state what is not included. Copywriting, photography, ongoing maintenance, third-party licences — whatever is plausibly assumed but is not yours to do. One short "not included" list prevents most of the awkward conversations that happen in month two, and it is the difference between a change request and an argument. Our guide on handling scope creep covers what to do when the requests start anyway.
Timeline, terms and one clear yes
Three short blocks close the proposal.
Timeline. Real dates, with the client's dependencies marked. "Delivery 14 March, assuming brand assets by 21 February" protects you from a delay that was never yours.
Payment terms. Deposit amount, when the balance is due, and the payment window. A deposit is standard practice — 50% for a new client, 30% for a returning one — and stating it plainly in the proposal makes it a term rather than an awkward request later.
The ask. One action, unambiguous. "Reply with the option you'd like and I'll send the agreement and deposit invoice today." Not "let me know your thoughts", which generates thoughts rather than a decision.
Length, format and the mistakes to avoid
Two to four pages. A twenty-page proposal signals that you charge by the page and reads as a document to be dealt with later — and later is where proposals go to die.
Send a PDF, not an editable file, and put the price in the body of the email as well. If your proposal is a link, the client cannot forward it to the person who actually approves spending.
Three mistakes worth naming: leading with your bio (nobody has been hired on page one), leaving the price to the last page (they scroll there first anyway, without context), and sending it days after the call (send within 24 hours, while they still remember why they wanted this).
Frequently asked questions
How long should a freelance proposal be? Two to four pages. Long proposals read as work and get postponed, and postponed proposals rarely get accepted. Include the goal, the problem, the outcome, three priced options, a specific scope, the timeline and the terms — nothing else.
Should I put the price in the proposal? Yes, and not on the last page. Clients read price first regardless, so give each option a real number early enough that they see it alongside the reasoning. Ranges like "from 2,000" invite a negotiation downward before the conversation has even started.
Why offer three options instead of one price? A single price turns the decision into yes or no, and no is the easier answer. Three options change the question to which one, which is a far better question to be inside. Label the middle option as recommended — that is the one most clients choose.
How soon should I send a proposal after the call? Within 24 hours. Enthusiasm decays fast, and a proposal that arrives while the client still remembers the conversation converts far better than a more polished one that arrives a week later.