Skip to content
Boxed Online, home

Case study

A 5.5-week refactor, 89% done in a morning

A whole-repository audit and refactor plan for a personal finance app, executed by agents the same morning.

KashPots (our own product)Personal finance
QuotedDelivered
Estimated 5.5 weeks, delivered in 4 hours
Quoted versus deliveredRefactor plan and branch commits, 7 September 2026

The problem

A growing codebase had collected inconsistencies that slowed every new feature.

How we approached it

  1. An audit produced a 64-task plan, estimated at 5.5 engineer-weeks
  2. Agents executed the plan in parallel lanes, with the test suite as the safety net

What was built

  • 57 of 64 refactor tasks
  • A test suite repaired to 607 of 607 passing

Stack

  • Angular
  • .NET 8
  • SQL Server
  • Azure Container Apps

What changed

  • Faster feature delivery afterwards
  • No regressions: every test green
This build: estimate against delivery
  • KashPots refactor

    Estimated: 5.5 weeks. Delivered: 4 hours

Bars are to one scale in working days, at five days to a week, using the lower figure of any range. A few hours is drawn as half a day, and the shortest bars have a minimum width so they stay visible. Builds that were never estimated are left out.

Want the same result on your problem?

In 30 minutes you'll know whether to fix it, buy it, build it or leave it. No pitch deck.

We reply within 2 business days.