30-second answer: Account journey stages describe the lifecycle of an account from anonymous to closed-won and beyond, with explicit entry and exit criteria at each stage so revenue teams measure progression consistently. The vocabulary covers stages, transitions, definitions, exit criteria, and dwell time. This glossary defines 20 journey-stage terms.
See account journey stages driving routing and re-engagement plays inside Abmatic AI, book a demo.
An account exists in observed traffic but is not yet resolved to a firmographic identity. The first stage of the journey.
An account has been resolved to a known company and added to the account graph. See account graph.
An account has shown topic-level engagement (research signals, ad views, content opens) but has not declared interest.
An account has shown active engagement (multi-page visits, content downloads, ad clicks) crossing a defined threshold.
An account meeting MQA criteria and ready for sales engagement. See marketing qualified account.
An MQA that sales has reviewed and accepted for active outreach.
An account with a CRM opportunity (a documented buying intent and rough deal sizing).
Terminal stages with binary outcomes.
Post-sale stage; tracks adoption, expansion, and renewal.
Stage triggered when a customer exits.
The explicit conditions an account must meet to enter a stage. Stages without explicit entry criteria become political.
The conditions under which an account leaves a stage (advance to the next stage, regress, or churn out).
Movement that bypasses an intermediate stage, common when a referral or warm intro starts at SAA or Opportunity directly.
Movement back to an earlier stage, usually when an opportunity disqualifies or churn risk fires.
Time spent in a stage before transitioning. Dwell time benchmarks tell programs whether stages are accelerating or stalling.
Maximum acceptable dwell before a triggering event fires (re-engagement play, manager review, or stage downgrade).
The rate at which accounts move through the journey. Velocity is the master output metric of orchestration.
An account exceeding the time-in-stage threshold without movement; stuck accounts trigger review.
Share of accounts at each stage that progress to the next stage.
A standard report showing population, dwell, and conversion at each stage.
Comparing accounts that entered a stage in the same period to control for seasonality.
Connecting closed-won pipeline back to the stage entry trigger to calibrate the journey definition. See ABM metrics glossary.
Worked example: a B2B vendor runs eight stages: Anonymous, Identified, Aware, Engaged, MQA, SAA, Opportunity, Customer. Entry criteria are documented (Identified requires firmographic resolution; MQA requires composite score above 75; SAA requires sales-rep acceptance within SLA). Time-in-stage thresholds fire re-engagement plays at the Engaged-to-MQA, MQA-to-SAA, and Opportunity stages. Cohort reports track stage conversion and dwell time monthly.
Counter-example: the same vendor uses six stages defined verbally rather than in writing. Sales and marketing disagree on what qualifies as MQA, dwell time is reported only as a rolling average that hides cohort-level deterioration, and no time-in-stage threshold fires re-engagement on stuck accounts. The pipeline review becomes anecdotal.
Operating tip: publish entry and exit criteria as a one-page document, refreshed quarterly, signed by marketing and sales leadership. The act of writing them down resolves more disputes than any tool configuration.
Healthy journey-stage programs report a canonical set: stage population, stage conversion, stage dwell, time-in-stage threshold breaches, and cohort-level conversion across periods.
Cohort framing matters because rolling reports hide deteriorating dynamics.
A team with rising stage population but falling conversion looks healthy in rolling reports and looks deteriorating in cohort reports.
The cohort lens is what surfaces real movement.
Stage-conversion ratios are inputs to forecasting models at every commercial level.
Programs running monthly closed-loop reports between forecast and outcome catch model drift; programs running only quarterly catch drift after the quarter.
The reporting hygiene improvement from cohort framing usually exceeds the lift from any new tool. Martech attribution covers the broader attribution context.
Journey stages connect tightly to revenue operations, ABM metrics, and attribution.
Stage definitions are inputs to forecasting models, conversion-rate analytics, and dashboards.
Without consistent stage definitions, comparisons across teams and across time degrade fast.
The reporting hygiene improvement from publishing crisp definitions usually exceeds the analytics improvement from any new tool.
Multi-product vendors usually run product-specific journeys with cross-product aggregation reports.
Land-and-expand motions add expansion-stage tracking on top of new-business stages.
Customer-marketing programs add adoption, expansion, and renewal stages that mirror the new-business journey.
The shape of the journey reflects the shape of the motion, and forcing one journey across motions consistently distorts reporting.
The most reliable journey-stage definitions follow three patterns. They publish explicit entry and exit criteria for every stage, in writing, with an owner. They publish time-in-stage thresholds that fire re-engagement or escalation actions. And they report stage performance in cohort form rather than rolling so seasonality and stage-mix do not distort interpretation. Common anti-patterns are stages defined verbally rather than in writing (definitions drift across teams), no time-in-stage thresholds (stuck accounts pile up unnoticed), and rolling reports without cohort context (stage performance looks fine when it is actually deteriorating). Programs that close these three gaps consistently build journeys that drive better forecasting.
See account journey stages driving routing and re-engagement plays inside Abmatic AI, book a demo.
Six to nine is the modal range, including pre-sale and post-sale. Fewer than six tends to lose precision; more than nine creates definitional friction without analytic gain.
Revenue operations or marketing operations, with sign-off from sales leadership. Without explicit ownership, definitions drift. See RevOps glossary.
A marketing funnel tracks lead-level progression from anonymous to MQL. The account journey tracks account-level progression including post-sale stages. Both are useful; they answer different questions.
Category-dependent. Enterprise software programs may set 30 to 60 day dwell on Engaged or MQA; PLG programs set 7 to 14 day dwell because cycles are shorter. Calibrate against historical conversion data.
Multi-product vendors usually run separate journeys per product line, with cross-line aggregation reporting. One-journey-fits-all hides motion-specific dynamics.
Stage-conversion rates and stage dwell are key inputs to pipeline forecasting at each commercial level. See the revenue operations glossary.
The account journey is the temporal backbone of a revenue program. Defined well, it makes routing, forecasting, and team calibration tractable. Use this glossary alongside the ABM playbook when designing or refreshing the stage model.
Ready to put this glossary into practice? Book a demo of Abmatic AI.