# The enterprise SaaS sales process

> A stage by stage enterprise process with exit criteria, buying committee mapping, security and procurement steps, and the six places six figure deals stall.

Source: https://saas-marketing.net/guides/enterprise-saas-sales-process/
Topic: SaaS Sales
Type: guide
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/enterprise-saas-sales-process/

## Short answer

The enterprise SaaS sales process runs seven stages: qualification, multi persona discovery, technical validation, business case, security review, procurement and legal, then signature. Above 100,000 dollars in annual contract value it typically takes 90 to 270 days and involves a buying committee of six to eleven people. Security review and procurement alone routinely add 30 to 60 days that most forecasts never account for. Each stage needs a written exit criterion tied to buyer evidence, not to seller activity.

## Key takeaways

- Gartner puts the typical B2B buying group at six to ten people, and enterprise SaaS deals sit at the top of that range or above.
- Stage exit criteria must be buyer evidence, such as a returned security questionnaire, never seller activity like a demo delivered.
- Security review and procurement add 30 to 60 days to a six figure deal and almost nobody forecasts for them.
- A single threaded deal above 100,000 dollars ACV is forecast fiction, because one departure resets the whole cycle.
- Champions sell internally without you in the room, so the most influential asset is a business case they can forward.
- Pilots without written success criteria and a pre agreed conversion path are how enterprise deals die slowly.

---

A six figure deal is not a bigger version of a mid market deal. It's a different mechanism. The buyer is not one person making a decision, it's a committee assembling a defensible case for a decision that already has internal politics attached.

Which means the seller's job changes too. You are not persuading a person in a meeting. You are arming someone to win an argument you will never attend.

## The seven stages and what actually exits them

Most CRM stages describe what the seller did. That's why forecasts are wrong. Rewrite every stage exit as something the buyer did, in writing, that a sales manager can verify by looking rather than by asking.

| Stage | Exit criterion (buyer evidence) | Typical duration |
| --- | --- | --- |
| 1. Qualification | Named initiative with a date and an owner, confirmed on a call | 1 to 2 weeks |
| 2. Multi persona discovery | Three or more personas met, pain quantified in their numbers | 3 to 5 weeks |
| 3. Technical validation | Pilot success criteria signed by buyer and seller | 4 to 8 weeks |
| 4. Business case | CFO or economic buyer has seen the numbers and responded | 2 to 4 weeks |
| 5. Security review | Questionnaire returned, findings closed or accepted in writing | 3 to 8 weeks |
| 6. Procurement and legal | Vendor record created, redlines exchanged, ticket number issued | 3 to 6 weeks |
| 7. Signature | Signed order form | 1 to 2 weeks |

Those durations overlap in a well run deal. Run security in parallel with the business case rather than sequentially and you take four to six weeks out of the cycle, which is the single largest legitimate acceleration available. Most teams don't, because nobody asked the champion to open the security ticket early.

Pull your last ten closed lost deals above 75,000 dollars. For each, write down which stage it was in when it died, and what the actual blocker was. If more than three died in a stage your CRM says is late stage, your exit criteria are describing seller optimism rather than buyer progress. The [sales cycle impact calculator](/calculators/sales-cycle/) will show you what fixing that is worth in pipeline terms.

## The buying committee and what each member needs in writing

Gartner's research puts the typical B2B buying group at six to ten people. Enterprise software sits at the top of that, and often above it. Here is who they are and what document each one needs, because "we'll cover that on a call" does not survive an internal review you are not in.

The pattern worth noticing: three of these seven can kill the deal and only one of them is ever on your calls. Security evaluators in particular tend to be invisible until they return a questionnaire with findings, at which point you are negotiating with someone who has never met you.

The fix is unglamorous. Ask in discovery who runs security review and what their process is, then offer the SOC 2 report and a pre completed questionnaire before anyone requests them. Vanta, Drata and their peers exist largely because that step became a sales bottleneck for the whole category.

## Discovery across three personas, not one

One discovery call with one person produces a story you like and a deal you lose. The minimum at enterprise is three conversations with three different functions, and the goal of each is different.

With the champion, you are looking for the initiative: what got funded, why now, and what they personally promised. With the technical evaluator, you are looking for the constraint: what in their stack makes this hard, and what a failed implementation would look like. With the economic buyer, you are looking for the comparison: what else this money could buy, because that is the real competitor in most enterprise deals, not the vendor you think you're up against.

Write down the buyer's own numbers, in their units. Not "improves efficiency" but "their support team handles 14,000 tickets a month at an average 11 minute handle time". That sentence is what the business case is built from, and if you cannot produce it after discovery, discovery isn't finished. [MEDDPICC](/glossary/meddpicc/) is the qualification frame most enterprise teams use to check whether those gaps are closed, and the gaps it exposes are exactly the ones that surface in month four.

## Pilots that convert, and pilots that eat a quarter

A pilot without written success criteria is a free trial with a bigger invoice for your solutions team.

**Designing a pilot that closes**

**6 to 10** People in a typical B2B buying group, per Gartner, with enterprise software deals routinely at or above the top of that range

## The six places six figure deals actually die

Every stalled deal is stuck for one of a small number of reasons, and each has a specific unblocking asset. Discounting is on this list exactly zero times.

