Repeatable Sales Process: A 6-Stage Template With Exit Criteria for B2B SaaS

Almost every B2B SaaS team I assess tells me they have a sales process. When I ask the AEs to describe it, I get six different versions. When I ask the sales manager, I get a seventh. The CRM stages exist — Discovery, Qualification, Proposal, Negotiation, Closed — but nobody can tell me what specifically moves a deal from one stage to the next. The honest answer, when AEs trust me enough to give it, is some version of "I move it when it feels like the right time."

That is not a sales process. That is a vibes-based timeline dressed up in CRM picklists. It works fine when the founder is closing every deal and carries the context in their head. It collapses the moment you hire your third AE — because each rep is now running a different process, and the data flowing into the pipeline is comparing apples to airplanes.

A repeatable sales process means three things, none of which are optional. First: every stage has a binary exit criterion that any rep can apply consistently. Not "the buyer seems interested" — something like "economic buyer identified by name and role, confirmed via direct response." Second: every disqualification path is named. If a deal cannot meet the exit criterion within a defined time window, there is a documented next action — recycle, nurture, or closed-lost — and the manager doesn't get to override it on a vibes basis. Third: every handoff has an owner and an SLA. MQL to SQL, AE to CSM, sales to legal — each transition has one person responsible, one trigger, and one maximum elapsed time.

If you don't have all three, you don't have a repeatable process. You have a CRM configuration with optimistic labels.

This article gives you the template I install in 12-18 week sales transformation engagements — the same 6-stage architecture with the same exit criteria, refined across 30+ B2B SaaS companies between $3M and $25M ARR. It is opinionated and unapologetic about being so. The point of a template is not to be flexible. The point is to give every rep on your team the same definition of "qualified" so that pipeline numbers from rep to rep are actually comparable.

Six stages, not eight, not ten. Every additional stage beyond six adds CRM friction without adding decision clarity — and I'll explain why in the anti-patterns section. The stages are named for the buyer state, not the rep activity, which is the single most important design choice in this entire framework.

Stage 1 — New (Inbound signal received). A lead has entered the system: form fill, demo request, content download, outbound reply, partner referral. The deal exists in the CRM but has not yet been worked.

Exit criterion to Stage 2: SDR or AE has completed a first outreach attempt and either (a) booked a discovery call, or (b) confirmed the lead does not match ICP and disqualified it. SLA: 1 business day from inbound signal. If 48 hours elapse without contact attempt, the lead is flagged and re-routed.

Stage 2 — Discovery (Problem and fit explored). A discovery call has happened. The rep is mapping the buyer's situation: what problem triggered the search, what they've tried, what timeline they're working against, what budget framework exists.

Exit criterion to Stage 3: All four answered, by name: (1) the specific business problem and its measurable cost, (2) the buying timeline with a target decision month, (3) the budget owner identified (the person whose P&L this hits, not the champion), and (4) a documented next step on the buyer's calendar with the champion confirmed. If any of the four is missing, the deal stays in Stage 2. SLA: 14 days from entry. If 14 days pass without exit, the deal is recycled to nurture or closed-lost.

Stage 3 — Qualified (Economic buyer access requested). This is the most consequential stage gate in the entire process. The deal is no longer about whether there's a fit — it's about whether the right people are at the table to make a buying decision.

