Guide

How to sell B2B SaaS when you are the sales team

Selling B2B SaaS when you do it yourself means taking each prospect from a conversation to a decision without losing weeks along the way. Here is how to run the first demo, when to offer a trial or a pilot, how to talk about price, what goes in the proposal and how to close without discounting for no reason.

By the GTM Flow team · Updated · 19 min read

How to sell B2B SaaS, in short

To sell B2B SaaS on your own, ask before you show, shape the demo around what you heard, and always agree on a dated next step. Offer a trial only with support and a success criterion. Give the price with its reason, keep the proposal to one page, and ask early who signs and what could stall the purchase.

Who writes this. This guide is written by the GTM Flow team, which makes a CRM with prospecting built in. The scripts, timings and examples are our recommendation, not the result of a measurement, and made-up figures are labeled. The only outside figures come from Gong, which sells call analysis software. We give no close rates or trial conversion rates: we have not found any we could verify.

This guide starts once someone has agreed to talk to you. To get that far, see how to get B2B clients, which compares channels, and the plan to build a sales pipeline from scratch, week by week. If you want to know how to sell SaaS as a founder over the longer run, including when to hire, that is founder-led sales.

We mean sales with a conversation: software bought after talking to someone, with one or several people deciding. If your product is bought by credit card in five minutes, this will help you less.

What is B2B SaaS sales

B2B SaaS sales is selling subscription software to companies rather than to consumers. Three things set it apart: the buyer is often not the only user, the money keeps coming only if the product gets used, and the decision can pass through several people. So the sale does not really end when someone says yes.

  • Several people. The person with the problem, the person who pays and sometimes procurement, legal or IT can all be different people.
  • A renewal comes next. You are selling a subscription, so a customer who never sets it up is a customer you lose later.
  • The product can show itself. Unlike a service, it can be demonstrated on the prospect's own case, which is why the demo carries so much weight.

This definition is ours. How much selling each account takes depends on price and on whether a buyer can try the product alone, and we cover that split in how to get B2B clients.

The B2B SaaS sales process, from demo to signature

The B2B SaaS sales process comes down to five moments: first conversation, demo, trial if needed, proposal and close. Each one should end in a fact you can check and a date. If your price is low, combine several in one meeting. If it is high, expect more people and more steps along the way to signature.

MomentWhat it is forIt went well ifTypical mistake
First conversationLearn whether there is a problem, who decides and how they buyYou see a reason to show the product, or you agree there is nonePresenting your company for twenty minutes
DemoShow how their case gets solvedThey ask questions and accept a dated next stepTouring every screen
Trial or pilotRemove the remaining doubtIt gets used and meets an agreed criterionGranting access and waiting
ProposalPut in writing what they are buying and what it costsThey asked for it, understand it and can forward itSending it when nobody asked
CloseGo from yes to signature and paymentIt is signed and paid, with a start dateAssuming “go ahead” is already a sale
Our judgment. The CRM stages, with an entry rule and a time limit for each, are in B2B sales pipeline stages.
Annual priceConversationsTrialPaperwork
Under $1,000One short call, or none if it explains itselfOn their own, if the product is built for thatPublic price and online acceptance
$1,000 to $10,000One or two, with a demoGuided session with their dataOne-page proposal and written acceptance
Over $10,000Several, with more than one personPilot with a written criterion, ideally paidProposal, contract and often procurement, legal and IT
Rough brackets we chose, not measured. How many people take part in the purchase matters more than the exact figure.

The first demo: how to run it if you have never sold

In the first demo, ask questions before you open the product and show only what solves what they told you. Pete Kazanjy sets aside five to ten minutes for questions and expects fifteen to thirty for the demonstration. If the meeting ends with no date for a next step, it will most likely go cold.

