Dormant customers: how to find and reactivate them

The word gets used loosely, which is the first problem. Before building any list or writing any outreach, it's worth separating four populations that all look similar on a pipeline report but need entirely different treatment.

Every revenue leader intuitively knows reactivation is cheaper than acquisition. The useful exercise is putting rough numbers against exactly how much cheaper, because that's what justifies allocating a rep's time to a list of quiet accounts instead of another batch of outbound.

The mechanism behind the gap is straightforward: a dormant customer has already been through procurement, already trusts the product enough to have paid for it once, and already has internal champions who know how to buy from you. None of that has to be rebuilt. The cost that remains is almost entirely the cost of finding the account, working out what changed, and writing one relevant message — which is a research and attention problem, not a demand-generation problem.

This is also why dormant revenue tends to be invisible on a standard pipeline report. It has no open deal, so it doesn't show up in forecast; it has no active campaign membership, so it doesn't show up in marketing attribution; and it isn't flagged as churned, so nobody's retention metric catches it either. It sits between reports, which is precisely why it accumulates.

Treating every dormant account the same — one list, one email, one send — is the single most common reason reactivation programmes underperform. A £180,000 account that went quiet eight months ago and a £4,000 account that went quiet two years ago need different owners, different channels, and different expected outcomes. Segment on three variables: recency of last activity, historical account value, and depth of prior engagement.

Those ranges are deliberately wide and should be treated as planning bands, not commitments — actual response depends heavily on category, prior relationship quality, and how well the message references what genuinely changed. Their purpose is to set expectations before the programme starts, so a 9% reply rate on tier 4 isn't mistaken for programme failure when it's actually within the expected band for that tier.

None of this requires custom development — it's four active lists built on standard and near-standard properties, refreshed automatically as accounts age into or out of each tier.

1. Base dormant filter. Start every list with lifecyclestage is customer, hs_last_sales_activity_timestamp more than your threshold days ago, and no open deal in dealstage.
2. Value split. Add a total_revenue filter to separate top-20%, middle-50% and bottom-30% bands — pull the actual percentile cut points from a quick export rather than guessing round numbers.
3. Recency split. Layer a second date filter on hs_last_sales_activity_timestamp to separate the 3–6/6–18/18+ month bands within each value band.
4. Engagement depth. Where available, filter on number of associated contacts or historical deal count to distinguish accounts with a known champion from single-touch accounts — this determines whether email alone is sufficient or a call is warranted.
5. Owner routing. Use hubspot_owner_id to keep tier 1 and tier 2 with the original account owner where that person is still active; reassign to a pooled reactivation owner only for tier 3 and tier 4.

Once the lists exist, the outreach itself is where most programmes either land or collapse. The architecture below applies across all four tiers — what changes by tier is who sends it and how many touches it gets, not the structure of the message.

• Mass "just checking in" blasts. A single templated email to the entire dormant list, sent from a generic alias, with no reference to what the account actually bought, reliably produces reply rates in the low single digits and trains recipients to ignore future outreach from the same domain.
• Discount-first offers. Opening with "come back and save 20%" signals that price was the only thing keeping the relationship alive, invites a negotiation on every future renewal, and compresses margin on revenue that a well-framed message would have recovered at full value.
• Treating all four categories as one list. Sending a dormant-customer message to a never-bought lead, or a lapsed-renewal message to a churned account, signals that nobody looked at the account before reaching out — which undermines the entire premise of a relevant, specific message.
• Assigning reactivation with no capacity. Adding "reactivate the dormant list" to a rep's existing workload with no protected time or account cap predictably results in the first fifteen accounts getting attention and the remaining two hundred never being touched.

Consider a mid-market services business with 240 accounts flagged dormant after applying a 150-day silence threshold across hs_last_sales_activity_timestamp. The tiering split out as 22 tier-1 accounts, 41 tier-2, 96 tier-3, and 81 tier-4, with combined historical total_revenue across the base of roughly £2.9 million.

A reactivation programme should be tracked with the same rigour as new-business pipeline, using metrics that show whether the list is actually being worked, not just whether it exists.

Tag every reopened deal with a distinct source or campaign value so recovered revenue never gets folded back into general pipeline reporting — if it isn't tagged, the programme's actual return becomes invisible within a quarter, and the case for repeating it disappears with it.

A one-off reactivation push recovers a backlog; it doesn't stop the next 240 accounts from going quiet in eighteen months. That requires a standing ritual, not another project.

1. Assign a dormancy owner. One person — typically a RevOps or customer success lead — owns the dormant-list definition, the threshold settings, and the monthly review, independent of whoever executes outreach.
2. Review the lists monthly, not quarterly. Accounts move between tiers as they age; a monthly review catches tier-1 accounts before they age into the much lower-response tier-2 band.
3. Add a renewal-gap alert. Flag any account where recent_deal_close_date plus the expected renewal interval has passed with no new deal created, so lapsed renewals are caught within weeks rather than discovered in a periodic audit.
4. Make ownership explicit at handoff. When a champion leaves an account or an owner changes in hubspot_owner_id, trigger a check-in task rather than letting the relationship go quiet by default.

Done consistently, this shrinks the dormant population over time instead of letting it rebuild to the size that made the original reactivation project necessary.