Pivix Logo
Back to glossary

Dead Lead

A dead lead is a prospect who is highly unlikely to ever convert, whether due to poor fit, no response, or an explicit no, and is no longer worth active pursuit.

Key takeaways

  • A dead status without a reason code cannot be reviewed or reversed later.
  • Hard reasons end the record; soft reasons only close it for now.
  • Pipeline-volume incentives discourage reps from marking anything dead at all.
  • Suppress rather than delete, so imports cannot silently resurrect the record.
  • A dead contact rarely means a dead company; people change jobs.

In depth

Dead is a terminal status written deliberately, not a state a record drifts into. It carries a reason code, and the code determines whether the record is truly finished or merely closed for now: a bounced address or a company that ceased trading is a hard end, while no budget this year or wrong contact is soft. Without that code, everything ends up in the same pile and nobody can tell which records could ever be revisited.

How much of the database goes dead depends on how strict the entry criteria were and how honest the team is allowed to be. Loose lead definitions produce a large dead pool later, since the disqualification happens downstream instead of at the form. Incentives push the other way: if reps are measured on pipeline volume, marking records dead looks like destroying their own numbers, so leads get parked as warm indefinitely and the true state is never recorded.

Operationally, dead should mean suppressed rather than deleted. The record stays, marked as excluded from sending and from active reports, with the reason and the date attached, so a future import cannot silently resurrect it and a later enquiry from the same company arrives with its history intact. Where a qualification quiz includes a disqualifying answer, such as a company size outside your range, the status can be written at submission with the answer as the recorded reason.

Most dead labels describe the contact, not the company, and the distinction gets lost. The person who said no has left, and their replacement inherits a record marked never contact. Silence is the weakest reason of all, since it may only mean the email went to a filter. Retention rules bite here too: a suppression list has to keep enough data to honour an opt-out, which is a reason not to delete, but keeping full profiles indefinitely creates its own exposure.

Example in practice

Suppose a RevOps lead audits the CRM and finds 800 contacts with no activity in 12 months and disqualifying quiz answers. They mark them dead, removing them from the active nurture and sales reports, which would lift the team's measured lead-to-opportunity rate from 4% to a more honest 9%.

How to measure it

The useful view is the reason mix: dead records grouped by reason code as a share of all disqualifications. A pool dominated by no response means the process is guessing; one dominated by out of target means the traffic is wrong upstream. Track the mix month by month, because a shift in it is an early signal that a campaign has changed who is arriving.

Then check the error rate of the decision itself. Sample dead records after six months and count how many later converted through another route or were re-engaged successfully. A resurrection rate above a few per cent means the criteria are too strict. Watch the disqualification point too: leads dying after a sales call cost far more than those filtered at the form.

Common mistakes

The first mistake is declaring a lead dead after a handful of unanswered emails. Non-response is a channel problem as often as a demand problem, and the record disappears while the company still has the need. Require either an explicit answer or a hard, verifiable fact, such as a bounced domain, before the terminal status is written, and route everything else to the cold track instead.

The second is deleting the records outright to tidy the database. The company reappears through a new form fill six months later, arrives with no history, and a rep repeats a conversation that already ended badly. Worse, an address removed from the system can be re-imported from a list and contacted again after opting out. Keep the row, mark it suppressed, and exclude it from reports rather than from existence.

Frequently asked questions

How do you know when a lead is truly dead?

Apply defined criteria such as repeated non-response across channels, an explicit no, or disqualifying facts like no budget or a bounced email. Relying on defined rules instead of a hunch prevents you from prematurely killing a lead that was only cold.

Can a dead lead ever be revived?

Sometimes. Circumstances change, such as new budget, a job change, or a new initiative, so it can be worth keeping a record and re-evaluating later. A lead marked dead for fit reasons, however, rarely comes back to life.

Why is marking leads dead good for reporting?

Disqualifying unworkable leads cleans your pipeline so metrics reflect real opportunities rather than inflated volume. This gives sales accurate conversion rates and lets the team focus its time on contacts that can actually close.

When should a lead be marked dead rather than cold?

Mark it dead when something rules the contact out permanently or for a stated period: an explicit no, a hard bounce, a company outside your criteria, or a legal opt-out. Use cold for silence and for anyone who might respond later. The test is whether you could write down the specific fact that ended it.

Should dead leads be deleted from the CRM?

Usually not. Suppress them instead, keeping the row with a reason and date, so imports cannot re-add them and any opt-out stays enforceable. Deletion is appropriate when a person exercises a data-erasure right or when retention policy requires it, and in that case keep only the minimum needed to honour the suppression.

Does marking leads dead hurt your reporting numbers?

It lowers the volume figures and improves every rate that uses them as a denominator, which is the point. Conversion rates computed against a database padded with unworkable records understate real performance and hide where the funnel is losing people. Agree in advance which reports exclude suppressed records so the change is not read as a collapse.

Can a dead lead ever come back?

Soft ones frequently do, when budget arrives, a contact moves on, or a requirement changes. Hard ones, such as a dissolved company or a formal opt-out, should not be revived at all. That is exactly why the reason code matters: it separates the records eligible for a future recycling programme from the ones permanently out of scope.

Who should have the authority to mark a lead dead?

Whoever holds the evidence, with the criteria written down so the decision is not personal. Reps can disqualify on an answer they heard, and automated rules can disqualify on a bounce or a disqualifying form answer. What causes trouble is one person clearing a queue in bulk without recording why, because that removes records nobody can audit afterwards.

How can a quiz reduce the number of dead leads?

It moves disqualification earlier. If a question asks about company size, budget range or timeline, respondents outside your criteria are identified at submission rather than after a sales call, and the answer becomes the recorded reason. The pool does not shrink, but it stops consuming sales time, and the reason mix becomes accurate enough to act on.

Related terms

Turn glossary theory into qualified leads

Build a scorecard quiz funnel that qualifies and captures leads in minutes — no code required.

Start for free
  • No credit card
  • Free plan
  • Launch in minutes