How to Write a Business Proposal That Actually Gets Signed

Knowing how to write a business proposal is not the same as knowing how to get one signed, and I learned that the hard way. In fact, the worst proposal I ever submitted was also one of the best looking. It had forty two pages, custom cover art, a slick pricing table, and an executive summary that read like a brochure. Even so, we lost it to a firm that sent eleven plain pages. Afterward, when I asked the buyer for a debrief, she told me something I have repeated to every writer I have trained since: “Yours told us who you are. Theirs told us what would happen to us.”

That sentence is the whole job. So if you want a proposal that actually gets signed, stop thinking of it as a document about your company. Instead, it is a document about the buyer’s future, with your company appearing as the most sensible way to get there.

I have spent years running bids for professional services firms, consultancies, and technology providers, on both formal RFPs and informal “can you send us something” requests. Therefore, what follows is not theory. Rather, it is the process my teams use, the habits that separate the proposals that close from the ones that disappear into a shared drive, and the mistakes I still catch in drafts every week.

Why Most Proposals Die Quietly

Proposals rarely lose loudly. After all, nobody calls to say your document was bad. Instead, you simply stop hearing back, or you get a polite note that “the committee went another direction.”

In my experience, quiet losses come from four places:

• The bid should never have been pursued. For example, the buyer already had a favorite, or the work was a poor fit.
• The writer did not know the buyer. As a result, the proposal answered the questions in the RFP but missed the worry behind them.
• The message was buried. Every section was competent, but nothing tied them into a reason to choose you.
• The document was hard to say yes to. For instance, it had confusing pricing, vague next steps, or terms that sent it straight to legal for three weeks.

Here is the encouraging part, however. Formal proposals already convert better than most sales channels. In fact, Loopio’s survey of more than 1,500 teams found the average RFP win rate across all industries is 45%, up from 43% in 2024. That means the difference between average and excellent is not luck. Instead, it is process, and process can be learned.

Before You Write a Business Proposal, Decide Whether to Bid

The most valuable thing a proposal manager does happens before anyone opens a template. Specifically, it is the bid or no bid decision.

Every proposal costs real hours. For example, Loopio’s benchmark research found the average time spent writing a single RFP response is 23.8 hours, and every RFP involves an average of 9 contributors to complete. So multiply that by your team’s hourly cost, and you will quickly see that chasing everything is the most expensive habit a growing firm can have.

Before I commit a team, I ask five questions, and I want honest answers, not hopeful ones:

• Did we know about this opportunity before the RFP landed? After all, if the first time we heard of the buyer was the day the request arrived, someone else probably helped shape it.
• Have we spoken to the actual decision maker, not just procurement?
• Can we deliver this work well, with people we actually have available?
• Do we have proof, meaning similar clients, comparable results, and references who will take a call?
• Finally, can we win at a price that still makes the work worth doing?

If we score poorly on three or more, I recommend passing, and I also put that recommendation in writing. Admittedly, passing feels painful in the moment. However, it feels much better six weeks later when the team has energy for a bid we can actually win.

Moreover, this discipline pays off in hard numbers. Bob Lohfeld’s research with the Association of Proposal Management Professionals is a good example: working with 45 proposal managers, his team found that government contractors with a 20 percent increase in their assessment score on average yielded a 20 percent increase in their win rate. Consequently, better qualification is one of the cheapest ways to move that score.

Learn the Buyer Before You Write a Business Proposal

Once we decide to bid, I do not let anyone start writing until we can answer one question in a single sentence: What does this buyer lose sleep over?

In our shop we call these hot buttons. Unfortunately, they are rarely written plainly in the RFP. For example, a request might ask for “a phased implementation approach,” but the real worry is that the last vendor went live late and the operations director took the blame. Similarly, a request might list twenty reporting requirements, but the real concern is that the CFO does not trust the current numbers.

You find hot buttons by talking to people. For instance, that includes sales calls, discovery meetings, clarification questions during the Q&A window, conversations with former employees, and even the buyer’s annual report and recent press releases. Then write them down in plain language and rank them. Finally, keep that list visible to everyone working on the bid.

The data backs this up, too. AutoRFP.ai’s 2026 survey of bid professionals found teams with customer research reported a 37% win rate, well above the low win cohort. In other words, research is not a nice extra. Instead, it is the raw material for everything you write next.

Build the Skeleton Before the Story

For a formal RFP, my first working document is not a draft. Instead, it is a compliance matrix: a simple table listing every instruction, requirement, and evaluation criterion in the request, with a column showing exactly where in our proposal we answer it.

This sounds boring because it is boring. Still, it is also the reason proposals stop getting thrown out on technicalities. After all, evaluators often score with a checklist in hand. So if they cannot find your answer to requirement 4.3.2 where they expect it, you lose points even if the answer exists somewhere on page 31.