Exit criterion to Stage 4: (1) Confirmed budget owner identified, (2) economic buyer access requested via the champion using a specific scripted ask, (3) a second stakeholder beyond the champion has had documented contact in the last 14 days, and (4) the buyer has articulated success criteria in their own words (not the rep's words). Multithreading is a Stage 3 exit requirement, not a best practice. SLA: 21 days from entry.

Stage 4 — Proposal (Solution and commercials presented). A proposal has been delivered: pricing, scope, timeline, terms. The buyer is evaluating the offer against alternatives (including "do nothing," which is always the strongest competitor).

Exit criterion to Stage 5: (1) Proposal reviewed in a live conversation with the economic buyer (not just the champion), (2) specific objections surfaced and documented, (3) competitor or alternative being evaluated named, and (4) a mutual close plan agreed with a target signature date. "Sent the proposal, waiting to hear back" is not Stage 4 — it's Stage 3 with a PDF attached. SLA: 21 days from entry.

Stage 5 — Negotiation (Terms being finalised). Pricing and contract terms are actively being negotiated. Legal and procurement are typically engaged on the buyer side.

Exit criterion to Closed-Won: (1) Final pricing agreed and approved at the appropriate discount tier, (2) contract redlines resolved or paper terms accepted, (3) procurement sign-off confirmed if applicable, and (4) signature date confirmed within 14 days. SLA: 21 days from entry. Deals stalling beyond 30 days in Stage 5 are almost always missing economic buyer alignment, not legal alignment.

Stage 6 — Closed-Won (Contract signed, ready for handoff). The deal is signed. This is not the end of the sales process — it is the start of the handoff. The AE owns the deal until the structured handoff to the CSM is complete, with the success criteria document populated.

Exit criterion to active customer: (1) Handoff document complete with success criteria, key stakeholders, and sales-cycle commitments captured, (2) joint AE-CSM-customer kickoff call held within 7 days, and (3) 30-day check-in from the AE scheduled.

That's the entire template. Six stages, each named for the buyer state, each with binary exit criteria, each with an SLA. A new AE should be able to look at any deal in your CRM and tell you within 60 seconds whether it actually belongs in the stage it's in. If they can't, your stage definitions are still subjective.

The MQL-to-SQL handoff is where most B2B SaaS teams quietly lose 20-30% of their qualified-by-marketing leads. The marketing team marks a lead MQL based on scoring. The lead sits in a queue. An SDR picks it up two days later. By the time outreach happens, the buyer has moved on, talked to a competitor, or stopped caring. The handoff isn't broken in the sense that someone is doing it wrong — it's broken in the sense that nobody owns the elapsed time between MQL flag and first contact.

In the 6-stage template above, MQL and SQL are not separate stages. They are routing states within Stage 1. Here is how I structure them:

MQL definition (binary): A lead matches ICP firmographics (industry, headcount, geography, tech stack if applicable) and has demonstrated buying intent via a specific trigger event — demo request, pricing page repeat visit, high-intent content engagement, or matching an outbound trigger list. "Downloaded a whitepaper" is not MQL. "Downloaded a whitepaper, then visited the pricing page within 7 days" might be.

MQL routing SLA: Marketing flags the lead MQL. The lead is auto-assigned to an SDR within 5 minutes via round-robin or territory rule. First outreach attempt happens within 1 business day. If no contact attempt logged in 24 hours, the lead is reassigned automatically. No manual reshuffling, no "I'll get to it after my current calls."

SQL definition (also binary): The SDR has spoken to the lead and confirmed three things: (1) the lead is in a role that participates in buying decisions for this category, (2) there is a problem in scope of what the product solves, and (3) there is an interest in a discovery conversation within the next 14 days. All three, or it stays MQL. "Seemed interested" is not SQL.

SQL handoff SLA: SDR books the discovery call directly into the AE's calendar. Maximum 5 business days between SQL flag and discovery call held. The handoff is owned by the SDR until the discovery call happens — if the buyer reschedules or no-shows, the SDR re-engages, not the AE. The AE picks up ownership at the moment of the held discovery call, which is the formal entry into Stage 2.

The single highest-leverage SLA in the entire process is the MQL-to-first-contact window. Companies that compress it from 48 hours to under 6 hours typically see 15-20% lifts in eventual closed-won rate from inbound leads. The conversion math is well-documented industry-wide, but the operational discipline to enforce it is rare. If you want to dig deeper into where stage-to-stage conversion math gets diagnosed, win rate and stage conversion diagnostics walks through the measurement framework.

One note on splitting the work between PLG and SLG motions: if you run both, the routing rules diverge here. Self-serve signups in a PLG motion don't enter this process until they hit a usage-based trigger that qualifies them for sales touch — and the question of when that trigger fires is what separates a clean PLG-with-sales motion from one that constantly fights itself. The full breakdown is in SaaS sales process: PLG vs SLG architecture.

Process documents in B2B SaaS almost always cover what happens when a deal advances. They rarely cover what happens when a deal can't advance — which is where the leakage is, and where pipeline integrity goes to die.

A repeatable process needs three explicit non-advance paths, and the rep needs to know which one applies without asking.

Disqualified — ICP miss. The lead is not in the target market. Wrong industry, wrong size, wrong geography, wrong problem. This is a one-way ticket: closed-lost with reason "ICP miss," no recycling, no nurture. The marketing team gets the data back for ICP refinement. The AE moves on within 30 minutes of identifying the miss — no second discovery call to "see if there's something there."

Recycled — timing or fit mismatch. The lead matches ICP but the timing is wrong or the specific problem isn't acute right now. This is the largest non-advance bucket and the one most often handled badly. The deal moves to a nurture status, the close-lost reason is logged as "not ready — revisit [target date]," and the lead enters a marketing nurture cadence appropriate to the trigger that fired in the first place. A specific re-engagement date is set, and on that date, the lead re-enters Stage 1 — not Stage 2, because the situation needs to be re-discovered.

Closed-lost — competitive or product gap. The lead bought elsewhere, decided to build in-house, or has a specific product gap that won't be addressed in the next two quarters. This is closed-lost with a documented reason, fed back to product and marketing. No nurture, no recycling — until the product gap closes, in which case marketing triggers re-engagement.

The critical rule: a deal that has been sitting in Stage 2 for more than 14 days without meeting the Stage 3 exit criteria is not "still in Stage 2." It is recycled or closed-lost. The SLA forces the decision. Without that forcing function, deals accumulate in mid-funnel forever, inflating coverage ratios, distorting velocity metrics, and giving managers a false sense of pipeline health.

I typically see 35-45% of all Stage 1 leads end up in one of these three non-advance buckets within the first 21 days. If your data shows less than 20% non-advance, you have a hygiene problem, not a high-conversion process. Real pipelines lose leads — the question is whether they lose them in a tracked, instrumented way that improves future ICP and process decisions, or whether they lose them silently into a black hole called "still working it."

The full process in text-flowchart form (because you'll want to translate this into your CRM's stage architecture and routing rules):

[Inbound Signal]
    │
    ▼
[Marketing Scoring]──► (Not ICP)──► [Closed-Lost: ICP Miss]
    │
    ▼ (ICP + Intent)
[MQL Flagged]
    │
    ▼ (Auto-assign, 5 min)
[SDR Queue]
    │
    ▼ (Outreach within 1 business day)
[STAGE 1 — New]
    │
    ├──► (No reply, 7 days)──► [Recycled: Nurture]
    │
    ▼ (Discovery call booked & held)
[SQL Flagged → STAGE 2 — Discovery]
    │
    ├──► (Discovery fails ICP)──► [Closed-Lost: Disqualified]
    │
    ├──► (Fit OK but timing off)──► [Recycled: Re-engage date set]
    │
    ▼ (Problem + timeline + budget owner + next step confirmed, ≤14 days)
[STAGE 3 — Qualified]
    │
    ├──► (No EB access in 21 days)──► [Recycled or Closed-Lost]
    │
    ▼ (EB access + multithreading + success criteria, ≤21 days)
[STAGE 4 — Proposal]
    │
    ├──► (No EB-attended review in 21 days)──► [Closed-Lost: Stalled]
    │
    ▼ (Mutual close plan + objections surfaced)
[STAGE 5 — Negotiation]
    │
    ├──► (No signature in 30 days)──► [Closed-Lost or Recycled]
    │
    ▼ (Pricing agreed + paper signed)
[STAGE 6 — Closed-Won]
    │
    ▼ (Handoff doc + joint call + 30-day check-in scheduled)
[Active Customer → CSM ownership]

What this flowchart makes visible is the thing most CRM stage diagrams hide: every advance path has a non-advance path next to it, and the SLA on each non-advance is what makes the process self-cleaning. The CRM should be enforcing these timing rules, not relying on AEs or managers to remember them. If your CRM can't auto-flag deals that have exceeded SLA, you don't have a repeatable process yet — you have a process design that depends on human vigilance, which means it will degrade within 90 days.

This whole architecture sits inside a broader sales playbook. The playbook documents who does what, the process documents how the work flows, and the qualification framework documents what counts as moving. If you want the full picture of how playbook and process interact, what is a sales playbook is the companion read.

Most broken sales processes were not built broken. They were built reasonable, then degraded over 12-24 months as one of three anti-patterns took hold. If you recognise any of these, you don't need a redesign — you need to stop doing the destructive thing first, then re-establish the original discipline.

Anti-pattern 1: Too many stages. I've audited CRMs with 11 stages. One had Stage 3a, 3b, and 3c. Every additional stage past six is the team trying to capture rep activity ("sent the deck," "had the technical review," "presented the ROI") as if it were buyer progression. Activity is not progression. A buyer who has seen your deck twice is not further along than a buyer who has seen it once — they're just a buyer who has seen your deck twice. Stages should track buyer state changes, not rep effort. If you have more than six stages, the extra ones almost always describe what the rep did, not what the buyer decided. Collapse them.

Anti-pattern 2: Stages defined by activity instead of buyer state. Related but distinct. "Demo Delivered" is an activity-based stage. "Solution Validated" is a buyer-state stage. The first one advances when the rep delivers a demo; the second advances only when the buyer confirms the solution fits the problem. Activity stages create a perverse incentive: reps deliver demos to leads who aren't ready in order to move the deal forward and show pipeline progression. Buyer-state stages create the opposite incentive: reps only deliver demos when the demo will produce a clear signal of validation, because a delivered demo with no validation doesn't move anything. This is the single most common design flaw I see across B2B SaaS pipelines, and it's the one with the largest pipeline-quality cost.

Anti-pattern 3: No disqualification gate. This is the most damaging of the three. The process documents how deals advance but doesn't document how deals don't advance, doesn't set time-in-stage SLAs, and doesn't force the manager or the rep to make a recycle/lost decision. Deals accumulate in Stage 2 and Stage 3 indefinitely. Pipeline coverage looks healthy. The forecast looks defensible. Then quarter-end arrives and 40% of the late-stage pipeline slips because none of it was ever real. The fix is a hard SLA per stage with auto-flagging, and a weekly pipeline review that explicitly addresses every flagged deal — recycle, hold, or close-lost — with no "let's keep working it" option for deals beyond SLA.

A secondary destructive pattern worth naming: "the manager override." A deal hits SLA, the system flags it for recycle, the manager overrides the flag because they don't want to see pipeline shrink before the board meeting. Three months later, the deal is still in the pipeline, having generated zero customer activity, and the manager has forgotten they overrode it. Cumulative manager overrides are how clean processes become contaminated processes. If you want managers to have override authority, fine — but every override gets logged, reviewed at the end of the quarter, and the override outcome (closed-won or eventually closed-lost) is reported back. Visible accountability for overrides eliminates 80% of casual ones.

A process you can't measure is not repeatable — it's repeated. Here's the minimum instrumentation set, which fits in any CRM that supports custom fields and stage-history reporting.

Per stage, track four things: (1) entries per period — how many deals entered this stage, (2) exits per period split by destination — to next stage, to recycled, to closed-lost, (3) median time-in-stage by ACV band, and (4) SLA breach rate — what percentage of deals exceeded the documented SLA before exiting.

Per handoff, track three things: (1) MQL-to-first-contact elapsed time, (2) SQL-to-discovery-call elapsed time, and (3) closed-won-to-handoff-complete elapsed time. These three numbers tell you more about your operational discipline than any other metric.

Per AE, track two things: (1) stage exit-criterion compliance — what percentage of advances had all documented criteria met at the time of advance, and (2) recycle vs lost mix — AEs who never recycle are usually marking deals lost prematurely; AEs who never lose are usually parking dead deals in nurture. Both distort the data.

Things to deliberately not track on a weekly basis: total pipeline value, average deal size, individual activity metrics (calls made, emails sent). They feel productive to measure and they generate management focus on the wrong things. Activity is an input — if the stage gates are tight and the SLAs are enforced, activity self-corrects. Activity metrics in a leaking process drive the wrong behaviour, which is reps padding numbers to hit activity targets instead of focusing on stage-gate quality.

Most teams I work with implement this template inside the broader 12-18 week sales transformation engagement because the process redesign needs to be accompanied by manager retraining, CRM reconfiguration, and 60 days of active reinforcement before it becomes the team's default. If you've already done the diagnostic work to know your process has structural gaps — the kind covered in sales process optimization — the template here is the design that fixes them. If you're a founder still doing most of the selling, the question of when to formalise this process versus when to keep moving fast is covered in fractional CRO first 90 days, which walks through how a structured process gets installed without breaking the deals already in flight.

For teams thinking about the commercial side — what an engagement to install this process actually looks like, scope, accountability, decision criteria — sales transformation consulting engagement covers the structure. The process design is the easy part. Making the team operate inside it for 60 consecutive days, until the new defaults harden, is where most internal attempts fail.