Proposals that close: the structure of a 15-page brand-story proposal
Why most proposals read like invoices
Open the last proposal your agency sent. Odds are it starts with your logo, your history, your team photos — and gets to the client's actual problem somewhere around page six, just before a price table. From the buyer's side, that document says: here is who we are, here is what it costs. It asks them to do the hard work of connecting your capabilities to their situation.
A proposal that closes does that work for them. It is structured as a story with four movements: problem → idea → proof → pricing. Everything in the document either advances that story or gets cut.
The four movements
Problem: prove you listened
Restate the client's situation in their own words — sharper than they said it, if you can. This is the most underrated section in any proposal, because it is where trust is actually won. A buyer who reads their problem accurately described stops evaluating you as a vendor and starts reading you as a partner. Include the cost of doing nothing: what stays broken, what the delay compounds into.
Idea: one clear thesis
Not a list of services — a point of view. "Your funnel does not have a traffic problem, it has a trust problem, and here is the campaign that fixes it." One idea, stated early, gives the rest of the document a spine. Deliverables then read as the logical consequence of the idea rather than a menu.
Proof: reasons to believe
Relevant past work, your process, the team who will actually do it. If you are a young agency without a case-study library, do not fake one — show process instead: how you will work, what week one looks like, how decisions get made, what the client sees and when. Specificity is proof. Vague credentials are not.
Pricing: make deciding easy
Price is where most proposals get nervous and go quiet. Do the opposite: present it clearly, with options.
A page-by-page skeleton
Fifteen pages sounds long; it reads fast because each page carries one idea. A structure that works:
- 1. Cover — the client's name larger than yours, and a title that names the outcome, not "Proposal."
- 2. A personal letter — five sentences from a named person, not "the team."
- 3–4. Their situation — the problem restated, and what it costs to leave unsolved.
- 5. The big idea — one page, one thesis.
- 6–8. The approach — phases, what happens in each, what the client receives.
- 9. Timeline — real dates, including what you need from the client and when.
- 10. The team — the people on this account, not the founders' bios.
- 11–12. Proof — the two most relevant pieces of work, or the process pages described above.
- 13. Investment — the pricing page (see below).
- 14. Terms and scope boundaries — what is included, what is extra, revision rounds, payment schedule.
- 15. Next steps — exactly what accepting looks like and what happens in the first week after.
Pricing pages that work
- Offer three tiers. A single number invites yes/no; three options invite "which one." Most buyers pick the middle, so build the middle tier as the engagement you actually want to run.
- Name tiers by outcome ("Launch," "Grow," "Lead"), not by size ("Basic," "Premium").
- Show the price in the client's currency and be unambiguous about tax treatment — GST line-itemed for Indian clients, VAT handling stated for European ones. Ambiguity here reads as inexperience.
- Anchor with the top tier. Its job is to make the middle look sensible. It should still be a real offer you would happily deliver.
Send fast, and lower the friction to yes
Two operational habits compound over a year of proposals:
- Speed. A proposal delivered within a day or two of the conversation lands while the problem is still vivid. One delivered in two weeks arrives after enthusiasm has cooled and rivals have called. Templating the skeleton above is what makes speed possible without lowering quality.
- Frictionless acceptance. The fewer steps between "reading" and "accepted," the better. A link the client can open without an account, an accept button, and a clear deposit step beats a PDF that must be printed, signed, scanned, and emailed back. Watching engagement — did they open it, which pages held attention — also tells you when to follow up and what to address when you do.
The story structure is not decoration. It mirrors how buyers actually decide: do these people understand my problem, do they have a real idea, can they deliver it, and is the price a decision I can defend. Answer those four questions in that order, and the proposal does the selling before the follow-up call.