This guide focuses on a written proposal for a prospective client. A presentation is organized around a spoken narrative; see the presentation design guide for that format.
1. Reflect the client’s needs accurately
Summarize the client’s stated problem, goals, and constraints before describing your solution. Use language that shows you understand the brief, and distinguish confirmed facts from assumptions that still need discussion.
Define what success would mean for this engagement. Keep the objective specific enough to guide the proposed work without promising an outcome outside your control.
Confirm the decision-maker, review process, and timeline for the proposal. This helps you prepare the right level of detail and a relevant next step.
A proposal is easier to review when it answers the client’s questions in a predictable order: what you understood, what you recommend, what will be delivered, when it will happen, and what it costs.
2. Define scope, deliverables, and responsibilities
List what is included, what is not included, and what the client will provide. Describe deliverables in concrete terms so both parties can understand what completion means.
Explain the proposed phases or milestones and identify dependencies. If the plan relies on client feedback or supplied materials, state that clearly rather than hiding it in fine print.
Present pricing, payment timing, and assumptions accurately according to your business terms. Have the responsible person review these details before the proposal is sent.
Use a short executive summary for the recommendation, then let readers inspect the scope and assumptions. This helps a decision-maker understand the proposal without hiding details from people who need them.
3. Design a proposal that supports a decision
Start with the recommendation and a concise summary, then provide the reasoning, scope, schedule, and terms. Use headings and a clear visual hierarchy so a reader can find the details relevant to their decision.
Use Section Spatial to refine individual groups such as deliverables and timeline. Use Pages Spatial to arrange the proposal sections and move or resize them so the overall flow feels clear and balanced.
Use charts or visuals only when they clarify an approach, comparison, or schedule. Keep essential terms and explanations in readable text.
If there are options, state the difference in scope and tradeoffs for each. Avoid presenting multiple packages with labels that do not explain what changes between them.
4. Check the proposal before sharing
Confirm the client’s name, project details, scope, pricing, dates, and contact information. Check that the proposed schedule matches the deliverables and that all assumptions are stated plainly.
Review the design on the screen where the client is likely to read it. Make sure the decision, response deadline if applicable, and next step are easy to find.
Ask a colleague to check the proposal for ambiguity. If someone cannot tell what is included or what happens after approval, clarify those points before sending.
Keep negotiation or approval steps clear, including who should respond and whether the proposal expires. Use the terms your organization has approved.
