Lifecycle Stage Definitions That Settle the MQL Argument

August 1, 2026

The dispute between marketing and sales about lead quality is not a relationship problem. It is two teams using different definitions of the same handoff, and it is resolved by writing the definition down.

Marketing reports a strong quarter for qualified leads. Sales reports an empty pipeline. Both are looking at the same records and both are telling the truth.

This is the most durable argument in B2B, and it is not about effort or good faith. It is definitional, and it persists because of a structural incentive rather than a personal failing.

The structural cause

Where marketing sets the qualification threshold and is measured on the volume clearing it, the threshold drifts downward — through the ordinary accumulation of edge cases, each of which seemed reasonable to include.

The fix is separation

Whoever is measured on the volume should not solely own the definition. Joint ownership with sales, or ownership by revenue operations, removes the drift mechanism rather than appealing to good faith.

Lifecycle is not the deal

Lifecycle stages describe a person; deal stages describe a transaction. Conflating them makes conversion reporting incoherent, because one contact can be associated with several deals and one deal with several contacts. Reporting that divides deal counts by contact counts across this boundary produces ratios with no meaning.

What a usable definition contains

The four components

A definition missing the fourth cannot self-correct, which is why most drift.

ComponentRequirementFailure without it
Entry criteriaObjectively verifiable, not inferredTwo people classify the same record differently
OwnerOne person accountable for movement into the stageDefinition drifts with no one answerable
Committed actionWhat the receiving team does, and within what timeLeads sit; the stage measures nothing
Rejection pathA route back with a required reason codeNo feedback loop; the definition cannot be corrected

Source: Components proposed here

Method: testing your definitions

  1. Take fifty recent records that crossed the threshold.

  2. Have one person from marketing and one from sales classify each independently against the written definition.

  3. Measure the disagreement rate. Above a small minority, the definition is ambiguous rather than contested.

  4. For every disagreement, record which criterion was read differently. Rewrite those criteria specifically.

  5. Add reason codes to the rejection path if absent, and review the reasons monthly — they are the correction mechanism.

  6. Re-run quarterly. Definitions drift, and the disagreement rate detects it earliest.

Expect the volume to fall

A tightened definition reduces reported lead volume. Agree in advance that this is the intended outcome, or the first month's report will be read as a marketing failure and the definition will be loosened again.

Where this fails

In account-based motions the contact is the wrong unit — qualification belongs at account level, and lifecycle stages on individuals become supporting detail rather than the primary funnel. Applying contact-level stage discipline to an account-based motion produces precise measurement of the wrong thing.

COMMON QUESTIONS

What are lifecycle stages?
The shared sequence describing a contact's relationship with the company over time. They describe a person, whereas deal stages describe a transaction — conflating them makes conversion reporting incoherent.
Why do marketing and sales disagree about lead quality?
Almost always because they use different definitions of the same handoff, not because either is wrong about the leads. The threshold is usually owned by the team measured on the volume clearing it, which causes drift.
What makes a lifecycle stage definition usable?
Entry criteria that can be objectively verified, a single owner responsible for movement into the stage, a committed action on receipt, and a rejection path with a reason code.
Should contacts be able to move backwards through lifecycle stages?
Decide explicitly and document it, because it materially changes conversion reporting. Allowing regression without a rule produces stage counts that cannot be reconciled period to period.

WHERE THIS HAS BEEN APPLIED

Client work and research from RevOps HQ, our consulting practice.

KEY TERMS

Go deeper: RevOps 101: Revenue Operations Foundations

The interactive tools behind this writing — process builders, inventories and the audit export — live inside the membership.

See the course