Fleet Management Software

How Ravn Turned Underspecified Tickets into Validated Specs with Claude Code

Ravn used Claude Code in plan mode to turn ADS's undefined business rules into validated specs and merged code, completing a warranty module that had been in development for six to seven months, and introduced a backend testing practice that took the codebase from zero unit tests to 1,602 and was adopted by ADS's own engineers.

Interested in AI Transformation?

The Challenge

ADS builds shop-management software for trucking fleets. Its warranty module had been in development for six to seven months and was roughly 30 to 40 percent complete by February 2026, held back by the complexity of the domain and by business rules the customer had never fully defined. The undefined-rules problem is the reason this needed a services partner rather than a tool. Somebody had to sit between a customer who could not specify the rules and a codebase that required them, produce a written interpretation, get it validated, and then build it.

The Solution

Ravn's backend engineers used Claude Code in plan mode on every feature: plan the change with Claude first, let it apply edits only when the plan is fully right, and otherwise approve edits piece by piece. The same loop turns loose requirements into written specs and prototypes that ADS validates before implementation. Ravn set up the backend testing practice, being test builders, a testing guide and a Given/When/Then pattern written into CLAUDE.md, which is how the practice propagated to the customer's own team rather than staying with the contractor.

The Outcome

The warranty module went from 30 to 40 percent complete after six to seven months of development to having the remaining roughly 60 percent finished, with the claims module finished rapidly. Tickets merged per month, each spanning backend, frontend and QA, went from about one per month between May and September 2025 and about 1.5 per month between October 2025 and March 2026, to about six per month between April and September 2026, peaking at nine in July 2026. The eleven months before Claude averaged roughly 1.3 tickets per month, so roughly six per month is about 4.7 times that average. Backend unit tests went from minimal coverage in March 2026 to 1,602 across 144 classes. Adoption: Claude Code is used on every feature Ravn delivered.

Tech & Cloud

Claude Code in plan mode, on ADS's enterprise Claude license. Project conventions and a Given/When/Then testing pattern are committed to the repository's CLAUDE.md, so every Claude session in the repository follows them, and ADS's own developers now write tests to that pattern. Specific model not yet confirmed; see internal notes.

MORE WORK