A pattern I see constantly at 10 to 50 person companies. The sales call goes well. The prospect is engaged, asks good questions, and says send me a proposal. You spend three hours on a document, send it, and then the thread goes quiet. Two follow-ups later you write it off as price.
It was rarely price. In most of these cases the proposal simply did not work as a document, because the person who asked for it was never the only person who had to read it.
The proposal is read by people you never met
Here is what usually happens to your document. Your contact opens it, skims it, and decides whether it is worth their reputation to push internally. If it is, they forward it to a finance person, an operations lead, and possibly an owner. Those people did not attend your call. They have no context, no rapport with you, and no memory of the problem you discussed.
So the document has to do the selling on its own, to people who are reading it cold, between other tasks, on a phone. Most proposals are written as if the reader already agrees that the problem matters. That assumption is where they fail.
Your contact becomes your salesperson the moment they forward the file. Everything in the document should make their job easier. If they cannot explain your proposal in two sentences to their boss, you lose, and you never find out why.
Fix one: write the problem back in their words
Open with a page that describes their situation, using the language they used on the call. Not your service description. Their problem.
If a distribution company told you their quoting process takes four days and they think they are losing jobs to faster competitors, the first paragraph of your proposal says that. Four days. Losing jobs. Their words.
This does two things. It proves you listened, which is worth more than any credentials page. And it gives the finance person who never met you a reason to keep reading, because the document opens with a business problem rather than a vendor introduction.
Take notes during discovery specifically so you can do this. The phrases people use about their own problems are more persuasive than anything you could write. A good discovery call gives you this material for free.
Fix two: price the outcome where you can
When a proposal prices hours, the reader compares your hourly rate to other hourly rates. That is the only comparison the document makes available, so that is the comparison they run.
Price the work as a defined scope with a defined result and a fixed number, where you can. Not because it earns more, though it often does. Because it moves the conversation from what does an hour cost to is this worth doing.
Where hourly is genuinely how the work is sold, put the total investment first and the rate breakdown second, in smaller type, as supporting detail. The reader should encounter the number they need to approve before the arithmetic behind it.
And show what the number is set against. If a company is losing two jobs a quarter to slow quoting, and an average job is worth $40,000, then a $12,000 project has an obvious frame. You are not claiming a result. You are giving the reader the arithmetic they would do anyway, using their numbers.
Fix three: give them one clear recommendation
The three-tier proposal is standard advice and it works in some markets. At a small company buying a service for the first time, it often produces paralysis.
Three options means someone has to build an argument for which option, on top of the argument for whether at all. That is two decisions where you wanted one, and the second decision needs a meeting. Meetings get scheduled for next month.
Lead with one recommendation, stated plainly: based on what you described, here is what I would do and why. If you want to offer flexibility, offer it as a note under the recommendation, along the lines of we could start with the audit alone if you would prefer a smaller first step.
One clear recommendation with an optional smaller version is easier to approve than a menu. It also signals that you have an opinion, which is most of what people are buying when they hire an outside adviser.
Fix four: answer the risk question before it is asked
Every person who reads your proposal is silently running a risk calculation. What happens if this does not work. Who looks bad. How much money is stranded.
Nobody says this out loud, which is why most proposals never address it. The objection stays unspoken and the deal stalls without a stated reason.
Address it directly in a short section. What the first 30 days produce, so there is an early checkpoint. What happens if they want to stop. Whether anything they pay for remains theirs if the engagement ends. Who does the work, specifically, including whether it is you or somebody else.
A named exit is reassuring rather than off-putting. A buyer who knows how to leave finds it much easier to start. The section takes a paragraph and it removes the reason most stalled proposals stall.
Fix five: make the next step small and dated
Most proposals end with let me know if you have any questions. That is not a next step. It is an invitation to do nothing, which is the default action in every organisation.
End with one specific, small, dated action. A 20 minute call on a named day to walk through questions. A signature line with a start date attached. A single decision you are asking for, by a date, with a reason for that date if one genuinely exists.
Do not invent urgency. Owners recognise a fake deadline instantly and it costs you more than it gains. If the date matters because of your capacity or their season, say why. If it does not, just propose a date anyway, because a date creates a moment where a decision is expected.
What to cut
Most proposals at small companies are too long, and the length comes from sections nobody reads.
Cut the company history. Cut the methodology diagram. Cut the page about your values. Cut the long client list where none of the logos are in their industry. Each of these adds a page that the finance person has to scroll past to find the number, and every scroll is a chance to stop reading.
Keep one piece of proof, chosen because it matches their situation. A short account of similar work, with what the situation was and what changed, does more than eight logos. If you do not have a close match, say what you would do rather than implying experience you lack. Owners are better at detecting overclaim than most salespeople assume, and getting caught costs the deal permanently.
How long it should take you
If a proposal takes three hours, something is wrong with your process rather than your writing.
Build a structure once: situation, recommendation, scope, investment, risk, next step. Then each proposal is 40 minutes of writing the situation and recommendation in their language, and 10 minutes of adjusting the rest. The parts that change are the parts that matter, which is the right way round.
If you are writing proposals for enquiries that were never qualified, the problem is upstream. A follow-up system and a tighter qualification step save more hours than any template. So does a clear view of who you are actually trying to sell to, which is what an ideal customer definition is for.
The takeaway
Write the proposal for the person who was not on the call. Open with their problem in their words, give one clear recommendation with a number, name the risk and the exit, and end with a small dated action.
Then cut everything that exists to make you look established. The document is not there to impress anyone. It is there to let your contact win an argument in a meeting you will never attend.