How to write a business proposal that defends your price

What is the right structure for a business proposal?

This order is not a matter of taste. It follows the order in which a reader makes decisions: first they have to recognize their problem, then understand what will change, and only then does the price have something to be measured against.

1. 01Describe their situation in their wordsUse phrasing from the call. The client should recognize their own company in the first paragraph.
2. 02Name what changes and what it is worthIn their units: hours, jobs, returns, days per month. Not in adjectives.
3. 03Define the scope and what is outside itAn explicit 'out of scope' removes risk from the buyer's head and protects the project.
4. 04Put the price next to the cost of inactionOptions rather than a single number to accept or reject.
5. 05Add proof from a comparable situationA described analogous problem and result beats a wall of logos.
6. 06Answer the call's objections in an FAQEvery question you had to think about is a candidate.
7. 07Offer one specific next stepWith a date and a person. The decision should be possible in a reply to the email.

How do you open a proposal so it gets read to the end?

The first paragraph decides whether the rest is read. It has to describe the client's situation specifically enough that they think 'yes, that is exactly how it works here'. The simplest way to get there is to use their own words from the call — not a paraphrase, the phrasing they actually used.

It is also the one section worth over-investing in. A proposal with excellent pricing and a weak diagnosis loses to one with a strong diagnosis and ordinary pricing, because the first reads like a form and the second reads like understanding.

How do you present price so it is not the first thing negotiated?

Price does not defend itself — it is defended by what stands before it. Three things work regardless of industry: the cost of inaction named in the client's units, a range of options instead of one number to accept or reject, and an explicit statement of what is not included.

The third is underrated. An explicit 'out of scope' does not reduce the value of the proposal; it removes risk from the buyer's head and protects you from scope creep at the same time.

What should you do with the client's objections?

Write them down. An objection raised on the call will come back at decision time — the difference being that you will not be there. An FAQ at the end of the proposal is the cheapest place to answer it once, calmly, in full sentences.

Rule of thumb: every question you heard on the call and had to think about is a candidate. If a question feels awkward, that is a reason to include it, not to skip it — a missing answer reads as a missing answer.

How should a proposal end?

With one step, not three options. 'Let me know if this is of interest' hands all the work to the client and carries no date. 'If the scope looks right, I suggest starting 2 September; a reply to this email is enough to hold the slot' is a decision that takes ten seconds to make.

If the decision needs somebody else — and it usually does — the next step can be a short call with that person. What matters is that there is exactly one, that it is specific, and that it can be taken from the email.