Sales Process & Stage Criteria

Audience & situation

For CRO/RevOps/Enablement leaders and managers who need a simple, enforceable sales process. Use this when forecast misses come from stage drift, duplicate data entry, or deals that “progress” without proof.

Introduction

Most sales processes look good on a slide and fall apart in the CRM. Stages are vague, exits are subjective, and reps retype the same MEDDICC facts in three different places. Managers compensate with more meetings; forecasts still wobble because nothing in the system forces proof before progression.

A strong process is an operating system, not a poster. Each stage exists for a reason, has clean entry and exit criteria, and requires a small set of artifacts that prove reality. The CRM enforces these rules at the moment of stage change—no side spreadsheets, no “we’ll fill it later”. Reps spend less time on admin because fields are mapped once to MEDDICC and reused; managers coach the gaps the system surfaces.

Clarity changes behavior. When “Stage 3 exit = MAP agreed + security intake started + economic buyer identified in CRM” (and the system prevents the move without those items), velocity improves and surprises drop. Finance trusts the numbers. Leadership can forecast with a narrower confidence band. Most importantly, deals move forward because the next task is obvious and owned.

This playbook gives you a practical, enforceable stage model with definitions, artifacts, a MEDDICC field map, governance and dashboards. It includes worked examples across enterprise, mid-market and public sector, plus a 90-day rollout and a companion template you can implement as-is.

What good looks like

• Explicit stages: purpose, entry and exit in one sentence each.
• Few, tight artifacts: proof beats prose—MAP, discovery brief, security intake, business case.
• Single source of truth: MEDDICC captured once and reused; no duplicate fields.
• Guardrails in CRM: cannot progress without required fields/files.
• Manager leverage: stage-change notes and reason codes drive coaching and pipeline hygiene.

Common pitfalls

• Vague exits: “stakeholders aligned” with no names or dates.
• Duplication: MEDDICC fields scattered; reps retype the same info.
• Compliance theatre: artifacts uploaded after the fact to unlock a stage.
• Too many stages: micro-stages that add clicks without clarity.
• No reason codes: stage jumps/laps without context → poor learning.

Playbook

1) Define the funnel (names & purpose)

• Stage 1 — Qualify: is there a problem we solve and a path to power?
• Stage 2 — Discovery: quantify pain, map stakeholders, agree evaluation shape.
• Stage 3 — Solution Fit: align on approach and scope; draft success criteria.
• Stage 4 — Validation: run proof (pilot/POC/ref calls); de-risk security/legal.
• Stage 5 — Business Case: confirm ROI and executive sponsorship; commit timeline.
• Stage 6 — Procurement: commercials, legal, ordering; exit to won/lost.

2) Make exits binary (per stage)

3) Required artifacts (proof over prose)

• Discovery brief (problem, impact, stakeholders, timeline cues)
• MAP (mutual action plan with owners/dates)
• Security intake (link/file + owner)
• Proof pack (pilot criteria & results / reference call notes)
• Business case (1-pager: assumptions, ROI, risk)

4) MEDDICC mapping (once, reused)

5) CRM guardrails & coaching

• Make exit fields required on stage change (not on save).
• Use stage change reason picklist (e.g., “proof passed”, “EB meeting booked”).
• Auto-create manager task when a deal regresses ≥1 stage.
• Dashboard tiles: “exits missing”, “security not started”, “no EB meeting”

Stage dictionary (quick reference)

Artifacts

• Discovery brief template • Security intake shortcut • MAP • Proof pack • Business case 1-pager

Worked examples

Example A — Enterprise SaaS with security heavy

Context: Bank; strict infosec; platform incumbent. Failure mode: pilots run before security → stall in Stage 4.

Fix: Stage 3 exit requires security intake submitted + EB path. POC limited to 2 use cases with clear success criteria.

Result: Validation time −28%; win rate +9 pts; fewer end-of-quarter slips.

Example B — Mid-market fast track

Context: Time-sensitive ops buyer; light security. Design: compress stages 3–4; proof via references + 14-day sandbox.

Result: Cycle time −21%; discount down 2 pts due to earlier EB engagement.

Example C — Public sector RFP

Context: Formal RFP; limited EB access. Move: Stage 2 exit includes decision process mapped and pre-bid Q&A logged. Stage 4 proof via site visits + third-party benchmarks.

Result: Higher compliance score; clearer loss reasons when not selected.

Metrics

Leading: % stage exits passed first time, security started by Stage 3, EB meeting by Stage 4, MAP adoption, proof completion rate.

Lagging: stage conversion, time-in-stage, slipped deals, win rate vs. incumbent, forecast accuracy.

Enforce exits at the point of stage change. Proof before progression.

Implementation checklist

• Draft purpose/entry/exit per stage (≤1 sentence each).
• Pick 5 artifacts max; map each to a stage exit.
• Create MEDDICC field map; delete duplicates.
• Configure CRM validation on stage change; add reason codes.
• Publish manager review script focused on exit checks.

Measurement

Team level: exit-pass rate, time-in-stage distribution, % deals with MAP, % security started by Stage 3, forecast error band.

Individual level: exit rejections, regression count, MEDDICC completeness, EB engagement by Stage 4.

Team buy-in

• Position exits as a coaching tool, not gatekeeping.
• Share 2 gold-standard examples per stage; celebrate clean exits.
• Keep admin light—remove a field for every new one added.

Why it matters

• Predictability: fewer end-of-quarter surprises.
• Speed: next actions obvious; blockers surfaced early.
• Trust: finance and leadership believe the numbers.

Pair with MAPs, strong discovery and clear give/get guardrails to keep momentum.

Metrics & pitfalls

90-day rollout

Weeks 1–2 — Design & align

• Draft stage purpose/entry/exit; select artifacts; agree MEDDICC map.
• Review with 3 top reps + 2 managers; tighten wording to be binary.

Weeks 3–4 — Configure & pilot

• CRM: require exit fields on stage change; add reason codes; build dashboard tiles.
• Pilot on 20 deals across segments; collect rejections and confusion points.

Weeks 5–6 — Enable & coach

• Publish cheat sheets; run live deal reviews using new exits.
• Tune artifacts (e.g., shrink discovery brief) based on pilot feedback.

Weeks 7–8 — Roll out

• Enable validation rules for all; managers own exit checks in pipeline review.
• Report exit-pass rate weekly; spotlight clean examples.

Weeks 9–10 — Tighten cross-functional

• Security intake SLA; legal LOA templates; finance guardrails for term/volume.

Weeks 11–12 — Bake into rhythm

• QBR includes stage hygiene; refresh examples quarterly.
• Target state: exit-pass rate ≥85%, forecast error band −25%, time-in-stage variance −20%.

Related

• Discovery Call Framework
• Mutual Action Plan (MAP)
• Give/Get Menu
• Competitive Deal Strategy

Next steps & CTA

• Adopt the stage dictionary verbatim for a 60-day trial.
• Turn on exit validation for Stage 3→4 and Stage 4→5 first.
• Review exit-pass rate weekly and coach the top 2 failure reasons.

Use the template

Sources & terms

Terms: MEDDICC (Metrics, Economic buyer, Decision criteria/process, Identified pain, Champion, Competition), MAP (Mutual Action Plan), Exit criteria (binary conditions required to move stage).