# What is SaaS sales? Three models, and where the trial ends and the deal begins

https://salesbond.app/blog/saas-sales/
Published: 2026-10-15 · Updated: 2026-10-15

What is SaaS sales? It is selling software on a subscription, and it runs on one of three motions: self-serve, transactional or enterprise. Which one you are in depends on the price and on who the buyer is.

For a small team the harder question is where the free trial ends and the deal begins. Our answer is the same line we use for any lead: create a deal when there is confirmed interest, a known pipeline and a dated next activity, and keep trial users out of the deal pipeline until then.

## What SaaS sales is, and what makes it different

SaaS stands for software as a service. Mailshake puts the sales side in one line: “SaaS sales is the process of selling internet-based software” ( [Mailshake: SaaS sales](https://mailshake.com/blog/saas-sales/)). The software lives online, the customer pays for access rather than for a copy, and the payment repeats.

That last part is the difference. Sell a physical product and the sale ends the deal; the money is in. Sell a subscription and the close is the beginning. The customer can leave next month, which is why SaaS companies watch churn as closely as new revenue. It is also why the trial sits in the middle of your pipeline, not before it.

One thing to keep apart. Search “saas sales” and a good share of the results are job listings. This article is about the work, not the career.

## Three models: self-serve, transactional, enterprise

Both guides that rank for this query split SaaS sales into the same three models, by price and by how much a human needs to be involved.

Self-serve: nobody sells. Mailshake is blunt about it: “The self-serve model does not involve any sales activity. Instead, marketing is fully responsible for bringing in revenue” ( [Mailshake](https://mailshake.com/blog/saas-sales/)). The buyer signs up, tries the product and pays without talking to anyone. Walnut files the same motion under product-led growth (PLG), “because the product itself is the primary driver of customer acquisition” ( [Walnut: SaaS sales guide](https://www.walnut.io/blog/sales-tips/saas-sales-guide/)).

Transactional: a higher price, a lower volume, and reps who step in during the trial. In Mailshake’s words, a company “will employ sales teams in addition to the content provided by the marketing team”, and the reps “help encourage the conversion throughout the process”. Walnut says the same from the other side: “Transactional sales models are used for SaaS with a higher price point and lower volume.”

Enterprise: sales-heavy, long, expensive. Mailshake says this model “demands a dedicated sales operation in order to work effectively”. Walnut calls it “the most expensive, highly involved, and time-consuming SaaS sales model”.

Most small teams we talk to are transactional whether they planned it or not. A rep calls the promising signups and the deal closes when someone agrees to a plan. That is where the trial-to-deal boundary gets messy, so the rest of this article is written for it.

## How the SaaS sales process runs

Strip the vocabulary away and a transactional SaaS sale moves through five steps. A lead arrives, usually as a signup or a demo request. Someone qualifies it: is this a company that could pay, and is there a person to talk to? Then comes the demo or the trial, often both,. The close is the first paid plan. After that the work continues as onboarding and, later, expansion to more seats or a bigger plan.

You may have seen “the 7 stages of sales”. There is no standard seven. Walnut, for example, counts “the 14 main events in the average SaaS sales cycle” ( [Walnut](https://www.walnut.io/blog/sales-tips/saas-sales-guide/)). We would rather have four or five stages that each mean something a rep did than seven that look like a textbook.

## Where the trial ends and the deal begins

There are three ways to handle a trial in a CRM, and we have seen all three go wrong for different reasons.

![Three ways to handle a SaaS trial in a CRM: kept in the product, a deal stage, or an automation creating deals; one rule says when a deal exists](https://salesbond.app/wp-content/uploads/2026/10/saas-sales-2.png)

### Option one: the trial lives in the product, not in the CRM

Trial users stay in the product’s own database or in your marketing tool. The CRM only sees a deal once a rep has had a real exchange with someone and booked the next step. The pipeline stays honest: every card in it is a conversation someone is actually having.

The weak spot is the gap. If nothing pulls the promising trials into the CRM, reps pick who to call from memory or a spreadsheet, and the best signups get missed. This option works when something reliable, a daily list or a simple trigger, puts the trial in front of a person before it expires. The mechanics of that list are in [how to handle free trial signups in Pipedrive](https://salesbond.app/blog/free-trial-signups-pipedrive/), and the problem is the same in any CRM.

### Option two: the trial is a stage of the deal

Every signup becomes a deal in a “Trial” stage, and the deal moves forward when the user upgrades.

The cost is that the funnel lies. If one trial in ten turns into a conversation, most of your pipeline is cards nobody will ever talk to. Reps stop reading the Trial stage because its noise. We think this option is only honest when the trial is already gated by a sales call, so the number of trials is close to the number of real conversations.

### Option three: the trial is an event that creates a deal

An automation creates a deal the moment someone signs up. It feels like option one with the gap closed. In fact it is option two with worse data: the deal exists before anyone has talked to the user, and the reports count it as pipeline anyway.

What works instead is to let the event create a task, a lead or a line on a list, and to create the deal by hand when the line is crossed.

So where is the line? It is the same one we use for every lead on this blog: confirmed interest (a reply, or a meeting held or booked), a known pipeline and a dated next activity, all three at once ( [leads vs deals: the three-line rule](https://salesbond.app/blog/pipedrive-leads-vs-deals/)). SaaS adds one practical detail. The conversation that confirms interest usually also tells you which plan the buyer is weighing, so write the plan and a rough amount on the deal when you create it. That is a refinement of the same threshold, not a second rule. A signup alone crosses none of the three lines.

## What the CRM should hold for each model

A self-serve product needs almost nothing in the CRM before payment. After the first payment you want a customer record with where they came from, when they signed up and which plan they are on. If a deal exists at all, it is created at the payment.

A transactional team keeps trial signups as leads or contacts with their source and trial dates, and creates the deal during the trial, once the line above is crossed. How to set up the trial fields themselves is covered in the [free trial signups](https://salesbond.app/blog/free-trial-signups-pipedrive/) article, so we won’t repeat it here. The one thing we would add: the decision date is not the close date. The close date is your expectation, the decision date is the buyer’s deadline. Keep both. Extensions move the decision date, and the reasons behind them tell you a lot about the deal; see [what to do with a trial extension request](https://salesbond.app/blog/trial-extension-request-pipedrive/).

An enterprise deal exists from the first qualified meeting, with a decision date and an expected value. If there is a trial, it is a step inside the deal rather than the thing that creates it.

## How SaaS metrics read differently

The metrics every SaaS guide lists are mostly post-sale. Mailshake names churn rate, customer acquisition cost, monthly recurring revenue and customer lifetime value ( [Mailshake](https://mailshake.com/blog/saas-sales/)), while Walnut adds revenue churn, annual recurring revenue, months to recover and lead velocity rate ( [Walnut](https://www.walnut.io/blog/sales-tips/saas-sales-guide/)). None of those tells a rep what to do on Tuesday. The pipeline metrics that do are cycle length and win rate, and both depend on where you drew the trial-to-deal line.

Cycle length is the time from when a deal is created to when it is won or lost. Mailshake says products “that cost under $5,000 may take about a month to reach a sale”, while “for products that exceed $100,000 per year, the sales cycle could last six months or longer” ( [Mailshake](https://mailshake.com/blog/saas-sales/)). If your deals start at signup, a fourteen-day trial sits inside every cycle and your average runs two weeks longer than a team that starts the clock at the first conversation. Neither number is wrong; they measure different things. More on that in [sales cycle length: what to measure and what to ignore](https://salesbond.app/blog/sales-cycle-length-pipedrive/).

Win rate, the share of closed deals that were won, is the same story in reverse. Count trials as deals and it reads like a conversion rate for a free product. Count only deals that crossed the line and it reads like a sales metric. Both are useful; they should not share a name.

If you want one number for a small team, we would pick velocity: how much expected value moves through the pipeline per week. The arithmetic is in [sales velocity for a small team](https://salesbond.app/blog/sales-velocity-pipedrive/).

## The graveyard with a forecast on top

Here is the pattern we see most. A founder sets up the CRM in the first month, when every signup is exciting, and every signup becomes a deal. Eighteen months later there are two reps, a few hundred open deals in a Trial stage nobody has opened since spring and a pipeline report the founder stopped trusting but never fixed.

The fix is not a new CRM. It is the rule applied backwards: close out every open deal that never had a real conversation and a booked next step, move those records to a lead list or back to the product, and start creating deals only when a rep has earned one. The first cleanup hurts, because the pipeline shrinks to a fraction of what it was. The smaller number is the true one, and keeping it that way is a weekly habit, not a project ( [pipeline hygiene for B2B teams](https://salesbond.app/blog/b2b-sales-pipeline-hygiene/)).

Handing trials to a chatbot doesn’t change this. A bot can decide who gets a call ( [chatbot lead qualification](https://salesbond.app/blog/pipedrive-chatbot-lead-qualification/)), but a qualified lead is still a lead.

One more, for founders. When the founder was the only seller, the trial-to-deal line lived in their head, and it worked. The moment a second person sells, the line has to be written down in the the CRM, or two people will build two different pipelines in the same tool. That handover is its own topic: [handing founder-led sales to the first rep](https://salesbond.app/blog/founder-led-sales-handoff-pipedrive/).

If you do one thing this week, open your Trial stage, sort by last activity and count the deals nobody has spoken to. That count is how far your pipeline is from the line.