Lead lifecycle

Lead Lifecycle Stages That Your Sales Team Will Actually Trust

Five stages, with the entry criteria, the exit criteria and the owner for each. This is the lead lifecycle model we build and run inside our clients' systems, not a diagram.
Rated 4.9 / 5 on G2. We run GTM systems for Mistral AI, Chainguard, AssemblyAI, Clio, factory.ai, Anrok and Integrate.io.
Cameron Legge, Chief Customer Officer at LeanScale, smiling in a black and white portrait

What is the lead lifecycle?

The lead lifecycle is the ordered set of stages a potential buyer passes through at the top of your funnel, from the first time you know they exist to the moment sales accepts them as a real opportunity. Each stage is a statement about one thing: how much qualification this person has passed, and therefore who should be working them.

One boundary, stated up front, because it is the most common source of muddle. The lifecycle answers “where is this person in the funnel, and what moves them forward”. It does not answer “where did this person come from”: that is a question about provenance, and we handle it separately on our lead source and attribution page. Keeping the two models apart is what stops both of them from becoming unusable. A lifecycle stage that encodes a channel is a lifecycle stage you cannot report on.

The other boundary is the far end. The lifecycle ends when an opportunity is created. Everything after that, stage weighting, pipeline coverage, forecast and capacity, is a different model with different owners.

Why your lifecycle model stopped working

Almost every B2B SaaS company has a lifecycle model. Far fewer have one anybody trusts. The failure is rarely the stage names, and that is why renaming them never fixes it.

It fails because the criteria are prose, not logic. “Shows buying intent” is a sentence a human can agree with and a system cannot enforce. So two people apply it differently, the stage stops meaning one thing, and every report built on it inherits the ambiguity.

It fails because the handoff crosses an ownership boundary. Marketing owns the early stages, sales owns the later ones, and the stage in between belongs to whoever is in the room. When leads go missing in that gap, both sides can prove it was not their fault, which is the clearest sign nobody owns it.

And it fails because it only moves forward. Real buyers go quiet, come back in two quarters, change jobs and reappear at a new company. A model with no route backwards forces your team to choose between lying to the system and ignoring it. They will ignore it.

The five lead lifecycle stages

This is the model we implement. Five stages, because every stage you add is another definition two teams have to agree on, and the generic eight-stage and nine-stage lists in circulation add stages most companies cannot police. The plain definitions of each stage are in our lifecycle documentation.

Stage Entry criteria Owner Exit
Anonymous Visitor Known device or account-level signal, no identified person Marketing Operations A person is identified
Lead An identified person with a name and a work email Marketing Operations Meets MQL criteria, or is disqualified
MQL Meets the agreed fit threshold and has taken a qualifying action Marketing Operations Sales accepts or rejects, within the agreed SLA
SAL A named rep has accepted the lead and owns the follow-up Revenue Operations, with sales as business owner Qualified to SQL, recycled, or disqualified
SQL Sales has confirmed fit and active buying intent Revenue Operations, with sales as business owner Opportunity created, lifecycle ends
  • 01

    Anonymous Visitor

    Someone is engaging and you do not yet know who. Account-level signal without an identified person. This stage exists for one reason: so that engagement data has somewhere to live before a form fill, rather than being discarded or incorrectly attached to a person who has not identified themselves.

  • 02

    Lead

    A real person with a name and a work email. Nothing more is implied. The most common mistake here is loading this stage with qualification it should not carry: a Lead is not a judgment, it is a fact.

  • 03

    MQL (Marketing Qualified Lead)

    Marketing has checked this person against the agreed criteria and is asserting they are worth a rep's time. Two conditions, both required: a fit threshold (does this person match the ICP) and a behavioural trigger (have they done something that indicates interest). Fit without behaviour is a list. Behaviour without fit is a student downloading your whitepaper.

  • 04

    SAL (Sales Accepted Lead)

    A named rep has looked at the lead and accepted it. This is the stage most companies skip, and skipping it is why their MQL number is disputed. Without an acceptance step, marketing reports leads delivered and sales reports leads worth having, the two numbers never match, and there is no record of which specific leads were rejected or why. SAL turns a quarterly argument into a weekly data set.

  • 05

    SQL (Sales Qualified Lead)

    The rep has had a real conversation and confirmed both fit and active buying intent. An opportunity is created and the lifecycle hands over.

