Skip to content

Proposal Writing

The proposal is the artifact you produce after the scoping call and before the SOW. It is a sales document — its job is to convince the prospect to pick your agency over alternatives, and to give the economic buyer the materials needed to authorize a purchase.

The proposal is not the SOW. The distinction is load-bearing for everything that follows:

  • The proposal sells the engagement. Persuasive tone, outcome-framed language, focus on the buyer’s business problem and your team’s credentials. It can be revised quickly because it is not yet binding.
  • The SOW commits both parties contractually. Precise scope language, defined deliverables, payment milestones, change-control mechanics, and termination clauses. It is reviewed by both parties’ legal or operations teams before signature.

A proposal that tries to be both ends up as neither: too long and legalistic to win the deal, too vague and aspirational to enforce. Treat the proposal and SOW as two separate documents, drafted in sequence.

A typical proposal moves through three states: an internal draft reviewed by delivery leadership, a polished version sent to the prospect, and a revised version after the prospect’s feedback. Once the prospect indicates intent to proceed, the proposal’s commercial commitments become the input to the SOW.

Use a standard section structure. Most winning agency proposals contain the same seven sections, in roughly the same order:

  1. Executive summary — one page maximum. Restates the prospect’s problem in their own language, names the proposed solution at the highest level, summarises commercial terms.
  2. Approach — how you will deliver. Phases, methodology, key milestones. This is where you demonstrate that you understand the work.
  3. Deliverables — what the prospect receives. A bulleted list with enough specificity to support the SOW.
  4. Team — named individuals where possible, with relevant credentials and the role each will play.
  5. Timeline — phase-level dates, key client decision points, and dependencies.
  6. Pricing — your fee structure, payment schedule, and what is included vs. excluded.
  7. Terms — high-level commercial terms (payment net, IP ownership, warranty), with the note that the SOW will contain the full contract.

Lead with the executive summary, write it last. The executive summary is the only section many decision-makers read in full. Write the rest of the proposal first, then distil the executive summary from it.

Quote what you know; phase what you don’t. When the scope contains genuine unknowns — integration with an undocumented legacy system, a new product whose requirements are still emerging — phase the engagement. Quote a fixed price for a discovery or proof-of-concept phase, and a not-to-exceed range or T&M model for delivery contingent on discovery output. Avoid pricing ambiguous scope as a single fixed-price commitment.

Anti-patterns to avoid:

  • The “kitchen sink” proposal. A 60-page document covering every capability your agency offers, in the hope that something resonates. Long proposals signal that you do not know which problem you are solving.
  • The boilerplate-only proposal. Reusing 80% of last quarter’s proposal with the prospect’s name swapped in. Buyers can tell, and it confirms their fear that they are a number to you.
  • The “we’ll figure it out” pricing. A T&M structure with no estimated range, no cap, and no checkpoint mechanism. Sophisticated buyers reject this on principle; unsophisticated buyers sign and then panic when invoices arrive.
  • The covert SOW. A proposal padded with 10 pages of contract terms. If you find yourself drafting termination clauses, you are writing the SOW — extract them.

Iterate fast on prospect feedback. When the prospect responds with questions or revision requests, turn the proposal around in days, not weeks. Slow response times signal slow delivery to come.

A successful proposal cycle ends with one of the following:

  • A client-countersigned proposal — formal acceptance of commercial terms, triggering SOW drafting
  • An informal verbal “yes” with feedback that you incorporate into a revised proposal, then countersign
  • A clear “no” with stated reasons, which you log for pipeline analysis
  • A defined next step that is not “we’ll think about it” — a follow-up meeting, a procurement review, an introduction to the economic buyer

In addition, you should have:

  • A shared understanding of scope between you and the prospect, validated by their feedback on the proposal
  • A clear path to SOW drafting with defined commercial terms agreed in principle
  • An internal record of the proposal version that the prospect approved, archived for reference during SOW drafting

Short-form vs. long-form. Boutique agencies often produce 4–8 page proposals — executive summary, approach, deliverables, team, timeline, price, terms. Enterprise-focused agencies produce 30+ page responses, especially for RFP-driven procurements where every scoring criterion must be addressed in writing. Short-form proposals win on relationship and clarity; long-form responses win on procurement compliance and breadth. Choose the format that matches the buyer’s procurement process, not the format your team prefers to write.

Fixed-price vs. phased pricing. Fixed-price proposals quote a single number for the entire engagement, with risk priced in as contingency. Phased pricing breaks the engagement into commitment-bounded stages: a fixed-price discovery, a fixed-price MVP, and an optional T&M continuation. Phased pricing is more honest when scope is uncertain, but it requires the buyer to make multiple commitment decisions, which slows the sale. Agencies in mature markets (Salesforce implementation partners, for example) lean toward phased pricing; agencies in emerging markets (early-stage product agencies) lean toward fixed-price headline numbers because they convert faster.

Proposal templates and tooling. Larger agencies maintain proposal libraries — pre-approved sections for team bios, methodology descriptions, case studies — assembled into custom proposals via a proposal-management tool (Proposify, PandaDoc, Better Proposals, or internal systems). Smaller agencies write each proposal from scratch in a word processor. Templated proposals win on speed and consistency; bespoke proposals win on perceived effort and customisation. Both approaches succeed when the underlying scoping work is rigorous.