AI Code Review Selling to the Director of Platform Engineering — 60-Min Training

Question

Pulse · Accepted Answer

![AI Code Review Selling to the Director of Platform Engineering — 60-Min Training](/assets/qa/tc0105.jpg)

### Direct Answer

![sales rep training software demo](https://image.pollinations.ai/prompt/realistic%20editorial%20photograph%20of%20sales%20rep%20training%20software%20demo%2C%20natural%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=34253)

> **AI Code Review Selling to the Director of Platform Engineering** is a 60-minute training for AEs running $30K-$400K ACV cycles against **Greptile, CodeRabbit, Qodo, Bito, GitHub Copilot Reviews, GitLab Duo, Sourcery, Snyk Code, Codium, Tabnine**. Qualify against the **Director of Platform Engineering + AppSec Lead + CFO**, run discovery on **false-positive rate (FPR), comment quality, language coverage, and CI/CD integration depth**, and close on a 7-day production-PR trial with a measurable FPR scorecard. Built on **MEDDPICC** with a developer-adoption metric (70%+ devs reading comments by day 30) as the only renewal trap-set that matters.

---

## Section 1 — Why AI Code Review Selling Is Different (5 min)

![platform engineering team meeting](https://image.pollinations.ai/prompt/realistic%20editorial%20photograph%20of%20platform%20engineering%20team%20meeting%2C%20natural%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=51953)

**False-positive rate (FPR) is the entire game.** Forrester's 2026 Developer Productivity Wave found that **63% of AI code review pilots fail by month 3 when FPR exceeds 20%** — developers disable the bot inside Slack and the contract dies at renewal. This is unlike traditional static analysis selling (where coverage is the wedge) and unlike LLM coding-assistant selling (where seat penetration is the wedge). For review tools, **comment quality beats comment count by 4:1** in adoption surveys (GitClear, 2026).

The buying committee is also unusual. The **Director of Platform Engineering owns the budget**, but the **AppSec Lead has a veto** (any security false positive that wakes them at 2am kills the deal) and the **CFO holds the per-developer math** ($19-$30/dev/month at Greptile and CodeRabbit; $25-$40/dev/month at Snyk Code; bundled with GitHub Copilot Business at $19/user/month).

> **Manager script:** "We don't sell AI code review like static analysis. We sell trust. If FPR climbs past 20% in week one, we lose the developer, and we lose the renewal. Every discovery question maps back to FPR."

End on **Mark Roberge's** rule from *The Sales Acceleration Formula*: *"Sell the metric the buyer wakes up worrying about."* For platform engineering, that metric is **dev adoption of AI suggestions, measured weekly**.

---

## Section 2 — The 60-Minute Discovery (15 min)

![discovery call video conference](https://image.pollinations.ai/prompt/realistic%20editorial%20photograph%20of%20discovery%20call%20video%20conference%2C%20natural%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=28497)%20AI%20Code%20Review%20Selling%20to%20the%20Direc%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=10633)

Run discovery with the **Director of Platform Engineering + AppSec Lead in the same call**. Pre-brief them by email 48 hours before with a one-page FPR scorecard so they show up calibrated. Do not let procurement or a VP of Engineering chief of staff substitute — both will derail the FPR conversation into seat-count negotiation.

> 1. **Opening (3 min):** *"Walk me through your current PR workflow. Where does the AI review bot sit in the lifecycle — pre-commit, pre-merge, or post-merge audit?"*
> 2. **Language + framework mix (3 min):** *"What's the language split — Python, TypeScript, Go, Java, Rust? Greptile and CodeRabbit have very different language coverage curves; we need this to scope."*
> 3. **FPR baseline (3 min):** *"What's your current FPR with whatever you're running? Less than 20% is best-in-class; less than 10% is rare."*
> 4. **Integration depth (2 min):** *"GitHub, GitLab, Bitbucket, Azure DevOps? Do you require self-hosted runners?"*
> 5. **Dev adoption target (2 min):** *"What percentage of developers do you need reading AI comments by day 30 for the contract to renew? We typically see 70%+ as the bar."*
> 6. **Security wedge (1 min):** *"Are you bundling AI review with a security scanner like **Snyk Code** ($25/dev/month) or **Veracode**, or treating them separately?"*
> 7. **Renewal posture (1 min):** *"Do you have an existing **Sourcery** or **DeepSource** contract we need to displace?"*

```mermaid
flowchart TD
    A[AE Pre-Brief Email] --> B[Director of Platform Eng + AppSec Lead]
    B --> C{Joint Attendance?}
    C -->|No| D[Reschedule]
    C -->|Yes| E[Language + FPR Discovery 6 min]
    E --> F[Integration + Adoption Targets 5 min]
    F --> G[Security Wedge + Renewal Posture 4 min]
    G --> H[7-Day Pr

Kory White

AI Code Review Selling to the Director of Platform Engineering — 60-Min Training

Section 1 — Why AI Code Review Selling Is Different (5 min)

Section 2 — The 60-Minute Discovery (15 min)

Section 3 — The Trial That Wins (15 min)

Section 4 — Handling the Incumbent (10 min)

Section 5 — Pricing Conversation (10 min)

Section 6 — Renewal Trap-Set Month 12 (5 min)

FAQ

Related on PULSE

Sources

Kory White

AI Code Review Selling to the Director of Platform Engineering — 60-Min Training

Section 1 — Why AI Code Review Selling Is Different (5 min)

Section 2 — The 60-Minute Discovery (15 min)

Section 3 — The Trial That Wins (15 min)

Section 4 — Handling the Incumbent (10 min)

Section 5 — Pricing Conversation (10 min)

Section 6 — Renewal Trap-Set Month 12 (5 min)

FAQ

Related on PULSE

Sources

Two scores — Gate vs IQ