Define your lifecycle stages before you touch a pipeline

Lifecycle stages are the backbone of revenue reporting, and you define them before any deal moves

Get your lifecycle stages right before you build a single pipeline, because every funnel report you will ever run, conversion rates, stage velocity, where revenue leaks, is measured against them. Define them late and you are re-segmenting your whole database to fix a foundation you should have laid first.

Lifecycle stage and pipeline stage are not the same thing, and conflating them is the most common RevOps mistake I see. The lifecycle stage is the contact's or company's position in the whole revenue journey: subscriber, lead, marketing-qualified, sales-qualified, opportunity, customer. The deal pipeline stage is where a specific opportunity sits inside an active sale: discovery, proposal, negotiation, closed. One describes the relationship over its lifetime; the other describes one deal in flight. You need both, and they answer different questions.

Why lifecycle stages come first

HubSpot lifecycle stages are the spine your funnel reporting hangs on. With them defined, you can ask how many leads became marketing-qualified last month, what share of sales-qualified leads became opportunities, and where the journey leaks. Without them, you have a pile of contacts and no sense of motion. And because lifecycle stage is set across thousands of existing records, redefining it later means a bulk re-segmentation of your live database, which is painful and error-prone. Define it once, early, and it just accumulates clean data.

What good lifecycle stages look like

HubSpot ships a default set, and for a lean team the defaults are close to right: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist. Do not invent your own taxonomy unless you have a real reason. Instead, write the precise entry criterion for each stage, the one thing that must be true to move a record into it. "Marketing qualified" must mean a specific, checkable thing, requested a demo, hit a lead score, downloaded the buyer's guide, not a vague feeling.

The discipline is definition, not invention. Two people who disagree on what "sales qualified" means will produce a funnel that does not reconcile, and the report dies of distrust. One written definition per stage, agreed once, is the whole job.

The exact steps

1. Adopt HubSpot's default lifecycle stages unless you have a concrete reason to differ. Fewer custom stages is better.
2. Write one entry criterion per stage, the single checkable fact that promotes a record into it. Keep it to a sentence.
3. Decide what sets the stage: which become automatic (a form fill sets Lead, deal creation sets Opportunity) and which a human sets. Automate every one you can.
4. Build your deal pipeline stages separately, as the in-flight steps of an active sale, and map which lifecycle stage each pipeline event drives.
5. Backfill lifecycle stage on existing records so historical funnel reports are not empty.

A worked example

A 12-person B2B fintech ran every contact as either "lead" or "customer" with nothing in between. Challenge: they could not see where deals stalled, so they could not tell whether the problem was lead quality or sales follow-through, and they kept arguing about it with no data. Approach: they adopted HubSpot's default lifecycle stages, wrote a one-sentence entry criterion for each, and automated stage changes off form fills and deal creation, exactly the steps above. Result: within six weeks the funnel report showed that 70 per cent of marketing-qualified leads never became sales-qualified, a follow-up gap nobody had quantified. Fixing the handoff lifted SQL conversion from 30 to 52 per cent in a quarter. The stages turned an argument into a number.

Pitfalls

• Confusing lifecycle stage with deal stage. They answer different questions. Build both, keep them distinct.
• Vague entry criteria. "Seems interested" is not a stage definition. Each stage needs one checkable fact.
• Inventing a bespoke taxonomy. Custom stages multiply maintenance and break HubSpot's built-in reporting. Start from the defaults.

With lifecycle stages defined as the reporting backbone, the records need to fill themselves with activity. The next chapter wires the automation glue between your tools, because a lean team will never log interactions by hand.