Default HubSpot lifecycle stages skip the SAL (Sales Accepted Lead) handoff, conflate Customer with Renewal and Expansion, and don't separate Churned from Closed Lost. The ten-stage model fixes this. Each stage has a clear definition, a clear transition rule, and a clear ownership. Once installed, every report (funnel conversion, velocity, win rate) becomes meaningful because the stage definitions are unambiguous.
The ten stages, with definitions
Subscriber: opted in to marketing communications, no qualifying signal yet. Lead: provided contact info via form fill, demo request, or content download. MQL: rule-based score crossed Marketing Qualified threshold OR explicit hand-raise. SAL: Sales has reviewed the MQL and accepted it for follow-up (the explicit handshake stage missing from the HubSpot default).
SQL: Sales has had a conversation, qualified the deal, and confirmed Budget/Authority/Need/Timeline (or your equivalent qualification framework). Opportunity: an active deal record exists in the pipeline, stage > Discovery. Customer: deal Closed Won, contract signed.
Renewal: Customer with renewal date within next 90 days, or active renewal motion. Expansion: Customer with active upsell or cross-sell deal in pipeline. Churned: previously a Customer, now lost (separate from Closed Lost which means the deal didn't close in the first place).
Transition rules
Subscriber → Lead: contact submits a form. Auto-set in workflow. Lead → MQL: score crosses 50, OR contact requests demo, OR contact downloads BOFU asset. Auto-set with manual override allowed.
MQL → SAL: AE clicks Accept on the MQL within the SAL SLA (we set this at 1 business day). If unaccepted within SLA, MQL drops back to a re-nurture path. This explicit acceptance gate is what separates a working pipeline from one where leads quietly rot.
SAL → SQL: AE has had a discovery call and confirmed qualification. Manual transition with required fields (next step, decision date, budget confirmed). Forces the AE to capture the qualification reasoning.
SQL → Opportunity: deal record created with stage Discovery. Customer → Renewal: 90 days before renewal date, automated. Customer → Expansion: new deal record created with type Upsell or Cross-sell. Customer → Churned: contract end date passed without renewal, OR explicit churn ticket resolved as Lost.
What the stages enable
Once the ten stages are installed, every funnel report becomes accurate. MQL-to-SAL conversion exposes lead quality and sales acceptance rate. SAL-to-SQL conversion exposes discovery effectiveness. SQL-to-Customer conversion is your pipeline-to-revenue ratio. Customer-to-Renewal-to-Expansion-to-Churned tracks net revenue retention.
The default stages can't surface SAL-to-SQL conversion because there's no SAL stage. They can't separate Renewal from Expansion because both fall under Customer. The ten-stage model is what makes the funnel diagnose-able.
How this ties to scoring and routing
The lifecycle stage is the result of scoring + qualification, not a substitute. Score determines the threshold for MQL transition. Sales acceptance determines SAL. Qualified discovery determines SQL. The stages are the visible record of the journey; the scoring and routing rules are what move contacts through.
Once this is right, your dashboards stop lying. The funnel chart matches what's actually happening, and the team can debug why conversion is low at a specific stage instead of arguing about whether the stage definition is right.
Backfilling existing data
If you already have a HubSpot portal with the default stages, backfilling the ten-stage model is a one-time exercise. Pull historical data, compute what each contact's stage should have been on a given date based on their activity, and bulk-update via Operations Hub or a CSV import.
The clean way: run the new stages in parallel with the old ones for 30 days, validate that workflows and dashboards still produce the right numbers, then deprecate the old. Don't rip and replace; the team needs continuity in the reporting they look at every Monday.
A B2B SaaS customer had been using default lifecycle stages for two years and couldn't answer basic funnel diagnosis questions (which stage drops out the most, which AE has the highest SAL acceptance rate, what's our renewal motion conversion). We installed the ten-stage model in three weeks, backfilled six quarters of history, and rebuilt the funnel dashboards. Forecast accuracy improved within a quarter; the bigger win was that leadership stopped arguing about pipeline definitions and started fixing the actual conversion gaps.
FAQ
Why not just add SAL to the HubSpot default stages?
You can. The ten-stage model is opinionated about adding SAL, separating Renewal from Expansion, and isolating Churned. You can install just the SAL addition if you don't have a renewal motion yet. Add stages as the motion adds them; don't install stages you don't have a workflow for.
How do I handle accounts vs contacts in lifecycle?
Lifecycle stage lives on the contact. Account-level lifecycle is derived (the highest-stage contact at the company sets the company's lifecycle). Use HubSpot's Account-Based Marketing dashboards or roll up via calculated company properties. Don't try to maintain account lifecycle independently from contact; the data integrity will rot.
What if our sales team uses different stage names?
Stage names are surface labels, the underlying transitions are what matter. Pick the labels your sales leadership will use in calls (some teams say SAL, some say Sales Reviewed, some say Accepted). The transition rule and the dashboard are the same regardless of label.
How long does this take to install?
Three weeks for a clean implementation. Week 1 audit current state, define new stages and transition rules with sales leadership. Week 2 build workflows, custom properties, and dashboards. Week 3 backfill historical data, run in parallel for validation, deprecate old. Add a week if integrating with Salesforce or another CRM that has its own lifecycle field.
Can I track movement between stages?
Yes, with HubSpot's Date Entered Stage and Time in Stage properties. Build dashboards that show stage transition velocity (median days from MQL to SAL, etc.). This is where bottlenecks surface; if MQL-to-SAL median is 7 days, the sales acceptance process is broken.
What about the Subscriber stage, do most companies need it?
Yes if you have a content motion, no if you're pure outbound. Subscriber is the marketing-only stage where someone is in your nurture but hasn't converted to Lead yet (newsletter sign-ups, podcast subscribers). If your motion doesn't include a content layer, skip the Subscriber stage; default to Lead as entry.
How INSIDEA works
