Software and apps
Legacy software, kept running and modernised.
When the developer is gone and the system still matters, we take it over: read it, document it, keep it running, and replace the parts that hold you back, one at a time.
- Move the next part over
When nobody dares to touch it
The system works, mostly. The person who built it left years ago, there's no documentation, and every change is a risk nobody wants to take. So the business works around it.
We start by reading it and writing down what it does. Then we keep it running, put it under version control and tests, and replace it piece by piece, so there's never a day without a working system.
Typical starting points
The developer is gone
We take the software over, read it, and write down what's there.
The platform is outdated
Moved to a current one, piece by piece, while the work goes on.
The data is a mess
Moved, cleaned and checked before the old system is switched off.
What's included
- A read-through and a written account of the system
- Version control, backups and tests around it
- A plan that replaces one part at a time
What's not
- A rewrite from scratch before we've understood the old one
How it runs
A call, a written scope and price, a build in steps you can try, and a handover with code and documentation.
More in this area
Tell us what slows you down.
A few lines are enough: what you want to achieve, and by when. We answer within one business day.