# Track job changes: catch champions when they move companies

> Re-check your customers and champions on a schedule, spot when someone changes company, and turn the move into a warm lead.

Source: https://www.b2benrich.com/guides/job-change-tracking  
Author: Dag Holmen, B2Benrich · Updated 2026-10-28

When a champion leaves one of your customers, two things happen at once. The customer loses the person who pushed for your product, and that person lands somewhere new, already knowing what you do. Job change tracking catches both moments, so sales can follow the champion to the new company and customer success can protect the account they left.

You build it as a scheduled job: store the LinkedIn URLs of the people who matter, re-check them, compare their company with what you stored, and act when it changes. This guide walks through the job, then covers the reverse case: new people joining accounts you already have.

## Decide who to track

Track the people whose move you’d act on:

- **Champions** at current customers: the person who brought you in, and the admin who runs your product.
- **Buyers** who signed, at customers and at former customers who left on good terms.
- **Fans from lost deals.** Someone who liked you but lost the internal vote may win it at the next company.

For each one, store the `linkedin_url`, the B2Benrich `id`, `company_domain`, `company_name`, `job_title`, the account they belong to and the date you last checked.

## Build the baseline

Run each LinkedIn URL through `/v1/enrich/person/linkedin-to-person` once and save what comes back. Keep the `id` as well. If someone changes their profile URL, you can still look them up with `/v1/enrich/person/get-by-id`. The [people enrichment API guide](https://www.b2benrich.com/guides/people-enrichment-api) covers the full response.

## Pick a schedule

The schedule is yours. Monthly works for most lists. Weekly makes sense for champions at your biggest accounts, and quarterly is fine for a long tail of past contacts. B2Benrich is one plan, unlimited API usage for $500 a month with no credits, so how often you check is a question of noise and workload, not budget.

## Re-check and compare

Compare `company_domain` first, since names vary (“Acme”, “Acme Inc.”, “ACME Corp”). Fall back to `company_name` only when a domain is missing. A new title at the same company is worth storing too: a promotion can mean more budget for you.

When the company changes, the job finds a work email at the new domain, adds a phone number and creates two CRM tasks: one for sales, one for the CSM.

```python
import os, requests
from datetime import date

BASE = "https://api.b2benrich.com"
HEADERS = {"X-Api-Key": os.environ["B2BENRICH_KEY"], "Content-Type": "application/json"}

def post(path, body):
    r = requests.post(f"{BASE}{path}", json=body, headers=HEADERS, timeout=30)
    r.raise_for_status()
    return r.json()

def norm(value):
    return (value or "").strip().lower().removeprefix("www.")

def get_phone(person):
    # TODO: replace with the B2Benrich phone endpoint once it's documented.
    return None

def moved(stored, current):
    old, new = norm(stored["company_domain"]), norm(current.get("company_domain"))
    if old and new:
        return old != new and new not in ALIASES.get(old, set())  # rebrands, acquisitions
    return norm(stored["company_name"]) != norm(current.get("company_name"))

for c in db.tracked_contacts():
    current = post("/v1/enrich/person/linkedin-to-person", {"input": c["linkedin_url"]})
    db.mark_checked(c["id"], date.today())

    if not moved(c, current):
        if current.get("job_title") and current["job_title"] != c["job_title"]:
            db.update(c["id"], job_title=current["job_title"])
        continue

    found = post("/v1/enrich/person/name-domain-to-email", {
        "first_name": current["first_name"], "last_name": current["last_name"],
        "domain": current["company_domain"],
    })
    crm.create_task(
        owner=crm.owner_for(current["company_domain"]),
        title=f"{current['full_name']} is now {current['job_title']} at {current['company_name']}",
        email=found.get("email"), phone=get_phone(current),
    )
    crm.create_task(owner=c["csm"], title=f"{current['full_name']} left {c['company_name']}. Find the next champion.")
    db.update(c["id"], company_domain=current["company_domain"],
              company_name=current["company_name"], job_title=current["job_title"])
```

`db`, `crm` and `ALIASES` stand in for your own database, your CRM’s API and a map of old domains to new ones.

B2Benrich returns phone numbers, including mobiles and direct dials, so the task can carry a number as well as an email. The [phone number API guide](https://www.b2benrich.com/guides/phone-number-api) covers when a call beats an email. Before anyone sends, check the email as covered in the [email verification API guide](https://www.b2benrich.com/guides/email-verification-api).

## Avoid false alarms

- **Rebrands and acquisitions.** The domain changes but the person didn’t move. That’s what the alias map is for.
- **Side roles.** An advisor or board seat can show up as a current company. Check the title before you treat it as a move.
- **Timing.** Profiles can lag a move by weeks, or show it before the person starts. Treat the alert as a prompt to look, not proof.
- **Failed lookups.** If a URL stops working, retry with the stored `id` before you assume anything.

A person should glance at each move before outreach goes out. It takes seconds and saves you from congratulating someone on a job they took two years ago.

## Turn the move into a conversation

The person who knew the champion should send the first message, not a sequence. Give them a few weeks to settle in. Then keep it short: congratulate them, mention the work you did together at Acme, and offer something useful for the new role, without a pitch in the first line.

Before sales picks it up, check that the new company fits. Enrich it with `/v1/enrich/companies/domain-to-company`. A champion at a company far outside your market is still worth a friendly note, just not a sales cycle.

At the old account, the CSM task matters as much. Find who now holds the role with `/v1/search/company-employees` on the old domain, filtered by the same `job_function` and `job_level`, and reach out before the renewal.

## Catch new people at existing accounts

The same job works in reverse. On each run, search `/v1/search/company-employees` at every customer domain for the functions and levels that use or buy your product. Compare the `id` values with the ones you stored last time. Any new `id` is someone who joined, or whose role changed into the ones you care about.

A new VP in the team that owns your product deserves an introduction and an onboarding offer early, before they review the tools they inherited. To keep these contacts current in your CRM, see [CRM data enrichment](https://www.b2benrich.com/guides/crm-data-enrichment).

## Frequently asked questions

### How do I track when my customers’ contacts change jobs?

Store each contact’s LinkedIn URL and current company, re-check them on a schedule with /v1/enrich/person/linkedin-to-person, and compare the company_domain you get back with the one you stored. When it changes, create a task in your CRM.

### How often should I check for job changes?

Monthly works for most lists. Check champions at your largest accounts weekly and long lists of past contacts quarterly. Pick the cadence based on how quickly you can act on what you find.

### What should I do when a champion leaves a customer?

Two things. Have the person who knew them reach out at the new company once they’ve settled in, and have the account’s CSM find who now holds the role at the old company before the next renewal.

### How do I get a champion’s new email after they move?

Take the first name, last name and new company_domain from the refreshed profile and send them to /v1/enrich/person/name-domain-to-email, which returns a status and the email when it finds one.

### Can I find new people who join my customer accounts?

Yes. Search each customer’s domain with /v1/search/company-employees, filtered by the functions and levels you care about, and compare the person IDs with the ones from your last run. New IDs are new people to introduce yourself to.
