SonaMation
All posts
Layer 28 min read

Lifecycle stages that don’t lie

Every HubSpot lifecycle audit starts with the same problem: nobody can tell you what ‘MQL’ actually means at this company.

By Yarkin Sakucoglu·April 22, 2026

Every HubSpot lifecycle audit starts with the same problem: nobody can tell you what "MQL" actually means at this company.

Marketing has a definition. Sales has a different one. RevOps has a third. They've all been arguing about it for so long they've stopped expecting agreement — and the lifecycle stages in HubSpot have just kept drifting, picking up new properties, new automation triggers, new exceptions.

What we look for

When we audit lifecycle stages on Layer 2, we look for three specific failures:

1. Stage transitions without measurable criteria. If "Lead → MQL" fires from a workflow that nobody can describe in one sentence, the stage doesn't mean anything anymore.

2. Stages that exit but never enter. This usually means a workflow upstream is missing.

3. Custom stages built around exceptions. Every "MQL — Self-Serve" or "Lead — Hand-Raise" stage is a sign that the original definitions broke and someone bolted on a workaround.

How we fix it

Every lifecycle stage gets:

  • A single-sentence definition
  • A measurable entry criterion (a property value, a workflow trigger, or an event)
  • A measurable exit criterion (the same)
  • An owner (one person, accountable)

If a stage can't have all four, it gets deleted.

What changes

Within 60–90 days post-rebuild, we typically see funnel reporting that all three teams agree on. The forecast doesn't always improve immediately — but the arguments stop, and that alone is worth the engagement.

Want to apply this?

Score your stack against the four layers.

12 questions. 4 minutes. Per-layer score plus a recommended next move.

Score your RevOps stack — 4 minStart