The frameworks, applied

An eight-part enterprise qualification checklist that forces a rep to name the money, the buyer, and the process behind a deal instead of a stage label.

WhenComplex, multi-stakeholder B2B deals over roughly $25K [unverified] where procurement and a decision committee decide the outcome. It is the qualification spine most RevOps teams wire into stage gates.

The framework
1. 01Metrics: the quantified economic impact the buyer will measure success by
2. 02Economic Buyer: the one person who controls the budget and can say yes alone
3. 03Decision Criteria: the formal requirements the buyer scores vendors against
4. 04Decision Process: the actual steps, approvals, and paperwork from verbal to signed
5. 05Paper Process: legal, procurement, and security review, the part that eats the last two weeks
6. 06Identify Pain: the compelling business problem that justifies spending now
7. 07Champion: an insider with power who sells for you when you are not in the room
8. 08Competition: who else is in the deal, including the status quo and do-nothing

Deals slip on procurement and approvals, not on whether pain got quantified on call one. MEDDPICC is the only qualification model that names the paper process explicitly, which is why it survives in enterprise. MEDDIC is the six-letter ancestor; MEDDPICC adds Paper Process and Competition.

A four-question lead-qualification filter (Budget, Authority, Need, Timing) that decides whether a lead is worth a rep time.

WhenTop of funnel, for fast inbound triage or SDR call scoring, not for running a complex late-stage deal. It is a gate, not a methodology.

The framework
1. 01Budget: can they fund a purchase in the relevant range
2. 02Authority: are you talking to someone who influences or controls the decision
3. 03Need: is there a real problem your product solves
4. 04Timing: is there a reason to buy in a defined window, not someday

It is fast and every rep already knows it, which makes it the right tool for lead routing and SDR handoff scoring. It is the wrong tool the moment a deal gets complex, where MEDDPICC or SPICED take over.

A five-part discovery and qualification framework (Situation, Pain, Impact, Critical Event, Decision) built for the buyer journey rather than the seller checklist.

WhenWhen you want one framework that runs from first discovery through close and maps cleanly onto CRM fields. It is the operator favorite because it is inspectable and gate-friendly.

The framework
1. 01Situation: the buyer current state, tools, and context
2. 02Pain: the specific problem and what it is costing them
3. 03Impact: the quantified business value of solving it
4. 04Critical Event: the dated deadline that forces a decision
5. 05Decision: the criteria, process, and people who approve the purchase

SPICED is the easiest qualification model to turn into a schema an operator can enforce and forecast on. Its Impact and Decision elements are the qualification-completeness inputs that predict slips 30 to 45 days before a stage label moves.

A discovery-questioning sequence (Situation, Problem, Implication, Need-payoff) that makes the buyer articulate the cost of their problem before you pitch.

WhenTo structure discovery calls and coach reps who pitch too early. It is a questioning discipline that feeds a qualification framework, not a replacement for one.

The framework
1. 01Situation questions: establish the buyer current context and facts
2. 02Problem questions: surface the difficulties and dissatisfactions
3. 03Implication questions: make the buyer feel what the problem costs if unsolved
4. 04Need-payoff questions: get the buyer to state the value of solving it in their words

Implication and Need-payoff questions are how you get quantified Impact into a SPICED or MEDDPICC field without pulling teeth. Good discovery is the raw material the qualification schema captures.

A selling model where the rep teaches the buyer something new about their business, tailors it to the buyer context, and takes control of the conversation, rather than just building rapport.

WhenCompetitive, commoditized, or status-quo-heavy markets where the buyer thinks they already understand their problem. It is a messaging and positioning discipline, less a CRM schema.

The framework
1. 01Teach: lead with a commercial insight, a reframe that points back to a differentiator only you have
2. 02Tailor: adapt the insight to the specific stakeholder and their metrics
3. 03Take control: direct the process, talk price and timeline without flinching

