You had a great conversation with a prospect. They nodded at the right moments, asked about pricing, and said to send something over. Now you’re staring at a blank document, and whatever you put in it decides whether that conversation turns into revenue.
A business proposal is that document. It’s the formal offer you hand a prospective client that says what problem you’ll solve, how you’ll solve it, what it costs, and why you’re the one to do it. It’s a sales argument with a signature line at the bottom, which is what separates it from a price list or a business plan.
Most owners write proposals badly because nobody teaches them how. They send a number in an email, or they send twenty pages of boilerplate nobody reads. This guide covers the whole job: which of the four proposal types you’re writing, what belongs in each section, how to price and scope the work, and what to do in the days after you hit send.
Key Takeaways
- The average RFP win rate reached 45% in 2025, up from 43% in 2024, but win rates fall sharply as deal size rises (Bidara).
- Where the work comes from matters more than the document. Relationship-based pursuits win 60-90% of the time; cold bids win about 15%.
- Speed is a real advantage. Sending a proposal within 24 hours of the conversation can lift your odds of winning by up to 25%.
- Proposals that get accepted are read fewer times, not more. Winners average 2.5 views before close; losers average 3.5 (Proposify).
- The four types are solicited, unsolicited, renewal, and partnership, and each one changes what you lead with.
Boost customer satisfaction with just a few clicks
Most-Loved Features:
- On-demand drivers
- Real-time GPS tracking
- Delivery confirmation photos
- Over 50% of customers report a smoother delivery experience
What Is a Business Proposal, Exactly?
A business proposal is a persuasive document you send to a specific prospect, proposing specific work at a specific price. Every good one does four things: it proves you understood the problem, it describes the solution in enough detail to be believable, it states the price and what’s included, and it makes the next step obvious.
The confusion usually comes from the neighboring documents. A quote is just a number. An estimate is a number with a margin of error. A business plan is about your company and is written for lenders and investors, not customers. A contract comes after the proposal is accepted. Here’s how they separate:
| Document | Who it’s for | What it argues | When it appears |
|---|---|---|---|
| Quote | A buyer who already decided | Nothing. It’s a price. | After the decision |
| Estimate | A buyer scoping a job | A likely range, subject to change | Early, informally |
| Business proposal | A prospect deciding between options | That you’re the right choice at this price | Mid-sale, before commitment |
| Business plan | Lenders, investors, partners | That your company is viable | When raising money |
| Contract | The client who said yes | Legal terms of the agreement | After acceptance |
The practical difference: a quote can be a text message. A proposal has to persuade, which means it needs structure.
Proposals also assume you already have something worth proposing. If you’re still figuring out what you sell, at what price, and to whom, the proposal isn’t your bottleneck. Our guide to building a service business covers that groundwork: the service model, the pricing structure, and the delivery capacity that a proposal is ultimately promising on your behalf.
The 4 Types of Business Proposals
Every proposal falls into one of four buckets, and the bucket determines what you lead with. Get this wrong and you’ll write a beautiful document that answers a question nobody asked.
| Type | Triggered by | Lead with | Biggest risk |
|---|---|---|---|
| Solicited (RFP/RFQ) | The client asked, often formally | Compliance with their stated requirements | Getting disqualified on a technicality |
| Unsolicited | You saw an opportunity they haven’t named | The problem, before the solution | They don’t agree a problem exists |
| Renewal | An existing contract is expiring | Results delivered so far | Sounding like you’re coasting |
| Partnership | Two businesses could do more together | Mutual benefit and the split | Vague ownership of the work |
Solicited proposals
The client asked for it, either in a casual “send me something” or a formal request for proposal with a deadline and a scoring rubric. Formal RFPs are the highest-stakes version. The average RFP win rate across industries reached 45% in 2025, up from 43% the year before, according to an analysis of proposal data from 2019 through 2026 (Bidara). That headline number hides a steep curve: on deals above $100,000, average win rates fall to somewhere between 12% and 18%.
With a formal RFP, follow their structure exactly. If they number their requirements, number your responses to match. Evaluators score against a checklist, and a proposal that makes them hunt for an answer loses points it didn’t need to lose.
Unsolicited proposals
You noticed a bakery running four separate delivery vans on overlapping routes, or a caterer losing weekend orders because nobody answers the phone after 5pm. Nobody asked you for a proposal. You’re writing one anyway.
These are harder, because you have to sell the problem before you sell the solution. Spend the first page establishing that the problem is real, expensive, and specific to them, with numbers from their operation if you can get them. If the reader doesn’t accept the problem, nothing after it matters. Keep unsolicited proposals short. You haven’t earned twenty pages of attention yet.
Renewal proposals
An existing client’s agreement is ending and you want the next term. The temptation is to send the same document with new dates. Don’t. Renewals are won on evidence: what you delivered, measured against what you promised. Lead with the scoreboard, then propose what changes next term and why.
Renewals sit in the highest-probability category there is. Relationship-based pursuits close at 60% to 90%, against roughly 15% for cold bids. A renewal you treat carelessly is the most expensive kind of loss, because it was nearly free to win.
Partnership proposals
Two businesses combining effort: a co-marketing push, a referral arrangement, a shared delivery route, a joint event. The document reads differently because there’s no clean buyer and seller. What kills partnership proposals is vagueness about who does what. Name the owner of every deliverable and state how the money and the credit split, in writing, before anyone gets excited.
What Goes Inside a Business Proposal
Formats vary, but the load-bearing sections don’t. Use these eight, in this order.
1. Title page. Client name, your company, the project name, the date. Boring and necessary. The date matters more than you’d think. It’s what people reference when three versions are circulating.
2. Executive summary. One page maximum, written last. It states the problem, your solution, the price, and the timeline. Assume this is the only page the decision-maker reads, because for larger organizations it often is. If your summary can’t stand alone, rewrite it.
3. The problem, in their words. Restate what they told you, using their vocabulary, with specifics. “Your Thursday wholesale drops are arriving after your accounts open” beats “you have logistics challenges.” This section is where you prove you listened, and it’s the single most common place proposals go generic.
4. Your proposed solution. What you’ll actually do, described concretely enough that a skeptical reader can picture it happening. Name the steps. Name the tools. Name the people if the people are the point.
5. Scope and deliverables. What’s included, and, equally important, what isn’t. Every dispute you’ll ever have with a client traces back to a scope line somebody skipped. Write the exclusions down.
6. Timeline. Dates or durations, with dependencies flagged. If you need something from them by a certain day for the schedule to hold, say so here, not in an email six weeks later.
7. Pricing. Covered in detail below.
8. Terms and next step. Payment schedule, validity window on the price, and one unmistakable action: sign here, or reply to book the kickoff call. A proposal that ends without a next step ends.
Everything else (case studies, team bios, credentials, references) is supporting material. It helps, and it belongs in an appendix or a short section near the end, not in front of the solution.
How to Price and Scope the Work
Pricing is where most proposals get quietly rejected, usually for reasons that have nothing to do with the number being too high.
Give options, not an ultimatum. Three tiers, a lean version, a recommended version and a full-scope version, change the client’s question from “yes or no” to “which one.” The middle tier should be the one you want to sell, and the one you describe in the most detail.
Price the outcome, not your hours. Hourly pricing invites the client to audit your efficiency and punishes you for getting faster. A flat price per outcome, or per month, or per delivery, moves the conversation to value. It also makes the proposal shorter.
Show the math on anything unusual. If there’s a setup fee, a minimum, or a surcharge, explain what it covers in one sentence right there in the table. Unexplained line items generate emails, and emails generate delay.
Put a date on the price. “Valid through October 15” is a normal commercial term and a mild, honest source of urgency.
Never bury the number. Hiding the price on page nineteen doesn’t make it feel smaller. It makes the reader skim nine pages hunting for it, which is exactly the reading pattern you don’t want. Proposals that end up accepted are viewed an average of 2.5 times before closing, while proposals that lose average 3.5 views (Proposify, from an analysis of more than 1.3 million proposals across 27 industries). Repeat visits usually signal confusion or internal debate, not enthusiasm.
Sending and Following Up
The document is maybe two-thirds of the job. The rest is timing and persistence.
Send it fast. Proposals delivered within 24 hours of the conversation that prompted them can improve win odds by as much as 25%. The reason is unglamorous: you’re competing with the prospect’s own attention, and the problem feels most urgent to them the day they described it out loud. Average industry response time now sits around 25 hours and is falling.
A useful consequence: build reusable pieces. Your company background, your terms, your standard scope language, and your case studies don’t change between deals. Keep them in a file so that writing a proposal means writing the problem, solution, and pricing sections only. That’s how a two-day job becomes a two-hour one. If you bid often enough to justify it, RFP and proposal software can automate the assembly step and keep your reusable answers in one searchable place.
Send it as a document, not a message. Attach a PDF or use a proposal link. A price typed into an email body reads as a quote, gets forwarded without context, and is trivially easy to compare against someone else’s number.
Follow up on a schedule, not a feeling. Day 3, day 7, day 14. Each touch should add something: an answer to a question they raised, a relevant example, or a note that the pricing window is closing. Three useful follow-ups beat ten “just checking in” messages, and most owners quit after one.
Ask for the loss. When you don’t win, ask why in a single, low-pressure question. Most people will tell you, and the answer is nearly always more useful than another hour spent polishing templates. Losses cluster: if three clients in a row cite timeline, your timeline section is the problem, not your price.
Five Mistakes That Sink Proposals
Boilerplate in the problem section. If you could paste another client’s name over the top and it would still read fine, it’s a brochure.
Leading with your company history. Nobody’s first question is how long you’ve been in business. Credentials support the argument, so put them after it.
Length as a substitute for substance. Long proposals are harder to approve and no more persuasive. Say what’s needed and stop.
No named next step. “Let me know your thoughts” is not a call to action. “Reply with an approval and we’ll start Monday the 14th” is.
Silence after sending. The most common reason a proposal dies is that nobody followed up on it. That’s a free loss, and it’s the easiest one to fix.
Frequently Asked Questions
How long should a business proposal be?
Long enough to answer the client’s questions and no longer. For most local service work, five to ten pages is plenty, and an unsolicited proposal should be shorter still. Formal RFP responses run longer because the requester dictates the structure. Length isn’t the variable that wins deals; specificity is.
What’s the difference between a business proposal and a business plan?
A business proposal sells your service to a prospective client. A business plan explains your company’s viability to lenders, investors, or partners. The proposal is a sales document; the plan is a financial and strategic one. They share almost no content.
Should I include pricing in the first proposal?
Yes. A proposal without a price is a brochure, and it forces an extra round of back-and-forth at exactly the moment the client’s attention is highest. If you genuinely can’t price the work yet, send a scoped estimate with a stated range and a date for the firm number.
How do I write a proposal when I don’t know the budget?
Ask before you write. If they won’t say, use tiered pricing: a lean option, a recommended one, and a full-scope one. The tier they gravitate toward tells you the budget without either side having to name it first.
What’s a good proposal win rate?
Context decides it. The cross-industry RFP average was 45% in 2025, top teams clear 60%, and large deals above $100,000 average 12% to 18%. Warm, relationship-driven work wins at 60% to 90% while cold bids sit near 15%, so a “low” win rate often means you’re bidding cold rather than writing badly.
Start With the Next One
You don’t need a better template. You need to write the problem section in your client’s own words, put the price where it can be found, and follow up three times instead of once.
Pick the proposal you owe someone this week. Open with what they told you their problem was. Describe what you’ll do about it in language a skeptic could picture. Name a price with two alternatives around it. End with a date and an action. Then send it before the conversation goes cold, and put the follow-ups in your calendar before you close the file.
