The lead lifecycle is where marketing and sales either align or go to war. When it works, leads flow smoothly from first touch to closed deal and everyone trusts the numbers. When it doesn't, sales complains about lead quality, marketing complains leads are ignored, and leadership gets three different answers to "how's the funnel?" Here's how to build one that holds.
What a lead lifecycle actually is
A lead lifecycle is the defined set of stages a person moves through from first contact to customer, plus the rules that govern movement between them. The stages are the easy part to draw on a whiteboard. The hard part — and the part that determines whether anyone trusts it — is agreeing what each stage means and what triggers the move to the next.
The standard stages
Most B2B lifecycles use some version of this progression. You don't need to copy it exactly, but you do need shared names.
- Subscriber / Lead: a known contact who hasn't shown buying intent.
- Marketing Qualified Lead (MQL): a lead whose behaviour and fit meet an agreed bar worth sales' attention.
- Sales Accepted Lead (SAL): an MQL that sales has agreed to work — the accountability checkpoint that prevents leads vanishing into a black hole.
- Sales Qualified Lead (SQL): a lead sales has actively qualified as a real opportunity.
- Opportunity / Customer: the deal and, ultimately, the close.
Why trust breaks down
Undefined stages
If "MQL" means different things to marketing and sales, every downstream number is contested. Most lifecycle dysfunction traces back to fuzzy definitions, not bad tools.
No accountability handoff
Without an explicit "accepted" step, marketing throws leads over the wall and sales quietly ignores the ones it doesn't like — with no record of what happened. The SAL stage exists precisely to close that gap.
No feedback loop
If sales can't easily tell marketing why a lead was rejected, marketing never improves its targeting, and the quality complaints become permanent.
How to design one that holds
Define every stage jointly
Get marketing and sales in a room and agree, in writing, the exact entry and exit criteria for each stage. This is a negotiation, not a marketing decision handed down. The shared definition is the entire foundation — everything technical comes after.
Build qualification on fit and behaviour
An MQL should reflect both who the lead is (fit — role, company, industry) and what they've done (behaviour — engagement, intent signals). Lead scoring is the usual mechanism, but validate the model against real conversion data rather than guessing weights.
Make the handoff explicit and accountable
When a lead becomes an MQL, route it with a clear owner and an SLA — a defined time by which sales must act. The acceptance step creates a paper trail and ends the "marketing says they sent it, sales says they never got it" argument.
Close the feedback loop
Give sales a fast, low-friction way to mark why a lead was rejected, and feed that back into scoring and targeting. A lifecycle that learns is a lifecycle people trust.
Encoding it in your tools
Only once the definitions are agreed should you build. Map the stages to lifecycle fields in your CRM and automation platform, build the routing and SLA logic, and make lifecycle stage move forward automatically on the agreed triggers — never backward by accident. Keep the technical implementation a faithful translation of the agreement; resist the temptation to let the tool's defaults define your process.
Reporting that both teams believe
The payoff of shared definitions is shared reporting. A funnel that uses the agreed stages, shows conversion between them, and surfaces where leads stall gives both teams one version of the truth. When marketing and sales argue about a number, the fix is almost always a definition, not a dashboard.
Keep it alive
A lifecycle isn't a one-time project. Revisit the definitions quarterly, adjust scoring as you learn, and treat the alignment between teams as an ongoing relationship rather than a settled contract.
Common lifecycle anti-patterns
Lifecycle stages that move backward by accident
A frequent bug: a record's lifecycle stage regresses because an automation or import overwrites it. If a customer suddenly shows up as a "lead" again, every funnel report is corrupted. Build your automation so stages only ever move forward, and guard against imports that reset them.
Scoring that nobody validated
Teams often invent point values out of thin air — 10 points for a whitepaper, 5 for a page view — and never check them against who actually converts. A scoring model that isn't validated against real outcomes is just a guess dressed up as rigour. Revisit it with conversion data and adjust.
An MQL definition that's really just "filled out a form"
If anyone who downloads anything becomes an MQL, sales learns to ignore MQLs entirely and the whole stage loses meaning. A real MQL bar combines fit and meaningful behaviour, not a single low-intent action.
Measuring whether the lifecycle is healthy
A well-run lifecycle gives you diagnostic signals, not just a tidy diagram. Watch the conversion rate between each stage, the time leads spend in each stage, and the rate at which sales accepts versus rejects MQLs. A sudden drop in MQL-to-accepted rate is an early warning that targeting has drifted or the definition has quietly broken. Treat these metrics as the dashboard for the relationship between marketing and sales — when they move, something in the process needs attention.
This kind of lifecycle design is core to senior Marketing Ops and RevOps roles. Browse current openings and you'll see lifecycle and lead-management ownership called out again and again.