An AI tool built your first version. We keep it working.
We take over software that was generated fast and now has to be depended on. We map it, stabilize it against acceptance criteria you agree in writing, then maintain and improve it, with the evidence for every change.
It is for you if the first version came together in weeks, customers now use it, and each fix seems to break something nobody touched.
Built by people who have since moved on, rather than by a tool? That has its own page.
Generating the code was never the slow part. Reviewing it is.
An app builder writes more code in an afternoon than one person can read in a week. The first version works because it is small. Then it grows, its parts start to depend on each other in ways nobody wrote down, and a change in one place fails somewhere else.
This is not a guess about your codebase. Published 2026 research found 1.7× more issues in pull requests containing AI-assisted code than in human-written code (arXiv preprint 2603.28592, March 2026).
Published figures, directional rather than audited. Three of the four come from the same 2026 analysis; the first is a separate preprint. Every one is linked so you can weigh it yourself.
Map it, stabilize it, keep it moving.
Map one system · no charge
Read access to one system. We map what it is, what depends on what, and where the gaps are, then write up what we found — what we would build, what we would not, and what we are assuming.
Stabilize it
Two to four weeks on the system we mapped. Before any work starts, we agree in writing what done means — the acceptance criteria each change has to meet — and the scope and price for reaching it. Every change goes through the same six checks as our own products, and you can watch it happen.
Maintain and improve it
Fixes, improvements and new features on a system you depend on, in small tracked changes, each through the same checks. A Forward Deployed Engineer is your named contact and watches the running product with you.
Done is written down first
All 6 checks, on every change
You watch the running product
That a rewrite will never be needed. Stabilizing is usually cheaper than starting again. When the map says otherwise, that is what the write-up says, and it is still yours to keep.
That our own process is finished. Our work record says 43% of the work was later redone, as at 2 August 2026. We publish it because it is the same measure you would be given. All of it →
Start with the map.
Read access to one system, and we come back with what we found and what stabilizing it would take, before any commitment. About a week from read access to write-up. One service or repository up to roughly 50,000 lines; a larger estate we scope first rather than promise a week for.
Map it — no charge