MinuteWhat you doA line to start with
0-2Agree on what the meeting is for and how it will end“I'll ask a few questions, show you what makes sense, and at the end we'll see if there's a next step. If there isn't, I'll tell you”
2-10Ask about the problem, how they solve it today and who decides“How do you handle this now, and what's the hardest part?”
10-22Show two or three things on their case, in their words and, if you can, with their data“You told me {{the problem}}. Here's how that would look”
22-27Stop, listen to doubts and talk about price if it fits“What else do you need to see to know if this works for you?”
27-30Agree on the next step, with a date and with whom“Who else should see this? Can we look at it together on Thursday?”
Sample script for half an hour, ours and not measured. The braces mark what you fill in. If the meeting runs longer, extend the questions before the demo. The questions themselves are in how to qualify B2B leads.

Chapter 7 of Pete Kazanjy's Founding Sales describes the same shape: quick pleasantries, discovery, a presentation and a live demo, then proof points and pricing. “The best option is using actual data or materials from the prospect in your demo,” he writes. If you cannot, use demo data that supports the use cases you want to show.

What Gong saysHow far to trust it
In demos that closed, nobody pitched for more than 76 seconds without interruption; in lost demos it reached 106A correlation: cutting yourself short will not close deals alone, but the rule costs nothing to follow
The seller talks 65% of the time in won demos and 66% in lost ones; in discovery calls that led to wins, 46%Gong calls the 65 to 66 gap too small to act on: not talking at length matters more than your total share
Won demos last 47 minutes and lost ones 36Gong itself warns that correlation is not causation. Interested people may simply stay longer, so do not stretch yours because of this
Won demos spend 12.7% more time on next steps, about four minutesThe easiest one to copy, though it does not prove cause either
Analysis of 67,149 demos published by Gong on September 14, 2017 and modified on March 4, 2026, checked on November 5, 2026. Gong sells this kind of analysis.

After the demo, a recap. Kazanjy says you should always follow up with a summary email, ideally in the thread that set the appointment, because “human memory is a fickle thing.” A made-up example to adapt: “Hi Sarah. Two things I took away: {{the problem}} and that you need this before {{date}}. I've attached {{what I promised}}. We're meeting Thursday at 10:00 with Ben from finance to go over pricing.”

Free trial or paid pilot: what to offer and when

An unassisted free trial often fails in B2B sales for a simple reason: nobody uses it. Before you offer one, ask what doubt it has to settle. Another demo or a guided session with their data is often enough. A pilot only pays off in larger deals, with a deadline, a written success criterion and, ideally, a payment.

OptionWhen it makes senseWhat to ask in returnHow it goes wrong
Reference or another customer's caseThe doubt is whether it works at companies like theirsNothing, if you have one. If you do not, say soInventing or exaggerating it
One-hour guided sessionThey want to see it in their own handsThe people who would use it, and their dataOnly one person shows up, who does not decide
Self-run trialThe product explains itself and sets up without helpA date to review it togetherNobody logs in and they ask for more time
Paid pilotThe deal is large and the result can be measuredPrice, deadline, owner and success criterion in writingIt ends and nobody knows who decides what comes next
Contract with an exitThey have doubts, but there is budgetA signature now and a period to leaveYou cannot tell whether that revenue is safe yet
Our judgment, based on the two sources below. We give no conversion rates: the ones in circulation carry no source we could verify.

What Founding Sales says. “The biggest issue in trials is always non-usage.” If the product is not set up for unattended use, Kazanjy calls handing users the keys and assuming they will know how to use it “a terrible idea.” He proposes asking what proof they really need, and keeps pilots for the largest deals because of what they cost in time, with success defined from the start.

What Y Combinator says. The talk “The Sales Playbook for Founders,” from its Startup School, argues for a financial commitment because the customer takes the pilot “much, much more seriously,” and if they will not pay anything, you want to know early. It also describes a monthly or annual contract with a 30- or 60-day opt-out or money-back period: if the customer does nothing, it is already a contract, with no second sale. We read it in an auto-generated caption transcript that does not name the speaker.

The two sources do not fully agree: the book treats a pilot as an exception and the talk as a regular step. Our recommendation: start with the guided session, which costs you an hour and shows you how people really use the product, and save the pilot for when the deal size justifies the time. If you choose an exit with a refund, have your adviser review the contract first.

How to talk about price when selling software to companies