Challenger is the methodology that reliably beats the do-nothing outcome, which is the largest competitor in most pipelines. It shapes the Pain and Impact a qualification framework then records.

A revenue model that extends the funnel past closed-won into onboarding, adoption, and expansion, drawn as two triangles meeting at the deal.

WhenAny time recurring revenue matters, which means always in SaaS. It is the corrective to a CRM that instruments acquisition to the decimal and describes retention with a single renewal-date field.

The framework
1. 01Left side, acquisition: awareness, education, selection, commit (the classic funnel)
2. 02The knot: closed-won, where most CRMs stop instrumenting
3. 03Onboard: the gap between signature and first realized value
4. 04Adopt: usage depth and health trajectory, the earliest churn signal
5. 05Expand: whitespace and buy-more signals routed into a real opportunity
6. 06Renew: retention crossed with days-to-renewal, the leading NRR view

NRR compounds on the right side and investors watch it harder than new bookings. A point of NRR on a $10M book is $100K of recurring revenue that costs $0.80 per dollar versus $1.63 to acquire. You cannot steer a number you have no fields for.

A five-stage lifecycle funnel (Acquisition, Activation, Retention, Referral, Revenue) that instruments a product-led or self-serve motion the way a sales funnel instruments deals.

WhenWhen growth runs through the product, not just reps: free trials, freemium, self-serve signups, PLG-assisted sales. It gives ops a shared metric spine when marketing, product, and revenue all touch the user.

The framework
1. 01Acquisition: how users first find and land on the product
2. 02Activation: the first experience that delivers real value (the aha moment)
3. 03Retention: whether users come back and keep using it
4. 04Referral: whether users invite others, the built-in growth loop
5. 05Revenue: whether and when usage converts to paid

In a hybrid motion, self-serve revenue often lives in a billing system outside the CRM, so AARRR is the only place product-led signal gets a funnel. It maps onto the left knot of the bowtie for products that land before a rep ever calls.

A one-number health check that says a software company growth rate plus profit margin should clear 40%.

WhenTo sanity-check whether growth is worth its burn, most meaningfully past roughly $25M ARR. It is a board and valuation metric, so RevOps should own the definition before finance quotes a different one.

The framework
1. 01Growth: year-over-year revenue growth rate
2. 02Profitability: your chosen margin (EBITDA, FCF, or operating), held consistent
3. 03The sum: growth plus margin, read against the 40 line

It reconciles the growth-versus-profitability tension in a single figure that maps to valuation multiples. When a board pushes on efficiency, this is the number the conversation orbits.

A go-or-no-go efficiency ratio measuring how much net new ARR each dollar of prior-period sales and marketing produced.

WhenA fast quarterly test before adding GTM spend or headcount. It answers whether the growth engine is efficient enough to feed more fuel.

The framework
1. 01Numerator: net new ARR in the quarter, annualized
2. 02Denominator: the prior quarter sales and marketing spend
3. 03The read: above 0.75 scale, above 1.0 strong, below 0.5 fix the model

It is the cleanest quarterly signal of whether your acquisition motion scales or saturates. A falling magic number is the early warning that the next dollar of growth is buying itself at a loss.

The ratio of a customer lifetime value to the fully-loaded cost of acquiring them, the headline unit-economics check.

WhenWhen deciding whether a segment, channel, or motion is worth investing in, and when defending GTM spend to finance. Pair it with CAC payback, which tells you when the cash comes back.

The framework
1. 01LTV: average revenue per account times gross margin, divided by churn
2. 02CAC: fully-loaded sales and marketing to acquire, per new customer
3. 03The ratio: 3:1 is the accepted target
4. 04CAC payback: CAC / (ARPA x gross margin) x 12, in months

It is the single ratio that says whether the business model works at the unit level. But it hides timing, which is why capital-efficiency conversations pair it with CAC payback and the burn multiple.

A top-down revenue model that builds the number from the operational drivers that produce it (leads, conversion rates, deal size, cycle time) instead of a growth percentage typed into a cell.

