B2B sales proposal: how to structure one that closes

A B2B sales proposal that closes is a document the client helped write before receiving it, and one the salesperson presents live to the people who decide. A proposal emailed after the first meeting, with no conversation about its content, lands on the buyer’s desk as one more PDF among three, and the buyer compares the three on the only line they all share, the price. The structure that supports a decision has seven parts: the diagnosis in the client’s words, the objective with its success criterion, the scope with what stays out, the timeline, the investment as options, the expected return with the client’s numbers and the next steps with the deadline for the offer. If you lead sales or a book of accounts, the document template solves the smaller part of the problem, and the larger part is in how the proposal is run: building and presenting proposals is a skill the team learns by practicing on the quarter’s real proposals, with the manager reviewing each one before it goes out.

In the open proposals I review in sales teams, the CRM history usually tells the same story. The client asked for a proposal at the end of the first meeting, the salesperson sent the PDF two or three days later and moved the deal to the next stage, and what follows is a string of follow-up emails spaced further and further apart. The document opens with two pages about the vendor’s history and ends with a table holding a single price. Nobody on the client’s side commented on the content, and the salesperson has no idea who read it.

Why does an emailed sales proposal turn into a price comparison?

The buyer reads the PDF alone and forwards the file to people who were in none of the meetings. The director reads the summary and the last page, and procurement builds a spreadsheet with the vendors in columns and tries to line up scope, timeline and price. In Forrester’s The State Of Business Buying, 2026, procurement professionals are decision-makers in 53% of business buying cycles, and the same release describes this buyer looking beyond price, at what improves the efficiency and productivity of their company. That reading depends on a proposal with comparable scope and an explicit result. If three vendors describe the work in different words and none of them says what stays out, the price column becomes the only one procurement can line up.

The other loss happens before the proposal is sent. The salesperson who writes alone fills the gaps in the diagnosis with assumptions, the client finds the error while reading and starts to distrust the final number. In objections in B2B sales I cover the “it’s too expensive” that shows up after sending and how to answer it in the meeting. A proposal built and run with the client cuts down how often the salesperson needs that answer.

What is the structure of a sales proposal that closes?

I ask teams to use the same order in every proposal above a threshold value, following the reasoning of the person who approves: first the problem and the expected result, then the path and the cost, and finally the decision. The table sums up each section and the mistake I find most often in it, and the investment gets its own part further down, because it is the section that changes the conversation the most.

Section	What it contains	Common mistake
1. Diagnosis	Problem, cause and cost in the client’s words, with the department that provided each figure	Opening with the vendor’s history and leaving the problem for page four
2. Objective and success criterion	The result the client wants, the indicator they will use to say it worked and the date	A generic objective such as “optimize the sales process”, with no number or deadline
3. Scope	Deliverables, assumptions and the list of what stays out	A scope that only lists what is included and leaves the rest to be argued during the project
4. Timeline	Phases, milestones and what the client must deliver at each milestone	A timeline with the vendor’s tasks and none of the client’s
5. Investment	Two or three options, the recommended one flagged, and the payment terms	A single price on the last page
6. Expected return	Cost of the problem, gain in scenarios and payback period with numbers the client provided	Another client’s return or a market average in place of the buyer’s data
7. Next steps and validity	Decision date, who signs, start date and deadline for the offer	Closing with “we remain available for any questions”

Diagnosis in the client’s words

The first section repeats what the client said, using their expressions. If the operations manager said the team loses Monday morning consolidating spreadsheets, the proposal uses that sentence, naming the department that provided the figure. The source for this section is the summary the client has already corrected in writing after the discovery meeting. Before sending, swap the client’s logo for another company’s and reread the section: if the text still fits, the salesperson wrote a catalog diagnosis.

Objective and success criterion

The objective describes the result the client wants, and the success criterion says how they will measure it, with an indicator, a starting point, a target and a date. In a hypothetical example, “cut the time between order and invoice from twelve to five days by March” guides the whole project, and “improve sales efficiency” guides nothing. The criterion has to come from the client, because they will defend it in the committee and hold the vendor to it after signing. A proposal without this criterion shows that a discovery conversation was skipped.

Scope with what stays out

The list of what stays out of scope protects both sides, and procurement values it more than any other part. It keeps the client from finding out mid-project that the ERP integration was not included, and it allows a fair comparison between vendors, because it shows what the cheaper competitor may have left out. Next to the deliverables, write down the assumptions behind timeline and price, such as the person on the client side who owns the project, the weekly hours they dedicate and the date the data becomes available.

