Custom Software Development
Systems that fit how your business actually runs, built from the ground up.
Learn more →A legacy system someone else built, or an in-house project that stalled. We take it over and get it moving again.
You have a legacy system that runs part of the business, but the team that built it has moved on, or the internal project ran out of momentum. The code still works, mostly, and starting again from a blank page would be expensive and risky.
We step in and read the codebase, then make it safe to change: a reliable build, plus tests around the parts that break. After that we fix what is brittle and build the features that were on hold.
We read the codebase and map how it is deployed, then give you a written account of its condition and what the fragile parts would take to fix.
We get a reliable build and deployment running, then add tests to the risky areas and clear the bugs that interrupt daily work.
We update the dependencies that are out of support and replace the parts that actively block progress. Hosting comes up to a current, supportable setup at the same time.
Once the ground is stable, we build the changes that were stuck in the backlog, in short cycles you can review.
You get up-to-date documentation and access to every account and service. The codebase is left in a state another developer could pick up without a long ramp.
Most stalled systems are worth keeping. A rebuild is a large cost, so we treat it as a last resort and show you the evidence before recommending one.
The original team has gone. Nobody wants to deploy on a Friday. Dependencies are out of support and bugs keep returning because there are no tests. Features have sat in the backlog for months.
The platform it runs on is end-of-life with no upgrade path. The data model fights how the business now works. The cost of each change is higher than the cost of replacing it.
| Rescue and modernise | Full rebuild | |
|---|---|---|
| Cost | Lower, spread across stages | Higher, mostly upfront |
| Risk | Lower: the system keeps running while it is fixed | Higher: a new system must match the old one before it replaces it |
| Business disruption | Small | Larger, especially at cutover |
| When it fits | The code works but is brittle, undocumented or stalled | The platform or data model cannot be saved |
The repository, or a copy of the code if there is no repository yet.
The servers, cloud accounts, domains and third-party services the system depends on.
A person who can answer questions about why it was built the way it was. The original team does not need to stay involved.
The bugs, delays and workarounds that cost you the most today, so we fix those first.
You get the condition of the code and the realistic options in writing, including the option to leave parts alone.
We make the risky areas safe and remove the worst friction, then work in short cycles.
A reliable build and tests on the risky parts so changes stop causing surprises.
Up-to-date documentation and access to every account, so no one is locked in, including to us.
Projects land roughly between $5k and $100k+, depending on size, complexity and deliverables. The code and infrastructure review comes first, and every stage after it is quoted at a fixed price.
| Project size | Typical cost | What it usually covers |
|---|---|---|
| Small | $5k–$10k | Review, then stabilising one system: a reliable build and tests around the riskiest parts |
| Medium | $10k–$30k | Stabilisation plus updating dependencies and hosting, and some of the backlog features |
| Large | $30k–$100k+ | Staged modernisation of a large or multi-system codebase |
Start with a fixed-price Discovery, which is separate from the build cost. For adding AI features to a system you already run, see AI assessment and deployment. More on pricing in the FAQ.
If this sounds like your project, Discovery is the next step.Start with a fixed-price Discovery — you get the scope, the plan and the number before you commit.
See how Discovery works →We spend the first days reading the code and running the system, not rewriting it. You get an honest assessment of where it stands and the realistic options, including the option to leave parts alone.
We resist a full rebuild. Most stalled systems need a smaller intervention that makes the risky areas safe and removes the worst friction, leaving a clear path for the rest.
Senior developers work in short cycles on a codebase that now has tests and a working pipeline. You see progress every couple of weeks and can change priorities as you go.
We stay on to keep dependencies current and add features as the business needs them, with an eye on performance and running cost.
An honest starting point, not a fixed menu. We pick per project and tell you why.
Systems that fit how your business actually runs, built from the ground up.
Learn more →Your own platform, built to your process — not another off-the-shelf tool you have to bend around.
Learn more →Fast, reliable apps your customers and staff will actually want to use.
Learn more →Last updated