The software works. Changing it is what hurts.
We replace the parts that block your roadmap, one at a time, without taking the product offline or asking for a rewrite you cannot fund.
This is for you if
- Every estimate comes back larger than it should, and nobody can say exactly why.
- A dependency, framework or platform is now old enough to be a risk.
- The people who wrote it have left.
- You need to keep shipping to customers while the work happens.
And it is not, if
We will not sell you a full rewrite because it is easier to quote. If the honest answer is that three modules need replacing and the rest is fine, that is the proposal you get.
What you actually receive
An assessment you could act on without us
What is actually slowing delivery, ranked by what it costs you, with the cheap wins separated from the structural ones.
A replacement sequence
Which part moves first, what it connects to, and how the product stays up while it happens.
Migrated, tested, in production
Each slice goes live on its own rather than waiting for a single terrifying cutover.
Documentation your team keeps
Written for the engineer who inherits it, not for the invoice.
How the engagement runs
It starts with an assessment against your real codebase and your real constraints. You get the findings whether or not you continue with us. From there we work in slices, each one shippable on its own, so the value arrives before the project ends and you can stop at any boundary.
What does a project cost?
We do not publish a number, because a quote written before anyone has looked at your problem is a guess dressed up as a price. We scope first, as a small paid piece of work, and that produces a fixed shape and a real figure. If the scope shows the project is not worth doing, you have spent a fraction of a build to find that out.
How long will it take?
Ask us after the scope, not before. Anyone quoting a duration off a first call is quoting a hope. What we can tell you up front is the shape: releases land continuously against a preview environment you can open, so you are never waiting months to see whether it is going the right way.
Do you work fixed price or time and materials?
Both, depending on what the work actually is. A defined release with an agreed scope can be fixed. Ongoing engineering against a moving roadmap cannot honestly be, and anyone who fixes it is pricing in the risk and charging you for it. We will tell you which one your project is.
We are early and pre-funding. Are we too small?
Possibly, and we will say so. If you are still testing whether anyone wants this, a full build is an expensive way to find out. Tell us where you are and we will tell you what would answer the question faster, even when the answer is not us.
Can you work with our existing team and codebase?
Yes, and most of our work is exactly that. We have joined codebases whose original authors had left and worked alongside in-house teams who needed a discipline they did not have, usually mobile or front end. We read before we rewrite.
Start the conversation
Tell us what you need to ship. You will get a straight answer on whether this is the right engagement for it.
The others
- Build a productA working release in your customers’ hands, design included.
- Fractional CTOSenior technical leadership without the full-time hire.
- Connected productsThe software that turns working hardware into a product a customer can use.
- Ongoing engineeringA senior team on your roadmap, release after release.