Lusha Dataset: 1,280+ VP of Sales who recently joined a new company

Built by: Lusha
Tools: Lusha
Type: Audience

This dataset surfaces VP of Sales contacts who recently changed companies — verified, enriched, and refreshed daily. A new VP of Sales arrives with a fresh mandate, a new budget line, and no inherited vendor loyalty. They haven’t built a relationship with the incumbent sales tech stack yet, which makes the first 90 days the highest-converting window for cold outreach in B2B.

This is fundamentally different from a new-hire signal at the company level — this dataset follows the person, not the company. Wherever they land next, Lusha tracks the move.

Why job-change contacts convert higher

No incumbent loyalty

They didn’t choose the current vendor stack. There’s no relationship to defend.

High intent

Active evaluation mode

New leaders audit every tool in their first quarter. They’re actively taking meetings, not avoiding them.

High intent

Fresh budget authority

New VP of Sales roles usually come with new or re-allocated budget for tooling and team build-out.

High intent

What you’ll get back — live contact sample

K.K.

K.K. · Regional VP of Sales · Dxxxon

Philadelphia, PA · Internet

Job change signal
✓ Email available
A.S.

A.S. · VP of Sales Strategy and Operations · Sxxx AI

San Ramon, CA · Computer Software

Job change signal
✓ Email available
S.S.

S.S. · Regional VP of Sales · Hxxxss

Singapore · Computer Software

Job change signal
✓ Email available
G.M.

G.M. · Assistant VP of Sales · SxxxxOne

Dubai, UAE · Computer Software

Job change signal
✓ Email available

Real contacts from the Lusha API, June 16, 2026. Names abbreviated for privacy. Full details available on reveal inside Lusha.

Use cases

1

Sales tech and GTM platforms

A new VP of Sales is rebuilding their team’s tech stack from scratch. CRM, sales engagement, enrichment, and intelligence tools are all on the table in the first 90 days. Reach them before the previous leader’s vendor relationships get inherited.

2

Competitive displacement

If you lost a deal to a competitor, this is your re-entry point. The VP who chose the competitor might have moved on — and the new VP has no allegiance to that decision.

3

Champion tracking and re-engagement

If a former champion or contact at a closed-lost account shows up here, that’s a re-engagement opportunity at their new company — with someone who already knows your product.

4

CRM hygiene and re-attribution

If a contact in your CRM shows a job change, that record needs updating immediately — both to keep the data clean and to flag the new account for outreach.

How to access this audience

1

In Claude or ChatGPT

With the Lusha connector enabled, ask: “Find VPs of Sales who recently changed companies in the last 60 days at B2B SaaS companies. Give me their verified email and direct dial.”

2

Via the Lusha API

Use prospecting_contact_search with jobTitles: ["VP of Sales"] and signals: { names: ["companyChange"] } to pull VP of Sales contacts with an active job change signal.

3

Via Make, n8n, or Zapier

Run this as a scheduled trigger against your CRM’s existing contact list. The moment a contact’s job change is detected, fire an enrichment and outreach sequence to their new company automatically.

FAQ

  • How does Lusha detect a job change?

    Lusha continuously monitors public professional profile data and detects when a contact’s current employer changes. The signal fires with the new company, new title, and approximate change date.

  • Can I run this against my own CRM contacts?

    Yes. This is one of the most common uses of the job change signal — matching it against your existing CRM contact list to detect when former champions, lost-deal contacts, or current customers move to a new company.

  • Does this work for other titles besides VP of Sales?

    Yes. The job change signal works for any title — CRO, CTO, VP of Marketing, VP of RevOps, and more. Filter by job title to build the job-change audience for any function.

  • Does accessing this dataset consume Lusha credits?

    Yes, signal-filtered contact searches consume credits per signal type returned, in addition to base search credits. Revealing emails costs 1 credit per contact; phone numbers cost 5 credits per contact.

  • Is this data GDPR and CCPA compliant?

    Yes. All Lusha data is sourced ethically under GDPR, CCPA, SOC 2 Type II, ISO 27701, ISO 31700, TRUSTe, and ISO 42001. No scraping. Learn more →

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.