How do HubSpot's lifecycle stages actually work?
Treat HubSpot's preset lifecycle stages as an education level, not a to-do list. Subscriber, lead, MQL, SQL, opportunity, customer, evangelist: they tell you how much a person knows about you, and people don't move backwards through them.
That last part is the bit everyone misses. Because you can't demote someone, the stage becomes a permanent record of how well they understand you. An SQL from a year ago who went quiet still has SQL-level knowledge of your product. Speak to them at that level, not as a cold stranger. An evangelist who's since left their company is still evangelist-level; they know you inside out. The stage isn't "where are they in my sales process", it's "how much have they already learned about us", and it's sticky on purpose.
Lifecycle stage is an education level, not a sales step. It tells you how to speak to someone, not what to do next.
So the preset stages are distinct from your sales-journey stages, and the critical transition between the two worlds is lead to opportunity. Define your marketing lifecycle stages first, the education ladder, then define the sales lifecycle stages that follow, the ones marketing stays involved in rather than walking away from. Get that boundary clear and the rest of the setup falls into place.
When should you create a deal?
The moment a meeting is booked. In B2B SaaS I'd create the deal there, and I'd do it every time, because a deal is the one object the whole company watches.
Nobody keeps an eye on scattered lead lists. Everybody keeps an eye on the deal pipeline. So the instant something becomes real, a booked meeting, get it onto the board where it's visible. The payoff is accountability. If a deal has been sitting in "meeting booked" for four weeks, everyone can see it, and that visibility forces a decision: move it forward, or close it lost with a reason. Left as a lead in a list, that same stalled opportunity just quietly rots and nobody notices for a quarter.
This is one of those "automate it or regret it" calls, and it links straight to the biggest mistake below. A deal created by hand, when someone remembers, is a deal that's often created late or not at all. A deal created automatically when the meeting is booked is always there, always on time, and always honest.
What makes a good deal stage?
Every deal stage should map to a specific action that has actually happened, with clear criteria. If a stage describes a feeling rather than an event, it's useless.
Good stages are events you can point to. "Meeting booked": it happened, there's a calendar invite. "Qualified": it meets preset criteria you agreed in advance, income over X, headcount over Y, budget confirmed at or above a threshold. "Proposal sent": a proposal was genuinely sent, not "about to be". Each one is a fact, so each one is reportable, and moving a deal into it means something specific occurred.
The failure mode is the vague stage. "Engaged." "Thinking about it." "In discussions." These describe a vibe, not an event. Two salespeople will read them differently, nobody can define when a deal enters or leaves them, and they're impossible to report on because there's no criteria to check. Worse, they let deals hide. A deal parked in "thinking about it" can sit there forever because nobody can say it's wrong. Clear criteria plus a required action per stage does two jobs at once: it makes the pipeline reportable, and it forces movement, because a deal either meets the criteria for the next stage or it doesn't.
How should you route leads in HubSpot?
Enrich first, then tier, then route on the tier. Never route on the raw form fill, because you almost never have enough to route well until you've enriched.
So the first step in any routing flow is an enrichment engine that fills the gaps: industry, revenue, headcount, what they actually sell. Only once the record is complete can you tier it sensibly:
- Tier one: hits all your criteria. Send it straight to a BDR. No delay, no qualification flow, this is the good stuff and it should reach a human fast.
- Tier two: hits some of your criteria. Route it to your GTM team to engage and qualify further before it's worth a BDR's time. It might be great, you just don't know yet.
- Tier three: doesn't fit the profile today. Drop it into a marketing education flow, webinars and content, to qualify it over time. If it keeps engaging, it moves up a tier. If it never does, it never wastes a salesperson's day.
That third tier is where a good email and lifecycle programme earns its keep, quietly warming the people who aren't ready yet so the ones who become ready arrive pre-educated. Routing and lifecycle work best when they feed each other.
What's the biggest mistake teams make in HubSpot?
Running lifecycle stages, tiering and deal creation as separate, manual ideas that don't connect, and then waiting for humans to keep them in sync by hand. That's the mistake, and it quietly poisons every decision downstream.
Here's how it goes wrong. Someone decides how leads come in, someone else decides where they're managed, someone else decides when a lead becomes a deal, and none of it's joined up. Then you rely on people to manually change statuses, create deals and move stages as things happen. They forget, they're busy, they do it a day late or a week late or not at all. The result is a pipeline that doesn't reflect reality, reports that are out of whack, and decisions made on data that's simply wrong. It's the same rot we described in why you can't trust your CRM data, just expressed through stages instead of fields.
The fix is to automate the lot. Lifecycle tagging, tiering, routing, deal creation when a meeting is booked, stage movement when a proposal is sent. Take the manual step out and the data becomes correct because it can't help but be correct. Correct data makes the analytics correct, and correct analytics makes the decisions correct. That chain is the whole reason to bother, and it's the line we draw in what to automate in GTM versus keep human: the mechanical status-keeping is automation's job, the human conversation is yours. If you're still choosing your platform, we also weighed the options in HubSpot versus Salesforce, or neither.
If your HubSpot pipeline relies on people remembering to move things, it's already lying to you a little. Book a free Growth Audit and we'll map the lifecycle stages, tiering and deal automation that keep it honest.
Frequently asked questions
Why treat lifecycle stages as an education level?
Because people don't move backwards through them, so the stage becomes a permanent record of how much someone knows about you. An SQL from a year ago still has SQL-level knowledge, and an evangelist who's left is still evangelist-level. The stage tells you how to speak to them, not where they sit in your sales process today.
When should I create a deal in HubSpot?
When a meeting is booked. A deal is the one object the whole company watches, unlike scattered lead lists, so creating it at that point makes stalls visible. If a deal sits in "meeting booked" for four weeks, everyone sees it and someone has to act: move it forward or close it lost with a reason.
What's wrong with deal stages like "engaged" or "in discussions"?
They describe a feeling, not an event, so nobody can define when a deal enters or leaves them and they're impossible to report on. Every stage should map to something that actually happened with clear criteria: "meeting booked", "qualified" against agreed thresholds, "proposal sent". That makes the pipeline reportable and forces deals to move.
How should lead routing work?
Enrich first, then tier. An enrichment engine fills the gaps (industry, revenue, headcount), then you route on the tier: tier-one hits all criteria and goes straight to a BDR, tier-two is partial and goes to the GTM team to qualify, tier-three doesn't fit yet and drops into a marketing education flow that moves it up if it keeps engaging.
