Which SQLs don't have a deal yet?

Why SQL-without-deal is a coaching signal, not a data hygiene one

The lifecycle stage Sales Qualified Lead means marketing or SDR has flagged the lead as ready for sales. The implicit contract is: the AE or sales-side rep takes over, has a discovery call, and creates a deal record to track the opportunity.

When that deal doesn't get created, one of two things is happening:

1. The lead is sitting in the rep's queue and being ignored. SQL came in, rep didn't pick it up, days pass.
2. The rep had the conversation but didn't create the deal record. They might be working it informally, or they decided it's not really an SQL but didn't update the lifecycle stage to reflect that.

Both are coaching moments. Both cause the same downstream problem: the lead is "sales qualified" in your reports, but there's no deal in the pipeline, so the lead is invisible to forecast and to deal-stage analytics. You're crediting marketing for sourcing the lead but can't measure whether sales did anything with it.

What three filter conditions actually catch

Three filter conditions:

1. Lifecycle stage is Sales Qualified Lead (or your equivalent).
2. Number of associated deals is 0.
3. Time at current lifecycle stage is more than 14 days.

The 14-day threshold is conservative. Some teams tighten to 7 or even 3 — depends on your sales motion. The point is to give the rep a reasonable window to do the discovery work before the alert fires.

Why SQL zombies pile up despite the filter

The lifecycle stage data is fragile in two ways:

Lifecycle stages don't auto-progress. A lead becomes SQL when something explicitly sets the property. If your SDR-to-AE handoff workflow misses, the lead stays at MQL and never enters this view — even if the rep is actively working it. The rule misses these cases.

SQLs that should be set back to MQL or Lead. A common mistake: rep does discovery, decides the lead isn't really qualified, but doesn't set the lifecycle stage backward. (Setting lifecycle stages backward also corrupts conversion reporting per HubSpot's docs, so this isn't a clean fix either.) The lead stays SQL forever, never creates a deal, and shows in this view as a permanent zombie.

The community recommendation is to add a custom Lead status workflow alongside lifecycle stage: when SQL has no activity for 21 days, set Lead status to Nurturing so it drops out of active-SQL counts. The lifecycle stage stays Sales Qualified Lead to preserve marketing attribution, but the operational status reflects reality.

That's two properties to maintain instead of one. It works. It's also the kind of layer that sales-ops teams build, document, and then watch silently rot when the person who built it leaves.

The manual HubSpot recipe

Three filters, one optional auto-demote workflow. The view itself is straightforward; the discipline of acting on the rows weekly is the harder part.