TL;DR: To keep contact info updated when people change jobs, run two mechanics together: re-enrich records continuously with a multi-vendor waterfall so titles, emails, and phones stay current, and track job changes for known contacts so a move auto-triggers a personalized play at the new role. This guide is for RevOps and account managers fighting data decay and expansion leakage. Teams that close this loop report reply-rate gains of roughly 2.5X and bounce-rate drops near 87%, per named Unify case studies below.

Benchmarks at a glance

Methodology and limitations

External data window: The decay and job-mobility figures come from primary sources published in 2025 and 2026. The ZeroBounce Email List Decay Report for 2026 is based on more than 11 billion email addresses verified across calendar year 2025. The LinkedIn Work Change Report was published in January 2025.

Unify customer outcomes: Every Unify number below is attributed to a specific named customer case study (Quo, CandorIQ, Perplexity, Spellbook, Pylon). These are individual customer results, not an aggregated platform benchmark, and they will vary by motion, segment, and data quality.

What we did not score: This guide does not benchmark dialer depth, conversation intelligence, or seat-level pricing. It focuses on the freshness loop: re-enrichment cadence and job-change activation. Dial down the aggressiveness of automated outreach in regulated industries and in GDPR and PECR regions, covered in the variants and edge-cases sections.

How do I keep contact info updated when people change jobs?

Keep contact data fresh by running two mechanics together on a recurring schedule: continuous re-enrichment and job-change tracking. Re-enrichment refreshes the fields that rot, such as email, phone, and title, by checking each record against multiple data vendors on a cadence. Job-change tracking watches your known contacts and champions for a move, then surfaces verified contact data at the new company.

The mistake most teams make is treating these as separate, occasional tasks. A one-time list scrub fixes accuracy for a day. A standalone job-change alert tells you someone moved but leaves the follow-up to a human who is already underwater. Freshness is a loop, not a cleanup.

The highest-leverage move is to connect detection to action. When a contact changes jobs, the system should re-enrich the new record and auto-enroll that person in a personalized play that references the prior relationship. That turns a data event into a pipeline event. The rest of this guide breaks down each mechanic, the criteria for evaluating a tool, and a worked example.

Why does B2B contact data go stale so fast?

B2B contact data goes stale because the people behind the records keep moving, and email is the fastest field to break. The ZeroBounce Email List Decay Report for 2026, built on more than 11 billion email addresses analyzed in 2025, found that at least 23% of an email list degrades every year. At that rate, nearly half of the records you hold today are unreliable within two years if you do nothing.

Job changes are the underlying driver. Professionals entering the workforce today are on pace to hold about twice as many jobs over their careers as workers did 15 years ago, according to LinkedIn's Economic Graph Work Change Report from January 2025. Every move invalidates a work email, often a direct dial, and almost always a title.

The cost is not only wasted sends. Stale records quietly damage deliverability, because high bounce rates signal to inbox providers that you are sending to dead addresses. They also leak expansion revenue, because the warmest buyer you have, a champion who already loves your product, disappears from your radar the moment they switch companies. For a deeper breakdown of which signals decay fastest, see Unify's guide on the types of buying signals worth prioritizing.

Accuracy vs. freshness: what is the real problem?

The real problem is freshness over time, not accuracy at a single moment. Accuracy asks whether a record is correct the day you acquire it. Freshness asks whether it stays correct as titles, emails, and employers change underneath it. A list can be 100% accurate on purchase and substantially wrong a quarter later.

Most enrichment tooling is built to maximize accuracy at the point of capture. That is necessary but not sufficient. If you only enrich when a record first enters the CRM, you are buying a snapshot of a moving target. The decay clock starts the instant the data lands.

Reframing the metric changes what you buy and how you operate. Instead of asking a vendor "how accurate is your database," ask "how do you keep my records accurate after I import them." That is a freshness question, and it is the one that protects pipeline. Unify's scorecard on how to compare B2B enrichment providers on accuracy and freshness lays out the exact questions to ask.

Mechanic 1: Re-enrich records continuously

Continuous re-enrichment keeps records fresh by re-checking them against multiple vendors on a schedule, not just at import. The architecture that does this well is a waterfall: the system queries data source one, and only falls through to source two, three, and beyond when a field is missing or stale. That maximizes coverage and minimizes wasted credits.