State the price with its reason, once, and stop talking. Before you give it, you should have heard what the problem costs them, so there is something to compare it with. If they ask early, give a real range. Gong finds that won demos reach price late and that lost demos spend more time on it.

  • Compare it with their problem, not your cost. The Y Combinator talk calls this a value equation: what percentage saving or revenue uplift makes your product a good return. Work it out with their figures, not yours.
  • Keep it short. What they pay, per what unit and for how long. Gong found that lost demos spend 8% more time on price.
  • Offer options only if they help the decision. Kazanjy suggests three options in the proposal, with the middle one as your target and the highest still a realistic reach. If there is only one sensible way to buy, go straight to the document to sign.
  • If they ask early, do not hide it. Gong puts price between minutes 38 and 46 in won demos, but that is an average from long meetings, not a rule. Dodging the question sounds worse, and you want to know early if you are far apart.

A worked example, with made-up figures. Two people lose five hours a week each on what your software solves. That is 10 hours a week for 46 weeks: 460 hours. At $30 an hour, that is $13,800 a year. If your price is $6,000 a year, you can say: “Based on what you told me, this costs you about $13,800 a year. This would cost $6,000. If those hours aren't right, tell me and we'll redo it.” The hours and the hourly cost have to come from the customer.

If the reaction is “that's really expensive.” Kazanjy says “an objection around price is actually a great place to be,” because they seem convinced and are now talking about the price. He suggests asking “Are we far apart here? How far would you say?” to tell a value problem from a discount request. Answers to this and other lines are in B2B sales objections.

In your first sales, price is also a test. Pete Koomen of Y Combinator advises treating each pricing conversation as an experiment and not undercharging out of fear, as we cover in founder-led sales. We read that talk on September 17, 2026. Write down the price you gave, the reaction and the outcome. With only a few sales no figure is conclusive, but you will see whether the complaint repeats.

The sales proposal: one page that can be forwarded

A B2B software proposal works best short, because it is often read by someone who was not in the meeting. It should cover the problem in the customer's words, what is included and what is not, the price, the rollout, the terms and the date to decide. Send it when they ask, not to fill a silence.

  1. Their problem, in two lines. In the words they used, so that someone who was not there understands it.
  2. What is included and what is not. What is left out prevents more arguments than what is included.
  3. Price. Amount, unit, period, payment method and taxes. No fine print you will have to explain later.
  4. Rollout. What happens in the first week, who does it and what you need from them.
  5. Terms. Length, renewal and how to leave.
  6. Validity and next step. How long it is valid, if that date is real, and when you will talk next.

Kazanjy separates two documents. The proposal is “more a piece of marketing collateral than anything else,” and the customer asks for it to consider pricing options. The order form “is simply there to memorialize the key terms” already agreed, with a link to the legal contract rather than the contract itself, and it gets signed electronically. At modest prices, one page can do both jobs if your adviser agrees.

Why one page. In the talk we read on September 17, 2026, Koomen recommended leaving a short document with the price and the benefits, because the decisive conversation usually happens without you in the room. When we rechecked it on November 5, the Y Combinator page returned only its title, so that earlier date is the one we give. That is the practical reason: your proposal has to stand on its own in front of whoever signs.

No customers yet? Do not use logos, percentages or results you cannot show. Say what you have built, who it is for and what you will do if something fails. A clear exit clause builds more trust than an invented case.

How to close a B2B sale without giving away the price

Closing a B2B sale means asking directly whether anything stands in the way of starting, then resolving what remains, in order. Find out early who signs and how the purchase runs. If you give a discount, ask for something in return. As Kazanjy puts it, you have to run all the way until the money is in the bank.

Ask. Kazanjy offers a line for the end of the presentation: “Is there anything that is preventing us from getting you started as a customer?” Resolve what they say and ask again. If there is nothing, move to the document. Once the price is agreed, get it signed as soon as you can.