A few rules I follow without exception:

• Mirror the buyer’s structure. If they number sections a certain way, then you number them the same way. In fact, Shipley’s training materials advise teams to develop the proposal outline exactly as the customer suggests, and that advice has saved me more than once.
• Allocate pages by evaluation weight. For example, if pricing is worth 20 percent of the score and the technical approach is worth 50 percent, your page budget should reflect that.
• Annotate the outline. Before writers start, each section heading carries a note: the requirement it answers, the hot button it addresses, and the proof point it should include.

For an informal or unsolicited proposal, there is no matrix. Nevertheless, the same logic applies. In short, build an outline around the buyer’s priorities, not around your company’s org chart.

Choose One or Two Win Themes, Not Seven

A win theme is the reason the buyer should choose you, stated in their terms and proven with evidence. In other words, it is not a slogan. For example, “We are passionate about excellence” is not a win theme. By contrast, “Our onboarding model has your team processing live orders in 30 days, half the time of your last rollout, because we embed two staff on site in week one” is a win theme.

New writers always want more of them. Typically, they list innovation, experience, quality, partnership, value, flexibility, and culture, and as a result the proposal says nothing memorable. The Shipley approach is blunt here: effective proposals usually have no more than one or two win themes focused on what customers care about.

A strong win theme has three parts:

• The buyer’s need or hot button. First, what they care about.
• Your discriminator. Next, what you do that competitors cannot easily claim.
• The proof. Finally, a number, a named client, a credential, or a guarantee.

Once you have your themes, they should appear everywhere: the executive summary, the opening line of key sections, the captions on graphics, and the closing page. Importantly, repetition across a long document is not redundancy. Evaluators read in pieces, often splitting sections among a committee, so the theme needs to reach each of them.

In fact, this is one of the clearest dividing lines in recent bid data. Teams with defined win themes reported a 37% average win rate, and win themes also correlated with a 56% shortlist rate versus 44% without.

How to Write a Business Proposal Executive Summary That Gets Read

Here is a hard truth: many decision makers will read your executive summary and almost nothing else. While the technical evaluators read the body, the person who signs often reads two pages, glances at the price, and then asks the team what they think.

That is why I never let anyone draft the executive summary first. After all, you cannot summarize an argument you have not built yet. Likewise, the Lindy team’s guide makes the same point, recommending you write this section last, even though it appears first, because after working through the full solution and pricing you will write a sharper summary.

A summary that gets proposals signed follows a simple order:

1. Their situation. First, open with the buyer’s challenge in their own language. So instead of “Acme Consulting is pleased to submit,” write “Your field teams are losing nearly a day each week to manual scheduling.”
2. The outcome they want. Next, describe what success looks like twelve months from now.
3. Your approach in brief. Then give three or four sentences, with no jargon.
4. Why you. After that, state your win themes, each with a proof point.
5. The investment and the next step. Finally, give a headline figure and exactly what happens after they say yes.

Above all, keep it short. Shipley training guidance suggests the executive summary run approximately 5 to 10 percent of total pages. On a twenty page proposal, for example, that is one to two pages. Therefore, if your summary runs four pages, it is not a summary.

One test I use is simple. First, hand the executive summary to someone outside the deal. Then ask them to tell you, in one sentence, why the buyer should pick you. If they cannot, rewrite it.

Describe the Solution Through the Buyer’s Eyes

The solution section is where most proposals slip back into talking about themselves. Too often, writers describe methodologies, frameworks, and proprietary tools at length, and consequently the buyer is left translating all of it into “so what does that mean for me?”

Instead, do the translation for them. For every feature or step you describe, attach the benefit. To help, I teach writers a simple sentence pattern: We will do X, so that you get Y, which matters because Z.

For example, compare these two lines:

Before: “Our team follows a four stage agile delivery methodology with biweekly sprint reviews.”

After: “Every two weeks you will see working results and decide what we build next, so your priorities shape the project instead of a plan written before anyone understood the details.”

It is the same process. However, it is a completely different reading experience.

In addition, a few more habits help:

• Use their vocabulary. For instance, if they call it “client onboarding,” do not call it “customer activation.”
• Show a timeline. Buyers want to know when things happen. As a result, a clear phased schedule with milestones does more than three pages of prose.
• Name the risks before they do. After all, every project has them. Identifying the two or three that worry the buyer most, along with your mitigation, therefore builds more trust than pretending the project will be smooth.
• Introduce the people. Buyers hire people, not logos. So name the project lead and include a short, relevant biography, not a generic résumé.

Prove Everything You Claim

Every claim in a proposal is either proven or ignored. In fact, evaluators have read “industry leading” and “proven track record” so many times that those phrases now trigger skepticism rather than confidence.

Instead, replace adjectives with evidence:

