~2 weeks · mostly async
Available nowAI Coding ROI Readout.
A 2-week diagnostic that finds exactly where your system is leaking the AI spend (review bandwidth, workflow, guardrails), and the on-ramp to installing the fix. You keep a board-ready deck and a keep, renegotiate, fix, or cut recommendation.
A fix-diagnostic on your rollout: where the seats are leaking value, what system change would recover it, and whether to keep, renegotiate, fix, or cut. Measurement is the proof layer, benchmarked against independent research and your own delivery data. Low access by design. Your code never leaves your infrastructure.
01 · Published tiers
Same SKU, sized to the org.
The Standard price is the anchor. Startup is published for smaller teams. Above 300 engineers the scope changes enough that the band is priced on the call.
Startup
5 to 25 engineers, funded startup, CTO buyer
1 to 2 teams, 2 interviews, about 1 week
Standard
Standard anchor25 to 300 engineers
Up to 4 teams, up to 5 interviews, perception pulse, full roughly 12-slide deck, about 2 weeks
Extended
300 to 600 engineers
Same Readout method, sized to representative teams and interview breadth
02 · What you get
What you walk away with.
Adoption and throughput data pull
Licensed versus active seats, pull-request throughput, review time, and change-failure rate, measured before and after the rollout.
Benchmark vs. independent medians
Where you land against the independent medians (METR, DORA, and academic research), with first-party studies from DX and Faros labeled as such. Never against inflated vendor marketing claims.
Spend versus value, by team
The cross-tab a CFO renews or cuts on: what each team's seats cost against what they actually returned.
A board-ready readout deck
Roughly 10 to 12 plain, sourced slides you keep, built to survive scrutiny from a skeptical finance team.
A one-page recommendation
Keep, renegotiate, fix-the-system, or cut, each with its hard-dollar impact spelled out.
A live 60-minute readout
Findings, the recommendation, and open Q&A with your engineering leadership.
03 · What I need from you
A deliberately small ask.
The low access is the point. Your code never leaves your infrastructure.
- Read-only dashboards, not your codebase: version-control insights, AI-tool admin consoles, and spend data.
- Three to five stakeholder interviews, 30 minutes each, across levels.
- Your actual seat spend: contract, unit price, and renewal date, from finance or procurement.
04 · The terms
Plain terms, published up front.
Book the discovery call.
Thirty minutes, free, no pitch. We walk your setup and I name the smallest thing that would move your numbers, even when that thing is not hiring me.
alextongme@gmail.com →I reply within one business day