Who can stall itWhat to askWhat to have ready
The decision-maker“Who has the final say, and when will they look at this?”The one-page proposal and half an hour with that person
Finance“How do you pay a new vendor, and what do you need from us?”Tax details and payment method
Procurement“Does this go through procurement? How long does that usually take?”Your discount limit. Kazanjy warns procurement will try for another one on top of what you agreed
Legal“Do you use your contract or ours? Who reviews it?”A short contract and a view on which clauses you will change
IT or security“Is there a questionnaire or requirements we need to meet?”Answers on where data lives, who has access and how it is recovered. If you have no certification, say so
Data protection“Who handles this at your company?”Your data processing agreement, if you process personal data on the customer's behalf
Our list for a sale with several people. In a small sale you may need only the first two rows.

Data protection. If you sell to customers subject to the EU's GDPR and your software stores personal data about their customers or employees, you will normally be a processor, and Article 28(3) requires that this be governed by a contract or other legal act. Have it ready before anyone asks. This is not legal advice: check your own case.

  • A discount in exchange for something. Kazanjy suggests better pricing if they buy more seats or extend the term, giving up one increment at a time and prioritizing more money up front. A discount with no reason teaches them the earlier price was not the real one.
  • Before you match a competitor, verify that competitor's pricing. If you match it, make it conditional on signing the day you deliver the price. Otherwise, Kazanjy warns, you are in “a reverse auction for your services.”
  • No fake deadlines. Founding Sales suggests saying a price is valid only this month, and starting with inflated pricing to leave room to negotiate. We do not recommend either if it is not true: an invented date shows, and you have to keep selling to that same person.
  • Real deadlines, yes. “If you want to start on February 1, I need the contract by the 20th” is a real reason, and it has to be true.

The close does not end at signature. Agree before signing on what happens in the first week. Why a sale with no rollout gets lost at renewal is told by the Optimizely case in founder-led sales. And if the deal does not happen, log the reason and when to come back: a well-logged loss is what lets you win it back later.

Mistakes when selling your own software

The most common mistakes when selling your own software come from knowing it too well: explaining how it is built, showing every feature, promising what does not exist yet and confusing a pleasant meeting with a sale. The trial with no follow-up, the proposal nobody asked for and the discount nobody demanded also cost you.

  • Selling the technology. The customer cares about what stops happening to them. How it is built is for when their technical team asks.
  • Promising features. If it does not exist, say so, and if you will build it, say when. A promise like that ends in a cancellation, and you are the one who handles it.
  • Changing the product for every meeting. Log what they ask for and see what repeats. One customer is not a roadmap.
  • Mistaking politeness for interest. “I loved it” is not a step. A date with someone else at their company is.
  • Not talking to the person who decides. If you only talk to the user, help them tell the story internally and ask for that meeting.
  • Leaving it open forever. If there is no next step, close it and note when to come back. How to do that without pushing too hard is in the sales follow-up process.

Selling B2B software with GTM Flow

GTM Flow keeps what surrounds the sale on one record: the call and its notes, tasks, email, LinkedIn, WhatsApp and the opportunity with its stage. We do not advertise proposals, contracts, e-signature or payments: you handle those with your own documents. It does not tell you what to answer either. It is in early access, in waitlist order.

  • What was said. If you record the call, and tell people you are, the notes capture key points, dated commitments, objections in the customer's words and unanswered questions, and create up to three tasks. See CRM with calling.
  • The next step. Each opportunity carries its next step and who owns it, with a warning when it is going cold. The call notes do not move the stage, as we explain in Close.
  • What was lost. The loss reason stays on the opportunity, so you know why deals are lost and who to call again.
  • The channels. LinkedIn on the same record, with manual steps and per-profile limits. WhatsApp only for people who gave their number and permission.

GTM Flow, the AI go-to-market platform, is in early access: it opens to teams in waitlist order, with no self-serve signup and planned prices on the pricing page. This guide works with any CRM or a spreadsheet: for your first demos, you do not need more.

Frequently asked questions

How do you sell B2B SaaS?

Start by talking to people who have the problem, and ask more than you show. Run the demo on what they told you, agree on a dated next step, offer a trial only with support, give the price with its reason, put it on one page, and ask early who signs. Each step should end in a fact you can check and a date.

What is B2B SaaS sales?

It is selling subscription software to companies rather than to consumers. The person using the product is often not the one who pays, several people may have a say, and the revenue only continues if the product gets used. That is why the sale includes rollout, and why a signature on its own does not finish the job.

