How Edmunds GovTech Reclaimed 550+ Dev Days

Edmunds GovTech's product and engineering org had no AI adoption. A Claude Code harness now runs its SDLC, reclaiming 550+ dev days and compressing a one-year rebuild into weeks.

550+ days

Reclaimed across customer products

4–8 weeks

Implementation Time

Not disclosed

Project Cost
the challenge
When Bonsai Labs came in, AI adoption across Edmunds GovTech's product and engineering organization was low. AI licenses acquired through the company's enterprise Microsoft agreement had never been operationalized: no program, no shared tooling, and no proof point the teams trusted. For an organization carrying live delivery commitments to thousands of public-sector customers, that caution was warranted. At the same time, Edmunds GovTech needed to accelerate a generational modernization, its next-generation Ethos web platform, without compromising the stability its customers depend on.
what they built
Bonsai Labs embedded with Edmunds GovTech in a forward-deployed model and built AI capability into how the organization works, function by function, from product management to engineering and QA. The centerpiece was a durable AI coding harness designed around Claude Code: documented, extensible, and easy to replicate across every codebase, with teams empowered to add their own skills. A custom toolkit carried a written product vision through specifications, requirements, and design in minutes. The engagement was designed so the capability stayed in-house after Bonsai left.
Bonsai Labs worked in a forward-deployed model, embedding with Edmunds GovTech's teams rather than handing over a deck. They started with product management, demonstrating a custom toolkit that carried a written vision through specifications, requirements, and design in minutes, work that normally took weeks. Winning that team created the first internal believers. Leadership followed by example: the CPTO, originally a coder, turned the Claude Code harness loose on one of the company's applications after a single pairing session and had a click-through prototype hours later. From the outset the engagement was built for durability. Bonsai left behind an AI coding harness designed around Claude Code, documented, extensible, and easy to replicate across every codebase, and taught teams to extend it with their own skills. The work moved function by function, from product management into engineering and quality assurance, pairing hands-on tooling with change management so adoption held after the engagement ended. Teams now extend the harness themselves and operate with an assumption of continuous change.
best fit for
Private equity-backed B2B software companies modernizing legacy platforms, and product and engineering organizations whose AI adoption has stalled at experimentation and who want a durable, owned capability rather than a purchased tool.
Ai ROLE
AI, via a Claude Code harness, acted as an embedded copilot across the SDLC: generating specifications, requirements, prototypes, and code, locating relevant code in large legacy codebases in minutes, and surfacing performance and bug fixes. The point was to build owned capability, not to do the team's work for them.
impact

550+ dev days reclaimed

Development time reclaimed across customer-facing products using the Claude Code harness during a six-week engagement.

1-year rebuild in weeks

A legacy codebase upgrade estimated at a year for a full team was completed by a single engineer in weeks; a three-month UI build shipped in three days.

~8x faster bug resolution

In one hackathon session an engineer cleared four bugs in an hour, about a day's work under the old process; AI also surfaced four performance fixes shipped within 24 hours.
implementation complexity
Inferred Medium. The build itself was a reusable Claude Code harness delivered in a six-week engagement rather than heavy custom architecture or data-infrastructure work, but it touched multiple legacy codebases and required organization-wide change management across product, engineering, and QA. Not partner-graded.
industry
Technology & Software
business organization
Product & Engineering
AI TYpe
AI Workforce Enablement
AI-Accelerated Custom Software
value type
Time Savings
Revenue Growth
frequently asked questions
How did Edmunds GovTech reclaim 550+ development days in its SDLC with AI?
The experts embedded with Edmunds GovTech's product and engineering teams and built a durable AI coding harness around Claude Code, then drove adoption from non-existent to organization-wide. Applied across customer-facing products, the harness reclaimed more than 550 development days during a six-week engagement.
What AI tools and approach did Edmunds GovTech use for software development?
The work centered on a custom AI coding harness built around Claude Code, activated on top of the company's existing enterprise Microsoft AI licenses. The experts paired the tooling with hands-on enablement across product management, engineering, and QA so teams could extend it themselves.
What results did Edmunds GovTech get from AI in product and engineering?
A codebase upgrade estimated at a year for a full team was completed by one engineer in weeks, a UI build scoped at three months shipped in three days, and requirements extraction dropped from a month to two or three days. The team also saw roughly 8x faster bug resolution and reclaimed 550+ development days across customer-facing products.
How long did Edmunds GovTech's AI adoption take to show results?
The engagement ran about six weeks, in the 4–8 week range, and the productivity gains appeared during that window rather than after a long rollout.
Who is this AI coding harness approach best for?
Private-equity-backed B2B software companies modernizing legacy platforms, and product and engineering organizations where AI adoption has stalled at experimentation and needs a durable, owned capability.

Have a similar challenge?

Ask whether this would work for you, or describe what you're trying to solve.
TELL US WHAT YOU'RE EXPLORING