A proposal should answer the question the client actually asked

Two documents get confused with each other

There is a document that describes your business — what you do, how long you have done it, what you have made before. And there is a document that describes what you propose to do about this client’s specific situation. Both are legitimate, and the second one is what wins work.

The common failure is sending the first while believing it’s the second. It arrives as several pages about the supplier with a price at the end, and the buyer finishes it knowing more about you and no more about whether their problem is going to be solved. A shorter document that engages with their actual circumstances beats it almost every time.

The buyer is choosing between risks

From the outside it looks as though the client is selecting the most capable supplier. Usually they are doing something narrower: eliminating the ones who might go wrong. They have limited ability to judge the work in advance, they will be answerable to somebody if the choice fails, and they are reading for signs of trouble more than for evidence of brilliance.

That reframes what a proposal is for. Its job is to reduce the perceived risk of choosing you: by showing the problem has been understood, by making the process predictable, and by leaving no obvious question unanswered. Ambiguity is not intrigue. It is an unresolved risk, and unresolved risks lose to clarity.

Begin by restating the problem in their words

The first section should say what you understood the situation to be, using the client’s language rather than your trade’s. This feels redundant, since they told you and they already know. It is the most valuable part of the document.

It proves you listened, which is rarer than it sounds. It gives them the opportunity to correct a misunderstanding before it becomes expensive. And it demonstrates, without any claim being made, that you can describe their problem clearly — which for many buyers is the strongest available evidence that you can solve it.

Then say what will happen, in order

The middle of a proposal should be a sequence: what you will do first, what comes after, what the client will see at each point and roughly when. Not a list of capabilities — a description of how the next several weeks will go.

This does more work than any amount of persuasion. A buyer who can picture the process can imagine explaining it to somebody else, and can see where their own obligations fall. It also produces better questions before the work starts, which is precisely when questions are cheap.

Say what you need from them

Almost every project that goes badly does so partly because the client did not supply something on time. A proposal that lists what you require, and when, converts that from an eventual complaint into an accepted condition.

It also has a slightly awkward benefit: it reveals the clients who were never going to engage. Somebody who reacts badly to being told they must provide information, access or a decision by a certain point is telling you something useful while it is still free to learn.

Write it for the room you are not in

The proposal will frequently be read by people you have never spoken to, forwarded without your covering note, and read again months later when somebody wants to know what was agreed. Very often it’s the only written record of the engagement that ever exists.

So it should stand on its own: dated, specific about what is included and excluded, clear about the price and the terms, and written in language a person outside the trade can follow. That is not bureaucracy. It is the difference between a document that keeps working after you leave the meeting and one that only made sense while you were explaining it.

The exclusions deserve particular attention, because they are the part everybody is tempted to soften. Writing down what is not included feels like introducing doubt into a document meant to persuade, and it is the single most useful paragraph in it. A client who reads that something is outside the scope may ask for it to be added and priced, which is a good outcome. A client who assumed it was included will discover otherwise at the worst possible moment, and the conversation will be conducted on the basis that you have failed to deliver rather than that they misunderstood.