Where it sits on the path: Follow-up · Sale

Lead to sale

How do you write a B2B proposal that gets read and approved when you're not in the room?

A proposal that vanishes for weeks after a good meeting was usually written for the people in the room. Here's a structure for everyone else, and an eight-question test for page one.

The short answer

Write it as a decision document, not a company brochure. People who've never met you will read it without you. So page one gives the problem in the client's words, the option you recommend, the price and the next step with a date. Detail comes next, and "About us" goes last. Don't write it before a discovery call, and don't send it before you've agreed when to review it.

The bottom line

  • Write the proposal for the people who weren't in the meeting, because it will be forwarded inside the client's company and read without you.
  • Make page one state the problem in the client's words, the option you recommend, the price and the next step with a date.
  • Move "About us" and the client list to the appendix, and add a line that says what the proposal doesn't include.
  • Put the price next to the cost of the problem, and don't open your first proposal with a discount.
  • Agree on a time to review the proposal before you send it. Then, with your contact's agreement, send it to both the decision-maker and the person who'll use the service.

Want this applied to your business?

Message me on WhatsApp
In this article7 sections
  1. Why does a proposal stall after a good meeting?
  2. What should the first page say?
  3. How should you order the rest of the proposal?
  4. How do you price it so the proposal doesn't turn into a price comparison?
  5. Test page one before you send
  6. What do you do after sending?
  7. What should you do this week?

The first meeting goes well. The client asks for "a detailed proposal" by the end of the week. You send a 20-page PDF, and then three weeks pass with no reply. When you call, you get a polite answer: "We're reviewing it internally." The problem usually isn't the price. The proposal was written for the person in the meeting, and the decision sits with people who weren't there.

My view is that a proposal isn't a brochure about your company. It isn't a price list either. It's a decision document, and it gets read and forwarded inside the client's company while you're not in the room. So its first page has to work for someone who has never met you. From that page alone, they should understand the problem, the option you recommend, the price and the next step.

I write proposals as part of my work at CoderZ For Software and Training, where I've been Marketing & Business Development Manager since January 2021. What follows is the structure I use today.

Why does a proposal stall after a good meeting?

Because the person who agreed with you in the meeting doesn't decide alone. They forward your file to their manager and to finance. Sometimes it also goes to the people who'll use the service every day. Each of them opens it with a different question.

In March 2026, Gartner published a survey of 646 B2B buyers. The survey ran in August and September 2025. Of those buyers, 67% said they prefer a rep-free experience. And 45% said they had used AI during a recent purchase. The release talks about buying groups, and about buyers who vet suppliers with fewer early interactions. The survey also found that buyers confident in their decision were twice as likely to report a high-quality deal as buyers with low decision confidence.

What I take from these numbers is simple. Your proposal will be discussed without you, by people who haven't met you. A clear first page gives them the confidence to decide. A vague one leaves them unsure, and unsure people put things off.

The usual proposal lets this reader down. It opens with the logo, "About us" and a client list, and pushes the problem and the price to the back. So the finance director hunts for the number, then compares it with a rival proposal they also know only by its number.

The usual proposal The proposal I recommend
First page Cover, logo and welcome letter Problem, recommendation, price and next step
"About us" The opening pages An appendix at the end, or nothing
Options Lots of similar packages One recommendation and two alternatives at most
Price A line-item table at the back One total on page one, the breakdown later
Scope Only what you'll deliver What you'll deliver and what the price doesn't cover
Closing "We look forward to working with you" The decision you need and the date of the review call
Who it serves The people in the meeting The people who weren't there, too

What should the first page say?

It says what someone who missed the meeting needs in order to decide. I write it in four short paragraphs, no more:

  1. The problem in the client's words. Use the phrase they used, not a generic description of their industry. If they said "our leads get lost between marketing and sales," write exactly that.
  2. The option you recommend. A clear name, and one line on why it fits this company in particular.
  3. The total price. One number for the recommended option, with the duration and how payment works.
  4. The decision and the next step. What you're asking them for, who decides, and when the review call is.

If you need more than a page for those four, the problem is your grasp of the situation, not your wording. Go back to your notes from the discovery conversation. And if you never had that conversation, don't write a proposal yet.

A proposal comes after discovery, not instead of it. I worked with colleagues at CoderZ on its Discovery sales system, which is why I don't separate a proposal from the conversation before it. The questions to ask before you talk price are in the discovery questions guide.

How should you order the rest of the proposal?

In the order the reader asks their questions. This is the order I use:

  1. The problem in detail. What you heard in the meeting, and what it costs to leave things as they are. One or two paragraphs are enough.
  2. The recommended option, plus two alternatives at most. An alternative differs from the recommendation in scope, not in discount. Say plainly why you don't recommend it.
  3. Scope, and what's not included. A line that starts "This proposal does not include" prevents a lot of arguments after signing.
  4. The first 100 days. What happens after signing, and in what order.
  5. Price and terms. The breakdown goes here, once the reader knows what they're buying.
  6. The decision and the date of the next step. A short repeat of page one, with the name of the person who signs.

"About us", the client list and testimonials belong in the appendix, if anywhere. Anyone who needs them will find them. Anyone who doesn't won't have to wade through them to reach the price. If you want to frame the option around value the buyer understands, see the value proposition article.

The first 100 days: diagnose, build, launch

In the proposals I write, I split the first 100 days into three phases. I start with diagnosis, then build, then launch. The one rule I won't bend is that I don't set a numeric target until I've confirmed the baseline. The baseline is what actually happens today, in the numbers held in the client's own systems, not the numbers someone remembers.