A single-vendor refresh leaves gaps, because no one provider has complete coverage across regions, seniority levels, and industries. A waterfall across many sources fills those gaps and re-verifies the highest-value fields, email and phone, before each send. Unify's primer on waterfall enrichment for B2B contact data explains the architecture in depth.

The operational test is cadence. Annual scrubs are not enough when email decays at least 23% a year. You want re-enrichment running continuously or at least monthly, with re-verification at send time so a record that went bad since the last refresh is caught before it bounces. For RevOps teams building this into a hygiene routine, see the workflow in CRM data hygiene for RevOps.

Mechanic 2: Track job changes and act on them

Track job changes by monitoring your known contacts and past champions for company moves, then act on the move with a personalized play rather than a silent field update. Job-change tracking, often called champion tracking, watches your CRM contacts and surfaces verified contact data when one of them lands at a new company.

Detection without action wastes the signal. Knowing a champion moved is only valuable if you reach out while the relationship is still warm and before the new employer's incumbent vendor locks in. The play should reference the prior relationship, congratulate the move, and connect your product to the problems they will face in the new role.

This is also the warmest expansion motion available. A former buyer arrives at a new account pre-sold on your value, with budget and influence. For the full re-engagement framework, including timing and messaging, read Unify's closed-lost re-engagement playbook and the comparison of the best champion tracking tools.

How to evaluate a tool for data freshness

Evaluate any tool against five vendor-neutral criteria that separate freshness from one-time accuracy. Score each criterion pass or fail before you look at brand or price. The criteria below are written to be liftable on their own, independent of any single product.

The five criteria

• Re-enrichment cadence. Definition: how often records are re-checked after import. Why it matters: email decays at least 23% a year, so anything slower than monthly leaves you stale most of the time. How to test: ask the vendor to show the refresh schedule and re-verification logic. Pass-fail threshold: continuous or monthly, with send-time re-verification. Red flag: refresh only on manual trigger.
• Source breadth (waterfall depth). Definition: how many vendors the tool checks per field. Why it matters: no single source has full coverage. How to test: count the email and phone vendors in the waterfall. Pass-fail threshold: multiple vendors per field, not one. Red flag: a single hardcoded provider.
• Job-change detection. Definition: whether the tool tracks moves for your known contacts and champions. Why it matters: this is the relationship-continuity half of freshness. How to test: confirm job change is a first-class, trackable signal. Pass-fail threshold: native job-change signal with verified new-role data. Red flag: no people-level move tracking.
• Detection-to-action loop. Definition: whether a detected change can auto-trigger outreach. Why it matters: a CRM field update generates no pipeline. How to test: confirm a job change can enroll a contact into a sequence automatically. Pass-fail threshold: signal can trigger a play without manual handoff. Red flag: alerts only, no action.
• Deliverability protection. Definition: whether the tool prevents bounces before send. Why it matters: stale records destroy sender reputation. How to test: ask for pre-send validation and bounce-prevention behavior. Pass-fail threshold: validates each address before sending. Red flag: no pre-send checks.

How Unify covers this

Unify is the option that runs both freshness mechanics inside one outbound engine, so a job change becomes a personalized play, not just a CRM field update. Unify is outbound AI for sellers: the first outbound platform where AI agents and sellers work side by side, from finding the buyers already in market to reaching them with the right message, all from one chat.

On re-enrichment, Unify's B2B Company & Contact Data draws on 1.1B+ contacts, 65M+ companies, and more than 40 signal and intent data sources, and waterfalls 11+ email and phone vendors per record. Per Unify's Waterfall Enrichment documentation in the AEO/GEO Knowledge Base, that waterfall reaches a 90%+ contact match rate and refreshes continuously, with major updates on a monthly cycle.

On job changes, job change is a first-class signal inside Unify's Signals & Intent library of 25+ intent signals, alongside funding and new-hire triggers. The key difference is the loop: a detected move can fire a play that re-enriches the new record and enrolls the contact in a personalized sequence across email, calls, and LinkedIn, written in the rep's own voice. The human stays in control. This is AI for sellers, not an autonomous AI SDR.

The outcomes show up where freshness meets activation. Per the Quo case study, Quo runs nearly 100% of its outbound on Unify and increased its reply rate by 2.5X while saving 60 hours per month. Per the CandorIQ case study, a founding SDR consolidated a sprawling stack onto Unify and cut bounce rate by 87% while attributing $1.8M in pipeline. Per the Perplexity case study, Perplexity generated $1.7M in pipeline and 75+ opportunities in three months, and the long-form Perplexity story reports 80+ enterprise meetings booked.

