A B2B sales process is a sequence of stages with objective exit criteria and clear ownership, one that repeats and scales. It's not a script, a kickoff PowerPoint, or a CRM pipeline slide. It's an operational system that turns selling from an individual art into a repeatable discipline, and that makes revenue predictable.
The difference between a sales team that performs and one that stagnates is almost never about raw talent. It comes down to method. Does every AE follow the same steps? Does a deal advance because an objective criterion has been met, or because the rep decides to move it forward? Can the manager coach on facts, or only on opinions? These questions determine revenue predictability, new hire ramp time, and the company's ability to scale without costs exploding.
In ACROSS's Revenue Health Score assessments, the Sales pillar is consistently where the gap between "we have a process" and "the process is actually followed" is widest. Nine companies out of ten have formalized a pipeline. One in ten has measurable exit criteria per stage. That difference is what separates teams that forecast at 85% from those that forecast at 55%.
This guide breaks down what a scalable sales process actually is: the precise definition, standard stages, exit criteria per stage, methodologies (BANT, MEDDIC, SPIN, Challenger, Sandler), the mistakes that derail most implementations, governance (who does what), CRM mechanics, impact metrics, and a 90-day adoption playbook for turning a theoretical process into a living one.
Key Takeaways
- A sales process = stages + exit criteria + ownership. Without all three elements together, it's a CRM pipeline, not a process.
- Exit criteria are not optional. Every stage must have objective, verifiable, documented conditions, otherwise the pipeline is fiction.
- Process and playbook are different things. The process describes the stages. The playbook describes how to execute within each stage. Both are necessary.
- Formalize once you hit 8+ AEs, a cycle longer than 30 days, or an ACV above €10k. Below that, a lightweight process is enough. Beyond it, improvisation costs millions.
- Methodologies: BANT for transactional deals, MEDDIC for enterprise, SPIN for discovery, Challenger for disruption. None is universal, the best teams combine them.
- Measured impact: +10 points of win rate, -20% cycle time, +15 points of forecast accuracy. On €10M of ARR, that translates into €2-3M of additional revenue per year.
- A process only stays alive if it's coached. Without weekly Revenue Reviews that challenge the exit criteria, the process dies within 60 days.
"Sales is the last major business function that has not yet been transformed from an art into a science. The companies that win in the next decade will be those that treat their sales process with the same rigor that engineering treats code." Mark Roberge, The Sales Acceleration Formula
What a Sales Process Actually Is (and What It Isn't)
The most common confusion: equating a sales process with a CRM pipeline. A CRM pipeline is a view, the stages displayed in HubSpot or Salesforce. A sales process is a system, the operational logic underneath that view. The first can exist without the second, which is why 80% of B2B companies have a pipeline but no process.
The Three Inseparable Components
A complete sales process has three elements that work together. Remove one, and the whole thing collapses.
Stages define the sequence: where a deal sits in its lifecycle. Prospect, Discovery, Qualification, Proposal, Negotiation, Closed Won. Each stage represents a milestone in the conversation with the customer.
Exit criteria define the rigor: what objective conditions must be met for a deal to move to the next stage. "The champion has confirmed the budget in writing" is an exit criterion. "It's going well" is not.
Ownership defines governance: who is responsible for what at each stage, who approves transitions, who coaches, who measures. Without clear ownership, every stage becomes no one's territory and the process dissolves.
Process vs. Playbook
This distinction escapes 70% of VPs of Sales. The process describes what (stages, exit criteria, transitions). The playbook describes how (scripts, discovery questions, objections, proposal templates, competitive battlecards). A process without a playbook leaves each AE to invent their own execution method. A playbook without a process produces content without structure.
Mature teams have both: the 6-stage process that serves as the backbone, and the 40 to 80-page playbook that details execution at each stage. This is the pairing recommended by the B2B sales enablement guide for any organization with more than 10 AEs.
When to Formalize a Process
Formalization has a cost: build time, adoption, coaching, tools. Below a certain threshold, a lightweight process is enough: a few stages, fuzzy transitions, an oral culture. Beyond it, improvisation becomes dangerous.
The three thresholds that trigger the need for a structured process: a team of more than 8 AEs (beyond that, individual variance becomes unmanageable), a sales cycle longer than 30 days (long deals lose track of their steps), or an ACV above €10,000 (the financial stakes justify the rigor). If two of these three criteria are met, formalization becomes a priority.
The Standard Stages of a B2B SaaS Process
There's a standard 6-stage sales process structure that covers 90% of B2B SaaS contexts. The names may vary, the substance doesn't.
| Stage | Objective | Owner | Typical Duration |
|---|---|---|---|
| Prospect | Identify an ICP-aligned lead with an intent signal | SDR / Marketing | 0-7 days |
| Discovery | Understand the business problem and decision context | AE | 1-3 weeks |
| Qualification | Validate budget, authority, need, timing, champion | AE | 1-2 weeks |
| Proposal | Present the solution and a quantified business case to the decision maker | AE | 1-3 weeks |
| Negotiation | Finalize terms, price, conditions, legal | AE + Deal Desk | 1-4 weeks |
| Closed Won | Signature + structured handover to CSM | AE + CSM | 3-5 days |
This structure is a starting point, not a dogma. Some companies add a "Technical Validation" stage between Qualification and Proposal for technical products. Others merge Proposal and Negotiation for transactional sales. What matters is choosing a structure that reflects your reality and documenting it.
Common Stage-Design Mistakes
Too many stages (10+) paralyze the team: every transition requires a justification, and AEs cheat to avoid the friction. Too few stages (3-4) make the pipeline unreadable: it becomes impossible to distinguish a deal that just entered from one that's close to closing. The sweet spot is between 5 and 7 stages for most B2B contexts.
Another trap: naming stages after activities (Demo sent, Proposal made) rather than states (Problem confirmed, Champion identified). Activities aren't milestones: they describe what the rep does, not what they've achieved.
Exit Criteria: The Backbone of the Process
Exit criteria turn a self-reported pipeline into a factual one. Without them, the forecast is fiction and coaching becomes impossible. It's the most underinvested discipline in most B2B sales teams, and the one that separates an organization that scales from one that flounders.
Criteria by Stage
Every stage should have 3 to 5 measurable exit criteria. Not 10 (unreadable), not 1 (insufficient). Here's the standard grid for an enterprise SaaS process.
| Stage | Mandatory Exit Criteria |
|---|---|
| Prospect | 1. ICP fit confirmed (factual criteria). 2. Contact with influence or authority identified. 3. Intent signal documented (hiring, funding round, change). |
| Discovery | 1. Business problem quantified in euros or metrics. 2. Decision process mapped (number of stakeholders, timeline). 3. Second meeting scheduled. |
| Qualification | 1. Budget confirmed (range or envelope). 2. Champion identified and engaged. 3. Economic buyer known. 4. Decision timeline set. |
| Proposal | 1. Proposal presented live to the decision maker. 2. Budget questions addressed. 3. Major objections identified. 4. Next steps confirmed in writing. |
| Negotiation | 1. Commercial terms aligned. 2. Legal has approved the contract. 3. Mutual Action Plan signed. 4. Signature date set. |
| Closed Won | 1. Contract signed by the decision maker. 2. CSM handover scheduled with full context. 3. First invoice issued. |
These criteria aren't boxes for the rep to check. They're facts the manager verifies during deal review. A deal without documented exit criteria doesn't move forward, no matter how convinced the rep is.
Why Exit Criteria Fail
Three reasons come up consistently in ACROSS audits. First: the criteria are subjective ("the prospect seems interested") instead of objective ("the prospect has confirmed in writing that our solution is on their shortlist"). Second: there's no consequence when a deal advances without meeting its exit criteria, the manager lets it slide. Third: the criteria aren't in the CRM, so they're invisible to the team and to reporting.
The solution: turn every exit criterion into a mandatory CRM field. If the field isn't filled in, the deal can't move forward. It's blunt, and it works. It's the mechanic that makes the difference between a living process and a theoretical one.
Sales Methodologies: BANT, MEDDIC, SPIN, Challenger, Sandler
The process describes the stages. The methodology describes how to qualify and how to sell within each stage. Five methodologies dominate modern B2B. None is universal. Each has its own playing field.
A Structuring Comparison
| Methodology | Focus | Ideal For | Typical Win Rate | Ramp Time |
|---|---|---|---|---|
| BANT | Budget, Authority, Need, Timing | Short cycles, ACV < €20k, junior teams | 15-20% | 2-4 weeks |
| MEDDIC | Metrics, Economic buyer, Decision criteria, Decision process, Champion | Enterprise deals, cycle > 3 months, ACV > €50k | 25-35% | 2-3 months |
| SPIN | Situation, Problem, Implication, Need-payoff | In-depth discovery, complex products | 20-28% | 1-2 months |
| Challenger | Teach, Tailor, Take control | Disruptive markets, prospects unaware of the problem | 22-30% | 2-3 months |
| Sandler | Pain, Budget, Decision, Peer posture | Long cycles, consultative selling, strong relationships | 22-28% | 3-4 months |
The win rate benchmarks come from Winning by Design and aggregated data across 200+ B2B SaaS organizations.
Choosing Your Methodology
Three criteria guide the choice. Deal complexity: more than 3 stakeholders, a cycle over 3 months, ACV above €50k points to MEDDIC. Team maturity: junior reps, short cycles, BANT as a base. Market posture: category-creation markets, prospects unaware of the problem, Challenger. Discovery as a competitive edge, SPIN.
In practice, the best teams combine them. MEDDIC as the qualification framework, SPIN as the discovery method, Challenger elements for sales posture during strategic presentations. What matters is formalizing this combination and making it repeatable, not letting each AE pick and choose on a whim.
BANT vs. MEDDIC Qualification
The most common choice pits BANT against MEDDIC. BANT asks 4 questions, MEDDIC asks 8. The difference isn't cosmetic.
BANT validates that a deal exists: is there a budget, a decision maker, a need, a timing? That's enough for transactional deals where the cycle is short and stakeholders are limited.
MEDDIC validates that a deal will actually close: beyond the budget, what are the impact metrics, who is the real economic buyer, what are the formal decision criteria, what is the internal buying process, who is the champion? This is necessary in enterprise, where deals involve 5 to 15 stakeholders.
The natural progression: start with BANT when the team is young or the product is simple, migrate to MEDDIC as deals get bigger. See the dedicated article on B2B lead qualification with BANT and MEDDIC for the operational detail.
Evaluez votre maturite sur les 8 piliers en 2 minutes. Score instantane, gratuit.
Faire le quiz gratuit →The 5 Classic Sales Process Failures
Five failure patterns show up in 90% of ACROSS audits. Identifying them makes it possible to quickly diagnose the state of an existing process.
1. Over-engineered. The process runs 60 pages, 12 stages, 40 exit criteria, 8 combined methodologies. No one applies it. The VP Sales who wrote it is proud of the document. The team ignores it. Symptom: the process exists in a PDF but not in the CRM.
2. Under-documented. At the opposite extreme, the process lives in the VP Sales's head. Exit criteria are passed on orally. New AEs learn by osmosis. Symptom: two experienced AEs describe the process differently when asked separately.
3. No training. The process is documented, but no structured training exists. New AEs get the PDF on day one and are expected to "figure it out." Ramp time is 9 months instead of 4. Symptom: an AE hired 6 months ago who still hasn't hit their ramp quota.
4. No coaching. The process exists, the training exists, but managers don't coach on it. Weekly Revenue Reviews are status meetings ("So, how's it going?") instead of structured deal reviews ("Which exit criteria have been met on this deal? Show me the proof"). Symptom: forecast accuracy is below 70%. See sales manager coaching for the deal review method.
5. No measurement. The process exists but no one measures stage-to-stage conversion rates, average cycle time per stage, or the stuck rate. It's impossible to diagnose where the pipeline is leaking. Symptom: the VP Sales talks about overall win rate but has no visibility into stage-by-stage conversion.
These five flaws are cumulative. An organization suffering from three or more has a process that isn't really one, and that's generally what surfaces in a diagnostic when the pipeline looks healthy but the forecast keeps slipping.
Governance: Who Does What
A process without clear ownership is a process that dies. Sales process governance involves four roles, each with distinct, non-overlapping responsibilities.
| Role | Primary Responsibility |
|---|---|
| VP Sales / CRO | Owns the process. Defines the structure, stages, and exit criteria. Approves quarterly changes. |
| Sales Managers | Enforce the process. Hold the line on exit criteria in deal review. Coach the AEs. First line of defense. |
| Account Executives | Execute the process. Fulfill the exit criteria. Surface friction from the field. |
| RevOps | Measure the process. Instrument the CRM. Produce the dashboards. Identify stuck deals and anomalies. |
The Manager's Critical Role
The weak link in the chain is almost always the sales manager. The VP Sales defines things well, the AEs execute, RevOps measures, but the manager, caught between enforcement and empathy, lets deals through without exit criteria to avoid straining the relationship with their team.
The fix: institutionalize structured weekly deal reviews with a fixed grid. The manager doesn't ask "how's it going?" but "show me the proof that the champion is engaged (an email, a meeting, a CRM note)." This rigor can feel harsh at first. It becomes cultural within 60 days if it's maintained.
See restructuring a sales team the CRO way for the typical reorganization of a team moving from an artisanal mode to a process-driven one.
CRM and Process: Which One Follows the Other
Fundamental operating rule: the CRM must reflect the process, not the other way around. Getting this backwards is the source of 50% of adoption failures.
The typical scenario: the company inherited a CRM pipeline configured 3 years ago by an outside consultant. The stages are "Lead," "MQL," "SQL," "Opportunity," "Closed Won." A new VP Sales arrives, wants to implement MEDDIC with "Discovery," "Qualification," "Proposal" stages. They twist the process to fit the existing CRM stages. Result: AEs see two realities (the written process + the CRM), they take the path of least resistance, and the process dies.
The right sequence: define the process first, configure the CRM afterward. CRM stages must be exactly the process stages, not an approximation. Exit criteria must be mandatory CRM fields: it must be impossible to advance a deal without filling them in. Stage durations should feed automatic stuck-deal alerts.
Critical CRM Fields
For a properly implemented MEDDIC process, the mandatory fields are: Champion (name + proof), Economic buyer (name + confirmation), Impact metrics (numbers), Decision process (steps + dates), Decision criteria (list). Every empty field blocks progression to the next stage. See pipeline management hygiene and forecasting for detailed CRM hygiene.
The Measurable Impact of a Structured Process
A well-implemented process produces measurable, repeatable effects on three key metrics. These benchmarks come from ACROSS's Revenue Health Score assessments, cross-referenced with public data from Gong, Winning by Design, and Forrester.
| Metric | Before Process | After 12 Months of Process | Delta |
|---|---|---|---|
| Win rate | 18-22% | 28-32% | +10 points |
| Average sales cycle | 120-180 days | 95-140 days | -20% |
| Forecast accuracy (30 days) | 55-65% | 75-85% | +15 points |
| Ramp time (quota achievement) | 7-9 months | 4-5 months | -40% |
| Pipeline velocity | Base 100 | 145-160 | +45 to 60% |
On €10M of ARR, with a win rate moving from 20% to 30%, the impact is €2 to 3M of additional annual revenue with the same team size. The return on investment of a rigorous process implementation (typically 6 to 9 months of work) is reached in less than a quarter.
Forecast Accuracy: The Metric That Changes Everything
If only one metric should be remembered, it's this one. A 30-day forecast that's 80% reliable or better changes the company's ability to allocate resources: hiring, marketing investment, geographic expansion. A 55% forecast is the equivalent of flying blind. The majority of dysfunctional board meetings I observe share one cause: the VP Sales can't commit to a number, because their process doesn't produce reliable data. See precision sales forecasting for the probabilistic forecasting method.
Adoption: The 90-Day Playbook
A process that only lives in a PDF is worthless. Real adoption, the kind where the team applies it without thinking, takes 90 days of structured work. Here's the typical playbook recommended by ACROSS.
90-Day Playbook Template
| Week | Focus | Deliverables |
|---|---|---|
| W1-W2 | Diagnosis | Existing process audit, analysis of 40 deals (20 won + 20 lost), current CRM mapping |
| W3-W4 | Design | Methodology choice, definition of 6 stages, exit criteria per stage, deal review grid |
| W5-W6 | Build | CRM reconfiguration (stages + mandatory fields), playbook v1 written, RevOps dashboards |
| W7-W8 | Training | Team kickoff (2 days), manager training (1 day), stage-by-stage roleplay, AE certification |
| W9-W10 | Pilot | Applied to new deals only, daily coaching, adjustments |
| W11-W12 | Rollout | Applied to all active deals, strict weekly deal reviews, public reporting |
| W13 | Review | 90-day impact measurement, v2 adjustments, board communication |
This sequence isn't negotiable. Skipping the Diagnosis phase produces a theoretical process. Skipping the Pilot phase produces adoption chaos. Skipping the Review phase produces a process that degrades within 6 months.
Conditions for Success
Three non-negotiable conditions. Executive sponsorship: the CEO must visibly sponsor the project, otherwise the VP Sales lacks authority. Immediate enforcement: from W11 onward, deals that haven't met their exit criteria are blocked. No exceptions. Public measurement: adoption metrics (% of deals with complete exit criteria, forecast accuracy, stuck rate) are displayed every week, by AE.
Without these three conditions, the process reverts to its original state within 4 to 6 months. With them, it becomes a cultural discipline within a quarter.
Scorecard for Evaluating Your Existing Process
To quickly diagnose the state of an existing sales process, ACROSS uses a 10-criteria scorecard. A score below 7/10 indicates a process that needs to be rebuilt, not adjusted.
| Criterion | Yes = 1 point |
|---|---|
| 1. The pipeline stages are documented in writing | |
| 2. Every stage has 3+ objective exit criteria | |
| 3. Exit criteria are mandatory CRM fields | |
| 4. A qualification methodology has been chosen and formalized | |
| 5. Managers run structured weekly deal reviews | |
| 6. The process is taught to new AEs in under 4 weeks | |
| 7. Stage-to-stage conversion rates are measured monthly | |
| 8. The 30-day forecast is more than 75% reliable | |
| 9. Deals stuck for more than 30 days are automatically flagged | |
| 10. The process is reviewed and updated every quarter |
Score 9-10: mature process, focus on optimization. Score 7-8: functional process with gaps to close. Score 4-6: theoretical process, needs real implementation. Score 0-3: no process, sales chaos, major business risk.
Integration with Other Revenue Systems
A sales process doesn't operate in isolation. It integrates with three other systems that determine its effectiveness.
Sales Process and Pay Plan
If the pay plan rewards activity (number of demos, number of emails) instead of results (deals advanced according to exit criteria), AEs will ignore the process to maximize their variable pay. Aligning pay plan and process is a structural condition for adoption. See sales pay plan compensation for design principles.
Sales Process and Deal Desk
On complex deals (> €100k, multi-product, specific terms), a B2B deal desk for closing takes over from the Proposal stage onward. It approves pricing exceptions, legal clauses, and payment terms. Without a deal desk, AEs negotiate alone and give away too much: the process builds in this control point.
Sales Process and Hiring
A mature process changes hiring criteria. Companies no longer hire "instinctive hunters" but disciplined executors who apply the method. This shift is detailed in hiring a VP Sales: CRO criteria and evaluating sales reps with a CEO-level scorecard.
Patterns Observed at ACROSS
Across ACROSS's Revenue Health Score assessments, certain patterns come up with striking regularity. Three deserve particular attention.
The €5M-10M ARR plateau. 70% of companies that plateau at this level share the same underlying problem: an artisanal sales process that worked below €5M but doesn't scale. The symptom isn't the process itself: it's the forecast becoming unpredictable and AEs missing quota. The cause is structural.
The top-performer / bottom-performer asymmetry. In teams without a process, the performance gap between the best and worst AE is 4x to 6x. In teams with a mature process, the gap narrows to 2x to 2.5x. The process doesn't prevent excellence: it raises the floor. This is the main reason the process is a scale lever: it reduces dependence on the top performer.
The retention effect. AEs who leave companies without a process do so after 2-3 years. Those who stay at companies with a mature process stay 4-5 years. Reason: the process gives them a clear path to quota, concrete coaching, and readable progression. The absence of a process is an underestimated turnover factor.
These patterns are detailed in revenue audit method for a CRO's first days and in the CRO's 100-day plan for CROs joining an organization without a structured process.
Additional Resources
- The CRO's 100-day plan
- Revenue audit method for a CRO's first days
- Restructuring a sales team the CRO way
- B2B sales enablement guide
- B2B lead qualification with BANT and MEDDIC
- Sales manager coaching
- Precision sales forecasting
- Pipeline management hygiene and forecasting
- Sales pay plan compensation
- B2B deal desk for closing
- Hiring a VP Sales: CRO criteria
- B2B revenue KPIs: CEO-level indicators
- ACROSS Methodology
Sources Cited
- ACROSS Insight, Revenue Health Score: our B2B assessments of French and European SaaS organizations (2024-2026)
- Mark Roberge, The Sales Acceleration Formula, HBR Press, 2015
- Winning by Design, B2B SaaS benchmarks: win rates by methodology, ramp time, average cycle (2024)
- Forrester Research: Mutual Action Plan and win rate correlation, 2024
- Gong: sales conversation analysis across 500k+ recorded calls, discovery and closing patterns
Article written by Charles-Alexandre Peretz, founder of ACROSS Insight. Last updated: February 25, 2026.