Skip to content
Boxed Online, home

Case study

The expensive platform we didn't buy

An architecture decision that avoided a costly licence, followed by a budget, vendor and approvals application built in two days.

A European healthcare distributorHealthcareAnonymised client work
QuotedDelivered
Estimated 15.5 team-weeks, delivered in 2 days
Quoted versus deliveredSlice plan and project notes, 6-7 September 2026

The problem

Technology spend, vendor contracts and approvals were tracked across spreadsheets and email. The obvious answer was a licensed low-code platform with a significant per-user cost.

How we approached it

  1. Compared the licensed platform with an in-house build on the new security framework
  2. Chose the build on total cost of ownership, and wrote the decision down
  3. Sliced the build into thin, testable increments

What was built

  • Budgets, virements and forecast versions
  • ERP actuals with run-rate status
  • Vendors with a four-condition contract activation gate
  • Approval tasks and tamper-evident ledgers

Stack

  • .NET 10
  • Angular
  • SQL Server
  • OpenTelemetry

What changed

  • Licence cost avoided before a line of code was written
  • A mobile-friendly app finance and IT both use
This build: estimate against delivery
  • Technology budget and approvals app

    Estimated: 15.5 team-weeks. Delivered: 2 days

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.