TL;DR: Track two signals at target accounts, new hires moving into buying roles and past champions who changed companies, then auto-trigger outreach the moment either fires. Built for Sales, RevOps, and Growth teams without a large BDR bench. Unify customers running these plays report pipeline from $300K in 3 months (Anrok) to $40M annualized.

Key Facts at a Glance

Methodology and Limitations

Sources and window: Unify product figures are pulled from live Unify product pages and named customer stories, current as of July 2026. Customer outcomes (Anrok, Unify's own team) are self-reported by those companies and describe their full signal-driven outbound program, not New Hire and Champion Tracking in isolation, since most teams run several signal types together.

Where to dial this down: In regulated industries (financial services, healthcare, EU/UK), add a compliance review step before auto-sending to a new hire or former champion, and confirm your outreach basis is compatible with local opt-in rules before automating any part of this play.

What Counts as a Job-Change Signal at a Target Account?

A job-change signal is either of two events: someone new joining a target account in a buying-relevant role, or a past champion of yours leaving for a different company. Both are proxies for the same underlying moment, a person with budget influence who is actively re-evaluating tools and vendors because they just started a job.

New-hire signals answer the question "who just showed up in a seat I care about." Champion signals answer a different question: "who already trusts us, and where did they just land." Treating these as one undifferentiated bucket is the single most common mistake teams make when they start signal-based outbound, because the messaging, urgency, and starting trust level are completely different for each.

Unify's Signals library tracks job changes as one of the intent types feeding its real-time account feed, alongside website visits, product usage, and funding events, and surfaces both new-hire and champion movement from the same underlying data pipeline.

How Do You Track New Hires at Target Accounts?

You track new hires by defining the two or three titles that match your actual closed-won buyer profile, then watching your target account list daily for people entering those roles. The daily cadence matters more here than with almost any other signal, because the value of a new-hire signal decays fast: a new VP of RevOps is a much warmer prospect in their second week than in their tenth.

In practice this means three setup steps. First, pull your closed-won deals from the last 12 months and identify the actual titles and seniority levels that signed or championed those deals, not the titles you assumed would buy. Second, build a target account list, whether that's your full ICP or a named-account list for enterprise motion. Third, set the signal to daily refresh and route matches straight into enrichment so the new hire's verified work email is ready the moment the signal fires, since outreach to a stale or unverified address wastes the timing advantage you're trying to capture.

Per Unify's product documentation, its New Hire Tracking signal refreshes daily and can be filtered by title, seniority, industry, and location, then handed directly to Plays for automatic enrollment. Unify's contact layer backs this with a database of 1.1B+ people refreshed daily in partial batches, so a new hire's contact record is enriched rather than guessed at.

How Do You Track Champions Who Change Jobs?

You track champions by building a defined list of past product users, closed-won contacts, and active champions from your CRM, then watching that specific list for job changes rather than scanning the open market. This is why champion tracking starts from your own customer and contact history instead of a target account list: the "target account" is wherever your champion lands next, which you can't predict in advance.

A monthly refresh cadence is standard for champion signals, which is slower than new-hire tracking because a champion's move to a new company is a lower-frequency, less time-sensitive event than a new hire's first weeks on the job. What matters more than speed here is contact accuracy: you need a verified new work email at their new company, not their old, now-dead corporate address.

Per Unify's product documentation, Champion Tracking refreshes monthly, draws its audience from CRM objects, custom lists, or filter logic you define, and pairs each detected move with updated contact data at the champion's new company. Anrok runs exactly this combination inside its New Hires and Champions play, engaging both newly hired finance leaders at target accounts and past champions who changed companies, as part of the broader signal-driven program that generated more than $300,000 in pipeline in its first three months with Unify.

How Do You Auto-Trigger Outreach From a Job-Change Signal?

You auto-trigger outreach by connecting the signal directly to a workflow that enriches the contact and enrolls them in a sequence the moment the job-change event is detected, rather than routing it to a person's task list to action manually days later. The gap between signal detection and first touch is where most of the conversion advantage of job-change signals gets lost.

Unify runs this as a Play: the job-change signal fires, the contact is enriched against Unify's waterfall of email and phone vendors, and the contact is enrolled into a sequence written with context about the move, rather than a generic template. Unify's own growth team runs two to three signal-driven Plays a week this way, a combination of new-hire, champion, and website-intent signals that has driven $40M+ in annualized pipeline and cut time spent on warm outreach in half, per Unify's customer story on its own usage of the product.

Whether or not you automate the send itself, the enrichment step should never be manual. A new hire's or new-role champion's contact record needs to be current at the moment of first touch, which is a large part of why Unify pairs its signals with a 1.1B-contact database refreshed daily rather than a static list.

Why Do Job-Change Signals Convert Better Than Cold Outreach?

Job-change signals convert better because they reach a person during a short window when they are actively re-evaluating vendors, rather than interrupting someone with no stated reason to care. Signal-driven outbound overall gets 73% more replies than cold outreach, per Unify's own product research, and job changes are one of the higher-intent signal types feeding that lift.

There's a trust dimension specific to champion signals that new-hire signals don't have. A former champion already has a working relationship with your product and, often, with your team, and relationship equity built through direct engagement is difficult to replace with data and dashboards alone, per Harvard Business Review's reporting on B2B sales relationships. Losing track of a champion when they change jobs means starting that relationship over from zero at their new company, even though the trust already existed.

Stacking signals compounds this further. Per Unify's Signals product page, reply rates roughly double once a team layers four or more signals onto the same account, for example a new hire at a target account who also visited your pricing page. A single job-change signal is a good reason to reach out; a job-change signal combined with a second corroborating signal is a much stronger one. For a deeper breakdown of how different signal types decay and when to stop acting on a stale one, see Unify's guide to signal half-life.

What Should You Look for in a Job-Change Tracking Approach?

Evaluate any job-change tracking method, whether that's a manual process or a platform, against five criteria, independent of which vendor or workflow you end up choosing.

• Refresh cadence: Definition: how often the underlying data updates. Why it matters: a weekly or monthly refresh on new-hire data misses the highest-converting first few weeks. How to test: ask for the exact refresh interval per signal type, not a blended average. Pass-fail threshold: daily or near-daily for new hires, monthly is acceptable for champions. Red flag: "continuously updated" with no stated interval.
• Contact accuracy at the moment of trigger: Definition: whether the new work email and phone are verified when the signal fires, not pulled from a stale record. Why it matters: outreach to a dead address wastes the timing advantage entirely. How to test: check a handful of triggered contacts against LinkedIn manually. Pass-fail threshold: high match rate on verified business email. Red flag: contact data that's clearly still tied to the person's prior company.
• Audience definition flexibility: Definition: whether you can define "champion" or "target role" using your own CRM fields and filters. Why it matters: a generic title list produces false positives. How to test: try building a filter using a CRM field specific to your business. Pass-fail threshold: supports custom CRM-based audiences, not just a fixed title list. Red flag: only supports a small preset list of job titles.
• Trigger-to-action latency: Definition: how fast a detected signal can enroll a contact into outreach. Why it matters: same-day enrollment captures more of the receptivity window than a weekly batch job. How to test: ask whether enrichment and enrollment happen automatically or require manual export. Pass-fail threshold: automated hand-off from signal to sequence. Red flag: signal shows up in a dashboard only, with no workflow connection.
• Exclusion logic: Definition: whether accounts already in an active deal or recently contacted get automatically suppressed. Why it matters: without this, job-change plays duplicate outreach an AE is already running. Pass-fail threshold: built-in exclusion rules tied to CRM deal stage. Red flag: no way to exclude owned or in-flight accounts before a play fires.

How Unify Covers This

Unify covers all five criteria from inside one product rather than requiring a separate tool per criterion. New Hire Tracking refreshes daily and Champion Tracking refreshes monthly, per Unify's product documentation; both pull from a contact layer of 1.1B+ people with daily partial refreshes and an 11-vendor enrichment waterfall, so contact data is current when a signal fires, not stale. Audiences for Champion Tracking are defined directly from CRM objects, custom lists, or filter logic, and Plays connect any signal, including job changes, straight to enrichment and sequencing with built-in exclusion rules, so an account already in an active deal doesn't get a duplicate cold touch from an automated play. Sign up for Unify to see how new-hire and champion signals connect directly to a live sequence, from the same chat where you built the audience.

Which Job-Change Signal Should You Prioritize First?

• If you're a lean team with no dedicated SDRs, prioritize New Hire Tracking on your top 20 to 50 target accounts before building out champion tracking, since it needs less historical setup.
• If you have 12+ months of customer history with named champions who've since left, start with Champion Tracking, since your audience is already defined by your own CRM data rather than an open market search.
• If your average deal involves a buying committee of six or more stakeholders, run new-hire and champion signals together and multi-thread rather than betting on a single contact, since either one leaving stalls a single-threaded deal.
• If you're sales-led with named accounts on Salesforce, route job-change signals as real-time alerts to the owning AE instead of fully automating the first send, so the rep keeps the relationship context.
• If you're a marketing-led or PLG team without SDRs, automate the first touch on both signal types and route only engaged replies to a human for follow-up.
• If you sell into financial services, healthcare, or the EU, add a manual compliance check before auto-sending to either signal type, and confirm your outreach basis complies with local rules first.

What Does a Job-Change Signal Play Look Like End to End?

Anrok, a sales-tax compliance platform, runs its New Hires and Champions play as one part of a broader signal-driven outbound motion built in Unify. The play engages newly hired finance leaders at target accounts and separately re-engages past champions who moved to new companies, alongside website-visitor and lookalike plays run by the same two-person go-to-market team. Over the first three months, that combined signal-driven program generated more than $300,000 in pipeline and let the team build campaigns 20% faster than their prior HubSpot setup, per Unify's published Anrok customer story.

Here is an anonymized, illustrative version of how a single job-change signal typically moves through the workflow, based on the mechanics described above rather than one specific company's exact timestamps: a VP of RevOps is hired at a target account (Day 0, new-hire signal fires and the record is enriched with a verified work email); the contact is enrolled in a three-touch email sequence referencing the account's public growth stage rather than a generic congratulations (Day 1, first touch sent); no reply after touch one triggers a LinkedIn connection request as a second channel (Day 4); the contact opens the second email but doesn't reply, so a third touch shifts the angle from a product pitch to a specific, narrow question about their first 90 days (Day 9); the contact replies and books a call (Day 11). The mechanism, not the exact days, is what to replicate: fast enrichment, a message tied to the actual signal, and an angle change rather than a repeat if the first attempt goes quiet.

Role and Segment Variants

• BDR/SDR: Own daily triage of new-hire alerts on your assigned book; treat champion alerts on your named accounts as a priority interrupt, not a batch task.
• Account Executive: Ask for real-time Slack or CRM alerts on job changes tied to your open and closed-won accounts specifically, since a champion move inside your own pipeline is higher stakes than a market-wide signal.
• RevOps: Own the exclusion logic and CRM field mapping that defines "champion," and audit monthly for title-list drift on the new-hire filter so the signal doesn't degrade into generic prospecting.
• Marketing/Growth: Own the sequence copy and A/B test congratulations-style openers against a more direct, business-case opener; job-change plays are usually one of the highest-performing automated segments in a signal-based program.
• PLG motion: Weight new-hire signals higher than champion signals early on, since you likely have less closed-won history to build a champion list from.
• Enterprise / sales-led motion: Weight champion signals higher, and use new-hire signals primarily to open a second thread into an account you're already working, not just net-new logos.

Job Changes vs. Adjacent Signals: What to Watch For

• Internal promotion vs. new-company hire: A promotion at the same company is a weaker buying signal than joining a new company in the same role, since an internal promotion doesn't necessarily come with fresh budget authority or a mandate to change vendors.
• Champion moving to a competitor vs. a prospect: Confirm the champion's new employer isn't a company you're contractually restricted from approaching, or a direct competitor of yours, before enrolling them in outreach.
• "Open to Work" vs. a confirmed new role: LinkedIn's open-to-work status is not a job-change signal; wait for a confirmed title and company change before treating someone as a new-hire signal.
• Interim or contractor titles vs. permanent roles: An interim VP or fractional executive often lacks the standing budget authority a permanent hire has; deprioritize these relative to confirmed permanent hires.
• Stale or duplicate CRM records: A job-change signal on a contact who was already marked Closed Lost or Do Not Contact should route to a suppression check, not straight into a new sequence.

When Should You Stop or Adjust a Job-Change Play?

Common Mistakes to Avoid

• Treating every job change as equally warm: a junior lateral move and a VP external hire are not the same signal and shouldn't share a sequence.
• Not refreshing contact data at the trigger moment: outreach to a person's old company email defeats the purpose of tracking the move at all.
• Leading with a generic congratulations: a message with no specific context reads as automated and gets ignored.
• Running new-hire and champion plays through one undifferentiated sequence: a stranger and a past advocate need different opening lines and different levels of assumed trust.
• Skipping exclusion rules: failing to suppress accounts already in an active deal creates duplicate, conflicting outreach from an automated play and a human rep at the same time.

Frequently Asked Questions

What is a job-change signal in B2B sales?

A job-change signal is an alert that a specific person moved into a new role, either a new hire joining one of your target accounts or a past customer champion who left for a new company. Both versions point to the same underlying opportunity: a person in a decision-making seat who is reassessing their tools and vendors during the first months of a new job. Sales teams track job-change signals to reach people while that reassessment window is open, rather than waiting for a generic outbound cadence to catch up.

How is champion tracking different from new-hire tracking?

New-hire tracking watches your target accounts for people who just joined, usually filtered by title and seniority, so you can reach a fresh decision-maker before a competitor does. Champion tracking watches the other direction: it follows people who already know and like your product, typically past users or contacts from closed-won or active deals, and alerts you when they move to a new company. New-hire tracking finds strangers in the right seat; champion tracking finds advocates in a new seat.

How often should new-hire and champion data refresh?

New-hire signals benefit from a daily refresh because the highest-converting outreach window is the first few weeks in a role, so a week-old data feed can mean a missed window. Champion signals are typically refreshed monthly, since a former champion's move to a new company is a lower-frequency event and doesn't decay as quickly as a fresh hire's receptiveness. Per Unify's product documentation, its New Hire Tracking signal refreshes daily and Champion Tracking refreshes monthly.

Which roles should you monitor for new-hire signals first?

Start with the two or three titles that most closely match your closed-won buyer profile, not every hire at the account. Most teams filter by function and seniority, for example VP and Director-level hires in Finance, RevOps, or Marketing, depending on who actually signs off on your category. Monitoring too broad a title list dilutes signal quality and produces outreach that reads as generic rather than genuinely relevant to the new hire's first 90 days.

How fast should you reach out after a job-change signal fires?

Most practitioners treat the first 30 to 45 days in a new role as the highest-receptivity window, with day 45 to 90 still workable but requiring a more direct, business-case-driven message rather than a soft congratulations note. Reaching out in the first week is usually too early, since the person is still onboarding and hasn't identified their priorities yet. Waiting past 90 days means competing against whatever vendor decisions they've already started making.

Do you need dedicated software to track job changes, or can you do it manually?

Manual tracking is possible at small scale using LinkedIn alerts on saved leads and a shared spreadsheet, and that's a reasonable starting point for a handful of strategic accounts. It breaks down once you're watching more than a few dozen accounts, because manually checking for new hires and past-champion moves across a full target account list is a job in itself. Most teams that outgrow the spreadsheet move to a platform with native new-hire and champion tracking, such as Unify, so the signal, contact refresh, and outreach trigger live in one place.

Does job-change-triggered outbound work without a dedicated BDR team?

Yes. Job-change signals are one of the more common plays run by lean, product-led teams that don't have a dedicated SDR function, because the signal itself does the targeting work that a BDR would otherwise do manually. Unify's own growth team, for example, runs new-hire and champion signals as part of a broader set of intent signals that has driven over $40 million in annualized pipeline with a small team, per Unify's customer story on its own usage. The mechanics scale down to a single growth or RevOps generalist running a handful of automated plays.

What's the biggest risk of relying on job-change signals alone?

The biggest risk is treating every job change as equally warm and sending the same templated message regardless of seniority, function fit, or account history. A junior individual contributor changing teams internally is not the same signal as a VP joining from outside with budget authority, and collapsing them into one sequence produces low reply rates and looks like spray-and-pray with extra steps. The fix is tiering job-change signals by role and account fit before they ever reach a sequence, and excluding accounts already in an active deal to avoid duplicate outreach.

Glossary

• Job-change signal: An alert that a specific person started a new role, covering both new hires at target accounts and past champions who moved companies.
• New-hire signal: A job-change signal specifically for someone newly joining a target account in a buying-relevant role.
• Champion tracking: Monitoring past product users or customer contacts for job changes so they can be re-engaged at their new company.
• Signal refresh cadence: How frequently the underlying data source rechecks for new job-change events; daily for new hires, monthly for champions is typical.
• Signal stacking: Combining two or more intent signals on the same account, such as a new hire plus a pricing-page visit, to prioritize outreach.
• Buying committee: The group of stakeholders, often six or more in complex B2B deals, involved in a single purchase decision.
• Trigger-based outreach: Outbound messaging sent automatically in response to a detected event, such as a job change, rather than on a fixed calendar cadence.
• Play: Unify's term for an automated workflow that connects a signal to enrichment and a sequence.
• Multi-threading: Building relationships with more than one stakeholder in an account so the deal survives if a single contact leaves or goes quiet.
• Warm outbound: Outreach initiated based on an existing signal of relevance or familiarity, as opposed to fully cold prospecting.

Sources

• Unify, Signals product page
• Unify, Plays product page
• Unify, B2B Company & Contact Data product page
• Unify customer story: Anrok
• Unify customer story: Unify's own growth team
• Harvard Business Review, "Sales Teams, Don't Undervalue Face Time with Customers"
• Unify, "Best Champion Tracking Tools for B2B Sales"
• Unify, "4 Types of Buying Signals to Prioritize Sales Outreach"
• Unify, "Signal Half-Life: 10-Signal Decay Table + When to Stop"

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.