The Library
Practices

B2B data accuracy: how job changes make contact data go stale

How fast B2B contact data goes stale as people change jobs: the corrected math, how long since your last refresh really costs, and how often to re-verify.

/ / 4 min read /5 sections /Updated November 6, 2026
Line-engraving of a row of engraved office-door nameplates, one plate being ground blank and re-etched with a fresh name while a cyan-to-violet band lights only the few plates still current: B2B contact records go stale as people quietly change jobs.

B2B contact data goes stale mainly because people change jobs. If a typical contact stays four to five years with an employer, about 2 percent of a list moves every month, so a list not refreshed for six months has lost roughly 11 percent of its contacts and a year-old list about 21 percent. Profile lag adds a second gap: some movers have not updated their public profile yet, so even a fresh pull misses a few percent.

Why B2B contact data goes stale

Contact data goes stale because people change jobs, and the records do not change with them. A contact who moves takes their title, email, phone and buying authority with them. The record in your CRM keeps all four, now wrong.

How fast that happens depends on how long people stay. The US Bureau of Labor Statistics put the median tenure with a current employer at 4.1 years in January 2026, up from 3.9 years in 2024, and at 4.9 years for management and professional occupations, the group most B2B lists target. As a rough rule, if a typical contact stays four to five years, about 1.7 to 2 percent of a list changes employer every month. (Median tenure is not the same as the average turnover rate, so treat this as an estimate. Younger staff, startups and high-turnover industries move faster.)

Job changes inside the same company add to it: a promotion, a new team, a new territory. The person still works there, but the role you were selling to is gone.

The corrected math

The first version of this post, published in June 2024, said people change jobs every 2.73 years and that this works out to about 4 percent of contacts a month. It does not: 2.73 years is 32.8 months, and 1 divided by 32.8 is about 3 percent a month. The 2.73 figure also had no source. This version uses the BLS figures above and keeps the rest of the model, with the arithmetic fixed.

There are two separate gaps, and they add up differently.

Gap 1: people who moved since your last refresh. This compounds with time. The share of a list that has changed employer since it was last verified is 1 minus (1 minus the monthly rate) raised to the number of months:

Months since the list was verifiedAt 2% a monthAt 3% a month
35.9%8.7%
611.4%16.7%
1221.5%30.6%

Gap 2: people who moved but have not updated their public profile yet. This one does not grow without limit, because people do update eventually. The original model assumed half of movers update in the first month and 30 percent of the rest update each month after. At those assumptions, the share of a list in this gap settles at about 1.7 times the monthly rate: about 3.3 percent at 2 percent a month, 5 percent at 3 percent. That is what a fresh pull from public profiles misses even on the day it is made.

The original post also added up its month-by-month figures (2 percent, 3.4 percent and 4.38 percent) into a 9.78 percent "calculated" stale rate. Those figures are running totals, not separate amounts, so adding them counts the same people more than once. On the post's own assumptions, the stale share after three months was 4.38 percent, not 9.78.

Months since the last refresh
Contacts who have moved since the list was verified 2% a month 3% a month 5.9% 8.7% 3 MONTHS 11.4% 16.7% 6 MONTHS 21.5% 30.6% 12 MONTHS Bar height: 2 px per percentage point.
Share of a list that has changed employer since it was last verified, at 2 and 3 percent of contacts a month. Computed as 1 minus (1 minus the monthly rate) to the power of the months. The 2 percent case assumes a typical contact stays four to five years (BLS median tenure, January 2026).

What graph8 measured

When this post was first published, graph8's data showed that about 12 percent of contacts in a typical customer list were no longer at the company on file. On the model above, that is roughly a list that had gone four to five months without verification at about 2 percent a month (7.8 to 9.6 percent), plus about 3.3 percent of profile lag: about 11 to 13 percent.

A real list can drift above the model over time, for reasons the model leaves out:

  • People who never update their profile. The lag assumptions treat everyone as updating eventually. Some never do.
  • Internal role changes. The person is still there, in a role you no longer sell to.
  • Turnover above the median. Some industries and roles turn over much faster than the overall median suggests.

How often to refresh B2B data

The table above is the case for refreshing on a schedule rather than once a year.

  • Before every campaign. Re-verify the emails and phone numbers on any list right before it goes out. Bounces cost the sending domain, not just the contact.
  • The whole database, at least quarterly. A quarterly cycle keeps job-change decay near 6 percent between refreshes at 2 percent a month. An annual cycle lets it reach about 21 percent.
  • Company data on a longer cycle. Headcount, technology and funding change more slowly than people do.
  • Faster for high-turnover segments. Startups, younger roles and high-churn industries decay faster than the median.
  • Log every signal back to the record. Hard bounces, auto-replies that name a replacement, and wrong-number calls are free evidence of a job change. A contact who moved is a lead at the new company, not a record to delete.

For a wider list of causes and fixes, including duplicate records and form data, CIENCE's guide to data decay in B2B sales goes further.

How graph8 keeps records current

graph8 keeps one record per contact and per company, with duplicate checks. Firmographics, technographics and intent refresh on their own, and waterfall enrichment asks several data providers in turn until one returns a match. Each change to a record is logged with what changed, who or which agent changed it, and when, and enrichment results go to staging for review before they are written to the records. See graph8 data.

graph8 light-abstract closing band: the architecture, running.
Re-etched on a schedule

The name on the plate is always going out of date. Verify before each campaign, refresh the whole list at least quarterly, and log every bounce and wrong number back to the record.

Frequently asked questions

How fast does B2B contact data go stale?

Roughly 2 percent of contacts a month from job changes alone, if a typical contact stays four to five years with an employer (the US median was 4.1 years in January 2026, 4.9 for management and professional roles, per the Bureau of Labor Statistics). That compounds to about 11 percent in six months and about 21 percent in a year without a refresh. Industries and roles with higher turnover decay faster.

What is the ideal frequency for updating B2B account data to maintain accuracy for sales teams?

Re-verify any list right before it goes into a campaign, and refresh the whole database at least quarterly. At about 2 percent a month, a quarterly refresh keeps job-change decay near 6 percent between refreshes; an annual refresh lets it reach about 21 percent. Company data (size, technology, funding) changes more slowly than contact data, so it can run on a longer cycle.

Why is some contact data wrong even right after a refresh?

Because the sources lag the people. A data provider can only find a job change once it shows up somewhere: a public profile, a company website, a bounced email. Some people update their profile the week they move and some wait months, so a fresh pull still carries a few percent of contacts who have already left.

How do you know a B2B contact has changed jobs?

The signals are a hard bounce from a work address, an out-of-office or auto-reply naming a replacement, a changed title or employer on a public profile, and a phone number that now reaches someone else. Log each one back to the record, and treat a contact who has moved as a new lead at the new company rather than deleting them.