How to Write a Proposal That Closes

Most proposals are brochures with a price at the end. They open with an introduction to the company, list capabilities, describe the process, and eventually arrive at a number the buyer skipped ahead to twenty seconds ago.

A proposal has a much narrower job: it is the written record of what you already agreed on the call. If it contains anything the buyer is seeing for the first time, something went wrong earlier.

The rule that governs everything

No new information.

Every element of the proposal — the problem, the approach, the rough price, the timeline — should have been discussed on the discovery call. The document exists so they can share it internally, compare it against their own memory, and sign it.

A surprise in a proposal is a surprise you have no opportunity to handle. You are not in the room when they read it.

The structure

1. Their problem, in their words

The first thing on the page. Not your company.

The situation Month-end reconciliation currently takes your team roughly two days, and in three of the last six months it has pushed the management accounts past the board deadline.

Quote them where you can. When a buyer reads their own words back, two things happen: they know you listened, and they re-experience the problem that made them take the call.

If you can't write this section from the call, you didn't diagnose properly and the proposal is premature.

2. What success looks like

The outcome, stated so it can be checked later.

Outcome Reconciliation completed within two working days of month end, without your team touching it, from the first month.

Note this is an outcome, not an activity. "We will provide bookkeeping services" describes what you do. The version above describes what changes for them.

3. Scope — and, more importantly, exclusions

Two lists. The second one does more work.

Included: specific deliverables, quantities, frequencies.

Not included: everything a reasonable person might assume comes with it and doesn't.

Not included Historic clean-up before the start date, VAT filing, payroll, or software licence fees. Any of these can be quoted separately.

This section feels awkward to write and it prevents most disputes. Every boundary you leave unstated becomes an assumption in the buyer's favour — not through bad faith, but because people fill gaps optimistically.

Add a change rate while you're there: what out-of-scope work costs. It converts an uncomfortable negotiation into a routine decision.

4. Options, not a price

Where possible, offer two or three. This is the single highest-leverage structural choice in the document.

| | Essential | Standard | Extended | |---|---|---|---| | Monthly reconciliation | ✓ | ✓ | ✓ | | Management accounts | — | ✓ | ✓ | | Quarterly review call | — | ✓ | ✓ | | Board-ready reporting pack | — | — | ✓ | | Monthly | £X | £Y | £Z |

One price invites a yes-or-no decision. Three options change the question from whether to buy into which to buy — and buyers who would have said no to one price frequently say yes to the smallest of three.

Keep it to three. Beyond that you've created work rather than clarity.

5. Timeline and what you need from them

Dates, and the dependencies that affect them.

Start within two weeks of signature. First delivery at the following month end, assuming access to the accounting system and read-only bank access within five working days.

Naming their dependencies protects the timeline and quietly sets the expectation that this is a two-sided arrangement.

6. Terms, briefly

Payment schedule, invoicing terms, notice period, what happens if either side wants out. A short paragraph, in plain language.

7. The next step

One instruction. Not "let us know your thoughts."

To proceed, reply to this email confirming the option you'd like and we'll send the agreement and get the start date booked.

What to leave out

• Your company history. Nobody buys because you were founded in 2019.
• A methodology diagram. Process detail reassures you and bores them.
• Every case study you have. One relevant example beats six irrelevant ones.
• Hedged language. "We would typically aim to" is not a commitment, and buyers read it as one you're avoiding.
• A price with no context. A number arriving after four pages about you feels like a demand. A number arriving after their problem and the outcome feels like a comparison.

Never send it into silence

This is where most proposals die — not rejected, just unanswered.

Book the walkthrough before you send. On the call, agree a specific time to go through it together. Then send it a day or two before, so they arrive having read it.

I'd rather walk you through it than have it sit in an inbox — can we do fifteen minutes Tuesday at 10?

A proposal you talk through gets a decision. A proposal emailed with "let me know what you think" gets a fortnight of nothing and an awkward chase.

If you must send cold, say exactly when you'll follow up and then do it on that day. The follow-up sequence matters more than the document once it has left your hands.

The mistakes

1. Opening with your company. The first page belongs to their problem.
2. New information in writing. Anything unagreed is a surprise you can't handle.
3. No exclusions. Unstated boundaries become assumptions in their favour.
4. One price. Turns a which-one question into a whether question.
5. Length as effort. Long reads as padded, not thorough.
6. Emailing and waiting. The most common way a winnable deal ends.

What to do next

Take your last proposal and check the first paragraph. If it's about you, rewrite it as their problem in their words — and add an exclusions section if there wasn't one. Those two changes address the most common reason proposals lose and the most common reason delivered projects turn unprofitable.