Revenue Execution
Qualification
The same lead should get the same decision, whoever takes it.
- Part of
- Revenue Execution
- Owned at
- Action layer
- Typical effort
- Ramp 3 weeks, then recurring
- Runs on
- HubSpot, Salesforce, Zoho, Odoo or Pipedrive
- Part of the discipline
- What is revenue operations
Why it breaks
The operating problem
Volume is not the problem. The problem is that qualification varies by person and by day. The same lead is qualified by one operator and disqualified by another, and not interested gets recorded with no reason behind it.
Self-check
Signs you need this
Qualification drift is the hardest problem to see, because every individual decision looks defensible on its own.
- Two operators reach opposite conclusions on similar leads.
- Not interested is your top outcome, with no detail behind it.
- Sales reject the leads they are handed.
- Discovery answers live in free-text notes.
- New operators take months to become consistent.
Page boundary
Where this capability ends
Lead Management defines the rules. Lead Routing assigns the lead. Qualification is the human or assisted execution of the decision.
Lead Management
Define lifecycle, ownership, prioritization, nurture and recycling rules.
Lead Routing
Assignment logic based on fit, intent, territory, language, offer or capacity.
Sales Pipeline
Design stages, evidence, progression rules and management cadence.
Concrete intervention
What Revops delivers
Qualification is made consistent through artefacts: a framework, a question set, a reason taxonomy and a scorecard people are coached against.
- ModelQualification framework and criteria
- DefinitionDiscovery question set per segment
- DefinitionDisqualification reason taxonomy
- DefinitionHandover package to sales
- MatrixCall quality scorecard
- RoutineOperator calibration routine
- DashboardQualification outcome dashboard
The reasoning model
How ROUTE applies
Here ROUTE is compressed into a single conversation, which is why the criteria have to exist before the call rather than after it.
Recognize
Take the lead the moment it is assigned.
Organize
Capture answers in structured fields, not in free-text notes.
Understand
Decide fit, need, timing and authority on written criteria.
Trigger
Accept, nurture, recycle or disqualify with a coded reason.
Execute
Hand over with context, and record the outcome.
The operating architecture
Revops OS mapping
Qualification runs in Action but depends entirely on Context. Without written criteria, judgement varies with the day and the person.
- 01
Data
Discovery answers stored as fields, outcome codes.
- 02
Context
The criteria that turn answers into a decision.
- 03
Workflows
Acceptance, recycling and disqualification routes.
- 04
Action primary layer
The qualification conversation itself.
- 05
Control
Sales acceptance rate, disqualification reasons, operator variance.
Outcomes
What changes
Variance between operators is the metric that matters. When it falls, everything downstream becomes predictable.
- One qualification standard applied by everyone.
- Every disqualification carries a coded reason.
- Handovers include structured context, not a note.
- Sales acceptance rate measurable per operator.
- New operators calibrated in weeks rather than months.
Questions
Frequently asked
Is BANT enough?
Can this be done by AI?
What happens to disqualified leads?
Next step
Where this gets repaired.
Qualification is scoped with lead management, because a standard without a lifecycle has nothing consistent to be applied to.
