Taking over existing software
Your developer has left, your vendor no longer responds or your software runs on outdated technology. We first map what's there, document it and then take it over, so your software has a partner again.
When to take over
Your developer has left
The freelancer or agency that built your software is gone. Nobody knows the code anymore.
Your vendor is slow to respond
Questions sit for weeks and every change costs too much. You want a partner who follows up.
An outdated stack
Your software runs on a version that no longer gets updates. We modernise step by step, without rebuilding everything.
No documentation
Everything lives in one person's head. We write down how your software works, so you're no longer dependent on them.
Understand first, then take over. You know what you have before you decide.
- 01Free
Code audit
We go through your code, servers and data and discuss what we found. Free and without obligation.
- State of the code
- Risks & security
- Advice: keep building, modernise or rebuild
- Price for takeover and maintenance
- 02
Documentation
We write down how your software works: architecture, setup, integrations and the key processes.
- Technical documentation
- Integration overview
- 03
Takeover
We put the code, servers and all access in your name and take over management, planned so your users notice as little as possible.
- Code & access in your name
- Planned handover
- 04
Maintenance plan
You choose a level: Maintenance, Support or Partner. From then on we keep your software safe and keep building where needed.
- Maintenance, Support or Partner
Frequently asked questions
Nothing. The audit is free and without obligation. You keep the report, even if you don't continue with us.
It depends on the size and state of your software. After the audit you get a timeline, so you know when we take over.
Then we work out together where the code and servers are and how you get access back. That's often the first step of the audit.
Usually not. We prefer to build on what's there and modernise step by step. We only advise a rebuild when it's cheaper or safer, and the audit explains why.
You do. Code, servers and access are in your name. If you stop working with us later, you take everything with you.