Map it, stabilize it, keep it moving. The first step costs nothing.
You have a system you cannot ship against fast enough, and you have already been burned by an agency that wanted a commitment before it understood the problem. Start by having one system read and written up, at no charge.
Engagements are monthly and sized to scope, and sized to land below the fully-loaded cost of one senior US engineer.
Map one system
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.
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.
Read access, and about an hour from someone who knows the system.
You want to see how we work before committing anything, and someone on your side can grant access and answer questions.
The assessment is yours whether or not we go further.
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.
The software was built by someone who is no longer around — an agency that moved on, a freelancer who left, or an AI tool that got you to a first version — and it now breaks in ways nobody can explain.
A system that meets the acceptance criteria, the evidence for every change, and a written list of what is still fragile.
43% of work was later redone, as of 2 August 2026. That is our own board, on the same measure you would get. We meter it as its own line rather than folding it into throughput, and it is still a watch item — not a solved problem.
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.
The system has to keep working while it keeps changing, and you would rather not hire a team to look after it.
Working software, the evidence for every change, and a dashboard of your running product.
Build something new
A defined scope taken through the same gated process our own products run on. You get the software and the delivery record — every ticket, every check, every decision and why it was made.
The scope is clear and delivery capacity is the constraint.
Working software, the evidence for every change, and the board we ran it on.
IT and security, managed
For a firm with no IT staff: an asset review, then infrastructure and access control set up properly once, then SIEM monitoring with a person reading it. The lightweight end of what we do — no full-time hire, no rip-and-replace.
Ten to two hundred people, enough infrastructure to matter and not enough to justify hiring for it.
A written inventory, an access policy you own, a restore you have watched succeed, and a monthly written position.
Four things, and you can estimate most of them yourself.
We would rather tell you what drives the figure than quote a range that turns out not to apply to you.
How much system there is
How old it is, and who is left
What it has to comply with
How long you need us
- —The initial assessment. If it is not useful you have lost nothing.
- —The delivery board. It is the same one we run on; there is no client edition.
- —Handover documentation. A handover you have to pay extra for is not a handover.
Step two is where we tell you if we are the wrong answer.
You can stop after any of these, and what we have written up by then is yours to keep.
A reply from a person
Usually within a working day, from a real address. Not a sequence.
A short call
The problem and the constraints. No deck, and no pitch — if we are not the right answer this is where we say so.
The map and the write-up
We read one system and report what we found, what we would build and what it would take. Yours to keep either way.
Some of what we are asked for, we should not be the ones doing.
The scope is genuinely unknown
Nobody on your side can say yes
A simpler tool would do
Start with one piece of work.
Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.
Talk to us