Lead and Account Stage Definitions: The Operational Foundation of a High-Performance GTM Engine

Your CRO’s pipeline velocity data shows a 12% MQA-to-pipeline conversion rate. The demand model assumes 18%. The six-point gap has the same root cause in almost every case: the definition of when an MQA transitions to a booked meeting varies by rep, by SDR, and by whether the SDR manager updated the playbook last quarter. The stage exists in the CRM. The criteria for moving through it do not.

Across go-to-market deployments, the pattern is consistent: loosely defined stages produce conversion rate data that looks accurate in aggregate and is unreliable at the segment level. A 6% variance between what your demand model expects and what your CRM records is not a pipeline shortage. It is a measurement architecture problem.

Lative’s Marketing Intelligence module tracks stage transitions including the ones CRMs miss, the MQA that moved to a booked meeting without a stage date, the lead that skipped a stage because the rep never updated the record. It surfaces those gaps as a side effect of how it reads your funnel data, not as a separate audit you schedule once a quarter.

The two non-negotiables

First, lead stages must be defined with enough precision that every person in the organization, marketing, SDR, sales, RevOps, uses the same term to mean the same thing.

Terms like “Sales Accepted Lead” and “Sales Qualified Lead” sound specific but are routinely interpreted differently by different teams. If you ask three SDRs what “Sales Accepted” means, you will get three answers. That ambiguity corrupts every conversion rate you try to calculate.

Second, stage transition dates must be recorded as custom fields, not inferred from activity logs after the fact. A stage date is the timestamp of when the actual conversion occurred. Without it, velocity calculations break: average days in stage either becomes meaningless or inflated, and the pipeline acceleration signals that matter for weekly KPI tracking disappear into noise.

Aberdeen Group research found that organizations with aligned sales and marketing teams achieve 67% better efficiency at closing deals. That alignment starts at the stage definition layer: when marketing’s MQL and sales’ SAL mean different things, the conversion rate data that should inform alignment is corrupted before anyone runs an analysis.

Lead stage definitions

The following definitions reflect what works in practice across B2B SaaS go-to-market teams. The terms are intentionally self-explanatory: if a stage name requires a training document to define, it will be applied inconsistently. The seven stages:

• Registered Lead: A prospect who has completed a form or attended an event. No qualification yet.
• Marketing Qualified Lead (MQL): A lead that meets firmographic and behavioral criteria established by marketing and sales together.
• SDR Working: An MQL that an SDR has accepted and begun outreach on. The clock on SLA compliance starts here.
• Meeting Booked: A discovery call or demo has been scheduled. The lead has responded positively to outreach.
• Meeting Held: The meeting took place and was logged. Conversion to opportunity can now be assessed.
• Nurturing: A lead that did not qualify for active sales engagement but remains in a structured marketing sequence.
• Disqualified: A lead that has been reviewed and does not meet the criteria for further engagement. Logging this stage is as important as logging qualification.

Registered Lead

A prospect who has completed a form and been registered in the marketing automation system. This lead has not yet engaged sufficiently to warrant routing to the SDR team. The registered stage exists to capture inbound activity without flooding the SDR queue with contacts who have not demonstrated enough intent to warrant follow-up.

Marketing Qualified Lead

A lead that has engaged sufficiently, typically via automated lead scoring, to be passed to the SDR team. “Marketing Qualified” means marketing is making the call to route this lead for SDR follow-up, regardless of original source.

That distinction matters: conflating qualification with sourcing distorts attribution and creates friction between marketing and the SDR team about ownership.

Lative’s Marketing Intelligence tracks stage progression and conversion rates across this full funnel in real time, so qualification and attribution decisions are based on actual stage data rather than manually maintained spreadsheets or conflicting CRM snapshots.

SDR Working

An SDR has accepted the MQL and initiated outreach with the goal of booking a meeting. A consistent outreach process must be defined here: which channels, what scripting, how many touches, over what time window.

Without a defined process, “SDR Working” is a bucket that leads fall into and never come back out of. The date this stage begins must be tracked: it is the start of SDR velocity, and it tells you whether your lead routing SLA is being met.

Meeting Booked

The SDR has connected with the prospect and a meeting is scheduled. This stage must be distinct from Meeting Held: they are different events with different conversion implications, and collapsing them into one stage destroys the ability to measure show rate, which is one of the most predictive signals in the SDR funnel.

Meeting Held

The scheduled meeting has taken place. After a held meeting, the SLA for routing to opportunity or nurturing must be explicit: how many days can a lead sit in this stage before a decision is required? An undefined dwell time here is how leads silently exit the funnel without being counted as lost, which inflates conversion rates and understates funnel leakage.

Nurturing

Leads that were unreachable, not ready to progress, or did not convert after a held meeting are routed back to marketing for continued engagement. The lead score should be reset when a lead enters nurturing.

