How to Track Dormant Accounts Before They Become Lost Accounts

A dormant account is one where meaningful activity has stopped. No back-and-forth emails. No meetings. No replies. The deal might still be marked open in the CRM, but nothing has moved in a while.

What counts as "a while" depends on your business. For a software agency with a three-month average sales cycle, an account with no activity in sixty days has gone quiet. For a firm with eighteen-month deal cycles, sixty days is just Tuesday.

A reasonable threshold is one and a half to two times your average sales cycle length. If your typical deal goes from first call to close in two months, an account with no movement in ninety days has drifted into dormancy. If deals take six months on average, adjust the window accordingly.

The important step is setting the threshold at all. That turns "this account has gone quiet" from a vague feeling into a CRM filter you can act on.

Most sales teams treat stale CRM records as if silence means no. It often does not.

B2B buyers go quiet for reasons that have nothing to do with disinterest. Budgets freeze. Internal priorities shift. Projects get deprioritized. Stakeholders change roles. A decision that was six weeks away in February might have been pushed to H2 by an unrelated internal reshuffle. An account that went silent in February because the CFO paused all new spend is not the same as an account that told you they went with a competitor.

Research consistently shows that 86 percent of B2B purchases stall at some point during the buying process. The majority of deals that go quiet are not dead: they are waiting for conditions to change. The probability of winning back a former customer is 20 to 40 percent. The average cold email to a net-new prospect gets a 1 to 5 percent reply rate. The math strongly favors working dormant accounts.

It also costs 5 to 7 times less to reactivate a dormant account than to acquire a new one. This changes how you should think about dormancy. A dormant account is an account where the context has not resolved yet. Treating it the same as a lost account means you will miss the moment when the context changes.

The first step is making dormancy visible. Most CRMs let you build saved views or apply filters. What you want is a list of accounts where:

That view shows you accounts stuck in a no-man's land: technically open, but not being worked.

If your CRM tracks last contact date at the company level rather than the deal level, use that instead. A deal marked "proposal sent" that has had no email activity in four months is using a status label that no longer reflects reality.

CRM data decay is usually thought of as contact information going stale. But deal statuses that no longer match what is actually happening are the same problem in a different form. The pipeline hygiene practice of auditing open deals catches this if you make dormancy part of the weekly review, not just something you notice when a deal has been open for a year.

• The deal is not marked closed won or closed lost
• The last logged activity was more than X days ago (your threshold)
• No open tasks are currently assigned

Not every dormant account deserves equal attention. These are the signals worth watching for:

A contact changed roles. A decision-maker who moved to a new company with a capital budget is a warm re-engagement opportunity. The relationship exists. The context exists. The only thing missing is a short note that acknowledges the transition.

A budget cycle reset. Most organizations start or restart budgets at the beginning of a fiscal year or a new half. January and July are common windows. An account that went quiet in October might be genuinely open to a conversation in February.

A new contact at the same company. A CTO who replaced the one who stalled your deal is not carrying the baggage of that previous conversation. A new stakeholder can be a real fresh start, not just a repeat approach.

An external trigger event. A funding announcement, a public expansion statement, a product launch, a merger, or a leadership change are signs that something inside the company has shifted. Any of these can unfreeze a buying situation that had been stuck.

Time elapsed. For some accounts, the signal is simply that enough time has passed. Six months in a fast-moving industry can mean an entire project cycle has come and gone. The person you spoke to last year may now have a new initiative that fits exactly what you do.

Trigger-based outreach, where you contact an account because a specific event just fired rather than on a generic schedule, achieves an 18 percent response rate compared to 3.4 percent for generic re-engagement messages. Context is not a nice-to-have. It is the variable that drives whether your message gets a reply.

This is the logic that relationship intelligence is built on: using context about people and companies, not just deal fields, to know when to reach out and what to say.

At a growing software agency, there might be twenty or thirty dormant accounts at any time. Trying to work all of them at once is not realistic. Here is a rough prioritization approach:

Deal value. An account that stalled on a $150,000 project deserves more re-engagement effort than one that was a $5,000 inquiry. That math applies even if both have been quiet for the same amount of time.

Recency. An account that went quiet four months ago is warmer than one that has been silent for two years. Newer dormancy is easier to revive because the original context is still fresher for both sides.

Known reason for dormancy. If you know why an account went quiet, use that information. "Budget freeze in Q1" is actionable when Q3 arrives. "Chose a competitor" is a different conversation. If you do not know why, that is worth finding out before crafting an outreach.

Quality of the last interaction. An account where the last meeting ended with "we will revisit this in the fall" is very different from one where the last email never got a reply. Both are dormant. One is warmer.

If your CRM supports custom fields or notes on deals, tagging dormant accounts by reason makes a real difference. A view filtered to "dormant, reason: budget timing" is a useful call list at the start of a new budget period. Without that tagging, you are making prioritization calls blind.

The goal is to get ahead of dormancy before accounts quietly become lost. The system does not need to be complicated. Three habits make a real difference:

Set a dormancy view as a saved filter. Every Monday, someone looks at the accounts that crossed the threshold this week. The goal is not to contact all of them immediately. It is to notice them before the list grows and becomes overwhelming.

Generate a triage task when an account hits the threshold. When an account crosses your dormancy window, create a task: review this account, then decide whether to re-engage, put it on hold, or close it. Forcing a decision is more useful than letting accounts accumulate silently under "open."

Log every re-engagement attempt regardless of outcome. If you send a check-in email and hear nothing back, log it. If you get a positive response, log that too. The activity trail is what lets you make better decisions on the next attempt and tells future team members what has already been tried.

The client retention CRM approach handles the accounts you are actively managing. Dormant account tracking handles the ones that have slipped. Both matter. The combination is what account health scoring surfaces at scale when you have enough accounts that manual monitoring becomes impractical.

For agencies with a lot of relationship-driven deals, the how to turn past clients into new revenue playbook picks up where dormant account tracking leaves off: what to actually do once you have identified which accounts to contact.

The most effective re-engagement messages are short and specific. They acknowledge the gap without over-explaining it and give a concrete reason why reaching out now makes sense.

Something like: "It has been a few months since we talked. We just wrapped a project similar to what you were exploring, and I wanted to see if the timing had changed on your end." That is enough. No lengthy recap, no apology for the gap, no pressure.

The more specific the message is to the original context, the better it performs. A generic "checking in" message tells the recipient you do not actually remember what you discussed. A message that references something real from the last conversation tells them you were paying attention. That difference matters in relationship-led sales, where the interaction style is part of what you are being evaluated on.

Sales leads, account managers, and founders at software agencies, consulting firms, and professional services businesses who have a CRM with open deals that are not moving and no systematic process for deciding what to do about them. Also useful for anyone who has tried to "clean up" the pipeline but is not sure whether to close or re-engage the accounts that have gone quiet.