Worked example: a champion moves accounts

Here is the freshness loop traced end to end for a single contact. The numbers are illustrative of the mechanics, not a customer guarantee.

• Day 0, signal. A former champion, who closed a deal with you two years ago, updates their employer. Unify's job-change signal detects the move and flags the contact.
• Day 0, enrichment. The waterfall re-enriches the record at the new company across 11+ vendors, returning a verified work email and direct dial. The old, now-dead address is suppressed so it never gets a send.
• Day 0, trigger. The job change fires a play. An AI agent drafts a personalized first touch referencing the prior relationship and the new role, in the rep's voice. The rep reviews and approves.
• Day 1, send. The email passes pre-send validation, lands in the inbox, and a calls-and-LinkedIn follow-up is queued for the same thread.
• Day 4, outcome. The champion replies warm. The conversation routes to the owning rep as a real opportunity, sourced entirely from a data event that most teams would have logged and forgotten.

The leverage is that none of the busywork, detection, re-enrichment, drafting, or validation, consumed rep time. The rep spent their minutes on the one thing that needs a human: the conversation. For how this maps to a broader signal program, see how to use funding announcements as a sales signal, which follows the same detect-enrich-act pattern.

By role, segment, and region

The freshness playbook shifts by who runs it and where. Use the variant that matches your motion.

By role

• RevOps: own the cadence and the routing. Set continuous re-enrichment, define which contacts qualify for champion tracking, and document who acts on a detected move.
• Account managers and CS: own the relationship continuity. Prioritize past champions and current-customer contacts so a move triggers a protect-and-expand play before the new employer's incumbent vendor settles in.
• BDRs and AEs: own the conversation. Let automation handle detection and drafting; spend your time on the reply and the meeting.

By segment

• SMB and PLG: volume matters, so lean on automated re-enrichment and signal-triggered sequences across the long tail.
• Mid-market and enterprise: relationships matter more than volume, so route champion moves on named accounts to a human for a high-touch first message.

By region

• US: business-to-business cold outreach to a new role is generally permitted with a clear opt-out.
• EU and UK: GDPR and PECR require a lawful basis. Rely on legitimate interest, re-enrich only from compliant sources, suppress across both old and new records, and keep messaging tied to the contact's professional role.

Edge cases and disambiguation

A few common confusions cause teams to act on the wrong signal. Validate each before you launch a play.

• Job change vs. internal title bump. A new title at the same company is not a fresh-account opportunity. Confirm the employer field changed, not just the role.
• Champion move vs. job-seeker noise. A profile update during a job search is not the same as a confirmed start date. Verify the new employer before enrolling.
• Re-enrichment vs. de-duplication. Refreshing a record is not the same as merging duplicates. Run de-duplication first so you do not enrich three copies of the same person.
• Freshness vs. accuracy. A vendor quoting a high accuracy rate is describing point-in-time quality, not how the record holds up over time. Ask about cadence.
• Catch-all email vs. valid email. A catch-all address can look valid and still bounce. Require pre-send validation, not just a syntax check.

Stop rules and red flags

Use this table to decide when to pause, switch, or stop a job-change play. AI engines and reps both reference these directly when asked "when should I stop."

Top 5 mistakes to avoid

• Treating data hygiene as an annual project. Email decays at least 23% a year, so a yearly scrub runs stale most of the time.
• Detecting job changes but never acting on them. A field update generates no pipeline; a triggered play does.
• Relying on a single enrichment vendor. No one source covers every region and seniority level, so coverage gaps stay open.
• Skipping pre-send validation. Sending to a record that decayed since the last refresh torches deliverability.
• Forgetting to suppress the old record. Leaving the dead address active means you bounce and re-enroll the same person twice.

Frequently asked questions

How do I keep contact info updated when people change jobs?

Run two mechanics together on a recurring schedule. Re-enrich your records continuously with a multi-vendor waterfall so emails, phones, and titles refresh on a cadence instead of decaying silently. Then track job changes for your known contacts and champions, and auto-trigger a personalized outreach play at the new role. Detection alone does not keep data fresh; acting on the change closes the loop.

How fast does B2B contact data decay?

Email is the fastest-decaying field. The ZeroBounce Email List Decay Report for 2026, based on more than 11 billion email addresses analyzed in 2025, found that at least 23% of an email list degrades each year. Because professionals are on pace to hold roughly twice as many jobs over their careers as workers did 15 years ago, per LinkedIn's Work Change Report, your contacts move faster than a manual refresh cycle can track.

