# Cold Outreach Email Drip: git-bus-factor-analyzer

## Email 1: Hook
**Subject:** What's your codebase's bus factor?

Hey [Name],

Quick question: if your top engineer left tomorrow, how many codebases would stall? 

Most dev teams don't know. We built a tool that answers it in 5 minutes.

Worth 5 minutes?

[git-bus-factor-analyzer.com]

---

## Email 2: Risk Identification
**Subject:** You probably have a concentration problem

Hey [Name],

We analyzed 26 open-source repos. Average result: 3 people control 60% of the codebase.

For closed-source teams? Usually worse.

That's a liability, not a feature.

We built a scanner that shows you exactly where your code is concentrated.

[Check yours free]

---

## Email 3: Proof
**Subject:** Here's what we found in [Popular Repo]

Hey [Name],

We analyzed Kubernetes, Redis, Django, and others. The findings are sobering.

One dev owns 34% of the auth layer. Another owns 28% of core consensus.

One departure could mean months of friction.

Your codebase probably has similar patterns. Want to know?

[Scan your repo—takes 90 seconds]

---

## Email 4: Social Proof
**Subject:** Used by teams at [context]

Hey [Name],

We've helped platform teams, fintech shops, and open-source maintainers spot concentration before it became a crisis.

Common reaction: "I had no idea."

Second reaction: "Let's fix this."

Your team might feel the same.

[See your metrics]

---

## Email 5: Final CTA
**Subject:** Last chance—free bus factor analysis

Hey [Name],

Free analysis, no credit card, results in minutes.

Know your code's concentration. Then decide if you want to reduce it.

Most teams do.

[Get your report]

Cheers,
[Sender]