KH
KC Haiker
GTM Profile
Growth
VP of Growth · DEPT
Talking Points
- Netlify gives DEPT's growth team deploy-on-demand — spin up landing pages, experiments, and funnels without eng tickets
- Built-in A/B testing with Edge Functions: define variants in code, ship experiments same-day
- Deploy Previews collapse the review cycle from days to minutes — growth moves at the speed of the hypothesis
- Netlify Analytics ties performance to conversion — load time, cache hit rate, and experiment data in one place
- The DEPT growth loop accelerates when every funnel page is a Netlify deploy, not a Salesforce or WordPress plugin
Engagement Sequence
Day 1
LinkedIn connect — send a connection request with a brief note. Reference a specific piece of content they've published or a shared industry challenge. No pitch.
Day 4
Engage on their content — comment thoughtfully on a recent post. Make it about their perspective, not yours. Build presence before direct outreach.
Day 8
Direct message — send the message below. Short, specific, no generic pitch. Reference their role and the Netlify angle that maps to their world.
Day 15
Follow-up value add — share a relevant resource: a case study, a Deploy Preview demo, or a Netlify blog post that speaks directly to their use case.
Day 22
Email outreach — send a short, personalized email with a soft CTA: "worth 20 minutes?" Reference the LinkedIn touchpoints briefly to show consistency.
✏️ Suggested Outreach Message
Hi KC,
Growth teams move fastest when the deploy cycle is measured in hours, not sprints.
Netlify gives DEPT's growth team direct deploy access — spin up landing pages, experiments, and funnel variants without engineering tickets. A/B tests run at the edge via Edge Functions. Rollbacks happen in seconds. Every variant gets a preview URL for internal sign-off before it goes live.
The hypothesis-to-data loop shrinks dramatically when "ship the experiment" is a one-click action.
Worth 20 minutes to walk through how other growth teams are using this?
— [Your name]
