What should a B2B SaaS proposal include?

A B2B SaaS proposal should include six things: the buyer's problem in their words, the outcome you'll deliver and by when, the scope, the price and terms, the steps to signature, and who to call with questions. Keep it to a page or two, because the people who decide will read it without you in the room.

Why does the proposal carry so much weight?

Because the buying group spends most of its time without you.

Gartner research from a survey of 750 B2B buyers found that when buyers are considering a purchase, they spend only 17% of that time meeting with potential suppliers. When they're comparing several suppliers, the time with any one sales rep may be only 5% to 6%. The proposal speaks for you the rest of the time. Your champion forwards it to finance, procurement, and the skeptic you never met.

A proposal written for the call dies in the forward. A proposal written for the forward works on the call too.

What goes in each section?

1. The problem, quoted. One or two sentences in the buyer's own words, with the cost if they gave you one. It proves you listened.
2. The outcome and the date. What changes and when they'll see it. Tie it to the first win onboarding will deliver.
3. Scope. What's included, what isn't, and the assumptions: seats, usage, integrations, support level. Vague scope turns into a fight at renewal.
4. Price and terms. The number, billing frequency, term length, and what happens at renewal. If you offer an annual prepay discount, show it here.
5. Steps to signature. Security review, legal, procurement, signer, with a date on each. If you built a mutual action plan, paste in the remaining steps.
6. Who to call. Your name, and one line inviting questions from anyone who reads it.

What should I leave out of a proposal?

Anything the decision maker doesn't need to say yes.

• The company history page
• Every feature you ship
• Customer stories unrelated to this buyer's problem
• Long legal terms. Put those in the order form or MSA, linked.

If a section exists because "proposals always have one," cut it. Your sales one-pager carries the general story. The proposal is about this account.

When should I send it?

After the buyer has agreed to the problem, the outcome, and the rough price on a call. Never as the first time they see the number.

A proposal that surprises the buyer gets parked while they work out how to react. A proposal that confirms what you already agreed gets forwarded. If they ask for a proposal before you've talked price, treat it like any "send me more info" request. Get the call first.

How do I keep a proposal from stalling?

Put the next step and a date on the last line, and send it with a calendar invite to walk through it.

Proposals stall in inboxes. A 20-minute review call booked when you send it keeps the deal moving and lets you hear objections live. Ask early whether security or procurement will need anything, so a security questionnaire doesn't land the week you planned to close.

Should I use a proposal tool or a doc?

Either, as long as it's easy to forward and easy to read on a phone.

Proposal tools give you view tracking. Treat it as a hint. An open tells you someone looked. It doesn't tell you they agreed. A clean shared doc or PDF works fine for early SaaS. The content does the selling.

What should I do this week?

1. Pull your last three proposals. Count the pages. Mark every section the buyer didn't need.
2. Rewrite your template around the six sections.
3. Add dated steps to signature to every open proposal.
4. Book a review call with every proposal you send.
5. Ask your last two closed-won buyers who else read the proposal, and what those people asked.

Gartner found buyers spend only 17% of their buying time meeting with potential suppliers. Write the proposal for the time you're not there.

Start Signals, Convert, Grow

FAQ

How long should a B2B SaaS proposal be?

One to two pages for most early-stage deals. Put legal terms in a linked order form. Any longer and the decision maker skims past the parts that matter.

Should the proposal include pricing options?

One recommended option, with at most one alternative. Three options turn the proposal into a menu and slow the decision.

What's the difference between a proposal and an order form?

The proposal explains why the deal makes sense: problem, outcome, scope, price. The order form is the document they sign. Send the proposal first and the order form once they agree.

Should I send the proposal before or after the demo?

After the buyer agrees on the problem, the outcome, and the rough price. Sending it earlier puts the number in front of people before they know why it's worth it.