Proposal Template

You are working from a proposal structure of eight sections, where the scope section states what is excluded and every milestone is tied to a named trigger. You have been activated to close with one specific action and date.

PROPOSAL TEMPLATE Proposals rarely lose on price — they lose money on two quieter mistakes: a scope section that never states what's excluded, and an ending that leaves the client nothing specific to do next. This template puts eight sections in the order a client reads them, with scope, assumptions, and a revision policy written down before anyone signs, so the work you get paid for matches the work you agreed to do. THE STRUCTURE 1. SUMMARY — two to three sentences: problem, fix, price, timeline. Write last, after everything else is drafted — a compression of the real proposal, not a pitch that overpromises against section 4. 2. UNDERSTANDING OF THEIR SITUATION — the specific problem, its cause, and what it's costing them, in their own numbers where you have them. Generic language ("companies today face challenges...") is the fastest way to read as an unedited template. 3. PROPOSED SOLUTION — what you'll do and why it solves the problem in section 2. Tie every major piece back to something specific there — a solution that doesn't visibly answer the stated problem reads as boilerplate. 4. SCOPE OF WORK, WITH EXCLUSIONS — deliverables, what's included in each, then explicitly what is NOT included — the section that protects your margin. No exclusions list is the single most common cause of scope creep. 5. ASSUMPTIONS AND REVISION POLICY — what has to be true (client inputs, access, a named contact) and what happens to price/timeline if it breaks. Revision policy: rounds included, cost or process beyond that. 6. TIMELINE TIED TO NAMED TRIGGERS — milestones with the event that starts the clock ("Week 1 begins on signed contract and deposit"), not just "Week 1." A calendar-anchored timeline breaks the moment the client signs late. 7. PRICING AND TERMS — total price, payment schedule, what triggers each payment, late terms, currency/taxes. Ambiguity here is where disputes start weeks after everyone thought they'd agreed. 8. TEAM — who's doing the work, one line of relevant experience each, and the client's point of contact. Skip if solo — an unnamed team on a multi-person project reads as a bait-and-switch risk. NEXT STEP — one specific action and date ("sign and return by Friday 28 August to hold the 8 September start"), not "let us know if you have questions." An open-ended ending gets read and shelved. A FILLED EXAMPLE PROPOSAL: CLIENT ONBOARDING REDESIGN