Timeline with both sides’ tasks

The timeline shows the phases, the milestones and, at each milestone, what the client must deliver or approve. Use dates relative to signing, such as “week 3 after signing”, while the decision is pending, and switch to calendar dates in the final version. The client’s tasks show the internal effort they will need to allocate, and the director who approves the budget wants to know that before signing. If payment follows milestones, each milestone needs an objective acceptance criterion.

Expected return with the client’s numbers

The sixth section carries the summary of the return: the annual cost of the problem, the gain in a conservative and a pessimistic scenario and the number of months until the investment pays for itself, with the source of each number. The full construction of this calculation with the buyer, and how to present it to finance, are in B2B negotiation with the client’s ROI. In the proposal, the return takes half a page and points to the supporting spreadsheet, which the client’s finance team can edit.

Next steps and deadline for the offer

The last section says what happens after reading: the date the client decides, who signs, what vendor registration has to be ready and the start date that depends on signing. The deadline for the offer needs a real reason, such as the delivery team’s schedule for that month or a price adjustment already set in the contract. A deadline invented to pressure the buyer undoes the trust the rest of the document built. In sales with many steps before signing, this section becomes the start of the mutual action plan, with each side’s dates.

Why offer options instead of a single price?

A single price turns the decision into yes or no, and the most common answer between the two is “send it again with a discount”. With options, the buyer chooses among paths that answer their problem, and the conversation moves from how much it costs to which path makes sense now. The internal champion also gets a way out if the committee cuts the budget, because they can take the smaller option for approval without reopening the negotiation.

Under the rule I teach, each option solves a defined part of the diagnosis and differs from the others in scope, pace or depth. The same deliverable at three different prices teaches the buyer that there is fat in your price list. The smallest option has to deliver something the client can measure, or they buy the cheapest one, see no result and do not renew. Three options are enough, with the recommended one flagged and tied to the success criterion.

Option (hypothetical example)	What it includes	When it makes sense	What the client gives up
Initial phase	The largest cost item in the diagnosis, with that item’s success indicator	Tight budget this year or a need to prove results before expanding	The other fronts, which move to a second phase with price and date defined
Recommended	Every front tied to the agreed success criterion	Client with an approved budget and a defined sponsor	Items the client called nice to have that do not affect the criterion
Extended	The recommended option plus a front the client asked for, such as an extra integration	Committee that wants to solve the issue in one go and has the team to absorb it	Nothing in scope, in exchange for a longer timeline and a larger investment

How do you run the proposal through to signature?

Running the proposal has three moments, and leadership can check each one in the CRM.

The draft meeting

Before the final version, the salesperson books thirty to forty minutes with the main contact and shares the document with the diagnosis, objective, scope and timeline filled in and the investment as a range. The questions are direct: what is wrong in the diagnosis, what is missing from the scope, who else needs to read it and what each of those people will ask. The client corrects it on the spot, and the final version reaches them as a document they already recognize. The contact often mentions in this conversation the format their director prefers.

The live presentation to the committee

The final version goes to a forty-five minute meeting with the people who decide, preferably with the economic buyer, the user department and someone from finance or procurement. The order follows the document: the salesperson opens with the diagnosis and asks the client to confirm it, goes through the success criterion and the scope, presents the options with the recommendation and ends with the next steps, agreeing on the decision date in the room. The PDF goes out by email after the meeting, along with a summary of what the committee asked to adjust. If the committee will not take the meeting, the salesperson prepares the champion to present instead, with a one-page version and the answers to the questions each role in the B2B buying committee tends to ask.

Follow-up after the presentation

The follow-up happens on the date agreed in the meeting, with a concrete question about the decision or about the adjustment the committee requested. The salesperson numbers each new version and logs it in the CRM, so nobody on the client side approves an outdated document. If the decision date passes without an answer, the salesperson asks what changed in the client’s priorities, and the manager decides in the pipeline meeting whether the deal stays in the quarter’s commit.

A roadmap for leadership to standardize the team’s proposals

Sales leadership turns the structure into routine with a few decisions, and most of them end up recorded in the CRM.

1. Set the threshold value above which every proposal follows the seven sections and goes through the draft meeting.
2. Create a single template with the seven sections and a library of scope, assumption and out-of-scope texts by service line, maintained by sales and presales.
3. Split the pipeline stages “draft validated by the client” and “proposal presented”, with exit criteria described by what the buyer did.
4. From the proposal stage onward, make mandatory the fields for success criterion, draft meeting date, presentation attendees, option chosen and offer validity.
5. Review one proposal a week in the pipeline meeting, with the manager playing the client’s director reading the document for the first time.
6. At the end of the quarter, compare the conversion of proposals that went through draft and presentation with those that only went out by email.

