NJ
Nora Jones
GTM Profile
Product
VP of Product Development · PagerDuty
Talking Points
- Netlify's platform gives PagerDuty's product team continuous deployment without the DevOps overhead
- Deploy Previews for every PR means product managers can validate before merge, not after
- Edge Functions enable feature flags, A/B tests, and progressive rollouts at the CDN layer
- Netlify's API-first architecture fits naturally into PagerDuty's composable product stack
- Instant rollbacks mean product incidents on the web layer resolve in seconds, not hours
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 Nora,
Product teams using Netlify get something that's hard to get elsewhere: a deploy pipeline where the PM can validate before merge, not after.
Every PR at PagerDuty gets a Deploy Preview URL. The product manager clicks it, sees exactly what's shipping, and approves or comments — all before it hits main. Edge Functions handle feature flags and progressive rollouts at the CDN layer, no backend required.
It's the feedback loop that makes "ship fast" actually mean something.
20 minutes to dig into the specifics?
— [Your name]
