How to Write a Business Proposal (and How Not To)
A proposal is not a price tag with feelings. Most read like a hostage note written by someone who wants the project less than you do.
A proposal has exactly one job: to make a busy person who has never met you feel safe handing you money. That is it. Yet somehow the average proposal manages to do the opposite, opening with three paragraphs about your 'passion for clean code' before mentioning, in passing, that it might cost something. The client did not ask for your origin story. They asked whether you understand their problem and whether you will disappear after the deposit clears.
The Full Truth
on A freelance web developer's project proposal to a small e-commerce client who asked for help with abandoned-cart sales
You spent 300 words on your 'design philosophy' and zero on the abandoned carts they actually emailed you about. You answered a question nobody asked, beautifully.
- 01
It is about you, not them
CriticalThe proposal opens with 'I am a passionate full-stack developer with 6 years of experience and a love for pixel-perfect design.' The client runs a shop bleeding money at checkout. They do not care about your pixels, they care about their cart. Open by naming their problem: 'You are losing roughly 7 in 10 shoppers between cart and payment. Here is how we get some of them back.' Make them feel seen in the first sentence, not paragraph five.
- 02
The price is naked and unanchored
CriticalPage four simply says 'Total: 4,800 dollars.' No breakdown, no link to value, no comparison to what those lost carts are costing them now. A number with no context is just a number to flinch at. Anchor it: 'You mentioned roughly 12,000 dollars a month walks out of the cart. This 4,800 build pays for itself in the first three weeks if we recover even a tenth of it.' Now the price is a bargain, not a bill.
- 03
Scope is a fog, so timeline is a guess
NotableIt promises 'a fully optimized, modern, scalable checkout experience' with a timeline of 'approximately 4 to 8 weeks, depending.' That range is a 100 percent margin of error and the word 'depending' is doing all the work. Define phases with concrete deliverables and dates, and list what is explicitly out of scope (no inventory migration, no new payment provider). Vague scope is how a 4-week job becomes a 4-month resentment.
A bit about me: I am a passionate full-stack developer with 6 years of experience and a love for building beautiful, pixel-perfect, scalable web experiences using modern best practices.
You told me roughly 70 percent of shoppers abandon their cart before paying. On your volume that is around 12,000 dollars a month walking out the door. This proposal is about closing that gap, not about me.
Deliverable: A fully optimized, modern, scalable checkout experience. Timeline: approximately 4 to 8 weeks, depending on requirements.
Phase 1 (week 1): one-page checkout, removing the 3 form steps where 60 percent of drop-off happens. Phase 2 (week 2): cart-recovery email triggered at 1 hour. Live by day 14. Out of scope: payment-provider changes and inventory migration.
- 1Delete your intro paragraph and rewrite the opening line as the client's problem in a number they will recognize.
- 2Replace the single 'Total' figure with a 3-line breakdown that anchors the price against the money they are currently losing.
- 3Turn the fuzzy deliverable into 2 or 3 dated phases, each with one concrete outcome, and add an explicit 'out of scope' list.
- 4Swap 'let me know your thoughts' for one specific next step with a date: 'Reply yes by Friday and I will send the contract and a Monday start.'
That was a stranger's business proposal. Drop yours, I will go just as hard.
One coffee, from €2,99. No mercy.
The good news is that proposals are absurdly easy to win, because the competition is mostly garbage. You do not need to be a poet. You need to restate the client's pain in their own words, show a path out of it, attach a number to it, and make the next step a single click. Do those four things in order and you will out-convert people with twice your experience. Now let me show you the gap between that and what actually lands in inboxes.
- 01Open with THEIR problem, in their own words, before you mention yourself once. Prove you were listening, not just waiting to pitch.
- 02Tie every deliverable to an outcome. Not 'I will build a website', but 'a checkout that stops losing you the 40 percent who bail on page two'.
- 03Price in fixed scoped packages, not hourly. Hourly punishes your speed and tells the client you have no idea how long this takes.
- 04State assumptions and what is OUT of scope explicitly. The boundary you draw now is the argument you avoid in week three.
- 05End with one clear next step and a deadline. 'Reply yes and I will send the contract Thursday' beats 'let me know your thoughts' every time.
- Leading with 'A bit about me' and a paragraph about your 'journey'. The client is not hiring your autobiography, they are buying a result.
- Burying the price on page four so it feels less real. It does not feel less real. It feels like you are ashamed of it, which makes them suspicious of it.
- Listing 47 services you offer when they asked for one. A scattergun proposal says 'I will take literally anything', which reads as desperate, not flexible.
- Quoting 'TBD' or 'depends on requirements' for scope and timeline. That is not honesty, that is you outsourcing your own planning to the buyer.
- Copy-pasting the same template with the previous client's name still in paragraph two. Yes, Sally has seen it. Twice. In the same week.