Existing Software

Rescue and modernise existing software

A legacy system someone else built, or an in-house project that stalled. We take it over and get it moving again.

Overview

What this is

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.

Included

What’s included

Code and infrastructure review

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.

Stabilisation

We get a reliable build and deployment running, then add tests to the risky areas and clear the bugs that interrupt daily work.

Modernisation

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.

New feature work

Once the ground is stable, we build the changes that were stuck in the backlog, in short cycles you can review.

Handover and documentation

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.

Signs

When software needs rescue and when it needs a rebuild

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.

Signs it needs rescue

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.

Signs it may need a rebuild

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.

Comparison

Rescue and modernise vs full rebuild

Rescue and moderniseFull rebuild
CostLower, spread across stagesHigher, mostly upfront
RiskLower: the system keeps running while it is fixedHigher: a new system must match the old one before it replaces it
Business disruptionSmallLarger, especially at cutover
When it fitsThe code works but is brittle, undocumented or stalledThe platform or data model cannot be saved
Getting started

What we need from you

Access to the code

The repository, or a copy of the code if there is no repository yet.

Access to hosting and accounts

The servers, cloud accounts, domains and third-party services the system depends on.

Someone who knows the history

A person who can answer questions about why it was built the way it was. The original team does not need to stay involved.

An honest list of what hurts

The bugs, delays and workarounds that cost you the most today, so we fix those first.

Risk

How we reduce the risk

A written assessment first

You get the condition of the code and the realistic options in writing, including the option to leave parts alone.

No big-bang rewrite

We make the risky areas safe and remove the worst friction, then work in short cycles.

Tests around what breaks

A reliable build and tests on the risky parts so changes stop causing surprises.

Documentation and handover

Up-to-date documentation and access to every account, so no one is locked in, including to us.

Cost

What rescuing or modernising software costs in Australia

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 sizeTypical costWhat it usually covers
Small$5k–$10kReview, then stabilising one system: a reliable build and tests around the riskiest parts
Medium$10k–$30kStabilisation 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 →
Approach

How we approach it

Understand

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.

Simplify

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.

Build

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.

Improve

We stay on to keep dependencies current and add features as the business needs them, with an eye on performance and running cost.

Stack

Tech we use

An honest starting point, not a fixed menu. We pick per project and tell you why.

  • Whatever's already in place
  • Python
  • Django
  • .NET (C#)
  • Angular
  • PostgreSQL
  • Next.js
  • Node.js
  • React
  • TypeScript
  • Flutter
  • AWS
  • GitHub
FAQ

Common questions

What is software modernisation?
Software modernisation means updating an existing system so it is safe, supportable and easy to change, without rebuilding it from scratch. It usually covers a reliable build, tests, up-to-date dependencies, current hosting and documentation.
How much does it cost to fix or modernise legacy software in Australia?
Projects land roughly between $5k and $100k+, depending on size, complexity and deliverables. Stabilising one system is about $5k–$10k, and wider modernisation $10k–$30k or more, at a fixed price after a review.
Can you work with old technology?
Yes. We start with whatever is already in place and only change what blocks progress. If part of the stack needs replacing, we explain why and what it would take before we start.
Can you take over a project from another agency or developer?
Yes. That is most of this work. We need access to the code and the hosting, plus someone who can answer questions about its history. We do not need the original team to stay involved.
Will you recommend a rebuild?
Only if the evidence points that way, and we will show you the reasoning. Most systems we look at are worth keeping and fixing. A rebuild is a large cost and we treat it as a last resort.
What if the code is in bad shape?
Codebases with no tests and no safe way to deploy are common. The first phase is about making one safe to change, and we tell you what that will take before you commit to it.
More

Related services

Three that often pair with this one. See all six services →

01

Custom Software Development

Systems that fit how your business actually runs, built from the ground up.

Learn more →
02

Bespoke SaaS

Your own platform, built to your process — not another off-the-shelf tool you have to bend around.

Learn more →
03

Web & Mobile Applications

Fast, reliable apps your customers and staff will actually want to use.

Learn more →

Last updated