• Case studies that match. Ideally, same industry, similar size, and similar problem. After all, one closely matched case study beats five loosely related ones.
• Specific numbers. For example, “Reduced invoice processing time from nine days to two” is believable. By contrast, “Dramatically improved efficiency” is not.
• References who will pick up the phone. Also, confirm they are willing and briefed before you list them.
• Credentials that matter to this buyer. These include certifications, accreditations, and security standards, but only the ones relevant to the work.

When a client is too small or too new to have strong case studies, I tell them to use what they have honestly. For example, that could be the experience of their senior people at previous firms, a pilot offer with clear success criteria, or a guarantee. Ultimately, honest proof beats inflated proof every time, because inflated proof falls apart in the reference call.

How to Write Business Proposal Pricing the Signer Can Defend

Pricing is where good proposals go to die. However, that is not because the number is too high. Rather, it is because the buyer cannot understand it, cannot compare it, or cannot defend it to their boss.

The person who signs your proposal usually has to justify the decision to someone else. Therefore, your pricing section should give them that justification ready to use.

Here is what works for me:

• Tie price to value. First, restate the outcome before the figure. For example, a fee of 180,000 reads differently directly after a line explaining that the current process costs the buyer 400,000 a year in overtime.
• Offer structured options. Two or three tiers give the buyer a sense of control and also turn the question from “yes or no” into “which one.” In addition, make your recommended option clear.
• Spell out what is included and what is not. After all, scope ambiguity is the leading cause of disputes after signing, and evaluators notice when it is missing.
• Match the buyer’s format. If the RFP includes a pricing template, then use it exactly. In other words, do not improve it.
• State payment terms plainly. Specifically, include milestones, invoicing schedule, and the validity period of the quote.

If you are competing on a formal tender, also do your homework on price to win. For instance, know roughly what the incumbent charges and what the budget allows. Otherwise, a beautiful proposal priced 40 percent above budget is still a losing proposal.

Make Saying Yes Easy

This step is so simple that people skip it. Yet at the end of the proposal, the buyer should know exactly what to do next and how fast things will move once they do it.

Therefore, include:

• A clear call to action. For example: “Sign the attached agreement by November 14 to secure a January start date.”
• What happens in the first 30 days. This means the kickoff meeting, who attends, and what you need from them.
• A named contact. Specifically, one person, with a direct phone number and email.
• Signature ready terms. If your proposal doubles as the contract, make sure legal has reviewed it before it goes out, not after the buyer asks.

Speed matters here too. After all, buyers lose momentum. As a result, a proposal that arrives three days after the meeting while the conversation is still fresh will usually outperform a more polished one that arrives three weeks later.

Review Like an Evaluator, Not an Author

Writers are the worst reviewers of their own work. Because they know what they meant, they read what they meant rather than what is on the page.

For that reason, on every significant bid, my teams run at least two structured reviews:

• A storyboard review before full drafting. First, we check that the outline, win themes, and proof points are right before anyone spends days writing prose.
• A red team review on the full draft. Then reviewers who were not involved in writing read the proposal as an evaluator would, ideally scoring it against the actual evaluation criteria. Their job, in short, is to find weaknesses, not to polish sentences.

After that comes a final compliance and production check: every requirement answered, every page number correct, and every client name spelled right. For example, I have seen a proposal lose credibility because the buyer’s company name was misspelled on the cover. Similarly, I have seen one go out with a competitor’s name left in from a reused template. Both, however, were preventable with one careful read.

Moreover, structure around the review process matters as much as the review itself. AutoRFP.ai found that 100% of high win teams (51%+ win rate) have at least one dedicated bid manager, compared with just 44% of low win teams who run bids as a shared sales and marketing responsibility. In short, someone has to own the document and the deadline, or no one does.

Mistakes I Still Catch When Teams Write a Business Proposal

Even experienced teams fall into these. So keep this list near your desk:

• Opening with company history. After all, the buyer does not care when you were founded until they care about you.
• Recycling content without tailoring it. Content libraries save time. However, a reused answer that does not mention the buyer’s situation reads as exactly what it is.
• Letting subject matter experts write unedited. Experts know the work, but they do not always know how to persuade. Interestingly, only 6% of high win teams use the “SME writes, proposal team reviews” model. Instead, the better approach is to interview experts and have proposal writers shape the content.
• Burying the answer. First, put the direct response to each requirement in the first sentence of the section, then elaborate.
• Walls of text. Instead, use headings, short paragraphs, tables, and graphics with action captions that state the benefit.
• Vague pricing. If the buyer has to email you to understand the cost, then you have added friction at the worst possible moment.
• Missing the deadline by minutes. Many formal tenders reject late submissions automatically. Therefore, plan to submit a day early.

A Simple Structure to Write Any Business Proposal

