Help every developer
get better with AI.

A personal AI plan for every developer, built from their work.

See the full report

Trusted by engineering teams

Kiwi.comFinshapePartners BankaPurple TechnologyGreysonItrinityESETFTMOKeggSecond Foundation
NYour AI adoption read-outYouOrg median, benchmarked across your 350 developersJun 8 to Aug 2 · 8 weeks
  • Agent fluencyYou 4.4 of 5, against an org median of 3.0 across 350 developers+1.4above median↑ +0.5 in 8 weeksKeep AI in the daily loop, not only on the tickets that look hardAI-active 7 of 8 weeks
  • Delegation depthYou 3.9 of 5, against an org median of 2.1 across 350 developers+1.8above median↑ +0.9 in 8 weeksHand agents whole tasks, not snippets, on every agent dayDeep delegation on 21 of 28 agent days
  • Roadmap alignmentYou 3.5 of 5, against an org median of 1.7 across 350 developers+1.8above median↓ −0.3 in 8 weeksPoint more AI hours at roadmap objectives72% of work credited to roadmap objectives
  • Context leverageStart hereYou 0.8 of 5, against an org median of 2.3 across 350 developers−1.5below median↓ −0.1 in 8 weeksAdd a why and an outcome to every prompt and ticket3 of 12 artifacts state a why and outcome
  • Agentic autonomyYou 0.5 of 5, against an org median of 1.2 across 350 developers−0.7below median↑ +0.4 in 8 weeksOne agent-owned task a week, start to finish2% of work owned end to end by agents
Not startedStartingFluentLeadingThe median is your own company’s, or one team’s when you filter to it. Scored from commits, pull requests and tickets. No survey.
01Across the org

140 developers have never let an agent finish a task.

One bar per level, across all 350 developers. Each row ends in the one thing to do about it.

Not started(below 1)Starting(1 to 2.5)Fluent(2.5 to 4)Leading(4 and up)
  • Agent fluency358215182Most people already use it daily. Get the last 35 started
  • Delegation depth4714610552Pair the 52 leading developers with the 146 still handing over snippets
  • Roadmap alignment761528735Link tickets to objectives, so AI hours land on the roadmap
  • Context leverage5813411741Add a why and outcome field to the ticket template
  • Agentic autonomy1401237017140 developers have never let an agent finish a task. Start there
02The payoff

Adoption shows up as capacity you did not hire.

The same company, measured before and after AI. Raise the levels above and these three numbers move.

+326engineers of capacity, on a team of 350
  • On the payroll350
  • Delivering like676
$696AI cost per engineer of capacity, a month
  • Engineer of capacity, from AI$696
  • Team member, all in$8,000
48.6%of that capacity went to roadmap work
Roadmap 48.6%Everything else 51.4%

Adoption is the coding part of the AI transformation report, and one stage of the engineering loop. The capacity is priced in AI ROI, and the bill behind it in token spend.

03How it works

No survey. No single score.

The five levels are never added up. An average hides the lowest row, and the lowest row is the one worth working on.

01

Connect

Read-only access to your repositories, tracker and AI tools.

  • Repositories
  • Tracker
  • AI tools
NRead-only
02

Score

Five levels per developer, read from the work every night.

  • Agent fluency4.4
  • Delegation depth3.9
  • Roadmap alignment3.5
  • Context leverage0.8
  • Agentic autonomy0.5
03

Next step

Every developer sees their own read-out and the one move to make.

Start here · Context leverageYou 0.8Org median 2.3→ Add a why and an outcome to every prompt and ticket
→Start here

See how your team
really uses AI.

Read-only setup, under an hour. The first read-out is built from history you already have.