How to Write a Business Proposal

How to write a business proposal: step by step

1. 1

   Restate the problem in the client's words

   Open by showing you understood the brief. Use the language the client used when describing the problem, not your internal terminology. This single move separates tailored proposals from templated ones.

2. 2

   Write the executive summary

   A short section stating the problem, your proposed approach, the expected outcome and the headline investment. Assume it may be the only part a senior decision maker reads. Write it last.

3. 3

   Set out the proposed solution

   Explain your approach and why it fits this problem. Keep it focused on how it addresses the client situation rather than on a generic description of your methodology.

4. 4

   Define the scope of work

   State exactly what is included and what is not. Ambiguity here is the single largest cause of unprofitable projects.

5. 5

   List concrete deliverables

   Name the artefacts the client will actually receive, with enough specificity that completion is not a matter of opinion.

6. 6

   Give a timeline with milestones

   Break the work into phases with dates or durations, and state what you need from the client at each stage. Dependencies you do not flag become delays you get blamed for.

7. 7

   Present pricing and the acceptance step

   Show the investment clearly, tied to the outcome. Include payment terms and a signature block so accepting the proposal is a single, obvious action.

The structure that works

Proposals vary by industry, but the sequence below holds up across most professional services work. It moves from the client, to the approach, to the commercial terms, in that order. Leading with your own credentials is the most common structural mistake.

Write the executive summary last

The executive summary is not an introduction. It is a compressed version of the entire proposal, and for senior stakeholders who were not in the original meeting it is frequently the only section read end to end.

It should stand alone: someone reading only that page should understand the problem, what you propose to do, what the client gets, roughly what it costs and how long it takes. Write it after everything else, when you know what you are summarising.

Show that you understood the problem

The fastest way to lose a proposal is to make it obvious that it is a template with the client name substituted in. The fastest way to win one is to reflect the client situation back accurately, including the constraints they mentioned.

Use their words. If they said "our invoicing takes three days every month and we keep making errors", do not translate that into "operational inefficiencies in the finance function". The former proves you were listening; the latter proves you have a thesaurus.

Deliverables must be checkable

A deliverable is something the client receives and can verify. "A comprehensive brand strategy" is not checkable. "A 12-page brand guidelines PDF covering logo usage, colour, typography and tone of voice" is.

This protects both sides. The client knows what they are buying, and you have a defensible definition of done. Vague deliverables are how projects end up with an extra month of unpaid revisions.

Timelines and client dependencies

Almost every overrun on a professional services project has the same cause: the client did not provide something on time. Feedback, content, access, approvals, sign-off from a third party.

Put those dependencies in the timeline explicitly, alongside your own milestones. "Week 3: client feedback on first draft (2 working days)" makes the dependency visible before it slips, and makes the resulting conversation a factual one rather than a blame one.

Pricing: give a choice, not an ultimatum

A single price is a yes or no decision. Two or three options turn it into a which one decision, which is a far better position to be in and frequently increases the value of the work won.

Where it fits, present a core option covering the essential scope and a broader one adding clearly valuable extras. Keep the difference substantive rather than cosmetic. Anchor on the outcome: what the work is worth to the client is a more useful frame than how many hours it takes you.

State payment terms here too. A deposit before work starts and the balance on delivery, or staged payments against milestones, is standard for anything substantial.

Length, and the "about us" trap

For most freelance and agency work, two to four pages wins more often than twenty. Length signals effort to the person writing it and signals work to the person reading it. Enterprise and public sector procurement is the exception, where formal requirements often dictate the format.

Keep credentials short and relevant, and put them near the end. Case studies earn their place only when they closely match the client situation. Three pages of logos and team biographies before the client reaches the scope is a proposal about you, and clients buy proposals about them.

Make accepting it easy

End with an unambiguous next step. A signature block for both the client and your authorised signer, with name, date and space for a signature, turns the proposal into its own acceptance document and removes a round of paperwork.

Then follow up. As with quotations, most proposals that go unanswered are lost to inertia rather than to a decision. One short, useful follow-up a week later is expected, not pushy.