# Email Drip: code-rewriter-ai
## Target ICP: Engineering leads, CTOs, code review teams at 50-500 person companies
### Voice: Direct, code-native, results-first. No fluff.

---

## Email 1: The Problem Recognition
**Subject:** Your code reviews are the bottleneck

Hi [NAME],

I watched a 20-person eng team spend 40% of their week on code review. Not refactoring. Not shipping. Reading the same structural problems in different pull requests.

I built code-rewriter-ai to automate that layer.

Instead of your team debating whether a function should be broken into three, or whether that loop should be async, we catch it first. Rewrite before review. Your reviewers see intentional changes, not structural cleanup.

Worth 15 minutes?

[LINK: https://wishdeal.com/factory/builds/code-rewriter-ai/]

[NAME]

---

## Email 2: The Ask (Day 2)
**Subject:** re: Your code reviews are the bottleneck

Quick follow-up.

The biggest unlock we see: teams using code-rewriter-ai get from 3-day PR cycles to 1-day. Not because reviewers are faster. Because the code arrives cleaner.

One CTO told us: "It's like having a senior engineer pre-flight every PR."

If that resonates, I'd love to show you how it integrates with your CI/CD in 10 minutes.

Available this week?

[LINK]

[NAME]

---

## Email 3: Case Data (Day 4)
**Subject:** 47% fewer back-and-forth cycles

Hi [NAME],

We just closed a case study with a 120-person fintech shop. They saw:
- 47% reduction in back-and-forth review comments
- 18% faster time-to-merge on average
- Zero false positives on structural issues (the AI learns your codebase style)

Full breakdown here: [LINK]

Thought you might find the benchmarks useful as you scope your own QA/review layer.

[NAME]

---

## Email 4: Usage Pattern (Day 6)
**Subject:** How teams actually use this

Hey [NAME],

Turns out most teams run code-rewriter-ai in two modes:

1. **Pre-commit** — developers catch structural issues before pushing
2. **Pre-merge** — your CI gates run it; reviewers see only intent, not cleanup

The second one is where the time savings compound.

We just published a playbook for both: [LINK]

Let me know if you want to pilot on a single team first.

[NAME]

---

## Email 5: Hard Close (Day 8)
**Subject:** One more data point

Last check-in.

We're limiting beta access while we stabilize multi-language support. If you want in before summer, now's the window.

Calendar here: [LINK]

If not now, I'll check back in September.

[NAME]