Find RevOps leaders who just changed companies

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own ICP and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

A new Head of RevOps or VP of Revenue Operations walks into a role with one immediate priority: understand what the team is running on and decide what to keep, what to replace, and what to add. Every tool in the inherited stack is under evaluation. Every vendor relationship is up for review. The window is 60 to 90 days — long enough for them to get their bearings, short enough that the decisions get made before the first QBR closes the budget conversation. This Claude prompt uses Lusha to find RevOps leaders who just changed companies in the last 30 days at accounts that match your ICP — verifies each one, checks for stacked signals, and drafts a first-touch message grounded in the specific moment they’re in.

The prompt

Open in Claude Open in ChatGPT 
<context>
I want to find RevOps leaders who just joined a new company
in the last 30 days at accounts that match my ICP. They're
evaluating their inherited stack and making tool decisions
before their first QBR — I want to reach them in that window.

My ICP: [describe your ideal customer — industry, company
size, geography, funding stage]

Target titles: Head of Revenue Operations, VP of Revenue
Operations, Director of Revenue Operations, Head of Sales
Operations, VP of Sales Operations, or equivalent

Signal: company change in the last 30 days

My product: [one sentence — what you sell and how it
fits into a RevOps motion]
</context>

<task>
1. SIGNAL SCAN — Use Lusha to find RevOps leaders who
   changed companies in the last 30 days:
   - Target titles as specified above
   - Company change signal within the last 30 days
   - Return all matching contacts before ICP filtering

2. ICP SCORING — For each contact found, score their
   new company against my ICP:
   - Firmographic fit: industry, size, funding stage,
     geography
   - Remove companies that fail must-have criteria
   - Score remaining: Strong fit / Moderate fit

3. STACKED SIGNAL CHECK — For each ICP-fit account,
   check for additional signals that strengthen
   the case:
   - Funding event since the RevOps leader joined
     — fresh budget alongside a new leader
   - Hiring surge in sales or RevOps function
     — team being built under new leadership
   - Tech stack changes — tools being added or
     removed since the new leader joined
   - Intent signals on relevant topics above
     score 60 — active evaluation in progress
   - Flag accounts with 2+ stacked signals as
     highest priority

4. CONTACT VERIFICATION — Verify each RevOps contact
   via Lusha:
   - Current title and company confirmed
   - Start date at new company — tenure in current
     role
   - Verified email and direct dial
   - Previous company and title — context for
     the outreach angle
   - Flag if contact moved from a direct competitor
     — they know your category well

5. RANKED OUTPUT — Return contacts ranked by signal
   strength and ICP fit. For each contact:
   - Current title, company, and tenure
   - Previous company and title
   - ICP fit score for new company
   - Stacked signals at the account
   - Verified email and direct dial
   - One-line outreach angle grounded in the
     new role and what they're walking into
</task>

What you'll get back

RevOps leaders who just joined a new company, filtered against your ICP, ranked by signal strength — each one with verified contact details, their previous company for context, and an outreach angle built around the specific moment they’re in.

RevOps leaders who changed companies in last 30 days: 28  ·  ICP-fit new company: 9  ·  High priority (stacked signals): 3  ·  Contacts verified: 9

High priority — stacked signals

These RevOps leaders just joined an ICP-fit company and have additional signals firing at the account. The evaluation window is open right now.

ContactNew titleNew companyTenurePrevious companyStacked signals
R.M.Head of RevOps[Company A]3 weeks[Previous Co A]Series B closed + RevOps hiring
J.K.VP Revenue Operations[Company B]2 weeks[Previous Co B]New CRO + intent score 74
S.L.Director of Sales Operations[Company C]4 weeks[Previous Co C]Salesforce adopted + SDR hiring

R.M. — full detail

Contact profile

FieldValue
NameR.M.
Current titleHead of Revenue Operations
Current company[Company A]
Tenure3 weeks ⚑ recent hire
Previous titleSenior RevOps Manager
Previous company[Previous Co A]
Emailr.m@[company].com
Direct dial+1 415 555 ••••

Contact confirmed live via Lusha connector, [date]

New company profile

FieldValue
IndustryRevenue Intelligence / SaaS
Employees180–220
FundingSeries B — $22M closed 5 weeks ago
HQAustin, TX
ICP fitStrong — matches 5 of 5 criteria

Stacked signals at new company

SignalTypeDate
Series B closed — $22MFunding event[date]
3 RevOps and Sales Ops roles postedHiring surge[date]
Salesforce adoptedTech stack change[date]

Outreach angle: R.M. just stepped into their first Head of RevOps role at a Series B company that adopted Salesforce the same month they joined. They’re building the stack from scratch with fresh funding behind them. Lead with how quickly teams at this stage can get a verified data layer under the new motion — and reference the Salesforce adoption specifically. They’re connecting tools right now and your integration is part of that conversation.

ICP-fit contacts — job change signal only

These RevOps leaders just joined an ICP-fit company. No stacked signals yet. Reach out within the next two weeks — the evaluation window is open but closing.

