Pipeline Health: Is Your Open Pipeline Real?

Ask most revenue leaders how healthy their pipeline is and they will answer with a ratio: open pipeline value divided by the remaining quota gap. A 3.5x or 4x coverage number is treated as reassuring, and a number below 3x triggers a pipeline-generation push. This is a reasonable starting heuristic and a poor final answer, because coverage ratio is blind to the single question that actually determines whether a forecast holds: would this specific set of deals survive a rigorous review today?

Coverage ratio treats a $50,000 deal that has had no logged activity in 74 days, whose close date sits three weeks in the past, the same as a $50,000 deal with a signed mutual action plan and a champion who replied to an email yesterday. Both count equally toward the numerator. A CRM full of the first kind of deal can show 4.5x coverage and still miss the quarter, because the ratio is measuring the presence of dollar amounts in open dealstage records, not the presence of a real buying process behind them.

Pipeline health is the corrective lens: it asks not how much pipeline exists, but how much of it is credible — meaning it has the data signature of a deal that is genuinely progressing, not one that is administratively still open because nobody has closed it as lost.

It helps to separate pipeline into three distinct measurements, because each one requires a different fix and confusing them leads to the wrong remedy being applied.

Each diagnostic below can be built as a filtered HubSpot deal view or a saved report using native properties — no custom objects or third-party enrichment required.

1. Stage age vs stage benchmark. Compare time-in-current-stage (derived from stage-entry timestamps, or approximated via hs_lastmodifieddate on the dealstage field) against your median time-to-convert for that stage. A deal sitting 2.5x longer than the stage median is stalling, not slowly progressing.
2. Days since meaningful sales activity. Use hs_last_sales_activity_timestamp, not hs_lastmodifieddate, to measure genuine human engagement — calls, meetings, and two-way email threads.
3. Close dates in the past. Filter for closedate less than today AND hs_is_closed is false. Every record in this view is a data hygiene failure by definition; the deal either closed and wasn't marked, or it's stalled and nobody moved the date.
4. Close-date pushes. Track how many times closedate has changed within the current stage (via property history). One push is normal; three or more pushes without a corresponding stage advance is a strong sandbagging or stall signal.
5. Missing amount. Filter for amount is unknown among open deals past the qualification stage. A deal without a value cannot be forecast accurately and typically indicates it was created reflexively rather than qualified.
6. Single-threaded contact count. Count distinct associated contacts with logged engagement per deal. One-contact deals collapse the moment that person goes on leave, changes role, or leaves the company — a materially higher risk profile than multi-threaded deals.
7. Unowned or reassigned deals. Filter for hubspot_owner_id is unknown, or cross-reference owner-change history for deals reassigned in the last 30 days. Reassigned deals lose institutional context and stall at a measurably higher rate immediately after handoff.

Bring the seven diagnostics together into a single scorecard, with explicit thresholds for healthy, warning, and critical. These thresholds are starting points calibrated to a typical 60–90 day mid-market sales cycle; adjust to your own historical cycle length.

The single most common false signal in pipeline health analysis is treating hs_lastmodifieddate as evidence that a deal is active. This field updates whenever any property on the record changes — including automated lifecycle stage transitions, lead-scoring recalculations, workflow enrollments, and integration syncs. A deal can show a modification timestamp of "this morning" while having had zero human contact with the buyer in six weeks.

hs_last_sales_activity_timestamp is the more reliable field, because HubSpot updates it specifically in response to logged sales engagement: calls, meetings, and two-way email activity associated with the deal or its contacts. Even this field has edge cases — a rep logging a one-line "checking in" email registers the same as a substantive discovery call — so the strongest practice pairs the timestamp check with a light content review for deals flagged as warning or critical.

A pipeline health scorecard identifies which deals need review. The deal review itself is where the health claim gets tested against reality. Structure it around evidence, not opinion.

• What was the last thing the buyer said or did? Require a direct quote or paraphrase from the most recent interaction, not a general status update.
• Who else at the account knows this deal is happening? If the answer is one name, the deal is single-threaded and should be flagged regardless of stage.
• What specifically has to happen before this closes, and by when? A vague "just waiting on legal" without a named contact and a follow-up date scheduled is not a credible next step.
• Why did the close date move? Every close-date change should require a one-line reason logged as a note, timestamped and attributed, so the pattern is visible in a future audit rather than silently overwritten.
• Would this deal survive being re-qualified from scratch today? If the honest answer is no, it should move to closed-lost this week, not linger for another forecast cycle.

Making close-date changes visible is a small process change with outsized effect: require reps to log a note any time they edit closedate, and surface a report of all close-date changes from the last 30 days in the weekly pipeline review. Deals with multiple undocumented pushes should be the first item on the agenda, not an afterthought.

Consider a mid-market SaaS sales organisation with $4.2M in open pipeline across 118 deals heading into quarter-end. On paper, against a $1.1M remaining quota gap, that is a comfortable 3.8x coverage ratio. Running the seven diagnostics against the same 118 deals tells a different story.

After removing overlap — many deals fail two or three diagnostics simultaneously, most often a past close date paired with no recent activity — the non-credible total comes to roughly $610,000, or 14.5% of the headline $4.2M. Once that amount is excluded, real coverage against the $1.1M gap falls from 3.8x to 3.3x: still workable, but a materially different starting position for the forecast conversation than the headline number suggested.

The more important output isn't the percentage — it's the list of 42 named deals (some overlapping across diagnostics) that now have a documented reason to be reviewed this week, rather than surfacing as a surprise miss six weeks from now when the quarter closes.

Pipeline health decays continuously, not at quarter boundaries, so the review cadence has to match. A weekly ritual, run consistently, catches decay while it is still cheap to fix.

1. Minute 0–5: Pull the four saved views. Past close dates, no activity in 7+ days, close-date pushed this week, and unowned/reassigned deals. These should be saved HubSpot views, not rebuilt from scratch each week.
2. Minute 5–12: Triage by value. Sort each view by amount descending and focus attention on the top 20% of dollar value first — this is where a false-credible deal does the most forecast damage.
3. Minute 12–18: Assign owners to fix. For each flagged deal, the manager either requires the rep to log a next step within 48 hours or moves the deal to closed-lost on the spot. No deal leaves the review in an ambiguous state.
4. Minute 18–20: Log the trend. Record the count and value of flagged deals week over week. A rising trend is an early warning that hygiene discipline is slipping before it shows up in a missed quarter.

Pipeline health is one of the five input categories behind knovaly's 0–100 Opportunity Score, alongside Renewals & Rebookings, Dormant Relationships, Win-Back Opportunities, and CRM Health. Within the pipeline health component specifically, the score weights the proportion of open pipeline value that clears all seven diagnostics against the proportion flagged as warning or critical, adjusted for how much of that flagged value sits in the current-quarter-critical window.

The output isn't a single abstract number for its own sake — it converts into a ranked list of deals, sized by dollar amount, with the specific diagnostic failure attached to each. A revenue leader can go from "our score dropped four points this month" to "here are the eleven deals responsible, and here is what to ask about each one" in the same view, which is the difference between a health metric that gets glanced at once a quarter and one that actually changes Monday-morning behaviour.