Guides
Field guides to AI coding ROI.
Straight, tool-agnostic playbooks for engineering leaders trying to answer one question before renewal: is our AI coding seat spend actually producing a return? Each guide anchors to independent research, labels every vendor number as vendor telemetry, and lands on a decision your CFO can act on.
Ex-Amazon · Ex-The New York Times · Anchored to independent research
How to Measure Claude Code ROI (When You Can't Tell If the Spend Is Working)
You bought Claude Code seats and finance is asking if they pay off. Here is the honest, tool-agnostic method to measure real ROI: idle seats, throughput vs baseline, review time, and the perception gap.
Read the guide →GuideHow to Measure Cursor ROI: A Metrics Method for Engineering Leaders
A tool-agnostic method to measure Cursor ROI: idle seats, PR throughput vs baseline, review-time trend, and the perception gap. Anchored to independent research, not vendor claims.
Read the guide →GuideHow to Measure GitHub Copilot ROI (Without Trusting Acceptance Rate)
A tool-agnostic method to measure GitHub Copilot ROI: idle seats, pull-request throughput vs baseline, review time, and spend-vs-value, anchored to independent research.
Read the guide →GuideShould You Renew Your AI Coding Seats? A Decision Guide
Renewal season decision guide for engineering leaders: use idle-seat, throughput, and review-time data to decide whether to keep, renegotiate, fix, or cut AI coding seats.
Read the guide →Bring your adoption numbers.
The call is thirty minutes and free. I name the smallest thing that would move your numbers, even when that thing is not hiring me. Not ready to talk? Run the free self-check first.
alextongme@gmail.com →