Twenty Percent of Your Contacts Change Jobs Every Year

I asked a sales manager how he finds out that a contact has left their company.

He said: they bounce.

That is the whole detection system. At most companies it is the whole detection system. You learn someone is gone by emailing them after they are gone.

The simple idea

About one in five business contacts changes job in a year.

Your CRM does not know. Nobody at the other company emails you about it. The record just sits there looking correct.

So your database rots at a steady 20% a year, silently, and the only alarm is a bounce.

How it shows up

One manager we work with owns about 2,000 contacts.

Twenty percent of 2,000 is 400 records going wrong every year. Call it 400 records that need a human to open them.

Each fix takes 5 to 15 minutes. Check LinkedIn. Find the replacement. Guess the new email format. Update the CRM. Reload the sending tool. Put the person back in the campaign.

That is somewhere between 33 and 100 hours a year of a salaried person retyping things that a computer already knows.

And the cleanup is the cheap part. The expensive part is the season you spent emailing people who were not there.

It gets worse when the record is not obviously broken. In one CRM we looked at, 181 companies had zero contacts attached to them. The contacts existed. They were filed under a personal Gmail address, or under a regional subdomain instead of the main company domain. The data was in the building. The join was broken.

What we found

Here is the part that changed how I think about this.

A job change is a signal, not a chore.

When a contact leaves, two things happen at once.

Someone who already knows you and already likes your product now works somewhere new. That is the warmest lead you are going to get this quarter, and it walked in for free.

At the same time, their old seat has a new person sitting in it. New people review the tools they inherited. Some of them get to pick again.

So one departure creates two openings. Most teams treat it as a data problem and delete the row.

The teams that log where people go end up building a referral list out of their own decay. Same event, opposite outcome, and the difference is whether anyone wrote it down.

How it works

The cheap version takes about a week to set up.

Check monthly, not never. Run your active contacts against a source that tracks current employer. Flag every mismatch. This is a scheduled job, not a project.

Write two rows for every flag. One for the person at their new company. One for the open seat at the old one. Route them to different plays, because they are different conversations.

Check emails before the campaign, not after the bounce. Validation up front costs a fraction of a cent. A bounce costs a rep fifteen minutes plus a little of your sending reputation.

Keep the history. Do not overwrite the old employer. A contact record showing three past companies is worth more than a clean one, because it tells you where this person has carried you.

None of that is clever. It is a scheduled check and two extra fields.

The reason it does not exist at most companies is not difficulty. It is that stale data never files a complaint. It just quietly makes every campaign a bit worse, and nobody can point at the moment it happened.

If you have never measured your bounce rate by list age, that is a twenty minute job and it usually surprises people.