How to write a business proposal
Proposals win or lose before the meeting.
Answer three questions in order: do you understand my problem, can you solve it, and what happens next. Build from a maintained library rather than writing from nothing each time, because rebuilding under deadline is why quality varies and items get missed.
Is it a fit?
Problem
It opens with their problem in their words, before anything about you.
Scope
What is in, what is out, and what happens when it changes.
Decision
One clear next step with a date, not a menu and a hope.
Start here. You get back what one inquiry is worth, which tells you how much a proposal can justify.
What an inquiry is worthThe plan
Do these six, in order
A time against each one and a way to tell it is finished.
Open with their sentence, not yours
Quote the words they used on the call.
30 minutes · Done when the first paragraph says nothing about you
Recommend one plan
Name the alternatives and set them aside.
1 hour · Done when there is one thing to say yes to
Put the proof beside the promise
Every claim sits next to its evidence.
1 hour · Done when no claim stands on its own
End every section with the next step
One number, one date, one action.
30 minutes · Done when the reader knows what happens if they agree
Design for the ninety second skim
Headings, bold first lines, a summary at the top.
1 hour · Done when someone reading only the bold still knows the plan
Send it while the call is warm
Same day.
30 minutes · Done when it went out inside twenty four hours
A proposal is not a description of your services. It is a document that helps somebody defend a decision to other people in their business, often when you are not in the room. Most proposals lose because they are written for the sender rather than for that conversation.
The sequence below assumes a considered purchase where more than one person has to agree.
01.Open with their problem in their words
The first paragraph should describe their situation so accurately that they recognize themselves in it, using the phrases they used on the call. Not your interpretation, their language. If they said the month end takes a week, do not translate it into reporting inefficiency.
This does two things.
02.Recommend one plan
Recommend one plan. Options feel generous and function as work handed back to the buyer, which is exactly what they were hoping to avoid by hiring someone with judgment.
If scope needs flexibility, offer a clear core recommendation and name what could be added or deferred.
03.Put proof beside every promise
Every claim about outcome needs something specific standing next to it. A similar situation you handled, a number, a named constraint you worked inside, a piece of the method that shows you have done this before.
Vague reassurance reads as risk.
Twenty minutes with a practitioner from our team, and you leave with a plan for your specific situation.
Talk to an expert04.Price with one clear next step
Present the number plainly, in the same place every time, with what it includes and what it does not. Burying it, splitting it across pages, or dressing it up all read as discomfort, and discomfort about price is contagious.
Then give exactly one next step, with a date.
05.Design for the ninety-second skim
Assume the first read takes ninety seconds and happens on a phone. Whoever is deciding will skim headings, the recommendation, the number, and the next step, then read properly only if that skim holds together.
So write it to survive being skimmed: informative headings, short paragraphs, one idea per section.
06.Send it while the call is warm
Send within twenty four hours of the conversation, while the problem still feels urgent and your explanation of it is still the freshest one they have heard. Every extra day lets the internal urgency cool and lets a competitor reframe the problem.
A good proposal sent quickly beats a perfect one sent next week, almost every time.
Rebuilding every proposal from the last deal's file.
Burying the ask under credentials.
A great call followed by slow paperwork; the delay reads as a preview.
Questions we get
The ones that come up on almost every call.
How long should a proposal be?
Long enough to answer the objections and no longer.
Should the price be in the proposal or discussed separately?
In the proposal, stated plainly.
Do options increase the chance of a yes?
Usually the opposite.
What do I do when a proposal goes quiet?
Assume a busy quarter rather than a no, and follow up with something useful instead of a nudge.
How should a proposal end?
With the next step, named and dated, and the smallest commitment that moves it. Most proposals end by thanking the reader, which asks for nothing and leaves them to work out what happens now. If the last page does not say who does what by when, the proposal has handed its own momentum back to the person least motivated to carry it.
Most of this is doable in house.
Your results so far
Kept in this browser, sent nowhere.
By Shaheer Shaikh, technology and operations consultant · Updated October 3, 2026
Read next
The service behind this guide, the questions people ask, and the next thing worth reading.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built