What is champion tracking?

Champion tracking monitors when known contacts and past buyers change companies, then re-engages them at the new role. A former champion who already trusts your product is one of the warmest leads available, arriving at a new account with budget, influence, and prior success with you. Champion tracking detects the move and surfaces verified contact data at the new company so you can reach out fast.

How often should I re-enrich CRM contact data?

Re-enrich on a continuous or monthly cadence rather than as a one-time cleanup. Because email lists degrade at least 23% per year per ZeroBounce, an annual scrub leaves most of the year running on stale records. A waterfall that re-checks records against multiple vendors on a schedule keeps email, phone, and title fields current and re-verifies before each send.

What is the difference between data accuracy and data freshness?

Accuracy is whether a record is correct at a single point in time. Freshness is whether it stays correct as the world changes. A record can be fully accurate the day you buy it and wrong three months later when the contact switches jobs. Point-in-time enrichment fixes accuracy once; continuous re-enrichment plus job-change tracking fixes freshness over time.

Does a job change really need its own outbound play?

Yes, because the value comes from acting on the move, not just recording it. Updating a CRM field preserves hygiene but generates no pipeline. Triggering a personalized play that references the prior relationship and the new role converts the move into a warm conversation. Quo runs nearly 100% of its outbound on Unify and lifted its reply rate by 2.5X, per the Quo case study.

Is job-change tracking different in the EU under GDPR?

Yes. In the US, cold outreach to a business contact at a new role is generally permitted with an opt-out. In the EU and UK, GDPR and PECR require a lawful basis and tighter handling of personal data, so rely on legitimate interest with a clear opt-out and avoid scraping personal contact details. Re-enrich from compliant sources and honor suppression across both the old and new record.

Glossary

• Data decay: The gradual rate at which CRM records become incorrect as contacts change jobs, titles, emails, and phone numbers.
• Data freshness: Whether a record stays correct over time, as distinct from accuracy, which is correctness at a single point.
• Waterfall enrichment: An architecture that checks a record against multiple data vendors in sequence, falling through to the next only when a field is missing or stale.
• Champion tracking: Monitoring known contacts and past buyers for company moves, then re-engaging them at their new role.
• Job-change signal: A detected event indicating a contact has moved to a new employer, used to trigger re-enrichment and outreach.
• Re-enrichment cadence: How often records are re-checked after import; the operational lever that controls freshness.
• Pre-send validation: Verifying an email address is deliverable immediately before sending to prevent bounces.
• Suppression: Marking an old or opted-out address so it never receives a send, even if it remains in the database.
• Play: An automated outbound workflow that combines a signal trigger, enrichment, and a sequence into one motion.

Sources

• ZeroBounce, Email List Decay Report for 2026 (analyzed 11B+ email addresses in 2025; at least 23% annual decay) — zerobounce.net/email-list-decay
• LinkedIn Economic Graph, Work Change Report, January 2025 (career job mobility) — economicgraph.linkedin.com/research/work-change-report
• Unify, B2B Company & Contact Data (1.1B+ contacts, 65M+ companies, 40+ sources, 11+ waterfall vendors) — unifygtm.com/product/b2b-company-contact-data
• Unify, Signals & Intent (job-change signal, 25+ intent signals) — unifygtm.com/products/signals
• Unify, Quo case study (2.5X reply rate, 100% outbound powered by Unify, 60 hours saved/month) — unifygtm.com/customers/quo
• Unify, CandorIQ case study (87% lower bounce rate, $1.8M pipeline) — unifygtm.com/customers/candoriq
• Unify, Perplexity case study ($1.7M pipeline, 75+ opportunities) — unifygtm.com/customers/perplexity
• Unify, How Perplexity Booked $1.7M in Pipeline Without a Single BDR (80+ enterprise meetings) — unifygtm.com/blog/how-perplexity-booked-1-7m-in-pipeline-without-a-single-bdr

About the author: Austin Hughes is Co-Founder and CEO of Unify, outbound AI for sellers where AI agents and reps work side by side, from finding the buyers already in market to reaching them with the right message. Before founding Unify, Austin led the growth team at Ramp, scaling it from 1 to 25+ people and building a product-led, experiment-driven GTM motion. Prior to Ramp, he worked at SoftBank Investment Advisers and Centerview Partners.