WhenAt annual planning and whenever the target changes mid-year. It is how you turn grow 40% into a chain of assumptions each team owns and can be held to.

The framework
1. 01Name the drivers: leads, MQL-to-SQL, win rate, ACV, cycle length, ramp
2. 02Chain them: drivers multiply forward into pipeline, then bookings
3. 03Assign ownership: each driver has a team accountable for its assumption
4. 04Stress-test: flex the weakest driver and watch the number move
5. 05Reconcile top-down against bottoms-up capacity

A percentage-growth plan cannot tell you which lever to pull when you are behind. A driver-based plan can, because it exposes exactly which assumption broke and who owns fixing it.

A staged ladder describing how a revenue operations function evolves from reactive firefighting to a predictive, governed system that owns the number.

WhenTo locate your team honestly, sequence investment, and set expectations with leadership about what the function can deliver at its current stage. Do not skip rungs.

The framework
1. 01Reactive: ad hoc requests, spreadsheets, no single source of truth
2. 02Foundational: clean CRM object model, defined stages, basic reporting
3. 03Defined: standardized processes, stage gates, documented definitions, SLAs
4. 04Predictive: driver-based planning, calibrated forecasting, health scoring
5. 05Optimized: closed-loop, governed automation, RevOps owns cross-functional strategy

It stops teams from buying Predictive capabilities on a Foundational base, which is the most common way RevOps budgets get wasted. It also gives leadership a shared language for why the forecast is not trustworthy yet.

A bottoms-up model that derives how much a team can actually produce from headcount, ramp state, and productivity, then sets quota so the sum of quotas can clear the target with slack.

WhenBefore setting quotas, before a hiring plan, and any time attainment craters (which usually means the quota was wrong, not the reps). It is the reality check on a top-down number.

The framework
1. 01Count heads by ramp state, not just headcount
2. 02Apply ramp-adjusted productivity per rep
3. 03Sum to real team capacity, the honest ceiling
4. 04Set quota coverage 1.15 to 1.25x the target for slack

Most quota misses are planning failures dressed as performance failures. When 76% of reps miss, recalibrate the model, do not PIP the room. Capacity is the honest ceiling; quota should be set against it, not against a board wish.

The systematic carving of accounts into balanced, equitable books so that opportunity, not luck of the draw, drives attainment.

WhenAt annual planning, after a segmentation change, or when reps openly complain their territory cannot support quota. Redesign is disruptive, so do it deliberately, not reactively.

The framework
1. 01Define the unit: geography, segment, named accounts, or vertical
2. 02Score account potential: fit, whitespace, existing ARR, propensity
3. 03Balance the books: equalize total opportunity, not just account count
4. 04Assign against capacity: match book size to rep ramp and coverage
5. 05Set rules of engagement: ownership, splits, and inbound routing

Territory imbalance is an invisible attainment tax: a rep in a thin book misses through no fault of their own while a rep in a rich one coasts. Fair design is the difference between a plan the team believes and a mutiny.

The two-part discipline behind a defensible forecast: a strict category taxonomy (Commit, Best Case, Pipeline, Omitted) that classifies every deal, and coverage math that sizes whether enough pipeline exists to hit at all.

WhenThe categories every week in the roll-up, and the coverage math at the start of every period as a capacity gate. Categories call the number; coverage checks the number is reachable.

The framework
1. 01Commit: economic buyer confirmed, process documented, close date in period, rep would bet on it
2. 02Best Case: real upside, close date in period, one gate still open
3. 03Pipeline: qualified but close date out of period or a gate unconfirmed
4. 04Omitted: no activity 21+ days or no confirmed buyer, flagged for triage
5. 05Coverage gate: open pipeline against 1/win-rate, checked in week 1 not week 10

A forecast is an output of inspection against enforced categories, not a number read off stage labels. Coverage tells you if hitting is even possible; categories tell you what will actually land. Elite teams hold under 5% variance by running both, weekly.