Quick answer
Different industries use different lifecycle-stage names, but the operating question is the same: what evidence proves that this contact, company, or account really belongs in its current stage?
For HubSpot teams, the practical move is to keep a stable lifecycle spine - Lead, MQL, SQL, Opportunity, Customer - and use industry-specific fields, workflows, lists, and deal context to explain what those stages mean in your business.
The mapping principle: keep HubSpot stable, translate the business language
Lifecycle-stage governance breaks when every team uses the same field to express different ideas. A real estate team may call a serious prospect a "qualified buyer." A manufacturing team may care more about "RFQ" and "sample." A healthcare team may need "verified" or "scheduled" before anyone should be called qualified.
That does not mean every portal should rebuild HubSpot's lifecycle field from scratch. In most cases, keep the main HubSpot lifecycle stage simple, then attach the industry meaning as evidence.
| Layer | What it should do | Example |
|---|---|---|
| HubSpot lifecycle stage | Keep the high-level funnel spine stable enough for reporting. | MQL, SQL, Opportunity, Customer |
| Industry-specific evidence | Explain why the stage label is true in this business. | Demo request, RFQ, pre-approval, insurance verification, first order |
| Sub-stage or process field | Capture the local workflow without polluting lifecycle reporting. | Technical scoping, underwriting, showing completed, in cart |
| FunnelLedger evidence report | Check whether stage labels are supported, stale, missing evidence, or conflicting. | "The MQL cohort is supported by demo requests and ICP fit, but follow-up is stale." |
Industry stage-language comparison
Use this table as a vocabulary map, not as a rigid template. The exact names will vary by company, region, and sales motion. The important part is to define what evidence should exist before a record moves forward.
| Industry | Common stage language | HubSpot mapping | Evidence to verify | Watch out for |
|---|---|---|---|---|
| B2B SaaS | Lead, MQL, SQL, Opportunity, Customer | Usually maps cleanly to HubSpot defaults. | Demo request, trial signup, score threshold, ICP fit, discovery call, deal created. | MQL volume that is driven by scoring noise instead of buyer intent. |
| PLG SaaS | Signup, activated user, PQL, PQA, opportunity, paid customer | PQL often sits between MQL and SQL. | Product activation, usage events, invite activity, workspace creation, payment event. | Treating every signup as sales-ready. |
| HubSpot agency / services | Inquiry, prospect, qualified, proposal sent, client, retainer | Proposal can map to SQL or Opportunity depending on deal policy. | Discovery call, project fit, budget, proposal, signed SOW, retainer start. | Calling a contact "customer" before the engagement is active. |
| Manufacturing | Inquiry, qualified lead, technical scoping, RFQ, proposal, account | RFQ is often SQL; proposal is often Opportunity. | Spec download, sample request, RFQ, engineer review, quote sent, PO received. | Long dwell times that look stale but are normal for the motion. |
| Healthcare | Inquiry, intake, verified, scheduled, visit, patient | Eligibility or appointment scheduled is often the real qualification gate. | Referral, form, insurance verification, appointment booked, treatment completed. | Overusing "customer" language in patient journeys. |
| Finance / fintech | Inquiry, prospect, qualified, application, underwriting, client | Application is often SQL; underwriting is often Opportunity. | KYC/AML status, application, risk fit, region eligibility, approval, account opened. | PII and compliance-sensitive fields in reports. |
| Insurance | Quote request, pre-qualified, application, underwriting, policy issued | Policy issued maps to Customer; application and underwriting sit before close. | Quote request, carrier fit, application, underwriting status, policy start date. | Counting quote shoppers as qualified pipeline. |
| Real estate / construction | Inquiry, qualified buyer, showing, under contract, closed, past client | Under contract is often Opportunity; closed is Customer. | Property inquiry, pre-approval, showing, offer accepted, escrow, closing. | Skipping qualification evidence before marking serious buyers. |
| B2B ecommerce | Visitor, account created, cart, quote, first order, repeat, loyal | First order often maps to Customer; repeat/loyal should be a segment, not the main lifecycle field. | Account creation, cart, quote request, purchase, repeat order, subscription. | Using lead-stage language for an order-based journey. |
| Education | Inquiry, applicant, admitted, enrolled, student, alumni | Applicant can map to MQL; admitted or advisor-validated can map to SQL. | Program inquiry, application, acceptance, deposit, enrollment, attendance. | Calendar-driven velocity that looks slow outside enrollment season. |
| Nonprofit / donor | Supporter, prospect, cultivation, solicitation, first gift, donor, major donor | Solicitation is often SQL; first gift can map to Opportunity or Customer by policy. | Event attendance, campaign response, gift officer activity, pledge, first donation. | Forcing donor journeys into customer language. |
| Cybersecurity | Researcher, qualified account, technical validation, security review, opportunity, customer | Technical validation can sit between SQL and Opportunity. | Security-content intent, ICP fit, evaluation request, POC, procurement, closed-won deal. | Low top-of-funnel volume that is normal for a narrow buyer set. |
| HR tech / recruiting | Demo request, qualified HR buyer, discovery, pilot, customer; or sourced, screened, interviewing, offer, placed | Separate buyer lifecycle from candidate lifecycle where possible. | Demo, HRIS fit, employee count, pilot, signed contract; or application, interview, offer, placement. | Mixing candidate and buyer journeys in one lifecycle field. |
| Legal services | Inquiry, matter evaluation, consultation, retainer proposed, client, opened matter | Consultation or matter evaluation is often SQL; retainer proposed is Opportunity. | Practice-area fit, conflict check, consult booked, retainer, matter opened. | Calling every inquiry qualified before fit and conflict checks. |
Industry lifecycle-stage library
Sales-led SaaS funnel
Most sales-led SaaS teams can use HubSpot's default lifecycle labels, but the evidence threshold matters.
Evidence to look for: form submission or demo request, score above threshold, trial signup, discovery call completed, deal created with MRR or ARR, active subscription.
Signup-to-revenue funnel
PLG teams often need product-qualified stages that HubSpot does not model out of the box.
Evidence to look for: workspace creation, activation event, invite activity, feature usage, product score, payment or plan activation.
Inquiry-to-client funnel
Agencies tend to talk about prospects and clients, not customers. Proposal stage is the core handoff.
Evidence to look for: discovery call, service fit, budget, decision maker, proposal sent, signed SOW, retainer start date.
Technical buying cycle
Industrial funnels often progress through technical proof before revenue. RFQ is usually the cleanest serious-intent signal.
Evidence to look for: spec sheet download, sample request, engineering fit, quote request, proposal, PO or contract.
Inquiry-to-patient journey
Healthcare teams usually need eligibility and scheduling gates before a lifecycle label is meaningful.
Evidence to look for: referral, form submission, insurance or eligibility verification, appointment scheduled, first treatment completed, care plan.
Application and underwriting journey
Qualification often depends on eligibility, risk, geography, and compliance context rather than simple engagement.
Evidence to look for: application submitted, KYC/AML status, risk fit, product eligibility, approval, account or policy opened.
High-touch transaction funnel
Real estate teams often skip generic MQL/SQL language and care more about readiness to buy, sell, visit, or close.
Evidence to look for: property page view, call, pre-approval, tour scheduled, offer accepted, escrow, recorded transaction.
Order and repeat-purchase funnel
Ecommerce lifecycle stages often need to reflect order behavior, not just marketing qualification.
Evidence to look for: account creation, item added, quote request, purchase confirmed, repeat purchase within the target window, subscription or loyalty marker.
Inquiry-to-student funnel
Education funnels are calendar-driven. Applicant, admitted, enrolled, and student are often more useful than generic sales labels.
Evidence to look for: program inquiry, application submitted, acceptance, deposit, course registration, attendance or start date.
Supporter-to-donor funnel
Nonprofits should avoid forcing donor relationships into customer terminology. The evidence is mission engagement and giving behavior.
Evidence to look for: event attendance, campaign response, gift officer outreach, proposal or ask, first donation, repeat giving.
Technical validation funnel
Cybersecurity funnels often have low early conversion but strong late-stage intent once a qualified buyer starts evaluation.
Evidence to look for: technical content intent, target-account fit, POC request, security review, procurement, closed-won deal.
Inquiry-to-matter funnel
Legal teams need fit and conflict checks before a contact should be treated as qualified.
Evidence to look for: practice-area fit, conflict check, consultation booked, retainer signed, matter opened.
Common traps when naming lifecycle stages
- Making lifecycle stages too local. If every industry-specific nuance becomes a lifecycle value, reporting becomes hard to compare.
- Calling activity evidence the same thing as stage evidence. A page view may support Lead. It rarely proves SQL.
- Mixing contact, company, deal, and candidate journeys. Recruiting and ABM motions often need separate objects or companion fields.
- Letting automation set stages without a receipt. If a workflow moves a contact to MQL, the report should show which workflow and which trigger supported the move.
- Ignoring custom properties. Custom fields often hold the real business language: ICP tier, qualification reason, product interest, territory, persona, or handoff status.
FAQ
Should every industry use custom lifecycle stages in HubSpot?
Not always. Many teams are better served by keeping HubSpot's default lifecycle stages stable and adding custom fields for sub-stage, reason, qualification, product interest, or process status.
What if my industry does not use the word "customer"?
Use the term your business actually uses in reports and enablement materials, such as client, patient, student, donor, account, or policyholder. In HubSpot, decide whether that term maps to the Customer lifecycle stage or a companion field.
How does FunnelLedger use this industry language?
FunnelLedger treats lifecycle stage as the main product question, then uses source, touchpoint, deal, workflow, score, ICP, persona, segment, and custom-property evidence to explain whether the stage label is supported.
Your industry language is only useful if the portal evidence supports it. FunnelLedger can scan your HubSpot lifecycle history and show which stage labels are supported, stale, unsupported, or contradictory.