This dataset surfaces Chief Revenue Officer contacts who recently changed companies — verified, enriched, and refreshed daily. A new CRO arrives with a board-level mandate to fix or accelerate the revenue motion. They haven’t built loyalty to the existing GTM stack, and they have the authority to change it.
CROs change companies less often than VPs, which makes every signal in this dataset rarer and higher-stakes. The new CRO is evaluating the entire revenue org — pipeline, tooling, team structure — in their first 90 days.
What you’ll get back — live contact sample
R.M.
R.M. · Chief Revenue Officer · Mongoxx
United States · Computer Software
Job change signal
✓ Email available
F.O.
F.O. · Chief Revenue and Commercial Officer · Coxxx
Miami, FL · Internet
Job change signal
✓ Email available
J.C.
J.C. · Chief Revenue Officer · Coxxx
Atlanta, GA · Computer Software
Job change signal
✓ Email available
T.O.
T.O. · Chief Revenue Officer · Matilxxxx
Franklin, MA · 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.
1
Enterprise revenue technology
A new CRO is reviewing the entire revenue stack — CRM, forecasting, pipeline management, data and intelligence platforms. They have board-level pressure to show results and the authority to make sweeping changes.
2
Strategic partnerships and co-sell
New CROs frequently rebuild their partner and co-sell ecosystem. This is the window to introduce a new strategic relationship before the program is locked in.
3
Re-engaging a former relationship
If a CRO you previously sold to or pitched shows up here, that’s a warm re-entry point at their new company — with someone who already trusts you.
4
Executive search and board advisory
Track CRO movement across the market for executive search mandates, board advisory work, or competitive talent intelligence.
How to access this audience
1
In Claude or ChatGPT
With the Lusha connector enabled, ask: “Find Chief Revenue Officers 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: ["Chief Revenue Officer", "CRO"] and signals: { names: ["companyChange"] } to pull CRO contacts with an active job change signal.
3
Via Make, n8n, or Zapier
Run this against your CRM’s historical contact list on a weekly schedule. When a past prospect or champion shows up with a CRO job change, trigger a personalized re-engagement sequence automatically.
