Software that
holds up.
We build, rescue and scale systems for teams that cannot afford to rebuild again. Senior engineers only, measured before and after, and a written exit plan from week one.
Not craftsmanship as an aesthetic — the ability to change something on a Friday and still sleep.
Measured, never assumed. We find the real ceiling, then name the one after it.
Small reversible steps, your conventions, and a consultancy that is easy to leave.
- Practising since
- 2019
- Consultants
- Six, all senior
- Cities
- Copenhagen & Odense
- Notice period
- One month, either way
Most systems do not fail. They stiffen.
Almost nothing we are called into is broken. It works, it makes money, and every change costs a little more than the last one — until someone proposes a rewrite and eighteen months disappear.
We do the unglamorous alternative. Measure first. Fix the handful of things that actually carry the load. Put tests around the parts nobody dares touch, and move the system seam by seam while the business keeps running. Roughly a third of the time our first honest answer is that you do not need us — and we say so before an invoice exists.
Every engagement leaves behind a pipeline that runs the full suite in under ten minutes.
No optimisation merged without a before and after figure attached.
No migration plan with an irreversible step in it leaves our hands.
Six ways in.
Every engagement starts with a diagnosis and ends with a handover. What sits between them depends on which of these you need.
Product engineering
From a whiteboard to something your users can break.
We build and ship product software end to end — domain model, API, interface, pipeline, on-call runbook. Small teams, short feedback loops, and a codebase your...
Read moreScalability & performance
Find the ceiling before your customers do.
Traffic rarely grows politely. We measure where a system actually bends, fix the handful of things that matter, and leave you with the load model and...
Read moreLegacy modernisation
Change the engine without stopping the car.
Most systems we meet are not bad, just rigid: every change costs more than the last. We make them movable again through incremental strangler work, with...
Read moreQuality engineering
Confidence, expressed as a pipeline.
Quality is not a phase at the end of a project — it is how fast you can change something and still sleep. We build the...
Read moreArchitecture & due diligence
An honest second opinion, in writing.
Before you commit a year of budget — or buy someone else's codebase — it is worth having people who build these systems read it. We...
Read moreEmbedded teams
Senior capacity that arrives already knowing how to work.
Sometimes the plan is fine and you are simply short of people. We embed senior engineers into your team on your process and your board —...
Read moreNumbers, not adjectives.
Client names are withheld where the contract requires it. The figures are not.
Twelve times the shipments, on the same infrastructure bill
A booking platform that fell over every Monday morning. We found the real bottleneck in three days, and spent the rest of the engagement making sure it could not come back.
- p95 at peak
- 8.4s → 310ms
- Peak throughput
- 12× capacity
A decade-old monolith, made changeable again — without a freeze
Eleven years of accumulated software, four PHP versions behind, and a regulated product that could not stop shipping. We modernised it in place, two weeks at a time.
- Change lead time
- 11 days → 0.8 days
- Clinical path coverage
- 0% → 94%
They spent three days measuring before proposing anything. Every other firm we spoke to had a proposal ready before they had seen the code.
“Two consultancies told us to start again. Codense told us the boring truth: this is fixable, and you will keep shipping the entire time.”
“They were the first supplier who treated leaving as part of the job.”
Five steps, and you can stop after two.
The diagnosis is a complete deliverable in its own right. If it says the work is not worth doing, that is where we stop and say so.
-
01
Conversation
One hour, free
You describe the problem; we ask uncomfortable questions. By the end of it we will tell you honestly whether this is work...
-
02
Diagnosis
One to four weeks, fixed price
We get into the code, the pipeline, the data and the incident history, and take a baseline of the numbers we intend...
-
03
Agreement
A few days
A scope, a price, a named team and an exit plan — all before the work starts. Monthly rolling, one month notice...
-
04
Delivery
Two-week cycles
We ship to production every cycle, working inside your process and your repository. You get a demo, the current numbers against the...
-
05
Handover
Built in from week one
The last stretch of every engagement inverts: your engineers write, ours review. We are finished when your team has shipped a meaningful...
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
- Copenhagen & Odense