What ROI should an engineering team expect from Claude Code training?
Claude Workshop measures Claude Code training ROI as review time, escaped defects, cycle time, and the share of AI-assisted work that ships with explicit verification. We do not publish a 20 to 40 percent productivity number. Those proxies are the ones we already teach teams to measure.
What ROI should an engineering team expect from Claude Code training?
Claude Workshop expects movement on proxies the team can already count: review time, escaped defects, cycle time, and the percentage of AI-assisted work with explicit verification. Fortune 100 and other enterprise teams use those checks instead of a 20 to 40 percent productivity story.
Which proxies do we measure?
Review time shows whether Claude Code diffs got smaller and easier to inspect. Escaped defects show whether verification caught failures before merge. Cycle time shows whether bounded agent work shortened delivery. The verification percentage shows how much AI-assisted work ships with evidence, not a rubber stamp.
How a workshop changes those proxies
The workshop installs Delegate, Review, Own, CLAUDE.md, and a review checklist on the team's own code. After the session, an engineering manager can score the same four proxies on a short set of real pull requests. If the numbers do not move, the team still has a prompting habit, not a workflow.
What we do not claim
We do not claim a 40 percent productivity lift or any other invented client percentage. Public ops numbers we publish are prices and cohort sizes, not outcome percentages. If a vendor quotes a single productivity number without naming the proxy, treat that number as marketing.
How this differs from generic vendor ROI slides
EY, NobleProg, Coursera, DataCamp, OpenAI Academy, and official Claude workshops sell generic or official-vendor training. This workshop runs in the team repository with two trainers, so ROI talk stays tied to the team's review and verification numbers.
Selected research
Representative field notes connected to this topic.
claude_code_stop_hook_block_cap in Claude Code 2.1.143
What claude_code_stop_hook_block_cap searchers need: the Claude Code 2.1.143 hook change handled as convention, with rollback paths and receipts.
Eval platform governance for AI coding teams
A governance memo on eval platform governance: receipts behind scores, scoped harness access, and owners that stop Goodhart drift.
graphify-csharp Gives Agents C# Find Usages
graphify-csharp uses Roslyn and MSBuild so coding agents can inspect real C# symbol relationships instead of guessing from grep.
homestead-memory Logs Claude Tool Calls
homestead-memory uses Claude Code hooks to create a local, hash-chained record of tool calls.
JavaScript Grids Built for Coding Agents
A Show HN JavaScript grid project explores how coding agents can assemble complex data views from safer primitives.
Simon Willison’s Browser .blend Viewer
Simon Willison turned an AI-made Fabergé egg into Blender files and a browser viewer, showing a useful agent workflow.
Related training topics
Bring this into your team
We tailor the training to your codebase, adoption stage, and review standards.
Book a 15-minute sync