The seven proposal sections that earn the decision
For a single-buyer service-business deal, seven sections do the load-bearing work. Treat this as the smallest set that lets the client say yes without coming back with questions. It is opinion, not a standard.
-
Problem framing
What the client is actually buying, in the client's own language. This is the section that answers "did you understand us?" before any pricing number can be taken seriously.
-
Scope
What is in and what is not in. Two short lists. The "not in" list is the one that prevents expensive arguments later, so write it more carefully than the "in" list.
-
Deliverables
The artifacts that prove the work happened. Each item is something the client will receive when the engagement ends. "Three rounds of revisions on the homepage and two interior templates, delivered as a Figma file with developer-ready specs" is a deliverable. "Iterative design process" is not.
-
Timeline
Dates with checkpoints. The client wants to see when their team has to show up, when the first thing lands, and where the off-ramps are. "Week 3: first round of identity directions. Week 5: chosen direction applied to homepage. Week 8: developer handoff." A single end date hides the moments when projects slip.
-
Pricing
The number, the structure, and what the number includes. Treated in its own section below because it deserves the most careful writing in the document.
-
Terms
The boundaries that keep both sides safe before the engagement begins. Payment schedule, change-order process, cancellation. These are not the client contract; Baker and Enns advise saving the actual contract document for after you reach agreement in principle.
-
Next step
The smallest commitment that moves the deal forward. Sign below, pay the deposit, book the kickoff. A proposal that ends without a clear next action leaves the client to invent one. They will not.
Two things are explicitly off the list. A separate proposal executive summary block on top duplicates the job the first hundred words and the problem-framing section already do; cut it. An "about us" section assumes a stranger; by the time the proposal lands, the buyer is not one.
What goes in the first hundred words
The opening paragraph earns the rest of the document a serious read.
The opening paragraph names, in the client's own words, the problem the client is buying a solution to. Studio introductions, thanks for the opportunity, and famous-designer quotes belong elsewhere if they belong at all.
A weak opener is recognizable on sight:
Acme Studio is pleased to present this proposal for your consideration. Founded in 2014, we are a multidisciplinary creative agency partnering with growing brands to deliver world-class digital experiences. We believe in the power of storytelling to transform businesses, and we look forward to bringing that belief to your project.
The prose is fine. The problem is that the reader has just spent the first hundred words reading about the studio. They opened the document to find out whether you understood them. The first thing they read was a paragraph about you.
A strong opener does the opposite:
Northgate is preparing to raise a Series A in Q3, and the current brand was built for the pre-product company you were two years ago. The work in this proposal is the brand refresh that the next room you walk into will judge you on: a cleaner identity, an investor-ready website that loads in under two seconds on mobile, and a deck template the founder can adapt without a designer. We have scoped it to land six weeks before your target raise date, with two checkpoints in week three and week five so you can pull or change direction without a sunk-cost conversation.
Why it works. A hundred words, give or take. It names the company, the outcome ("Series A in Q3"), the deliverables in plain language, the timeline relative to the client's actual deadline, and the off-ramps. The client knows in one paragraph whether to keep reading.
Brennan Dunn names the underlying job directly: "you want to make it clear to your clients that you have a plan for how hiring you will yield some sort of financial return." The first hundred words are where that clarity lands.
What the proposal is actually for
A business proposal is the written half of a sale that has, by the time you sit down to write, mostly happened in conversation. The buyer does not decide inside the document; the document is the artifact that lets them say yes to a decision they have already begun to make.
Chris Do puts it bluntly: after value and price have been talked through, the proposal "is not a guess; it is a confirmation document for an agreement you have already made."
That lens changes what counts as failure. A proposal that documents the work in exhaustive detail but never names the outcome the client is buying has missed the document's job. It is what happens when the writer treats the proposal as a description of the work rather than as the document the client will use to make a decision.
It also changes how much the proposal has to carry.
"If you do your work up until this point, the first three conversations, then your proposal should be one page."
The proposal is short because the conversation did the heavy lifting. The proposal is long because the conversation did not.
The implication for writing is simple. If the discovery conversation produced a clear outcome statement, a budget shape the client has acknowledged, and a sense of the constraints (timeline, internal stakeholders, prior burns), the proposal almost transcribes itself. Without that, detail papers over the gaps.
If you cannot finish the sentence "this client is buying ______" in plain language, in one sentence, naming the outcome, the proposal will document the work but will not earn the decision. "A brand refresh" names a deliverable. "A quarterly bookkeeping engagement" names a deliverable. What sits behind them is the outcome the client is buying: a brand the founders feel ready to take into a Series A room, books closed cleanly enough that the CFO can sleep before the audit.
The pricing section is the page the client often opens first
Here is the working assumption of this guide: the pricing section is the page the client opens first.
That assumption is opinion, not benchmark. The behavior is shaped by how proposals actually get opened: a buyer wants to know the number before they decide how much attention to give the rest. Plan for that buyer. The other sections back up the pricing decision.
The pricing section should be visually clean. The price, what the price includes, and the payment structure should be readable in one scan. If the buyer has to read a paragraph to figure out what the number is, the writing has failed them at the moment they are paying the most attention.
The number on the page should be the number the client already heard. Chris Do's posture on this is direct: "say a price before you show a price so the client knows what to expect when you send the proposal." If the pricing page contains the first figure the client has ever seen from you, the proposal is doing work the conversation should have done.
Where appropriate, give the client more than one shape to react to. Baker and Enns describe the leverage of options: "we're changing the question that we're asking the client from: 'is this worth $10,000?' to 'which of these options is the best value?'" Three options reframe the client's job from yes-or-no on a single price into a comparison among shapes the studio is willing to deliver. Each option must be a real engagement, not a decoy to make the middle one look reasonable.
The pricing section is not where pricing decisions get made. The choice between fixed fee and hourly, the case for packaging, the structure of retainers belong upstream of the document. For that work, our post on how to price a creative project proposal goes deep on the decision itself. The pricing section inside the proposal is the presentation of a decision the conversation already made.
After hit-send
You write the proposal, you send it, and then the document goes quiet. The writer has no way to know which sections were read carefully, which were skipped, and which one made the buyer put it down to think. The post-send half of the workflow has its own tools and its own decisions; the deeper guide is our companion post on how to follow up on a proposal. The choice of platform sitting one step upstream (PDF email attachment versus branded client link) lives in our category post on online proposal software. Once the proposal is accepted, the next artifact is the client contract; the proposal is what earns the yes, and the client contract is what the signatures land on.