Built for RevOps teams who need lead evaluation to actually drive the motion
A sales lead evaluation framework is only useful when it drives the next action automatically.
BANT, MEDDIC, GPCTBA/C&I, FAINT, ANUM: five frameworks, same purpose, different fit for different motions. The question is not which framework is best; it is which one your CRM can enforce without turning into a tribal checklist nobody fills out. Below are the five frameworks compared and the Strkr workflows that make each one operational.
A sales team adopts a lead evaluation framework at an off-site, documents it in a Google Doc, trains the reps once, and then nothing changes operationally because the framework lives in tribal memory rather than in the CRM. Below are six places lead evaluation frameworks typically fail in production, and the Strkr workflows that make each framework drive the next action rather than sit in a doc nobody reads.
The framework lives in a Google Doc
The off-site training was 11 months ago.
Most lead evaluation frameworks fail in production for the same reason: they live in a training deck and a Google Doc rather than in the CRM. Reps know BANT exists; they do not fill in the specific fields on the opportunity record. The framework becomes a vibe check rather than a qualification artifact. Strkr enforces framework fields at stage exit criteria so a deal cannot progress without the qualification evidence present.
Framework fits one segment but not another
BANT works for SMB, breaks for enterprise.
BANT (Budget, Authority, Need, Timeline) works for transactional SMB deals but breaks for enterprise where authority is distributed across 4 to 12 stakeholders and budget is often formed during the sales cycle rather than before. The common failure is applying one framework across all segments. Strkr supports per-segment framework assignment: BANT on SMB opportunities, MEDDIC on mid-market and enterprise, GPCTBA/C&I on strategic accounts.
Framework fields never enforced
Deals in commit without documented pain, budget, or champion.
Most CRMs allow free-form stage transitions regardless of framework completeness. A deal moves to "commit" with no documented economic buyer, no pain articulation, and no budget confirmation. Forecast collapses in the final week because the deals were never actually qualified. Strkr's stage exit criteria enforce framework fields: a deal cannot sit in "qualified" without the required MEDDIC or BANT fields completed.
Framework scoring not reflected in routing
High-BANT leads route to the same SDR as low-BANT.
When framework data lives on the opportunity but routing fires on firmographic criteria only, high-qualification leads do not get the right routing. Strkr's scoring and routing use framework fields: a lead with high BANT score (confirmed budget, authority, timeline) routes to the AE directly rather than through SDR triage, which cuts cycle time on hot inbound.
Framework fatigue
Reps fill in fields to pass the gate, not to qualify the deal.
When framework fields become bureaucratic checkpoints, reps fill them in to pass the gate rather than to qualify the deal. "Economic buyer: TBD," "Budget: unknown," "Pain: process improvement" become default values that pass validation without producing qualification evidence. Strkr's AI-assisted qualification flags obvious framework filler and prompts the rep for substantive detail, which keeps the framework honest.
Framework data drives no reporting
The win-loss analysis ignores framework fields.
When framework data lives on the opportunity but reporting runs on stage and amount only, the framework never produces operational learning. Strkr's win-loss analysis cross-tabs framework completeness against win rate: deals with fully documented MEDDIC fields close at X percent, deals missing economic buyer close at Y percent, which is the specific evidence that justifies the discipline.
The five frameworks compared
What each one is for and when to use it.
The five most-used lead evaluation frameworks each have a specific motion fit. The cards below are the specific framework definitions, the motion fit, the fields they enforce, and the Strkr implementation for each.
BANT
Budget, Authority, Need, Timeline.
BANT (coined by IBM in the 1960s) covers Budget (does the buyer have budget allocated), Authority (is the contact the decision-maker), Need (is there a specific pain to solve), Timeline (when does the buyer need the solution). Fits transactional SMB deals with single decision-makers. Breaks for enterprise where authority is distributed. Strkr's BANT template enforces the four fields at the "qualified" stage with picklists for each.
MEDDIC (originated at PTC in the 1990s) covers Metrics (what quantified impact the buyer expects), Economic buyer (who has the signature authority), Decision criteria (what the buyer is evaluating against), Decision process (how the buying decision gets made), Identify pain (what specific pain the solution addresses), Champion (who is advocating internally). Fits enterprise sales with distributed authority. Strkr's MEDDIC template enforces all six fields at stage exit, with the economic buyer field tracking the Strkr stakeholder role tag.
MEDDPICC
MEDDIC + Paper process + Competition.
MEDDPICC extends MEDDIC with Paper process (procurement, legal, security review) and Competition (who else the buyer is evaluating). Fits late-stage enterprise motions where procurement risk and competitive dynamics drive outcome. Strkr's MEDDPICC template enforces all eight fields and surfaces competition tracking on the opportunity record with per-competitor positioning notes.
GPCTBA/C&I (HubSpot's discovery framework) covers Goals (what the buyer wants to achieve), Plans (what they have in place to get there), Challenges (what is blocking them), Timeline, Budget, Authority, Consequences (what happens if they do not solve the problem), Implications (what the positive impact of solving would be). Fits consultative mid-market and SaaS motions. Strkr's GPCTBA/C&I template enforces the eight fields with free-text qualification evidence.
FAINT
Funds, Authority, Interest, Need, Timing.
FAINT replaces BANT's "Budget" with "Funds" (the buyer has money available even if not budgeted for this specific use) and adds "Interest" as a leading indicator of fit. Fits motions where the buyer may not have pre-allocated budget but has the authority to acquire it. Strkr's FAINT template distinguishes allocated budget from available funds, which is a meaningful distinction in mid-market where budget often gets created to acquire the right solution.
ANUM
Authority, Need, Urgency, Money.
ANUM reorders BANT to lead with Authority (because speaking to the wrong person wastes the rest of the discovery). Fits inside sales motions where cycle length is short and the rep needs to qualify authority first. Strkr's ANUM template prompts the authority check in the first conversation and gates further qualification on authority confirmation.
CHAMP
Challenges, Authority, Money, Prioritization.
CHAMP leads with Challenges (identify the pain first), then Authority, Money, and Prioritization (whether the specific pain is a priority relative to other initiatives). Fits consultative motions where leading with discovery questions produces better qualification than leading with budget questions. Strkr's CHAMP template builds pain articulation into the opportunity record with free-text evidence from discovery calls.
Framework hybrids
Combine qualification layers for mixed-segment teams.
Many teams run framework hybrids: BANT for SMB, MEDDIC for mid-market, MEDDPICC for enterprise strategic accounts. Strkr supports per-segment framework assignment with the right template firing based on the account segmentation. The common pattern of "one framework for everyone" produces either over-qualification on SMB or under-qualification on enterprise; the segmented approach fits the motion to the segment.
Framework-driven routing and scoring
Qualification evidence feeds the scoring model.
Lead scoring in Strkr weights framework fields: completeness of BANT or MEDDIC, specific pain articulation, economic buyer identified, procurement engaged. Deals with higher framework completeness score higher and route to the right rep automatically. The framework stops being a bureaucratic checkpoint and starts being a signal that drives the next action.
How Strkr enforces framework discipline without framework fatigue
The structural ways to make the framework operational.
The failure mode of lead evaluation frameworks is almost always fatigue: reps fill in the fields to pass the gate rather than to qualify the deal. The cards below are the specific Strkr surfaces that make the framework honest without turning qualification into bureaucratic theater.
Stage exit criteria
The deal cannot progress without the framework evidence.
Every stage carries exit criteria specific to the framework: discovery requires documented pain and need, qualified requires economic buyer and budget confirmation, proposal requires decision process and timeline. A deal with incomplete fields cannot advance. The alternative (free-form stage picklist) produces deals in commit without qualification, which is where the forecast collapses in the final week.
AI-assisted qualification
Strkr AI flags obvious framework filler.
When a rep fills a field with filler ("Economic buyer: TBD," "Pain: process improvement," "Budget: unknown"), Strkr AI flags the entry as low-quality and prompts for substantive detail. The AI reviews the discovery call transcript (via Gong, Chorus, or Fathom integration) and suggests specific detail that was actually mentioned on the call but did not land on the record.
Per-segment framework assignment
The right framework fires for the right segment.
The segmentation rule drives framework assignment: SMB opportunities get BANT, mid-market get MEDDIC, enterprise get MEDDPICC. The reps see the right template for the deal they are working, which keeps the framework fit to the motion. The common pattern of "one framework for all" produces either SMB over-qualification or enterprise under-qualification.
Discovery-call transcription
Qualification evidence lives on the call recording.
When calls record and transcribe (via Gong, Chorus, Fathom integration), Strkr auto-extracts qualification evidence from the transcript: pain mentions, budget references, authority signals, timeline statements. The rep reviews and confirms the extracted evidence rather than typing it from memory, which lifts the quality floor on qualification data.
Framework completeness scoring
The lead score weights framework completeness.
Lead scoring in Strkr weights framework completeness alongside firmographic fit and engagement. A deal with full MEDDIC fields completed scores higher than a deal with partial MEDDIC regardless of firmographic match. The scoring drives routing and prioritization, so the framework completeness has operational consequence.
Framework-driven reporting
Win-loss analysis cross-tabs framework data.
The win-loss report cross-tabs framework completeness against outcomes: deals with fully documented MEDDIC close at X percent, deals missing economic buyer close at Y percent, deals missing identified pain close at Z percent. The specific numbers justify the discipline and surface where qualification is weakest, which drives coaching focus.
How teams actually run lead evaluation frameworks on Strkr
The specific motions on customer accounts.
A framework becomes operational when the sales team runs on it daily rather than referencing it quarterly. The cards below are the specific rituals that produce clean framework discipline on customer accounts today.
Discovery call framework fill
The rep completes the framework fields during the call.
During the discovery call, the rep opens the opportunity record with the framework fields visible and fills them in real-time rather than from memory after. Strkr AI (via Gong or Chorus transcript integration) suggests specific evidence from the call. The rep confirms or edits, and the qualification evidence lands on the record with the call recording linked.
Weekly pipeline review on framework gaps
The manager coaches on the specific missing field.
In weekly pipeline review, the manager sees framework completeness per deal and coaches on the specific missing field: "You have the champion but no economic buyer identified on Deal X, let's talk about multi-threading this week." The coaching conversation runs on evidence rather than generic advice.
Stage advancement review
Deals that fail exit criteria get held.
When a rep tries to advance a deal to the next stage, the exit criteria validation runs: a deal moving to "qualified" without economic buyer and documented pain gets held with a note explaining what is missing. The rep either completes the qualification or acknowledges the deal is not actually ready to advance.
Framework effectiveness review
Quarterly check on whether the framework is driving outcomes.
Every quarter, the ops lead runs a framework effectiveness review: do deals with higher framework completeness close at better rates, which fields correlate most with win rate, which fields are most often incomplete. The review drives framework evolution: adding fields that matter, dropping fields that produce fatigue without signal.
Framework hybrid tuning
The per-segment assignment evolves with the data.
The per-segment framework assignment gets tuned over time based on segment-specific win rates. If MEDDIC on mid-market is producing better outcomes than BANT on mid-market, the assignment shifts. The framework assignment is a parameter the ops lead tunes rather than a fixed design decision.
New-rep onboarding on framework
The system teaches the framework rather than the training deck.
When a new rep joins, the Strkr workflow surfaces framework prompts on every opportunity: "This deal needs economic buyer, click to add," "Pain not documented, suggest reviewing call transcript." The system teaches the framework through daily use rather than relying on an off-site training deck the new rep attended once.
Head-to-head
Strkr framework enforcement vs the generic CRM framework field.
Most CRMs ship a "qualification" tab with free-form fields for framework data. The gap between a free-form tab and operational framework enforcement is the gap between training-deck adoption and daily workflow. Head-to-head on the surfaces that matter.
How teams actually operationalize framework discipline.
The pattern across teams that make a framework operational: enforcement at stage exit, AI-assisted qualification, and framework-driven reporting. The playbooks below are three motions live on customer accounts right now with the specific framework and outcome.
Enterprise sales floor, 60 reps on MEDDPICC
Framework enforcement at stage exit cut forecast error 40 percent.
A 60-rep enterprise sales floor had been running MEDDIC for 3 years with no operational enforcement. Fields were on the record but reps filled them in to pass stage gates with minimal detail. The team moved to Strkr with MEDDPICC enforcement at stage exit: deals could not advance to "qualified" without documented metrics, economic buyer, decision criteria, decision process, identified pain, champion, paper process, and competition. Forecast error (gap between week-four commit and quarter actual) dropped from 32 percent to 19 percent over two quarters because the deals in commit actually had qualification evidence.
Mid-market SaaS, 22 AEs on MEDDIC + call transcript extraction
Qualification completeness climbed 60 percent after AI assist.
A 22-AE mid-market team ran MEDDIC with manual qualification entry. Framework completeness audits showed roughly 55 percent of deals had partial MEDDIC entries (3 or 4 of 6 fields filled with substantive content). The team integrated Gong for call transcription and enabled Strkr AI qualification extraction: the AI reviewed call transcripts and suggested specific evidence for each MEDDIC field. Framework completeness climbed to 88 percent over two quarters because the AI did the extraction work the rep had been skipping.
SMB inside sales, 14 reps on ANUM
Authority-first qualification cut cycle time 18 percent.
A 14-rep SMB inside sales team ran BANT for 2 years with a pattern of late-stage discovery that someone else was the real decision-maker. The team moved to ANUM (Authority first) with Strkr enforcement: the first discovery call required authority confirmation before the opportunity could advance. Deals where the initial contact was not the authority got routed to multi-threading motion. Cycle time dropped 18 percent because the reps stopped burning time qualifying buyers who could not sign.
B2B SaaS, 18 AEs on hybrid BANT/MEDDIC
Per-segment framework assignment improved SMB and enterprise simultaneously.
An 18-AE B2B SaaS team ran MEDDIC for all deals, which produced over-qualification on SMB (reps spent 30 minutes qualifying 10k deals) and about-right qualification on mid-market. The team moved to per-segment assignment: BANT on SMB opportunities, MEDDIC on mid-market and above. SMB cycle time dropped 22 percent because the qualification matched the deal complexity. Mid-market close rates improved 7 points because MEDDIC fields were enforced rather than optional.
Healthcare SaaS with HIPAA sensitivity
Framework audit trail supported SOC 2 and HIPAA compliance.
A healthcare SaaS team required a documented qualification audit trail for both SOC 2 Type II compliance and HIPAA BAA accountability. The team moved to Strkr with MEDDIC enforcement, call-transcript extraction, and the framework audit log retained on every opportunity. The audit evidence (what was qualified, when, by whom, with what evidence) satisfied both compliance requirements without additional engineering, which replaced a custom audit-log layer that had added 8,000 lines of code to maintain.
Framework discipline that actually drives revenue.
Start a 14-day trial with BANT, MEDDIC, MEDDPICC templates, stage-exit enforcement, call-transcript extraction, and framework-driven reporting on every pipeline. Compare the qualification discipline to your current motion.
There is no single best framework; the right one depends on the motion. BANT fits transactional SMB with single decision-makers. MEDDIC and MEDDPICC fit enterprise sales with distributed authority. GPCTBA/C&I fits consultative mid-market where discovery depth matters. FAINT fits motions where budget forms during the cycle rather than before. ANUM fits inside sales where cycle length is short and authority must be qualified first. The useful discipline is to pick the framework that matches the segment and enforce it at stage exit; running the wrong framework for the segment produces either over-qualification (fatigue) or under-qualification (bad forecast).
How is MEDDIC different from BANT?
BANT (Budget, Authority, Need, Timeline) is a four-field qualification focused on transactional readiness. MEDDIC (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion) is a six-field qualification focused on complex enterprise motion. The specific differences: MEDDIC requires quantified metrics (what business impact the buyer expects), decision process (how the buying decision gets made across stakeholders), and a named champion (who advocates internally); BANT does not. For single-decision-maker SMB deals, BANT is sufficient and MEDDIC produces fatigue. For enterprise deals with 4 to 12 stakeholders, MEDDIC captures the complexity BANT misses.
Can I use multiple frameworks for different parts of my sales motion?
Yes, and most mature teams do. Strkr supports per-segment framework assignment: BANT on SMB opportunities, MEDDIC on mid-market, MEDDPICC on enterprise strategic accounts. The segmentation rule drives the framework assignment, and the right template fires based on the deal segment. The common failure pattern of "one framework for everyone" produces either SMB over-qualification or enterprise under-qualification; per-segment assignment matches the qualification depth to the deal complexity.
How do you enforce a lead evaluation framework in the CRM?
Three ways: enforce at stage exit (a deal cannot advance without the required framework fields completed with substantive content), weight framework completeness in lead scoring (deals with higher completeness get higher priority routing), and run win-loss analysis cross-tabbed against framework data (so the ops team sees which fields correlate with outcomes). Strkr ships all three. The failure pattern in most CRMs is making framework fields free-form optional, which produces 20 to 40 percent completeness and no operational consequence. Enforcement at stage exit is the single highest-leverage move.
Does Strkr AI help with lead qualification?
Yes. Strkr AI reviews call transcripts (from Gong, Chorus, Fathom, or native Strkr recording) and extracts qualification evidence for each framework field: pain mentions, budget references, authority signals, timeline statements, metric commitments. The rep reviews and confirms the extracted evidence rather than typing from memory. Strkr AI also flags obvious filler ("Economic buyer: TBD," "Pain: process improvement") and prompts the rep for substantive detail. The AI lifts the floor on qualification quality by about 30 to 50 percent based on customer data, and the specific labeled surface in the UI is Strkr AI (vendor model routing happens behind the scenes to manage cost).
Should sales qualification run on the first call or across multiple calls?
Depends on the motion. SMB inside sales typically qualifies in the first call because cycle length is short and the discovery conversation is efficient. Mid-market and enterprise sales qualify across multiple calls because the stakeholder count is higher and the discovery depth takes more time to establish. The useful discipline is to set a framework completeness target per stage (discovery requires N fields, qualified requires M fields, proposal requires all fields) and run the qualification over the right number of touches for the segment. Strkr's stage-exit criteria handle this per segment with per-stage framework requirements.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
