Sales stage architecture
A stage without criteria is a label. A stage with criteria is a gate.
We rebuild pipelines so every gate is a buyer decision you can verify — and win rate climbs at each one.
First principles
The stages describe what the rep is doing instead of what the buyer has decided. That single design error is the root cause of unreliable forecasts, deals that rot in stage, and board meetings that turn into data fights.
A deal is only in a stage when it has met that stage's entry criteria, and it can only leave when it has met the exit criteria. No criteria, no gate — just a colored column that tells you nothing.
"I sent a proposal" is an input the rep controls and can fake. "The buyer confirmed the business case with their economic buyer" is a buyer action the rep cannot manufacture.
Demand in, revenue out. Constraints and bottlenecks live between stages, at the gates. That's where you find the leak, and that's where conversion is won or lost.
The steps the buyer takes to solve their problem. They'd take these with or without you.
Your operational mirror of that journey — the gates a deal passes through in the CRM.
The questions, qualification, and behaviors reps use inside each stage — MEDDICC, SPICED, BANT.
Stages are the skeleton. Methodology is the muscle.
The two laws
Everything else on this page is downstream of these two.
The condition that lets a deal advance must be something the buyer did or agreed to, observable and logged in the CRM — not the rep's optimism. Exit criteria are more predictive than entry criteria precisely because they require a buyer action, not a rep's judgment call.
Of the deals that reached Stage N, what percentage eventually closed won? That number must climb monotonically as deals move forward. If deals in Stage 4 don't close at a higher rate than deals in Stage 3, the boundary between 3 and 4 carries no information — merge or redefine the stages.
This is the fastest audit of whether a pipeline is real or theater.
Reference stage model
A defensible B2B default. Adapt the names and gates to the client's actual buyer journey — the point is the shape.
Exit criterion — the buyer action required to advance
Buyer confirms a real, quantified problem worth solving now.
The jump in forecast category — Pipeline to Best Case to Commit — should coincide with the biggest jumps in historical win rate. If it doesn't, your gates are in the wrong place.
Highest-leverage object in the system
They are where conversion is designed. Rewrite every activity-based criterion as a buyer commitment.
| Weak — rep activity | Strong — buyer commitment | |
|---|---|---|
| "Held discovery call" | → | Buyer confirmed a quantified pain and agreed it's worth solving now |
| "Gave the demo" | → | Buyer confirmed solution fit and named their decision criteria |
| "Sent proposal" | → | Buyer agreed on scope, pricing range, and a decision date |
| "Following up" | → | Buyer committed to a mutual action plan with dated next step |
| "Verbal yes" | → | Economic buyer confirmed budget and started procurement/security review |
The right-hand column is unfakeable, forecastable, and coachable. The left-hand column is why forecasts miss.
It records something the buyer did or explicitly agreed to.
Met or not met. No "kind of." If you can argue about it, rewrite it.
An artifact or field proves it — an email confirmation, a signed document, a completed field.
Deals that clear it close at a materially higher rate. If it isn't predictive, it isn't a gate.
Wiring in qualification
Pick the framework by deal complexity and cycle length, then embed its fields into the relevant stages' exit criteria — so qualification is captured as a byproduct of moving the deal.
Budget, Authority, Need, Timeline
Transactional and mid-market motions with few stakeholders. Fast screening: is this even real?
Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition
Complex, multi-stakeholder, procurement-heavy deals. Rigor for the back half of the pipeline.
Situation, Pain, Impact, Critical event, Decision
Consultative selling focused on transformation and value. Depth in discovery.
BANT-style screening at the top, then deepen with SPICED discovery and MEDDICC rigor as the deal gets bigger.
Identify Pain and Metrics to exit early stages. Economic Buyer and Decision Process to exit mid-stages. Champion and Competition before a deal can be called Commit.
What a gate is worth
Move the sliders to your own numbers. Then move the two levers a stage redesign actually pulls — win rate and cycle length — and watch the arithmetic.
Annual pipeline velocity gained
$1.36M
Additional closed-won revenue per year from the same demand — no new leads, no new headcount.
Velocity today
$8,337/day
Velocity with clean gates
$12,072/day
Thresholds
Benchmarks orient you; they never define "good" for a specific motion. Calibrate every threshold from the client's own 6–12 month history, then band it.
Materially below your median
This triggers a play. Not a discussion — a play, with an owner and a date.
Your trailing median
Computed from stage-to-stage conversion over the trailing 6–12 months.
Top quartile of your own history
Or a stretch you can defend with the data in front of you.
| Directional B2B range | Orientation only |
|---|---|
| Lead/MQL → SQL | Low-to-mid double digits |
| SQL → Opportunity | ~40–60% |
| Opportunity → Closed Won | ~15–30% |
| Time-in-stage stall flag | >1.5× median |
Where the leak is.
Validates Law 2.
Surfaces stalls and bottlenecks.
(Opps × value × win rate) ÷ cycle length. The revenue impact of any change.
Treat the ranges as smell tests, not scorecards. A motion far outside a range isn't automatically broken — but it's a question worth asking.
The design procedure
This is the sequence a pod runs when standing up or rebuilding a client's stages.
Interview reps and recent buyers — won and lost. Document the decisions a buyer makes to get from unaware to signed. You are mapping their path, not yours.
One stage per meaningful buyer decision. Merge steps the buyer experiences as a single decision. You should land on 5–7.
Exit criteria carry the weight. Write them first, and write them as buyer actions.
Artifacts make the gate auditable. Methodology makes it repeatable.
One accountable owner, one primary motion per stage. Ownership kills the "whose deal is this" ambiguity that lets deals rot.
Pull 6–12 months of closed deals. Stage-to-stage conversion, win rate by stage, time-in-stage become your bands and stall alerts.
Exit criteria become required fields to advance. A stage gate a rep can skip is not a gate.
Re-run Law 2 quarterly. Kill dead deals so they stop inflating the pipeline and poisoning the forecast.
Below 5, stalls hide inside big stages. Above 8, rep compliance collapses and the columns stop being updated honestly.
If two reps can disagree about whether a deal belongs in a stage, the name is too vague.
Closed Won is a gate, not the end of the system. Post-sale stages get the same gate discipline.
Failure modes
Name them and they stop being mysteries. Each one has a known fix.
Stages named after rep tasks.
FixRename to buyer decisions; rewrite exit criteria as buyer actions.
Colored columns, no gates.
FixAdd binary, buyer-verifiable exit criteria; make them required to advance.
Later stages don't close better than earlier ones.
FixMerge or redraw the gates until Law 2 holds.
Nine-plus columns nobody updates honestly.
FixCollapse to 5–7.
Reps jump ahead to look advanced.
FixEnforce entry criteria in the CRM; block skips.
Dead deals inflate pipeline and lie to the forecast.
FixAuto-flag on time-in-stage; force an advance / close-lost / recycle decision.
Deals parked in Best Case or pulled to Commit on a verbal.
FixGate forecast categories on artifacts — procurement started, order form out — not vibes.
MEDDICC exists in training but nowhere in the CRM.
FixEmbed the fields into stage exit criteria so qualification is captured as a byproduct of advancing.
Built once, never audited.
FixQuarterly re-run of Law 2, plus a pruning cadence.
Rollout checklist
Getting reps to run them honestly is the other half. Change management is where most redesigns die.
How we run it
A pipeline that tells the truth about what's moving and why — so forecasting stops being fiction and every gate earns its place with data.
Sources
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
