HubSpot/No. 01/8 min read

The 4 lifecycle stages most HubSpot accounts get wrong

Most HubSpot accounts quietly use “Lead” and “MQL” to mean the same thing. That single overlap breaks your funnel reporting, and every conversion rate you have shown the board is built on it. Here is how to restructure four stages in under a week.

SM

Sage M.

LSR Marketing · May 26, 2026

Open your HubSpot lifecycle stage property right now. If "Lead" and "MQL" are both catching every contact who fills out a form, your funnel report is fiction. And every conversion rate you have ever shown the board is built on top of it.

This is not a labeling nitpick. Lifecycle stages are the backbone of funnel reporting. When two of them mean the same thing, you lose the one number that actually matters: where qualified demand stalls. You can fix it in under a week, and you do not need to rebuild your portal to do it. You need four stages to mean four different things.

Here are the four most accounts get wrong, why they drift, and the structure that holds.

Stage 1: "Lead" is doing two jobs at once

In most portals, "Lead" means "a contact exists." Someone downloaded a guide, hit a form, got imported from a list, and HubSpot stamped them as a Lead. That is fine, except the same accounts then treat Lead as if it also means "marketing has looked at this and thinks it is worth something." It cannot mean both.

The fix is to decide, on purpose, that Lead means exactly one thing: a known contact who has not yet been qualified by anyone. No scoring judgment, no interest signal, no "this one looks good." It is the raw top of the funnel. The moment you ask Lead to carry an opinion about quality, you have nowhere clean to put the contacts that genuinely earned that opinion, and they pile up in the next stage instead.

Stage 2: "MQL" means whatever the last workflow said

This is the stage that breaks the report. In a healthy funnel, Marketing Qualified Lead is a deliberate marketing decision: this contact crossed a threshold we defined, so we are vouching for it. In most portals, MQL is whatever a tangle of old workflows happens to set. One workflow promotes on a score of 50. Another promotes anyone who books a demo. A third, built two years ago by someone who left, quietly promotes anyone who opens three emails.

So MQL stops being a qualification and becomes an accident of automation history. The symptom you will recognize: sales does not trust the MQL queue, because half of what lands there is a contact who opened some emails. Once sales stops trusting the stage, they work their own list, and your funnel report and your actual pipeline are now two different stories.

The fix is to write the MQL definition down as one sentence a human can read, then make exactly one workflow responsible for setting it. Everything that promotes a contact to MQL routes through that single workflow. If you cannot say in one sentence what makes a contact an MQL, that is the actual problem, and no property structure will paper over it.

Stage 3: there is no stage for "sales accepted it"

Most accounts jump straight from MQL to SQL, and that gap is where the marketing-and-sales fight lives. Marketing says it sent 200 MQLs. Sales says half were junk. Both are looking at the same stage and seeing different things, because there is no stage that records the one event that settles it: sales looked at the lead and accepted it as worth working.

The fix is to add the stage almost everyone skips. Call it Sales Accepted, sitting between MQL and SQL. MQL is marketing's claim. Sales Accepted is sales agreeing to work it. SQL is the lead proving real, qualified opportunity. With that middle stage in place, MQL-to-Sales-Accepted becomes the cleanest health metric you have: it is the rate at which sales agrees with marketing's definition of quality. When that number is low, you do not have a lead volume problem, you have a definition problem, and now you can see it.

Stage 4: "Customer" hides everything after the first deal

The last one is quieter but it distorts retention and expansion reporting. The instant a deal closes, the contact flips to Customer and stays there forever. Renewal, churn risk, expansion, win-back: all of it collapses into one flat stage. For a business that lives on recurring revenue, that means the entire post-sale motion is invisible in the lifecycle property that every other report keys off of.

HubSpot will not let you add native lifecycle stages past Customer, so the fix is a parallel custom property, a Customer Stage, that runs alongside the lifecycle stage and tracks the post-sale states that matter to you: onboarding, active, at-risk, expansion, churned. Lifecycle stage owns the road to the first deal. Customer Stage owns everything after. Keep them separate and both reports finally tell the truth.

What good looks like

Put the four fixes together and each stage carries exactly one meaning:

• Lead is a known contact, not yet qualified by anyone. No quality opinion attached.
• MQL is one written definition, set by one workflow, that marketing will vouch for.
• Sales Accepted records sales agreeing to work the lead, so the marketing-versus-sales argument becomes a number instead of a meeting.
• Customer marks the first deal, and a separate Customer Stage property carries everything that happens after it.

Now your funnel report survives a follow-up question. When someone asks why conversion dropped, you can point to the exact stage where contacts stalled instead of guessing, because each stage finally means one thing and the transitions between them are real events, not accidents of old automation.

None of this is a week of rebuilding. It is a definition exercise, a handful of property changes, and consolidating the workflows that promote contacts down to one per transition. Most of it is data and definitions, which is true of nearly every CRM problem worth fixing. This is the work we do in almost every Marketing Operations & CRM engagement, because you cannot improve a funnel you cannot trust.