ContactNew titleNew companyTenurePrevious companyICP fit
K.T.VP Revenue Operations[Company D]3 weeks[Previous Co D]Strong
M.B.Head of Sales Operations[Company E]4 weeks[Previous Co E]Strong
A.C.Director of RevOps[Company F]2 weeks[Previous Co F]Strong
P.H.VP Revenue Operations[Company G]3 weeks[Previous Co G]Moderate
D.W.Head of RevOps[Company H]4 weeks[Previous Co H]Strong
L.N.Director of Sales Operations[Company I]1 week[Previous Co I]Strong

Filtered out: 19 RevOps leaders changed companies in the last 30 days but their new company did not meet ICP criteria — wrong industry, outside size range, or geography exclusion applied.

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own ICP and connectors to see live results.

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude, Lusha
Type: Prompt

Why use Lusha in Claude

A new RevOps leader is one of the highest-value signals in B2B for one specific reason: they inherit a stack they didn’t choose and a mandate to improve it. Every tool the previous team bought is under review. Every vendor relationship is being assessed against the new leader’s standards and the company’s current stage. The evaluation isn’t announced — it just happens, quietly, in the first 60 to 90 days. The vendors who show up in that window with a relevant conversation get considered. The ones who show up after the first QBR find a stack that’s already been locked.

Lusha tracks executive job change signals as named, verified, time-stamped events — confirmed across multiple independent sources, not inferred from a LinkedIn update that may have been posted weeks after the actual start date. The tenure figure in the output reflects when the contact actually joined, not when they updated their profile. That precision matters here because the window is measured in weeks, not months, and reaching someone in week three is a fundamentally different conversation from reaching them in week ten.

The previous company field adds context that most outreach completely ignores. A RevOps leader who came from a company that used your product extensively is a warmer conversation than a cold introduction. A RevOps leader who came from a direct competitor is already fluent in your category — the conversation can skip the education and go straight to differentiation. Lusha surfaces both so the outreach angle can be calibrated before the first message is written.

The stacked signal check identifies the accounts where the evaluation is most active. A new RevOps leader at a company that just raised a Series B, adopted Salesforce, and is hiring three RevOps roles simultaneously isn’t just settling into a new job. They’re building something at speed, with budget, and with an open calendar for vendors who show up with the right conversation. Lusha’s 1.2B+ data points processed daily surface that pattern in real time so you find it in week two, not after someone manually pieces it together from three different news feeds.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use.

FAQ

  • How is this different from the Find People Who Just Changed Roles play?

    The Find people who just changed roles play is a broad signal sweep — it finds any contacts in your target persona who changed roles recently across any function. This play is narrower and more specific: it targets RevOps and Sales Ops leadership exclusively, filters against your ICP, includes the previous company for outreach context, checks for stacked signals, and drafts a first-touch message grounded in the specific evaluation motion a new RevOps leader is always in. Different scope, significantly more actionable output for this specific signal.

  • Why RevOps specifically — why not target all job changers?

    RevOps leaders have a disproportionate influence on tool decisions relative to their seniority. A new VP of Sales decides which reps to hire and what targets to set. A new Head of RevOps decides which tools the entire revenue team runs on — CRM, data enrichment, sequencing, attribution, forecasting. Every vendor in the stack goes through them. That makes a job change signal in RevOps more commercially valuable than the same signal in most other functions, because the evaluation scope is broader and the purchasing authority is real. If your product touches the RevOps stack in any way, this signal is worth tracking specifically.

  • Can I target other functions with the same play structure?

    Yes — replace the target titles in the prompt with any function you want to track. “Head of Customer Success, VP of Customer Success, Director of CS” produces the same play for CS leadership job changes. “CFO, VP of Finance, Head of FP&A” produces it for finance leadership. The signal logic is identical — new leader, inherited stack, evaluation window. The outreach angle changes based on what you sell and which function the new leader runs. If you regularly prospect into multiple functions, run the play separately for each one rather than mixing titles in a single pass.

  • What if the contact just joined a company that's already a customer?

    That’s an expansion signal, not a prospecting one. A new RevOps leader at an existing customer account is a relationship-building priority — introduce yourself before they inherit the vendor relationship cold and start questioning whether to renew. Flag any accounts in the output that are current customers and route them to your CS or AM team rather than your outbound motion. If your CRM is connected, the play can filter out existing customers automatically — add “exclude current customers” to the context field.

  • How long does the evaluation window actually stay open?

    For most RevOps leaders, the active evaluation phase runs from week two through week ten. Week one is onboarding and relationship-building. Weeks two through six are assessment — they’re learning what the team has, what’s working, and what isn’t. Weeks seven through ten are decision-making — tools get shortlisted, vendors get demo’d, and recommendations get made to the VP of Sales or CRO. After week ten, the stack starts getting locked in ahead of the first QBR. Contacts with tenure under six weeks in this play are in the sweet spot. Contacts with tenure between six and ten weeks are still reachable but the window is narrowing. Adjust the 30-day timeframe in the prompt to 45 or 60 days if you want to capture the full evaluation window rather than just the earliest stage of it.

Related Prompts

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs