When a Prospect Goes Dark: How to Handle It in Your CRM

Here is a scenario that plays out at nearly every B2B sales team before a quarterly business review.

You pull up the pipeline to prep, and something catches your eye: five deals clustered at "Proposal Sent" or "Demo Delivered," each carrying a close date in the current quarter. Combined pipeline value: over $150,000.

Then you check the Last Activity Date.

Three of those five show the last logged touch as 47, 53, and 61 days ago.

You ask the rep. They say they reached out last week. But there is no call log, no email note, no task completion. The CRM does not know anything about what happened in the past three weeks. And if you are honest about it, you have no real signal on whether those deals are alive, stalled, or dead.

This is the dark deal problem. It is one of the most common sources of forecast misses at small B2B sales teams, and the damage is specific: a pipeline that looks healthy because stages and dollar amounts are intact, but that carries deals nobody is actively working and nobody has officially written off.

Why Prospects Go Dark

Understanding the root cause matters because it determines how you handle the re-engagement, and it changes what belongs in your CRM note.

Most prospects go silent for behavioral reasons, not personal ones. A few patterns show up repeatedly:

Budget or procurement freeze. The evaluator wanted to move forward, but finance or leadership paused discretionary spending. The prospect does not have an answer yet, and admitting that feels awkward, so they go quiet rather than explain an internal delay they cannot control.

Champion changed roles or left. The person who was driving the evaluation is no longer the owner. Their replacement has no context on the deal and may not even know it was in progress. The deal is effectively orphaned inside the buyer's organization.

Internal priority shift. A larger initiative landed on the prospect's team. Your solution is still relevant, but it fell to the second page of the priority list, and that is where it will stay until the bigger project ships or stalls.

Decision avoidance. Some prospects find it genuinely difficult to say no. Going quiet feels less confrontational than declining explicitly. This is the most common pattern in smaller deals where there was real interest but not enough urgency to push a decision.

In each case, the prospect has not necessarily decided against you. They have deprioritized the decision. That distinction matters for how you re-engage, and for how you classify the deal in your CRM.

How Dark Deals Corrupt Your Pipeline Data

When a deal goes dark, your CRM does not know. The deal stays in its last-known stage with its last-entered close date. It counts as open pipeline. It contributes to your coverage ratio. It shows up in your forecast.

This creates a compounding problem. Every week a dark deal stays open, it adds weight to a forecast that does not reflect reality. A manager relying on CRM data to call the quarter is working with corrupted inputs, and the forecast miss that follows looks like a rep performance problem when the root cause is pipeline data that no one has updated.

Three things break at once when dark deals accumulate:

Stage labels stop reflecting reality. "Proposal Sent" may have been accurate 60 days ago. Today that deal might be dead, or it might be a real opportunity that needs one good re-engagement email. The stage label cannot tell you which.

Win rate and conversion data get polluted. If you close a deal as lost after it has been open for 90 days with no prospect activity, the 90 days of zombie time skews your average sales cycle and your stage conversion rates. The metrics understate real performance.

Rep time goes to the wrong places. If the CRM does not surface that a deal is dark, the rep may keep treating it as active, spending follow-up time on an account that is not going anywhere while a genuinely live opportunity gets less attention.

The fix requires two things: a clear inactivity threshold that triggers action, and a consistent logging protocol so the CRM captures what actually happens next.

Set Inactivity Thresholds by Stage

Not every deal stage has the same normal rhythm. A deal at "Qualified" should show buyer activity more frequently than a deal at "Legal Review," where delays of a week or two are expected.

A useful starting rule: treat a deal as dark when the gap between the last prospect-initiated response and today exceeds roughly half your average stage duration.

For example:

• 30-day average cycle: flag at 10 to 14 days without a prospect reply
• 60-day average cycle: flag at 21 to 30 days
• 90-day or longer cycle: flag at 30 to 45 days

The key phrase above is "prospect-initiated." An email you sent is not buyer engagement. A response from the prospect is. Your CRM should track both, but only the latter is a real signal that the deal is alive. Most email sync integrations log sent and received messages separately; make sure your activity reports distinguish between outbound and inbound.

If you have not already built automated inactivity alerts for your team, the stale deal alert setup guide covers the configuration steps in HubSpot, Salesforce, and Pipedrive. The threshold logic above is what tells the alert system where to draw the line.

Log the Re-Engagement Attempt Before You Send It

When a deal hits the inactivity threshold, the first operational step is to log the re-engagement outreach in the CRM before or immediately after you send it. Many reps do the opposite: they send the email, wait to see if it produces a reply, and then log it if the reply comes. Touches that produce no response often go unlogged entirely, which means the CRM shows a deal with no recent activity when in fact the rep has been trying for weeks.

A consistent note format for every re-engagement touch:

