Short answer: to find a contact’s new work email after a job change, you need three things in order. First, detect the move and capture the new employer. Second, resolve the address, either from a provider that re-identifies the person at the new company or from the company’s dominant email pattern. Third, verify the address with a validator before you send anything. Skipping step one means you never knew they moved. Skipping step three means your warmest first touch lands as a bounce.
That sequence matters because the common approach runs it backwards. Someone notices a bounce, guesses a pattern, sends again, and hopes. By then the move is months old and the window has closed.
What happens to a work email when someone changes jobs?
The old mailbox is deactivated, usually within days to a few weeks of the person’s last day, and the address stops being a usable contact point. Some companies forward to a manager, some reject hard, and some accept quietly into a mailbox nobody reads. All three outcomes look the same from your side of the wire: your messages stop reaching the human.
This is the mechanical reason your database decays. Roughly 2 to 3% of B2B contacts change jobs every month, which means a meaningful slice of your CRM email column is wrong at any moment. We covered the economics of that drift in CRM data decay. The point here is narrower: when a champion moves, the relationship survives and the address does not.
Why can’t you just wait for them to email you?
Because almost nobody does. Only about 6% of customer contacts tell a vendor they changed jobs. The other 94% simply move on, and the first evidence you get is a bounce notification six weeks later from a sequence that should never have been running.
That asymmetry is the whole problem. The person who moved still remembers you, still knows your product worked, and often has budget and a mandate to change things at the new company. Champion-sourced deals close with a 2.7x higher probability and in roughly half the sales cycle. You lose that not because the relationship cooled but because you lost the mailing address.
How do you find the new work email, step by step?
1. Detect the move before you need the address
You cannot look up an email at a company you do not know about. Detection comes first, and it is the step most teams skip because it is the one you cannot do by hand. Manually checking thousands of contacts for job changes does not scale and never stays current.
Automated job change detection watches every contact in your CRM continuously and writes the move into the record: who moved, from which company to which company, their new title, and which rep or CS owner held the original relationship. That record is your lookup key. Without it you are not finding a new address, you are archaeology.
2. Resolve the address from the new employer
Once you know the destination company, there are two honest paths to the mailbox.
The better one is a provider that re-identifies the same human at the new company and returns the current work address. Match rate through the move is the metric that matters here, not raw coverage. A dataset can claim to have a hundred million profiles and still fail to connect “Sarah at Acme” to “Sarah at NewCo.” If you are evaluating vendors, that is the question to press on, and it is the axis we break down in choosing a people data API.
The fallback is pattern inference. Most companies use one dominant format across the whole domain, so if you know two or three real addresses at the destination you can usually infer the rest.
| Pattern | Example | Notes |
|---|---|---|
| first.last | [email protected] | Most common at mid-market and enterprise |
| firstlast | [email protected] | Common at smaller and newer companies |
| flast | [email protected] | Frequent in finance, legal and healthcare |
| first | [email protected] | Startups and very small teams only |
| first_last | [email protected] | Rarer, but persistent where it exists |
Two cautions. Acquired subsidiaries often keep a legacy domain, so check which domain the person’s own team actually uses. And common names collide, which is how sjones@ reaches the wrong Jones. Pattern inference is a hypothesis, never a confirmation.
3. Verify before you send
Never send an inferred address cold. A bounce on your first touch after a job change costs you twice: you miss the warmest message you will send all quarter, and you hand your sending domain a penalty that degrades every other campaign you run.
Run the candidate address through a validator first. A verification pass with a tool like Scrubby separates a real mailbox from a guess that happens to be syntactically correct, including the catch-all domains that accept everything and deliver nothing. This is the cheapest step in the sequence and the one that protects the other two.
4. Write the record back, both directions
Update the contact with the new company, new title, new verified email, and the detection date, and keep the old record linked so you do not lose the deal history that makes the relationship warm. Then route it twice: the arrival is a warm lead for the rep who owned the original relationship, and the departure is a churn warning for customer success, because the account the champion just left lost its internal sponsor. Both halves belong to the teams that own the number.
How accurate is guessing an email pattern?
Accurate enough to be tempting and wrong often enough to hurt you, which is the worst combination. Pattern inference tells you what the domain’s format probably is. It cannot tell you whether this specific mailbox has been provisioned yet, whether the person uses a nickname internally, whether two people share a surname, or whether the company moved to a new domain after an acquisition.
Treat it as a last resort rather than a method, and always follow it with verification. The reason detection plus resolution beats guessing is not that guessing never works. It is that guessing gives you no idea which of your guesses worked until the bounces come back.
When should you email someone at a new role?
As soon as you can confirm the move and verify the address, not weeks later. New leaders get evaluation windows and discretionary spend precisely because they are expected to change things, and their first 90 days are when they rebuild their stack. Arriving in week two with a short, genuinely personal note beats arriving in month four with a polished sequence.
What you write matters as much as when. Lead with the shared history and the new mandate, not the pitch. We have the actual copy in job change outreach email templates. When the reply lands, send a real calendar invite with something like Kali rather than volleying availability back and forth, because the momentum from a warm reply is short-lived.
Do you need a job change API for this?
You need one if you want the sequence to run on its own rather than as a manual research project per contact. The difference is whether a job change arrives as a task or as an event.
A manual process starts when someone notices a bounce, which means the clock started weeks ago. A job change API or webhook feed pushes the event the moment a move is detected, and the new address, once verified, lands in the CRM field your reps already look at. No app to install, no logins for reps, and it works across Salesforce, HubSpot, Pipedrive, Zoho and others. The how it works page walks through the flow end to end.
What does this look like at scale?
On a CRM of 10,000 contacts, roughly 20% surface as hot leads the day you turn detection on, about 2,000 relationships that have already moved, and then 200 to 300 new warm leads arrive every month as people keep changing jobs. That is the backlog of addresses that are currently wrong in your database, reframed as the queue that is currently warm.
Working that queue is also just better odds than prospecting. About 65% of a company’s business comes from existing customers, you have a 60 to 70% chance of selling into an existing relationship against 5 to 20% for a brand-new prospect, and it costs roughly 6x more to acquire a customer than to retain one.
Quick answers
- Where did my contact’s email go? Their mailbox was deactivated when they left. The address is dead even when it does not visibly bounce.
- Can I find a new work email without knowing the new company? No. Detect the move first, then resolve the address.
- Is pattern guessing safe? Only after verification. An unverified guess risks both the relationship and your sender reputation.
- How fast should I act? Same week. Budget and mandate peak in a new leader’s first 90 days.
- What should I store in the CRM? New company, new title, verified email, detection date, prior deal history, and the original relationship owner.
Where to start
The email address is the last mile, not the problem. The problem is that you do not know the move happened. Fix detection and the address becomes a lookup; leave detection broken and no amount of pattern cleverness will help, because you will always be reacting to a bounce instead of an arrival.
Because those leads convert, Champions backs the job-change signal with a contractual ROI guarantee: if champion-sourced revenue does not reach 2x your annual service fee, you are covered under our terms. Among the tools compared on the job change tracking landscape, only Champions offers that.
Want to see how many of your contacts have already moved and where they went? Book a demo and we will run detection against your CRM so you can watch the warm pipeline surface. Prefer email? Reach us at [email protected] and we will walk you through it.
