Open with a short executive summary that names the client's problem in their own words. Follow it with your approach, a timeline, pricing broken into two or three options, and one piece of proof (a result or a testimonial). Close with a single next step and a deadline. Send the whole thing within 24 to 48 hours of the conversation that triggered it, while the client still remembers what they asked for.
Use this structure when (and skip it when)
This structure works for:
Client-facing service or project proposals (agencies, consultants, freelancers, B2B vendors)
Both solicited proposals (someone asked you for one) and unsolicited ones (you're reaching out cold)
Deals in the low thousands up to six figures, where a client is comparing you against at least one other option
It's the wrong structure for:
Formal government or enterprise RFPs with a fixed response template. Follow their format exactly instead; compliance beats creativity there.
Internal business proposals pitching your own company on a new initiative. That's closer to a business case than a client proposal.
Investor pitches. Those need a business plan, not a proposal.
The one thing that changes your odds before you write a word
I sent a proposal two years ago to a mid-sized logistics company. Good research, clean formatting, competitive price. Silence for three weeks, then a one-line rejection. No specifics.
After that one, I did something different: a 20-minute call before writing anything, just to ask what was actually going wrong on their end. That proposal closed in four days.
The difference wasn't the writing. It was the input. Agencies that require a discovery conversation before sending a proposal see win rates roughly 38% higher than agencies that skip straight to drafting, according to Pitchsite's 2026 win rate benchmarks. A proposal built on guesses about the client's problem reads like a template with their name swapped in, even when it isn't one.
So before you open a blank document: get on a call or send three specific questions by email. What's not working right now? What have they already tried? Who signs off on this? Everything after that is easier.
Read Also: How to Save an Email As a PDF (and what actually happens to attachments)
Step-by-step: writing the proposal
Confirm what kind of proposal this is. A response to a direct request reads differently from a cold pitch. See the comparison table below.
Write the problem statement first, not the summary. Describe what's currently happening to the client's business, in their language, not yours. This becomes the opening of your executive summary once it's written.
Write the executive summary last. One to two paragraphs: the problem, your proposed fix, and the outcome. This is the only section some readers get to, so it has to stand alone.
Lay out your approach. What you'll actually do, in plain steps. Avoid vague phrases like "full-service support." Name the deliverables.
Add a timeline. Even a rough one. Three phases with dates beats a vague "we'll move quickly."
Break pricing into two or three options. A single price invites a yes-or-no decision. Two or three tiers invite a which-one decision, and clients compare options more readily than they accept a flat number.
Add one piece of proof. A past result with a number, or a short testimonial. Skip a client list; it's the weakest form of proof in a proposal.
Close with one clear next step and a date. "Reply by Friday to lock in the March start date" works. "Let me know if you have questions" doesn't.
Send it within 24 to 48 hours of the conversation that prompted it. After that, the client's urgency starts to fade.
How to know it worked: a real signal isn't silence followed by a signature. It's the client replying with a specific question, about scope, a date, or a line item in the pricing. That means they read past the summary and are already picturing the work. Silence for more than a week is a signal too, just the other kind, and it's worth a short follow-up rather than a second full proposal.
What the client actually does with it
Most proposals aren't read start to finish in one sitting. A decision-maker skims the executive summary and pricing first, then forwards the document to whoever else needs to sign off, often with no context attached beyond "thoughts?" That's why the executive summary and pricing section both need to make sense completely on their own, without the rest of the document as backup.
If there's a competing proposal on the table, most clients compare on three things in this order: whether the proposal addresses their specific problem (not a generic version of it), price, and how clearly the timeline is laid out. Formatting and design come after all three.
Common mistakes that get proposals rejected
Reusing last month's proposal with the company name changed.
Clients can tell. Even one paragraph that clearly wasn't written for them undermines the rest. Fix: rewrite the problem statement fresh every time, even if the rest of the structure is reused.
No clear call to action
A proposal that ends on "hope to hear from you" leaves the next move to the client, and busy people default to doing nothing. This is one of the most common reasons proposals stall, according to a Quora thread on why companies reject business proposals, where the top answer names a missing call to action before it names price. Fix: name the next step and a date in the closing line.
Burying pricing on the last page
Some writers hide price behind pages of methodology, hoping the value lands first. It usually reads as evasive instead. Fix: put pricing where a skimming reader will find it, and let the value section support it rather than precede it.
Writing for every stakeholder in one document
Trying to satisfy the technical reviewer, the budget holder, and the end user in the same paragraphs makes the whole thing vague. Fix: structure the document so each audience can find their section quickly (methodology for the technical reviewer, pricing and ROI for the budget holder).
Read Also: 12 best Lusha Alternatives in 2026 (now that phone credits cost double)
Solicited vs. unsolicited vs. informally solicited proposals
Type | Works when | What you need to prepare | What the client expects |
|---|---|---|---|
Solicited (RFP) | Client issued a formal request, usually to several vendors | Every requirement in their RFP addressed, in their order | Strict compliance with their format |
Unsolicited | You're reaching out to a prospect with no prior request | Independent research into their business and pain points | A short, tailored pitch, not a full document dump |
Informally solicited | A conversation led to "send me something" with no formal brief | Notes from that conversation, confirmed back to them before writing | A document that reflects exactly what was discussed |
FAQ: How to Write a Business Proposal
Do I need a business proposal template, or should I write from scratch?
A template is fine as a starting skeleton. The risk is stopping there. A template supplies section order, not the client-specific problem statement, pricing logic, or proof that make a proposal persuasive.
What's the difference between a business proposal and a business plan?
A proposal is written for one external client to win a specific piece of work. A business plan is an internal roadmap for the business overall, covering long-term strategy and goals rather than a single deal.
How long should a business proposal be?
Long enough to cover the problem, approach, timeline, pricing, and proof, and no longer. Most land between two and eight pages depending on deal size. A 20-page proposal for a $3,000 project signals disorganization more than thoroughness.
Is a business proposal for a small business different from one for an enterprise client?
The sections stay the same. What changes is depth: a small-business proposal can move faster and lighter on formal compliance language, while an enterprise buyer often expects a security or terms section even outside a formal RFP.
Should I send a business proposal as a PDF or an editable document?
PDF for anything with a signature or fixed pricing, since it won't shift in transit. An editable format only makes sense if the client explicitly asked to redline it before signing.
Before you hit send
Proposal-writing consultant Tom Sant makes the asymmetry clear in Persuasive Business Proposals: a great proposal rarely wins a deal by itself, but he writes that "a bad proposal can definitely lose one". The research and the conversation before you write matter more than the polish after. Standardized structure helps too: teams that use a consistent proposal template report win rates around 56%, against a 43% average for teams that rebuild the format each time, per Proposify data cited by CalcStack.