Re-engagement attempt [#1 / #2 / #3]
Date: [date]
Channel: [email / LinkedIn / phone]
Summary: [One sentence describing what you sent and the specific angle you used]
Response: No reply as of [date] / [Summary of what they said]

Add a custom deal property called something like "Re-engagement status" with values such as Active, Re-engaging, and Pending close. Update it when the deal enters this phase. This field does two things: it makes dark deals visible at a glance in a pipeline board view, and it gives you clean data for pattern analysis later.

Update the close date to a realistic re-engagement horizon at the same time. If the deal was originally closing this month, move the close date to 30 days out while re-engagement is in progress. A past-due close date with active re-engagement in the notes is more honest than an unchanged close date from two months ago.

Run a Three-Touch Sequence and Log Each One

A three-touch re-engagement sequence over two to three weeks catches most prospects who are recoverable. After three touches with no response, the probability of a successful re-engagement drops enough that closing the deal as lost is the right call. Experienced RevOps teams find that most late-stage replies, when they come, arrive on touches two through four, not touch one.

Touch one (Day 0). Direct and low-friction. Reference something specific from the last conversation, not a summary of everything discussed. Ask a simple, non-pushy question: "Has the timing shifted, or is this still something the team is working toward this quarter?" Short enough to read in 20 seconds.

Touch two (Day 7). Add a new angle. A relevant product update, a piece of content tied to a pain point they raised, something from their industry that connects to the problem you discussed. Keep it brief. The goal is to demonstrate that you are paying attention and that there is a reason to re-engage now, not just to remind them you exist.

Touch three (Day 14 to 21). The break-up email. Be direct: name what you are about to do. "I am going to assume the timing is not right and close this out on my side. If priorities shift, I am easy to reach." This email has a high response rate among deals that were genuinely still alive, because it creates real urgency where nothing else did. The prospect who wanted to buy but was waiting for the right moment often replies to this one.

Log each touch in the format above, immediately. If touch three produces no reply within five business days, move to the close-lost step.

Close as Lost, With the Right Reason Code

The most common failure mode at this point is leaving the deal open indefinitely. Reps resist marking something lost because it reduces their pipeline coverage number and feels like admitting defeat. But keeping a dark deal open is worse than closing it: it distorts the forecast, wastes future pipeline review time on non-deals, and skews your stage conversion data.

Close the deal as lost and use a specific reason code. If your closed-lost dropdown includes "Gone dark / no response," use it. If it does not, add it. Structuring your closed-lost reason field to distinguish "gone dark" from "lost to competitor" or "no budget" matters in aggregate: if 30 percent of your losses are prospect silence rather than competitive losses, that signals a different problem from the one your messaging is solving.

Once closed, the prospect is not gone. They remain in your CRM as a contact. Flag them for a re-engagement campaign at 90 days or at a relevant trigger (a new product launch, a job change they make, a timing signal you pick up). Closed-lost is a pipeline status, not a permanent end of the relationship. A systematic pipeline cleanup process keeps these closed records organized so nothing falls through for the second time.

How Auto-Captured Email Data Changes What You Can See

One practical challenge with the process above is that it requires the rep to notice when a prospect has gone quiet. In a pipeline of 20 to 30 open deals, that noticing often does not happen until the deal is already weeks past its inactivity threshold. The rep is focused on their active accounts. The dark deals just sit there.

This is where email thread auto-capture changes the picture. When a system continuously reads and syncs your rep's outbound emails and incoming replies, it knows when the last prospect response came in across every open deal, not just the ones the rep has been paying attention to. That data surfaces dark deals before the rep has noticed them.

The Company Brain takes this further: it reads the email thread context and drafts CRM updates for the rep to review before anything writes to the record. If the last three outbound emails on a deal produced zero replies, that pattern becomes a proposed "Re-engaging" status update and a suggested note, not a question that surfaces only at the quarterly pipeline review. The rep reviews the draft and approves or edits it; the deal gets its correct status without requiring the rep to manually dig through a sent folder and count days.

The result is a pipeline that reflects reality earlier, so re-engagement happens when recovery is still possible, not after it is too late.

Keep the Pipeline Honest

Dark deals are not a rep character flaw. They are a system problem: the CRM defaults to silence when buyer activity stops, close dates do not update on their own, and the re-engagement workflow lives in the rep's head rather than a logged process.

The operational fix is repeatable and straightforward: set inactivity thresholds by stage, log every re-engagement touch at the time it happens, run a defined three-touch sequence, and close as lost on a clear timeline when the sequence produces no response.

A pipeline that reflects reality does not just help with forecasting. It tells you where to direct re-engagement resources, it keeps win-loss analysis honest, and it stops your next pipeline review from becoming a debate about whether a five-month-old deal is really still in play.

Frequently Asked Questions

Why do prospects go dark after a demo or proposal?

Prospects go silent for behavioral reasons, not personal ones. The most common triggers are a shift in internal priorities, a budget or procurement freeze, a change in the champion's role or employment, and the genuine difficulty of saying no. Most dark deals are not dead outright but have become lower priority for the buyer, with no clear internal owner pushing them forward.

How long should I wait before closing a deal as lost when a prospect stops responding?

A useful threshold is roughly two times the average duration of your current stage without any prospect-initiated response. For a 30-day deal cycle, close it lost after 21 days of no two-way engagement. For a 90-day cycle, 30 to 45 days is reasonable. These thresholds are not punishments but a discipline that keeps your forecast honest and your active pipeline clean.

What should I log in my CRM when a prospect goes dark?

Log each re-engagement attempt as an activity with a short structured note: the date, the channel used, a one-sentence summary of what you sent, and whether you received any response. Add a deal property to mark the deal as Re-engaging or At Risk. If you close as lost, log the reason as Gone dark / no response so the pattern is visible in aggregate win-loss analysis.

Should I keep a ghosted deal open in my CRM?

No. A deal with no two-way prospect engagement for more than roughly 30 to 45 days should be closed as lost. Keeping it open inflates your pipeline, distorts stage conversion rates, and causes forecast misses. Close as lost rather than delete so the record stays in your win-loss history and can be reactivated if the prospect re-engages later.

How do I re-engage a prospect who stopped responding?

Run a three-touch sequence over two to three weeks. Reference something specific from the original conversation, add a new angle on touch two, and send a direct break-up note on touch three naming that you are closing the deal. That final email has a surprisingly high response rate because it removes ambiguity for the prospect. If all three touches produce no reply, close as lost and move to a long-term nurture track.