Lifecycle stage is not lead status

These two fields get conflated in most implementations and the resulting mess is hard to unpick, so it is worth being precise.

  • Lifecycle stage

    Lifecycle stage is how far through qualification someone is. It is coarse, it has a defined order, and in normal operation it moves one way. It is the field you report the funnel on.

  • Lead status

    Lead status is what is happening right now. Attempting contact, connected, nurturing, on hold. It is finer-grained, it changes often, it has no fixed order, and it is the field a rep actually works from.

You need both. When you collapse them into one field, you get a funnel report that changes every time a rep logs a call, and a work queue that cannot tell you who to call next. If your current model has a single field doing both jobs, splitting it is usually the highest-value hour of work available.

What happens when a lead goes backwards

A model that only moves forward does not survive contact with real buyers. Three cases need an explicit route.

  • 01

    Rejected at SAL

    A rep declines the lead. It needs a reason code from a short fixed list, and it needs to go somewhere: back to nurture, or to disqualified. The reason codes are the point. After a quarter of them, you know precisely which part of your MQL definition is wrong, which is a conversation you cannot otherwise have with evidence.

  • 02

    Recycled

    Fit is right, timing is not. The lead returns to nurture with a re-entry condition and a date. These are frequently the best leads in the database and they are the ones most often lost, because "not now" and "not ever" end up in the same bucket.

  • 03

    Disqualified

    Genuinely not a fit. Keep the record, keep the reason, and suppress it from qualification rather than deleting it, so that the same person arriving from a new company next year is a new opportunity rather than a duplicate.

Implementing a lead lifecycle in Salesforce or HubSpot

A model is a document until it is enforced. Five things have to be true in the system.

  1. One authoritative field for lifecycle stage, on one object, in one system. If both your CRM and your marketing automation platform can write it, decide which one wins and enforce it.
  2. Entry criteria expressed as rules, not as a definition in a wiki. If a criterion cannot be written as a rule, it is not a criterion yet.
  3. A routing rule per transition. When a lead becomes an MQL, it should arrive with a named owner within a defined window, with escalation when that window is missed. Assignment, territory and round-robin logic all live here.
  4. A timestamp on every stage transition. Without these you cannot see stage velocity or the conversion rate between stages, which means you cannot tell whether a change you made helped.
  5. Alerting on leads that stop moving. A lead sitting in MQL past the SLA should generate an alert, not wait for someone to notice it in a report.

The mapping between your marketing automation platform and your CRM is where most of this breaks. Get the direction and the conflict rules explicit for every lifecycle field, and the rest of it holds.

That mapping is one part of your GTM tech stack, and the lifecycle model is one part of your wider GTM architecture.

We build and run this inside client systems as part of our Revenue Operations and Marketing Operations practices. Run a GTM Diagnostic.

Who owns each stage

The handoff is the part that fails, so it needs the clearest ownership.

Marketing Operations owns Anonymous Visitor, Lead and MQL: the stage definitions, the fit threshold, the behavioural triggers and the data quality of everything entering the funnel.

Revenue Operations owns SAL and SQL, with sales leadership as the business owner: acceptance, the SLA, routing, and the point of opportunity creation.

The MQL to SAL transition itself needs one named owner, not shared custody. Our recommendation is that Revenue Operations owns the transition, because RevOps owns the system of record where acceptance is recorded, while the fit and trigger criteria stay with Marketing Operations. One person owns the pipe, one person owns what goes into it.

Whatever you choose, write it down and put a name against it. “Both teams own it” is the condition you are trying to escape.

We design the lifecycle, then we run it

Most teams do not need a better diagram. They need someone to build the model, configure it, fix the three integrations it depends on and keep it honest after the first month.

That is what we do. LeanScale is an embedded GTM Ops team: a pod from our Revenue Operations and Marketing Operations practices works inside your systems, with your team. For a lifecycle engagement that usually means a diagnostic of the current model, a rebuilt stage model with configurable criteria and named owners, the routing and SLA logic to enforce it, the reporting layer on top, and ongoing ownership of all of it. See how our RevOps practice works. If you are on Salesforce, we can also run your Salesforce org day to day.

It runs as a 90-day rolling subscription. Projects move on 4 to 12 week cycles, ad hoc support is uncapped with a same-day SLA, and there is no multi-year contract.

Run A GTM Diagnostic

Teams we do this for

