Taking over maintenance of existing software
The developer has left, the company that built the application doesn't answer, and the business depends on it. We take over such systems: we analyze them first, then propose a plan.
Who it is for
- Companies left without the developer who built their application.
- Companies whose legacy system works but nobody dares to touch it.
- Companies that need a new feature in an application someone else built.
What you get
- Analysis of the code, database and servers, with a list of risks and priorities.
- Stabilization: backups, monitoring, fixes for critical bugs.
- The documentation that was missing.
- New features and gradual modernization without shutting the system down.
- Ongoing maintenance as agreed: monthly or on demand.
What we work on
ERP and business databases
More than ten years of experience with ERP implementations, SQL databases and business system integrations.
How we work together
- 1.A short call: you describe the process and what slows you down. It costs nothing and commits you to nothing.
- 2.Analysis and proposal: scope, solution, timeline and cost estimate, written so that a non-programmer can follow it.
- 3.Development in small steps: every week or two you see a working part and can try it out.
- 4.Delivery and support: we stay with you after launch, with fixes and improvements.
Frequently asked questions
Can you take over an application without documentation?
Yes. We write the documentation along the way, from the code and the database, and it stays with you.
Do you have to rewrite the application from scratch?
Rarely. It is usually cheaper and safer to stabilize the system and change it piece by piece.
How much does the analysis cost?
We agree on the scope and price of the analysis after the first call, once we see how large the system is.
Have a process worth fixing?
Write a few sentences about what your company does and where things get stuck. We reply quickly and to the point.