Coming soon
The public leaderboard
A growing record of teams and tools reporting their cost per accepted change — so the industry has shared, comparable data to learn from, not just each vendor's own framing.
Why a leaderboard
The metric only helps the conversation if there are real numbers to point to. Until teams and vendors publish their own CPAC, a benchmark mostly reflects whoever produced it — which is no one's fault, just the nature of having no shared yardstick yet. The leaderboard is the place to put real numbers — with full disclosure of assumptions, window length, and what was counted.
What will appear here
- Tool benchmarks. Popular AI coding agents run against a fixed task set, with full cost accounting.
- Self-reported team numbers. Engineering organizations publishing their CPAC alongside their assumptions.
- Trend lines. Quarter-over-quarter movement for teams that report repeatedly.
How to submit
Open an issue at github.com/brennhill/cost-per-accepted-change/issues with the tag leaderboard. Include:
- Reporting entity (team, organization, or tool — anonymous submissions accepted with caveats)
- Measurement window (start date, end date)
- All six inputs to the formula
- How "change" was defined for this submission
- How review and engineering time were valued
- Any caveats or known biases
Submission criteria
- Numbers must be reproducible from the assumptions disclosed.
- Window length must be at least two weeks.
- "Accepted" must mean reached production and stayed there for the full window.
- Submissions that omit rework cost are flagged as such.
Subscribe at the repo to be notified when the first cohort of numbers is published.