Eleven years of grant software, made changeable again
A working system nobody dared touch. We moved it seam by seam, in production the whole time, with no cutover weekend.
- Change lead time, before
- 6 weeks
- Change lead time, after
- 4 days
- Cutover weekends
- None
- Coverage on money paths
- 94%
Example An illustrative case, not a delivered engagement. The figures below are invented and are here so the layout can be reviewed — replace this record with real work before publishing.
The situation
The platform processed grant applications correctly and had done for eleven years. It also took six weeks to make a change that should take two days, ran on a framework two major versions out of support, and had one developer who understood the payment reconciliation. A rewrite had been costed at eighteen months and shelved twice.
What we did
We characterised the parts nobody would touch with tests before changing anything — the reconciliation logic first, because that was the risk that mattered. Then branch-by-abstraction, one seam at a time: each step shipped on its own and could be reversed on its own. The framework upgrade happened underneath, in increments, rather than as an event. No migration plan we handed over contained an irreversible step.
Where it landed
Change lead time went from six weeks to four days. The framework is current and on a supported track. The reconciliation logic has tests and three people who can explain it, and the last quarter of the engagement was their engineers writing while ours reviewed.
More work.
A monitoring platform that keeps European data in Europe
Six monitoring tools most teams buy separately — uptime, API checks, recorded browser flows, visual regression, sitemap scanning and heartbeats — behind one dashboard, one alert engine and one on-call chain. Built and operated by us, hosted entirely in the EU.
- Tools in one suite
- Six
- Pages per full-site scan
- 500
- Fastest check interval
- 60s
A checkout that stopped falling over on campaign days
Peak traffic took checkout down three times in one quarter. We measured where it actually bent, fixed four things, and left the load model behind.
- Checkout p95, before
- 4.2s
- Checkout p95, after
- 780ms
- Peak orders held
- 2x
Tell us what is not working.
An hour on a call, no charge and no deck. We will tell you honestly whether this is work we are good at — and if it is not, who to talk to instead.
- Reply within
- One working day
- First call
- One hour, free
- Notice period
- One month, either way
- Based in
- Odense & Copenhagen