The reason is practical. A proposal that promises a growth rate before seeing the data sounds bold in the meeting. It looks dubious when the finance director reads it. A line that says "targets are agreed with you at the end of diagnosis" gives them a reason to approve the first phase.

I also write down what will be measured. If the work is campaigns, my measure is a qualified booked call confirmed in the CRM, not the number of forms filled in.

Want this applied to your business?

Message me on WhatsApp

How do you price it so the proposal doesn't turn into a price comparison?

Put the price next to the cost of the problem, not on its own. A number standing alone gets compared with the cheapest proposal on the reader's desk. Next to what the client is losing today, it reads as a business decision.

Hypothetical example, rounded numbers:

  • In the meeting, the sales manager said his team loses about 10 deals a quarter because follow-up slips.
  • His average deal is SAR 20,000.
  • So the lost deals are worth about SAR 200,000 a quarter.
  • The recommended option in the seller's proposal costs SAR 45,000 for the first 100 days. This is an illustrative figure, not a price for my services.
  • The proposal states that the 10 lost deals are the sales manager's estimate, to be checked in the CRM during diagnosis.

Now the finance director reads the price next to the cost of the problem, not next to a competitor's proposal.

Put one total on page one, and save the line-item table for the price section. A long table invites the reader to strike out a line to bring the number down. Don't offer a discount in your first proposal, because it tells them your first price wasn't serious. If your options differ in price, let the difference be in what the client gets.

Test page one before you send

Before you send any proposal, give its first page to a colleague who wasn't in the meeting. Give them two minutes, then ask the eight questions below. Any question they can't answer from that page alone gets fixed before you send.

The question someone who's never met you must answer Where it sits on the page The line passes if
What problem are you solving for us? First paragraph It uses a phrase the client said, not a generic industry description
What happens if we do nothing? Right after the problem It names one concrete effect: money, time or a missed deadline
What exactly do you recommend? Heading of the second paragraph One option with a clear name, and a line on why that one
Are there alternatives? Under the recommendation Two at most, with the reason you don't recommend them
What does the price include, and what doesn't it? Two lines before the price It states what's outside the proposal
How much, and how do we pay? The price line One total, with the duration and payment method
When do we see the first concrete step? The first-phase line A specific week for the end of diagnosis
What decision do you need from us, and by when? Bottom of the page One decision, the name of who makes it, and the review call date

If two or more questions fail, don't send it today. Rewrite the first page instead of adding new ones.

What do you do after sending?

The most important step after sending happens before it. At the end of the meeting, agree on a time with the client for a call to review the proposal. Then you're not chasing a reply. You're showing up to a call you both agreed to.

With your contact's agreement, send the proposal to at least two people: the decision-maker, and the person who'll use the service every day. The first one signs. The second tells colleagues whether the proposal really solves their problem.

With the file, send a short message on WhatsApp or by email. Three lines are enough: the problem as you understood it, the option you recommend and its price, and the review date. Some people won't open the file before the call, but they'll read the message.

Then log the proposal in the CRM with the review date and the decision-maker's name. If the date passes with no reply, follow up with something new, not "Any update?" The full follow-up system is in the guide to lead follow-up on WhatsApp and the CRM.

What should you do this week?

Open the last proposal you sent that never got a decision. Run the first-page test on it, honestly. If it fails, don't send a whole new file. Write a new first page and send it with a request for a specific review time.

Then open your company's proposal template. Move "About us" to the end. Add a "This proposal does not include" line and a line that states the decision you need. That's a few hours' work, and every proposal after it benefits.

If the proposal is part of a sales pipeline where nobody clearly owns each deal, that's what I work on in sales pipeline and CRM design.

Questions

How long should a B2B proposal be?

There's no fixed number, but the first page should be enough on its own for a decision. My view is that most services and training proposals need only a few pages after it, and the rest can go in appendices. If it's long because you're explaining your company, cut it. If it's long because the scope really is complex, that's fine, as long as page one stays one page.

Should I put the price in the first proposal or send it later?

Put it in the first proposal, on page one. A proposal without a price delays the decision, and the price then turns up later in a separate message with no context. This assumes you had a discovery conversation before you wrote it. If you didn't, give an honest price range and ask for the meeting before the proposal.

Should I offer one option or three?

One you recommend, and two alternatives at most. A single option leaves the client with a yes or a no. Too many send them back to comparing. Make the options differ in scope, not in discount.

Does this structure work for government tenders?

A government tender follows its own tender documents and forms, so stick to them exactly. The same goes for any company that sends an RFP with a required template. If that template has an executive summary, make it your page one. This structure is for private-company proposals where you choose the format.

What if the client asks for a proposal before any meeting?

Ask for a short call first, and be honest about why. You want to recommend the right option, not send a list of services. If they say no, send one page with the options and their price ranges, and offer the call again. The full proposal gets written after discovery.

Sources

  1. Gartner Sales Survey Finds 67% of B2B Buyers Prefer a Rep-Free Experience · Gartner Newsroom
Portrait of Mohammad Marwan Al-Qudah

Mohammad Marwan Al-Qudah

Marketing & Business Development Manager

Marketing & Business Development Manager at CoderZ in Amman, working with companies and online stores in Jordan and Saudi Arabia since 2014. He starts with the market and the offer before any ad, and judges marketing by what reaches the bank, not by what the platform dashboard shows.

Want this applied to your business?

Tell me where things stand. I usually reply within two working days with what I need to start.