How do you sell SaaS as a founder if you have never sold?

Talk to people who have the problem and ask more than you show. Run the demo on what they told you, agree on a dated next step and note what holds each one back. Selling can be learned, and knowing your product is already an advantage. You do not need to sound like a salesperson: you need good questions and the truth.

How do you sell B2B software to companies larger than yours?

Expect more people and more steps: the user, the decision-maker and often procurement, legal and IT. Ask early how the purchase runs, have your answers on data and security ready, and prepare a data processing agreement if you process personal data on the customer's behalf. If you have no similar customers, say so and offer a clear way out.

How do you run a software demo that works?

Ask first and show only what solves what they told you, with their data if you can. Pete Kazanjy sets aside five to ten minutes for questions. Gong finds, across 67,149 demos, that in those that closed nobody pitched for more than 76 seconds straight. It is a correlation, but cheap to copy. End with a dated next step.

Is a free trial or a paid pilot better?

It depends on the price and on whether the product explains itself. Without support, the problem with trials is that nobody uses them, as Founding Sales says. In sales with a conversation, we recommend a guided session with their data first. A pilot pays off in large deals, with a deadline and a written criterion; asking for payment, as Y Combinator argues, helps them take it seriously.

When should you bring up price in a B2B sale?

After you know what the problem costs them, unless they ask sooner: then give a real range. Gong puts price between minutes 38 and 46 in won demos, and says lost demos spend 8% more time on it. These are averages from a vendor, not rules. Say it briefly, with its reason, and listen.

Does GTM Flow prepare proposals or contracts?

We do not advertise that. GTM Flow keeps conversations, the notes from each recorded call, tasks and the opportunity with its stage on one record. You handle the proposal, contract, signature and payment with your own documents and tools. It is in early access, in waitlist order and with planned prices.

The CRM with prospecting built in

GTM Flow brings the CRM, cold email, LinkedIn, WhatsApp and calls into one system, with AI that tells you what to do next. Early access for founders and small sales teams. See how it works

No spam. One email when we open, and you can leave with one click.

Sources

  1. Founding Sales (Pete Kazanjy), chapter 7: pitching, demos and objections · checked on
  2. Founding Sales (Pete Kazanjy), chapter 8: negotiating, closing and pipeline · checked on
  3. Gong: analysis of 67,149 sales demos (September 14, 2017, modified March 4, 2026) · checked on
  4. Y Combinator: The Sales Playbook for Founders, Startup School (auto-generated caption transcript) · checked on
  5. Y Combinator Startup School: Enterprise Sales for Founders (Pete Koomen) · checked on
  6. EUR-Lex: Regulation (EU) 2016/679 (GDPR), official text · checked on
  7. GTM Flow: Pricing · checked on

Keep reading

  • Guide

    Founder-led sales

    How to run founder-led sales with a method: ideal customer profile, pipeline, what to log from day one, the metrics that matter and when to hire a rep.

    29 min15 sources
  • Guide

    How to get B2B clients

    How to get B2B clients and find B2B customers on a team of 1 to 5: channels compared by time cost, your first customers, and when an agency pays off.

    17 min12 sources
  • Guide

    Build a sales pipeline from scratch

    How to build a B2B sales pipeline from scratch in 90 days with a team of 1 to 5: ICP, list, multichannel sequence, weekly activity and what to measure.

    15 min7 sources
  • Guide

    B2B sales objections

    B2B sales objections with examples and responses: price, "not interested", "we have a vendor", "send me information" and when to walk away.

    19 min6 sources
  • Guide

    How to qualify B2B leads

    How to qualify B2B leads on a small team: what BANT and MEDDIC really ask for, which to use, and ten questions for a first call.

    15 min9 sources
  • Guide

    Sales follow-up process

    A sales follow-up process for small B2B teams: when to follow up, which channel, what to log, emails after no response and when to stop. No made-up stats.

    14 min11 sources
  • Guide

    How to prospect on LinkedIn

    How to prospect on LinkedIn by hand: profile, search, invitation, first message and follow-up, with message examples to adapt for B2B sales.

    15 min10 sources