Lusha Dataset: 869+ verified CTOs who recently joined a new company

Built by: Lusha
Tools: Lusha
Type: Audience
Type: AudienceRecords: 869+Signal: Job changeUpdated: DailyTools: Lusha, Claude, ChatGPT, API

This dataset surfaces Chief Technology Officer contacts who recently changed companies — verified, enriched, and refreshed daily. A new CTO inherits a technology stack they didn’t choose and arrives with a mandate to evaluate, modernize, or replace it. They have no loyalty to the existing vendor relationships.

This is one of the most disruptive moments in any enterprise tech sale — a new technical decision-maker reviewing infrastructure, developer tooling, security, and AI platforms with fresh eyes and a board-level expectation to show progress.

What you’ll get back — live contact sample

N.L.

N.L. · Chief Digital and Technology Officer · Nxx Cxxx Australia

Sydney, Australia · Media

Job change signal
✓ Email available
H.S.

H.S. · Chief Technology Officer · Cxxxow

London, UK · Internet

Job change signal
✓ Email available
P.B.

P.B. · Chief Technology Officer · Axxxxed British Foods

Guildford, UK · Food & Beverage

Job change signal
✓ Email available
M.P.

M.P. · Chief Technology Officer · Pxxx

London, UK · 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

Cloud, infrastructure, and developer tools

A new CTO is auditing the entire technical stack — cloud provider, developer tooling, CI/CD, observability. Every contract is up for review. Reach them while the audit is happening.

2

AI platforms and LLM infrastructure

New CTOs are frequently brought in specifically to lead AI adoption. They are the highest-intent buyer for LLM platforms, agent infrastructure, and AI tooling — often with an explicit mandate to modernize.

3

Security and compliance platforms

New technical leadership often triggers a fresh security review. CTOs new to a role are receptive buyers for security, compliance, and risk management tools as they establish their own standards.

4

Technical recruiting and team build-out

A new CTO frequently rebuilds their leadership team. They are a buyer for executive search and a candidate source for engineering leadership roles elsewhere.

How to access this audience

1

In Claude or ChatGPT

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

2

Via the Lusha API

Use prospecting_contact_search with jobTitles: ["Chief Technology Officer", "CTO"] and signals: { names: ["companyChange"] } to pull CTO contacts with an active job change signal.

3

Via Make, n8n, or Zapier

Run this against your CRM’s historical technical contacts on a weekly schedule. Surface former evaluators or champions who now hold CTO authority at a new company.

FAQ

  • Does this include Chief Digital Officer and Chief Information Officer?

    CTO is the primary title in this dataset. Related titles like Chief Digital and Technology Officer or CIO with equivalent technical authority can be added as separate filters or combined into one search.

  • Can I filter by industry or company size?

    Yes. Layer industry, company size, and geography filters on top of the job change signal to match the audience to your specific ICP.

  • 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.