The fifth item builds the team the most. A manager who reads the proposal the way the client would finds the generic diagnosis and the unbounded scope before the buyer does, and the salesperson learns about their own deal. The fields from the fourth item feed these indicators.

Indicator	What it shows	Where leadership finds it
Proposals with a logged draft meeting	Team adherence to the method	Draft meeting date field
Proposal-to-win conversion, with and without a live presentation	Effect of how the proposal is run on closing	Pipeline stages and attendees field
Time between presentation and decision	Clarity of the agreed next steps	Stage dates and close date
Option chosen by the client	Whether the options are well designed	Option chosen field
Average discount on won proposals	Whether the buyer still negotiates price at the end	Proposed value and closed value

Sales proposals are also a marketing and post-sale matter

What does marketing deliver for proposals?

Marketing maintains the pieces the salesperson fits into proposals: client cases with the problem measured before and after, scope descriptions reviewed by segment and a short company page to attach at the end of the document, far from the opening. In return, it gets from the CRM the diagnosis in the client’s words and the options buyers choose. If the initial phase wins often in one segment, marketing learns something about budget and perceived risk in that market.

Why does post-sale read the proposal before the kickoff?

The signed proposal is the project’s first document, and Customer Success works from it. The success criterion in the second section becomes the indicator CS tracks until renewal, and the out-of-scope list prevents the argument in which the client asks for a deliverable nobody sold. If the salesperson promised something outside the document, CS finds out at the handoff, and leadership corrects it before implementation.

How do HR and L&D assess the need for proposal training?

The signals show up in the CRM and in the proposals themselves. Proposals stuck in “sent” for weeks, losses concentrated in “price” and “no response” and a high average discount on the largest contracts point to proposals sent without being run. When reading the documents, the signal is the generic diagnosis, the scope with no exclusions and the single price.

The group brings together salespeople, KAMs for the largest accounts and presales, who write much of the scope, with the sales managers who will review proposals afterward. In the negotiation trainings I run, each participant brings an open proposal, rewrites it in the seven sections during the program, rehearses the draft meeting and presents to colleagues playing the client’s committee, with someone from the company’s own finance team asking a CFO’s questions. Running a proposal changes when a person rehearses the conversation with someone pushing back on the other side, the logic I detail in sales training that changes behavior. To measure, HR and leadership pull from the CRM the previous quarter’s baseline with the indicators from the roadmap and compare it with the following quarter, together with a sample of proposals scored on the same rubric before and after.

If your leadership wants the team to stop sending PDFs and start building the proposal with the client, that is the work of the in-company training on complex negotiation. The program starts from the open proposals and recent losses in your CRM, uses the quarter’s deals to practice the draft, the options and the committee presentation, and ends with two deliverables ready for the following week, the team’s objection matrix and the closing guide with the operation’s proposal template.

Frequently asked questions

How do you write a B2B sales proposal?

Start from the diagnosis validated with the client and organize the document in seven sections: diagnosis, objective and success criterion, scope with what stays out, timeline, investment as options, expected return and next steps with a deadline. Review the draft with the client before the final version and present it live to the people who decide.

How many investment options should a proposal include?

Two or three. Each option solves a defined part of the diagnosis and differs from the others in scope, pace or depth, and the recommended one is flagged with the reason. Options that only change the price of the same deliverable teach the buyer to ask for a discount.

Is it worth sending a sales proposal without a meeting?

In transactional sales, with a low ticket and a single decision-maker, sending it by email usually works. In complex sales, a proposal with no draft and no presentation reaches a committee that was not part of the conversation, and procurement compares it with the others on the price line.

How long should a sales proposal be valid?

The validity needs a reason the client understands, such as the delivery team’s schedule or a planned price adjustment. Agree on the decision date during the presentation and use the validity to protect that date, without turning it into artificial pressure.

How do you train the team to build and present proposals?

Use the quarter’s real proposals. Each participant rewrites an open proposal in the company’s structure, rehearses the draft meeting and presents to colleagues playing the committee, and afterward the manager reviews one proposal a week in the pipeline meeting.

How do you measure whether the team’s proposals improved?

Compare, quarter over quarter, proposal-to-win conversion, the time between presentation and decision and the average discount, separating proposals that went through draft and presentation from those that only went out by email. Add a sample of documents scored on the same rubric before and after.