The proposal should confirm a conversation

A proposal is often asked to do work that should have happened in discussion. It introduces the diagnosis, scope, price and decision process all at once, then waits for a response. Silence is unsurprising when the buyer has so much to resolve alone.

Before writing, confirm the problem, intended outcome, responsibilities and commercial range. Not every detail must be settled, but fundamental surprises should be removed. The document can then record an emerging agreement rather than launch a new negotiation by attachment.

Begin with the client's situation in language they would recognise. Describe the proposed work and why it follows from that situation. Separate deliverables from outcomes: a workshop is something you provide; improved decision quality is something the client hopes to achieve through it and subsequent action.

State dependencies. If success requires timely data, access to managers or an internal owner, make those conditions visible. A proposal that leaves client responsibilities implicit can create avoidable conflict once delivery begins.

Keep the decision clear. What exactly is the buyer approving? Which options remain open? What happens after acceptance? A beautifully designed document that obscures these points is commercially weaker than a plain one that resolves them.

Where possible, arrange a discussion of the proposal before sending it. The purpose is not to watch someone read. It is to make space for questions while the reasoning is still fresh and the next step is understood.