**Email 1** Subject: Your Kubernetes footprint Send timing: Send on Tuesday Body: Many Series B DevTools teams I follow have reached the point where engineering efficiency matters as much as feature velocity. As a VP of Engineering, you're likely balancing platform reliability with growing cloud spend as customer usage scales. One result stood out from our work: we helped a Series B cloud infrastructure company reduce cloud costs by **40%** through automated right-sizing while maintaining application performance. The engineering team spent less time reviewing idle resources and manual sizing decisions. It's interesting how infrastructure optimization often becomes a byproduct of growth rather than a planned initiative. CTA: It seems to be a common pattern as engineering organizations mature. **Email 2** Subject: Following up on Kubernetes Send timing: Send 3 business days after Email 1 Body: I wanted to share one benchmark that engineering leaders often find useful. The annual **FinOps Foundation State of FinOps Report** consistently highlights that rightsizing compute remains one of the highest-impact cloud optimization practices, yet many teams struggle to keep recommendations current because infrastructure changes so quickly. That gap is especially common in fast-moving DevTools organizations where deployments happen daily and manual reviews quickly become outdated. Would it be useful if I shared a short summary of how engineering teams automate this process without adding operational overhead, or would a 10-minute conversation be easier? CTA: Would either of those be helpful? **Email 3** Subject: Wrapping up Send timing: Send 4 business days after Email 2 Body: I'll leave this here since now may not be the right time. I know priorities shift quickly for engineering teams, and I don't want to keep filling your inbox. If infrastructure optimization becomes more relevant down the road, I'm happy to reconnect. CTA: If the timing changes, I'm here.