ai receipts
Search your own problem
Case study · From the Pluris libraryReceipt no. 7112
What sucked

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.

Technology & SoftwareProduct & Engineering4–8 weeks
What they built

Bonsai Labs embedded with Edmunds GovTech's product and engineering teams and built a durable AI coding harness around Claude Code: documented, extensible, and replicable across the company's codebases. Alongside the tooling, they ran hands-on enablement from product management through engineering and QA, so teams could extend the harness and keep building on their own.

What changed
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.

Time to results
4–8 weeks
Company size
251-1,000 people
More fixes like this
Who did it
Csongor Barabasi
Bonsai Labs

Vetted by Pluris.