Claude case studies: 9 sourced stories
Stories using Claude. Of the 9 stories, 2 were published by a tool vendor and 7 by the people who did the work. 8 involve an existing codebase and 1 started from scratch. Every number links to where it was published.
Cisco DevNet's 12-engineer team ships a mandatory PubHub rewrite in Go in about five and a half months instead of nine, using Claude, Copilot and Cursor
Cisco (DevNet PubHub team) · Claude, GitHub Copilot, Cursor
CaveatsWritten by the team itself. Compared against their own pre-AI estimate, not a measured baseline. Claude only joined in June, so the first two months ran at the old pace. No cost, PR or line counts. Engineering detail is promised in a separate AI for SDLC series.
Nine planned months shipped in about five and a half (39% reduction against the pre-AI estimate)
Schedule
Seven Anthropic engineers use Claude to build Scion, an in-house version control system, and move the monorepo off git in five months
Anthropic · Claude, Scion (Anthropic), Antique (Anthropic)
CaveatsAnthropic writing about its own model, so a vendor source. The post doesn't say how much of the code Claude wrote, give a line count or token cost, and notes Anthropic spends far more on tokens internally than other companies would. The infrastructure numbers describe Scion's performance, not the agent's work.
7 people
Team
Cockroach Labs' agent pipeline adds IBM Db2 support to its migration tool in under two days for $4,172 in tokens, then lands 1,238 PRs in five months
Cockroach Labs · Claude, MOLT Sinai (Cockroach Labs)
CaveatsSelf-reported on Cockroach Labs' own blog. The Db2 sprint ran in a mirror repo with no human review, and the authors say they are still confirming the Db2 support is correct. The Oracle comparison is against a 2024 human project of different scope, so the 164x and 38x figures are rough. Human approval was turned on for every merge after the first week.
"less than two days" vs 9 months for Oracle support in 2024
Db2 support time
DoorDash's multi-agent system turns stale feature flags into merge-ready PRs for $4.79 and 14 minutes each
DoorDash · Claude
CaveatsSelf-reported by the team that built it, on 50 flags in Kotlin repositories. A human still confirms each target value and reviews the PR. Complex flags reached 85% (22/26) and outliers took about 40 minutes and $19.
45 of 50 stale flags
Usable PRs
Claude plans and reviews, Codex builds: a production music site migrated from a React SPA to Next.js in 36 hours
Nik McFly · Claude, OpenAI Codex
CaveatsSelf-reported by the site owner on his own blog. A single, fairly small site. The post does not say which Claude product (Claude Code or chat) was used. A staging Docker build filled the server disk and briefly caused production API errors during the migration. The author notes the performance numbers are for this migration only.
36 hours
Migration time
Datadog migrates its live Stream Router from FoundationDB to PostgreSQL with Claude and Cursor; 45-minute operations now take ~1 second
Datadog · Claude, Cursor
CaveatsSelf-reported by the Datadog team that did the work. The AI tools were not autonomous: humans designed the schema, reviewed every generated skeleton, and wrote the optimised SQL (batching, UNNEST, CTEs), which the models then copied. Most of the performance and cost gains come from the new relational design, not from the AI tools; the post credits AI with making the implementation possible in the time frame. No count of methods, PRs or lines is given, and token spend is described only as significant.
~3 months (Dec 2025 – Feb 2026); proof of concept in 4 weeks
Design to production
Spotify's Honk agent rolls out 240 dataset migration PRs across downstream pipelines, saving an estimated 10 engineering weeks
Spotify · Claude, Honk, Backstage, Fleetshift
CaveatsCompany writing about its own platform. Scio pipelines weren't migrated by the agent, and without tests in most repos the agent couldn't verify its changes. The post doesn't say how many of the 240 PRs merged. Publish date read from page metadata.
240
Automated PRs
Intercom lets an AI agent approve 19% of pull requests, with 93% of PRs now agent-driven
Intercom · Claude
CaveatsSelf-reported by Intercom. The post names Claude as writing the code but not the exact tool or the models behind the review agent. Revert-rate comparison is observational: AI-approved PRs are filtered to be small, which may favour them.
Over 93% (two main codebases)
Agent-driven PRs
Stripe migrates 10,000 lines of Scala to Java in four days
Stripe · Claude
CaveatsVendor-published. No cost or team-size figure given.
10,000
Lines migrated