Explicit rules must define when a nurtured lead can re-enter the SDR queue. Without those rules, leads cycle back through SDR Working indefinitely without adding value and inflate MQL-to-pipeline rates.

Disqualified

Reserved for junk leads, opt-outs, and contacts with no relevance to the product offering. Disqualified should be used sparingly. Overuse turns it into a catch-all that masks the real reasons leads are not converting, and removes data that would otherwise help diagnose funnel quality problems.

The marketing-to-sales handoff: where MQL to SAL to SQL conversion breaks

The seven stages above describe what a clean funnel looks like inside a single CRM. The marketing-to-sales handoff is the seam where most demand waterfall models actually leak. An MQL that gets routed to an SDR but never accepted as a Sales Accepted Lead (SAL) is the most common form of silent funnel loss in B2B SaaS. The MQL count looks healthy. The pipeline numbers do not move. The conversion rate calculation cannot tell you why, because the handoff event was never recorded as a stage transition.

A defensible MQL to SAL to SQL conversion model needs three things in addition to the stage definitions themselves. First, a service-level agreement that defines how many hours an SDR has to accept or reject an MQL after routing. Second, a documented rejection reason taxonomy so that a rejected MQL feeds back into the lead scoring model rather than disappearing. Third, a Sales Accepted Opportunity (SAO) stage downstream of SQL for organizations that want to separate “this is a real opportunity” from “this opportunity has been formally accepted into the pipeline by an account executive.” Without that SAO checkpoint, lead-to-opportunity conversion rates blend two distinct events and the demand model loses resolution at exactly the point where forecast accuracy matters most.

The conversion benchmarks that show up in most B2B demand models, roughly 70 to 90 percent MQL-to-SAL, 30 to 50 percent SAL-to-SQL, 20 to 30 percent SQL-to-customer, are only meaningful if the stage transitions producing those numbers are recorded with dated custom fields. A handoff that happens by Slack message or a verbal SDR-manager-says-yes is not a stage transition. It is a measurement gap, and every conversion rate downstream of that gap inherits its ambiguity.

Aligning account stages with lead stages

In an account-based go-to-market model, lead stages are data points about where an account stands, not the primary unit of measurement. Account stages must be defined in parallel and kept synchronized with the lead stages underneath them.

The lead-to-account ratio is one of the most useful depth metrics in an ABM program. A 1:1 ratio means marketing is engaging one contact per target account, surface-level penetration.

A 5:1 ratio means marketing has reached five personas within the same account, which reflects the buying committee coverage that actually accelerates B2B deals.

Why Stakeholder Depth Matters in Account Stages

A February 2026 analysis of more than one million sales cycles found that won deals in the $50K–$250K range typically involve at least 10 stakeholders by the time they close. A stage definition model that tracks only the primary contact misses the depth signal that distinguishes deals likely to close from those that stall in late-stage review.

Account stage definitions must account for stakeholder breadth, not just the lead at the top of the queue.

Tracking this ratio over time shows whether the program is deepening engagement with target accounts or just adding net-new contacts. The hybrid demand engine model, tracking leads and accounts in the same funnel, is built on exactly this principle.

Stage dates and CRM sync

Every stage transition listed above requires a date field, set at the moment of conversion, not inferred from a later activity log.

For stages that originate in an SDR platform (Working, Booked, Held), custom workflows must extract those dates and write them back to the CRM bidirectionally. Without that sync, the CRM data quality issues that distort pipeline velocity calculations are baked in from the start.

When stage dates are clean and consistently applied, every downstream calculation, conversion rates, average days in stage, SDR SLA compliance, pipeline velocity by segment, becomes accurate enough to act on.

Seismic: Stage Cleanup in Two Weeks, Stable Conversion Rates

When Seismic’s RevOps team completed this stage definition cleanup, it took under two weeks and conversion rate calculations stabilized immediately across all five funnel stages. That accuracy is what separates a demand engine that produces reliable forecasts from one that produces numbers the RevOps team has to caveat in every QBR.

For the full demand engine framework that these stage definitions feed into, see How to Build a World-Class Demand Engine. For how Lative’s Marketing Intelligence surfaces the stage transition data that clean lead stages make possible, see the Pipeline Growth Insights overview.

Clean stage data is what makes capacity decisions trustworthy, which is why Lative feeds it straight into sales capacity planning on the same platform.

If your conversion rate calculations are being caveated in every QBR because the underlying stage data is ambiguous, that is the problem these definitions were built to fix. See how Lative’s Marketing Intelligence tracks stage-level pipeline movement at the resolution your capacity decisions require.

Frequently asked questions about lead and account stage definitions

---

Lative Team — Lative is the AI-native GTM platform that connects marketing intelligence to sales capacity planning on one shared data foundation.