Write Proposals That Support a Decision

A proposal is a decision document. Its job is to help a customer understand what you recommend, why it fits the situation, and what accepting it would involve. A polished document can still fail at that job if the actual commitment is scattered across pages of background material. Before adding design or detail, identify the decision the customer needs to make. Then organize the proposal around the information required to make that decision responsibly.

Open with the problem and the intended outcome. Use language the customer recognizes from your conversations, but do not copy vague wording without clarifying it. If the customer wants a process to become “more efficient,” explain which part of the work the engagement addresses. State what you understand and where that understanding depends on assumptions. This gives the reader an early opportunity to recognize a mismatch before reaching the price or implementation schedule.

Describe the scope through concrete work and deliverables. Explain what you will do, what the customer will receive, and how the work fits together. A list of activities alone can leave a buyer uncertain about the result. A list of outcomes alone can conceal the effort and dependencies involved. Connect the two. Where something important is excluded, state it clearly and explain how it will be handled if it becomes necessary during the engagement.

Make responsibilities visible. Identify the information, access, participation, and decisions required from the customer. Explain how missing inputs affect the work rather than hiding that issue in a general disclaimer. A timeline that assumes immediate feedback is fragile if nobody has agreed to provide it. Show major milestones and the conditions needed to reach them. Use dates when they are supportable; otherwise explain the sequence and what must be resolved before a firm schedule is established.

Present the fee in a way that matches the scope. Explain what is included, when payment is due, and which circumstances could change the price. If you offer alternatives, give each one a meaningful difference. Three packages that vary only in vague labels force the buyer to guess. A useful comparison explains the work included, the tradeoffs, and the responsibilities associated with each option. Keep recommendations grounded in the customer's needs rather than the package you prefer to sell.

Explain how progress and completion will be assessed. For some engagements, that means accepted deliverables. For others, it involves measures agreed at the start. Distinguish the work you control from business outcomes affected by other factors. Avoid promising a result that depends on unverified assumptions or decisions outside your scope. Include a clear process for questions and changes. A customer should understand how to raise a concern without wondering whether every discussion creates an additional charge.

Keep the accepted version with the project record. When the scope changes, document the revised commitment so the delivery team and customer are working from the same agreement.

End with the next action and give the buyer a practical route to clarification. Before sending, ask someone unfamiliar with the opportunity to read the document and describe the commitment in their own words. If their account differs from yours, revise the proposal. The test is whether a reasonable reader can understand what will happen after acceptance. Good proposals reduce ambiguity before work begins, which protects the customer relationship as much as it supports the sale.