How many contacts should I target for a VP of Engineering webinar?

Build a raw Apollo list of 800-1,200 VP Eng contacts, then filter in Clay to 300-600 high-fit contacts based on company stage, tech stack, and hiring signals. This size produces 30-80 registrations for a focused topic.

What filters matter most beyond job title for a VP Engineering list?

Company stage (Series A-C for mid-market), engineering team size (10-50 for concentrated buying authority), tech stack signals (adjacent tools), and hiring velocity (5+ engineering roles in last 60 days indicates scaling).

What webinar topics earn the highest VP Engineering registration rates?

Topics tied to specific engineering problems: deployment incident reduction, platform engineering vs DevOps organizational shifts, security review readiness, and AI tooling in the engineering stack. Generic leadership topics underperform.

How do I use Clay to improve a VP Engineering list from Apollo?

Use Clay to verify employment status, enrich with tech stack data via BuiltWith, check engineering team headcount via Claygent, and filter for hiring velocity via PredictLeads job posting enrichment. This typically cuts the raw list to 30-50% of original size at much higher quality.

Does LinkedOtter build VP Engineering target lists for clients?

Yes. LinkedOtter builds ICP lists in Apollo and Clay for clients targeting VP Engineering, DevOps leads, and heads of infrastructure — as part of the done-for-you event-led pipeline service.

How to Build a VP of Engineering Target List for Webinar Outreach in 2026

Why a Title Search Is Not Enough

Searching "VP of Engineering" in Apollo returns hundreds of thousands of contacts. Sending a webinar invite to all of them produces a low-quality attendee list and wastes event capacity on people who will never buy.

A qualified VP of Engineering webinar list requires three layers of filtering beyond job title:

Company stage alignment — the VP Eng at a 15-person seed startup has different budget authority and pain points than the VP Eng at a 500-person Series D
Tech stack signals — the tools a company uses reveal the problems they are trying to solve and whether your product is adjacent to their current stack
Engineering team size and growth — a rapidly hiring engineering org is a buying signal for tools that help with onboarding, productivity, security, or infrastructure at scale

Step 1: Define the Qualifying Criteria

Before opening Apollo or Clay, define exactly which VP Eng profile you are targeting:

Company stage: Series A-C (50-500 employees) for mid-market tools; 500+ employees for enterprise products
Engineering team size: 10-50 engineers (tool evaluation authority concentrated in VP Eng); 50+ engineers (may involve additional stakeholders)
Industry: Fintech, AI/ML, DevOps platforms, SaaS — pick the 2-3 verticals where your product has the most traction
Tech stack signals: Companies using GitHub + Datadog + AWS = cloud-native engineering culture; companies using Jira + Jenkins + on-prem = different procurement pattern
Geography: US-based for most B2B vendors; EMEA if you have EU presence

Step 2: Build the Base List in Apollo

In Apollo, set filters:

Job title: "VP of Engineering," "Vice President of Engineering," "VP Engineering," "Head of Engineering" (include variants)
Company employee count: 50-500 for mid-market; 200-2,000 for enterprise
Industry: select 2-4 verticals
Geography: United States (or UK/DACH if targeting Europe)
Funding stage: Series A, B, C (or exclude bootstrapped if your product requires budget)

Export 800-1,200 contacts. This is your raw list.

Step 3: Enrich and Filter in Clay

Import the Apollo export into Clay and run waterfall enrichment:

Verify employment status: flag any contacts where LinkedIn last-updated > 6 months ago
Tech stack enrichment: use BuiltWith or Clearbit tech stack data to filter for companies using your adjacent tools
Team size signal: use Claygent to check LinkedIn for engineering team headcount signals ("how many engineers does this company have?")
Hiring velocity signal: PredictLeads or Clay job posting enrichment — companies posting 5+ engineering roles in the last 60 days are scaling; that is a buying signal

After Clay filtering, your 1,000-contact list typically shrinks to 300-500 high-fit contacts. This is your webinar invite list.

Step 4: Personalize the Invite Sequence

For VP Eng outreach, the event topic must address a specific engineering problem — not a generic "leadership" topic:

Topics that earn VP Eng registrations:

"How [X] engineering teams cut deployment incidents by 40% without slowing release velocity"
"Platform engineering vs DevOps: what does the organizational shift mean for tooling in 2026?"
"What does a CISO-level security review of your engineering stack actually look for?"

Build the sequence in Apollo: 3 emails over 8 days, one LinkedIn step, topic-specific subject lines.

What to Expect

LinkedOtter builds VP Eng target lists for clients across devops, cloud security, and AI infrastructure:

Typical list size after filtering: 300-600 qualified VP Eng contacts
Typical event invite open rate: 40-55% with topic-specific subject lines
Typical registration rate from an event invite sequence: 8-15% of reached contacts
Typical live attendance rate: 60-70% of registrants

Events from $6,000 per event. LinkedOtter builds the list, runs the event, and follows up.