B2B data decays monthly. Plan for it.

B2B contact data decays because it describes people, and people move: industry estimates commonly put the rate at 2–3% a month, which compounds to somewhere between a quarter and a third of a database going stale within a year. You cannot prevent it, only build around it. A prospect list is a stock that leaks, not an asset you buy once.

Why does the data go stale?

Because every field in a prospect record is a snapshot of something that changes. People change jobs — the single biggest driver — and their mailboxes are retired behind them. Companies close, merge, rebrand and migrate email domains. Roles shift internally, so the address still works but the person no longer owns the number you are writing about. Even firmographics drift: the 8-person firm you filtered for is 30 people by the time you email, with a different buying structure.

None of this is a data-quality failure by any vendor or builder. It is the ordinary churn of an economy, ticking away underneath every list ever built — which is why decay handling is a standing part of The B2B Database Building Guide rather than a troubleshooting appendix.

How fast does it decay, and what does stale cost?

Precision is impossible and anyone quoting decay to a decimal place is selling something, but the commonly cited range — 2–3% a month — is consistent with what we see in practice. The cost arrives through two doors. The loud one is bounces: dead addresses that hard-bounce, and when bounce rates climb past the low single digits, mailbox providers downgrade your sending domain and even good emails start landing in spam. The quiet one is misses: the contact moved, someone new owns the number, and your correctly delivered email is read by the wrong person. Verification catches the first; only refresh catches the second.

What happens to a campaign that ignores decay?

Walk the timeline. A list is built and verified in January; it is loaded, unverified, in July. When six months have passed at 2–3% decay, roughly one record in eight is dead. When those records are sent to, bounces spike in week one. When bounces spike, deliverability drops for the whole mailbox — including sequences to live prospects already mid-conversation. The campaign underperforms, the list gets blamed, and the actual culprit was the calendar. Re-running verification before loading would have cost pennies per record.

How do you build refresh into the system?

The mechanism is a set of standing rules, not a rescue project:

1. Build in 60–90 day batches, sized to sending capacity rather than ambition — the arithmetic is in how many prospects you actually need. Small batches mean nothing sits long enough to rot.
2. Date-stamp every record's last verification. The field costs nothing and makes every later rule enforceable.
3. When a record's verification is older than about 60 days at load time, re-verify before sending. No exceptions for lists you built carefully — care does not slow the calendar.
4. When a send bounces or a reply says "no longer here", retire the record the same day and log the reason. A bounce is information; ignoring it is how the same damage repeats.
5. When the unsent remainder falls below 30 days of sending, trigger the next build. Refresh becomes a rhythm instead of a recovery.

Run these five rules and decay stops being a risk and becomes a line item — a predictable percentage rebuilt each quarter.

Can decay ever work in your favour?

Yes, and this is the part most firms miss. The same churn that kills records creates openings: a decision-maker new in post is reviewing suppliers, a just-funded firm is spending, a leadership change reshuffles every number's owner. Decay viewed from the other side is a stream of trigger events — readiness you can actually detect — and a list system that refreshes on a cycle is exactly the system positioned to catch them, because it is already looking.

Either way, the discipline is the same one that runs through the rest of the outbound playbook: treat the list as infrastructure under maintenance, not inventory in a warehouse.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.