| Where it stalls | What it looks like | What unblocks it |
| --- | --- | --- |
| No funded initiative | Enthusiastic calls, no date, "we're building the business case" | Qualify out, or find the funded project this can attach to |
| Single threaded | Champion is responsive, nobody else has ever appeared | Ask the champion to introduce the technical evaluator using a specific reason, such as an architecture review |
| Business case not written | Champion says "leadership is reviewing it", nothing moves | A filled in one page CFO model they can forward without editing |
| Security review | Silence for three weeks after a questionnaire | Proactive SOC 2 Type II, completed SIG Lite, and a named security contact on your side |
| Procurement queue | Contract agreed, nothing happening | Ask for the ticket number and the queue position, then supply the vendor forms before they are requested |
| Legal redlines | Two rounds turn into six | Publish your standard positions in advance and name which clauses you will never move on |

The single threaded row deserves emphasis. Roughly one in five contacts at a large company changes role within a year. A deal held together by one relationship is not a forecast, it's a bet on someone's career staying still for five months. The [sales process teardowns](/examples/saas-sales-process-teardowns/) show what multithreaded deals look like in practice, including the emails that actually get an introduction.

Rigorous stage gating slows the top of your pipeline down, and in the first two quarters after you introduce it your reported pipeline will fall, sometimes by 30 or 40 percent. That is the model correcting, not the business breaking, but you have to tell the board before it happens rather than after. Teams that introduce exit criteria mid quarter, without warning finance, tend to abandon them by the following quarter under pressure to show coverage.

## What marketing owes this process

Enterprise sales is where the marketing to sales relationship either works or is exposed. Three things matter and none of them are lead volume.

The first is committee assets. Every buying committee role in that table above needs a document, and sales should not be writing them one deal at a time. A security overview page, a CFO business case template with the model logic, an integration and architecture page for technical evaluators, a procurement pack with standard terms. This is the content gap in almost every B2B content programme, which produces practitioner content exclusively and then wonders why deals stall at CFO review. The [enterprise SaaS marketing playbook](/playbooks/enterprise-saas-marketing/) covers building that set.

This second is handoff discipline. An enterprise lead handed over with no account context is worse than no lead, because it burns a first touch on a company you may only get one shot at. Write down what constitutes a valid handoff in a [sales and marketing SLA](/templates/sales-marketing-sla-template/) and enforce it in both directions, then run the [marketing to sales handoff](/playbooks/marketing-to-sales-handoff/) process properly rather than relying on a lifecycle stage field.

The third is honest cycle reporting. If your average [sales cycle length](/glossary/sales-cycle-length/) is 160 days, marketing's Q1 spend shows up in Q3 revenue, and any attribution conversation that ignores that lag will produce the wrong budget decision. Say it out loud in the planning meeting.

## Where to start

Take your current pipeline above 100,000 dollars and count the engaged contacts per deal. Anything with fewer than three is at risk regardless of what the close date says. That one count usually explains most of a bad quarter before it happens.

Then rewrite your stage exits as buyer evidence, put the six stall remedies into your [sales playbook](/templates/saas-sales-playbook-template/), and get the security pack built before the next deal needs it. The wider [SaaS sales strategy](/saas-sales/) hub covers the motions that feed this process, but none of them help if the process itself is measuring the wrong thing.

## Frequently asked questions

### How long is an enterprise SaaS sales cycle?

Above 100,000 dollars in annual contract value, plan for 90 to 270 days from first qualified conversation to signature, with a median around five months. Deals touching regulated data, or requiring a security architecture review, sit at the longer end. Cycles shorten materially when the buyer has a funded, dated initiative rather than an exploratory interest.

### How many people are involved in an enterprise SaaS purchase?

Gartner's research puts the typical B2B buying group at six to ten people, and enterprise software deals commonly run to eleven or more once security, procurement, legal, IT and end user representatives are counted. Each of them can slow the deal, and only two or three of them can actively advance it.

### What is multithreading and why does it matter?

Multithreading means holding active relationships with several members of the buying committee, not just your champion. It matters because roughly one in five enterprise contacts changes role within a year. If your only relationship leaves, a single threaded deal restarts from zero. Three or more engaged contacts is the working minimum at six figures.

### What should exit criteria look like for each stage?

Exit criteria should describe something the buyer did, in writing, that a manager can verify without asking the rep. A returned security questionnaire, a named economic buyer on a call, a pilot success document signed by both sides, a procurement ticket number. A demo delivered or a proposal sent is seller activity and proves nothing about the deal.

### How do you accelerate a stalled enterprise deal?

First find out where it is stalled, because the remedy differs. If it is stuck at business case, give the champion a one page CFO document with the numbers filled in. If it is stuck at security, offer a completed SIG Lite and your SOC 2 report proactively. Discounting rarely unsticks a deal that is blocked on process rather than price.

### Should you run a paid pilot or a free pilot?

Paid, almost always, above 100,000 dollars ACV. A paid pilot forces a budget decision, which reveals whether the money is real, and it puts a named owner on the buyer side. Free pilots attract evaluation without commitment and tend to expand in scope while the close date drifts. If you must go free, cap the duration hard and write the success criteria first.

### What is MEDDPICC and is it worth using?

MEDDPICC is a qualification framework covering metrics, economic buyer, decision criteria, decision process, paper process, identified pain, champion and competition. It is worth using at enterprise ACVs because the gaps it exposes are the gaps that kill deals. It is overhead at transactional ACVs, where a simpler qualification model moves faster.