Rated 4.9 / 5 on G2 by the teams we operate with. We work with teams backed by Lightspeed, a16z, General Catalyst, Insight Partners, Bessemer, Updata and Sapphire. See how this has worked for other B2B SaaS teams.

Selected customers

  • Mistral AI
  • Chainguard
  • AssemblyAI
  • Clio
  • Fountain
  • RunPod
  • Factory.ai
  • Ocrolus
  • Anrok
  • Act-On
  • GreyNoise
  • Integrate.io
  • CallRail
  • Patlytics
  • SpyCloud
  • Scandit
  • Coactive
  • wealth.com
  • OpenArt
  • OnBoard
  • CUSTOMER REVIEW · G2

    MANAGER, REVOPS

    “They combine strategic RevOps thinking with hands-on execution, not just high-level recommendations. They help us actually design, document, and implement the systems we need.”
    Nicholas B., via G2
  • CUSTOMER QUOTE

    CEO, INTEGRATE.IO

    “LeanScale provided the playbook and technical expertise to get us up and running in 60 days. We were impressed by the speed, but even more impressed by how smooth and thorough the process was.”
    Donal Tobin

FAQ

Lead lifecycle questions, answered

  1. What are the lead lifecycle stages?

    We use five: Anonymous Visitor, Lead, MQL, SAL and SQL. Each one has entry criteria you can configure in the CRM and a single named owner. Longer lists exist, including HubSpot's eight-stage default, but most companies cannot police more than five definitions consistently.

  2. What is the difference between an MQL and an SQL?

    An MQL is marketing asserting that someone matches the ICP and has taken a qualifying action. An SQL is a rep confirming, after a real conversation, that the person is a fit and is actively buying. The acceptance step between them is SAL, and it is the step most teams skip.

  3. What is a SAL and do we need one?

    A Sales Accepted Lead is a lead a named rep has explicitly accepted and now owns. You need it if marketing and sales disagree about lead quality, which is almost everyone. Without it there is no record of which leads were rejected or why, so the disagreement never resolves.

  4. How is the lead lifecycle different from lead source?

    The lifecycle is where someone is in the funnel. Lead source is where they came from. They are separate models and separate fields, and mixing them produces reporting you cannot use.

  5. What is the difference between lifecycle stage and lead status?

    Lifecycle stage is how far through qualification someone is: coarse, ordered, slow-moving, and the field you report the funnel on. Lead status is what is happening right now: fine-grained, unordered, fast-moving, and the field a rep works from. You need both as separate fields.

  6. Can a lead move backwards through the lifecycle?

    Yes, and the model needs explicit routes for it: rejected at SAL with a reason code, recycled to nurture with a re-entry condition, or disqualified with the record retained. A model with no backwards route gets ignored by the people using it.

  7. How many lifecycle stages should we have?

    Five is the right number for most B2B SaaS companies. Every additional stage is another definition two teams have to agree on and keep agreeing on. Add a sixth only when you can name the specific decision it enables.

  8. Who should own the lead lifecycle?

    Marketing Operations owns the stages up to MQL. Revenue Operations owns acceptance onwards, with sales leadership as the business owner. The MQL to SAL transition needs one named owner, and we recommend RevOps, because RevOps owns the system where acceptance is recorded.

  9. What SLA should we set on MQL follow-up?

    Fast, and enforced, and we would rather scope the specific number with you than publish one here, because it depends on your motion and your inbound volume. What matters more than the number is that it is measured, alerted on and escalated when missed.

  10. Does this work in HubSpot as well as Salesforce?

    Yes. The model is platform-independent. What changes is where the authoritative field lives and how the sync between your marketing automation platform and your CRM is configured, which is usually where existing implementations have gone wrong.

  11. Where does the lead lifecycle end?

    At opportunity creation. Everything after that, stage weighting, pipeline coverage, forecasting and capacity, is a separate model covered on our pipeline and forecasting page.

  12. Can you fix a lifecycle model somebody else built?

    Yes, and that is how most of these engagements start. The diagnostic reads the current model, identifies which criteria are unenforceable and which transitions have no owner, and gives you a ranked list of what to change.

Get started

Get a lifecycle model your team will use

A GTM Diagnostic reads your current lifecycle model, shows you where leads are actually going missing and gives you a ranked list of fixes. Then you decide whether you want us to build it.

Powering startups backed by the biggest VCs in tech