When there is no RFP dictating format, this is the structure I hand to new writers. Of course, you can adapt it, but do not skip pieces:

1. Cover page with a title that names the outcome, not just “Business Proposal”
2. Executive summary of one to two pages
3. Understanding of the buyer’s situation and goals
4. Proposed solution and approach, with benefits attached to every element
5. Timeline and milestones
6. Team and relevant experience
7. Proof: case studies, results, and references
8. Pricing and options
9. Terms, next steps, and signature section

Short is fine, too. In fact, most informal business proposals I see succeed land somewhere between eight and fifteen pages. Ultimately, length should follow the complexity of the work, not your desire to look thorough.

Final Thoughts on How to Write a Business Proposal

Learning how to write a business proposal well is less about writing talent than about discipline. First, choose your bids carefully. Next, learn what the buyer actually fears and wants. Then pick one or two clear reasons to choose you and prove them relentlessly. After that, price in a way your signer can defend. Finally, review the whole thing through the eyes of a tired evaluator reading it at 9 pm on a Thursday.

Do that consistently, and you will notice something. Over time, the proposals start getting shorter, the debriefs get friendlier, and the signatures start arriving faster. At that point, you know you are writing about the buyer’s future instead of your own company, which, as that buyer told me years ago, is the only thing that ever gets signed.

FAQs About How to Write a Business Proposal

1. How long should a business proposal be?

It should be long enough to answer every requirement and short enough to read in one sitting. For informal proposals, eight to fifteen pages is common. For formal RFPs, however, follow the page limits exactly. In addition, PandaDoc’s proposal writing guide advises keeping most proposals under ten pages unless the product is complex.

2. What is the difference between a solicited and an unsolicited proposal?

A solicited proposal responds to a direct request, such as an RFP. By contrast, an unsolicited proposal is sent without a formal request, usually to introduce an idea to a prospect. Adobe’s overview of proposal types also breaks down formally solicited, informally solicited, and unsolicited formats.

3. What should go in the executive summary?

Include the buyer’s challenge, the outcome they want, your approach in brief, your win themes with proof, and finally the investment with a next step. For more depth, Shipley’s Winning Executive Summaries course focuses on organizing summaries around the customer’s most important issues.

4. What is a good proposal win rate?

Averages vary by industry and company size. However, Loopio’s RFP win rate benchmarks put the cross industry average at around 45%, with top performers winning more than half of their submissions.

5. Should I use a proposal template?

Templates help with structure and speed. Still, the content must be tailored to each buyer. For a starting point, Upwork’s breakdown of proposal components covers the core sections most templates share.

6. How do I decide whether to respond to an RFP?

Run a bid or no bid review. Specifically, assess your relationship with the buyer, your fit for the work, your available proof, and whether you can win at a viable price. For guidance, APMP NCA’s Go/No Go Decisions 101 is a solid starting point.

References

1. Loopio. RFP Statistics: Win Rates and Benchmarks. https://loopio.com/blog/rfp-statistics-win-rates/
2. Loopio. RFP Response Trends and Benchmarks 2025 Report. https://link.loopio.com/hubfs/loopio-trends-report-2025-digital.pdf
3. AutoRFP.ai. RFP Statistics: 47 Benchmarks on Win Rates, Teams and Process (2026). https://autorfp.ai/blog/rfp-statistics
4. Lohfeld, Bob. Here’s How to Raise Your Win Rate by 20 Percent. Washington Technology. https://www.washingtontechnology.com/2012/01/heres-how-to-raise-your-win-rate-by-20-percent/337570/
5. Maryland Department of Commerce, Technical Training Classroom. Proposal Writing 2: Developing a Proposal Outline. https://gomdsmallbiz.maryland.gov/Documents/Technical%20Training%20Classroom/2022/Attendee%20Copy%20Proposal%20Writing%202%20Developing%20An%20Outline%20June%2030%202022%20TTC.pdf
6. Shipley Associates. Proposal Manager Bundle. https://www.shipleywins.com/tools-and-guidebooks/proposal-manager-bundle
7. Shipley Associates. Winning Executive Summaries. https://www.shipleywins.com/courses/winning-executive-summaries-online
8. Lindy. Business Proposal Writing Guide. https://www.lindy.ai/blog/how-to-write-a-business-proposal
9. Adobe. Business Proposal Guide. https://www.adobe.com/acrobat/resources/how-to-write-a-business-proposal.html
10. PandaDoc. Proposal Writing Guide. https://www.pandadoc.com/blog/how-to-write-a-proposal/
11. Upwork. Business Proposal Components and Steps. https://www.upwork.com/resources/how-to-write-a-business-proposal
12. APMP NCA. Go/No Go Decisions 101. https://apmpnca.org/blog/go-no-go-decisions-101/