How Do You Find Job Change Signals in Clay?

How do you find out when your past customers change jobs?

Put the people who already know and like your product into a Clay table with their LinkedIn URLs, then turn on Clay's job change monitoring. Clay checks those profiles on a schedule you set and flags people who move. You then filter the movers to companies that fit your ideal customer profile and reach out while the switch is fresh.

This tutorial is for one specific reader: a B2B team with a few years of happy customers and champions in its CRM, and no system for noticing when those people move to new companies. Every week, someone who already trusts your product starts a new job somewhere, and nobody on your team finds out until it is too late.

Job changes are one of the few outbound signals I trust by default. The person knows you, has seen your product work, and is often building a new stack in their first months. This is how I set the system up for clients.

Who should go into the job change list?

Include people who have a reason to remember you well: champions on closed won deals, active users at current customers, and strong contacts from deals you lost on timing rather than fit. Leave out cold contacts who never engaged. A smaller list of people who know you produces far better signals than a large list of strangers.

Start in your CRM. Export contacts associated with closed won deals, plus anyone tagged as a champion or power user. If your CRM does not track those roles, ask your account managers to mark the people they would happily hear from again.

Lost deals deserve a careful look. A buyer who loved your product but lost an internal budget fight is an excellent person to watch. Their next company may not have the same constraint.

Keep the list honest. Including everyone inflates your signal volume and your costs without improving results.

What data does each row need?

Each row needs the person's LinkedIn profile URL, because Clay's documentation says the table must contain the contact's LinkedIn URL as an identifier. Also include their name, current company, email, and a CRM record ID, so you can match any change back to the right record later. Clean, complete rows make every later step easier.

If your CRM lacks LinkedIn URLs for many contacts, fill that gap first. Enrichment providers can often suggest a profile URL from a name and company, but check matches by hand for your most important contacts. A wrong profile means you will be watching the wrong person.

The CRM record ID matters more than people think. When someone changes jobs, you want to update the right contact in your CRM, not create a duplicate. Keeping the ID in the table makes that match reliable.

If you are new to building Clay tables, my walkthrough on building a Clay table to find the right contact covers the basics of sources and columns.

How do you turn on job change monitoring in Clay?

In Clay, click Actions, then select Monitor for job changes, and choose the table of contacts you want to watch. Set how often the signal should run. Clay's documentation describes an optional initial check that adds rows when current company data already differs from your records, which helps catch people who moved before you started.

Turn on the initial check the first time. It surfaces people who have already moved since you last updated your CRM. In an older customer base, that first batch can be the most valuable list you build all year.

Choose the frequency based on how fast you can act. If your team only reviews signals weekly, running checks more often does not help much. Match the schedule to your follow-up rhythm.

Watch the cost. At the time of writing, Clay's documentation says each check consumes 1 action plus 0.2 data credits. Multiply that by your list size and frequency before you switch it on, and check Clay's current documentation, since pricing details can change.

How do you filter job changes to the ones worth acting on?

Enrich the new company for each mover, then filter against your ideal customer profile: industry, size, region, and any must-have technology or team. A champion who moves to a company you cannot serve is a nice note to send, not a sales opportunity. Only movers who land at good-fit companies should go to sales.

Add a column that labels each mover as "sales opportunity," "relationship only," or "ignore." Sales opportunities go to a rep. Relationship-only movers might get a friendly congratulations from their old account manager. Ignore covers false positives and poor fits.

False positives happen. A title change at the same company, or an updated profile without a real move, can look like a job change. Review the first few batches by hand until you trust the pattern, and add a rule that checks whether the company actually changed.

How do you send job change signals to your CRM and sales team?

Push qualified movers into your CRM with the new company, new title, and a clear source label, then alert the right rep. Update the existing contact record rather than creating a new one where your setup allows, and create a task or deal so the follow-up is tracked. A signal that sits in a spreadsheet does not become pipeline.

Ownership matters here. Decide whether the mover goes to the rep who owns the new company, the rep who worked with them before, or a dedicated person for these signals. Write that rule down, or two reps will both reach out.

Also update the old account. If your champion has left a current customer, that account just lost its internal advocate. Flag it for the account manager. I covered what to do in that situation in what to do when your champion leaves mid-deal.

What should the outreach say?

Keep it personal and short. Congratulate them on the new role, mention one specific thing from your work together, and ask a light question about their new priorities. Do not pitch in the first message. The person already knows what you do. What they need is a reason to talk, not a product tour.

The best job change messages come from someone the person actually worked with. If their old account manager or a founder sends the note, it reads as a relationship. If a stranger from your team sends it, it reads as automation.

Timing helps, but do not rush. People in the first days of a new job are overwhelmed. A message in the first few weeks, framed around helping them settle in, often lands better than one on day one.

How do you know if the system is working?

Track how many movers you detect, how many land at good-fit companies, how many conversations start, and how many become pipeline. Review those numbers monthly. If many signals are false positives or poor fits, tighten your list and filters. If good movers are not being contacted, fix ownership and alerts.

This system is not about volume. A handful of warm conversations each month from people who already trust you can be worth more than a large cold campaign.

If you are still deciding which tools belong in your outbound stack, my comparison of Clay or Apollo first for a seed startup covers that choice.

What should you do next?

Export your champions and closed won contacts with LinkedIn URLs and CRM IDs, build a Clay table, and turn on job change monitoring with the initial check. Enrich new companies, filter against your ideal customer profile, route qualified movers to the right rep, and send short, personal outreach from someone they know.

Run it for a quarter and judge it by conversations and pipeline, not by how many signals it produces.

If you want help building job change tracking, enrichment, and routing into your GTM systems, reach out. I build these workflows for B2B teams and I am happy to look at your setup. Let's chat.