Inherited a System You Don’t Trust? We’ll Take It Over.
Developer gone quiet? Agency disappeared? Your in-house dev left and nobody understands the code? Netgen takes over existing software systems. We audit what is there, stabilise what is broken, and give you a local team you can actually reach.
Signs you need a software takeover
Not every software problem calls for starting over. But some situations go beyond normal support and maintenance. If any of the following sounds familiar, a formal takeover is likely the right move.
Your business depends on a system nobody fully understands
The original developer — whether a freelancer, an internal team member, or an agency — is gone. The person who built the system never wrote documentation, or what documentation exists is out of date. New developers you have brought in have looked at it, shaken their heads, and walked away. Your business keeps running, but only because nothing critical has broken yet.
Your developer disappeared and you do not have the source code
This is more common than it should be. In some cases, the code lives on a developer's personal server or laptop and was never handed over. In others, it sits in a repository you do not have access to. Without the source code, you cannot fix bugs, add features, or move to a different developer. You are stuck.
The system is live and breaking and there is nobody to call
An error message has appeared. A report is producing wrong numbers. A key function stopped working after a server update. You have raised it with whoever built it, and either nobody responds or the fix costs more than the original build. Meanwhile your team is working around the problem and your clients are noticing.
You have inherited a system as part of a business acquisition
You bought a business and the software came with it. Nobody who sold it to you really understood the technical side. You are now responsible for something you did not build, cannot easily modify, and are not sure you can trust.
You are locked in because moving feels too risky
The thought of rebuilding feels expensive and disruptive. But staying put feels worse. Staff have developed workarounds. The system has not been updated in years. Security patches have not been applied. You know there is a problem — you just do not know how bad.
If you recognise any of this, the right first step is a code and security audit. Not a commitment to rebuild — just a clear, written picture of what you have and what it will take to make it safe. Netgen has done this for businesses across South Africa since 2000. We will tell you honestly what we find.
What we do
Technologies we take over
We are not tied to one language or framework, so we can adopt most established stacks without forcing a costly rebuild. We regularly work in:
- Backend: C#, .NET, Python, PHP
- Web front-end: React, JavaScript, WordPress
- Mobile: React Native, .NET MAUI, Xamarin (iOS and Android)
- Databases: Microsoft SQL Server (MS SQL), MySQL
- Integration and AI: REST APIs, SaaS platforms, and GPT/RAG bolted into your existing system rather than a rebuild
Inherited something not on this list? Tell us. Chances are we have worked with it or something close.
Rewrite vs rescue — when each makes sense
One of the most common questions we get after a code audit is: should we fix what we have, or start again? There is no universal answer. What we can tell you is what we look for when we make that recommendation.
When rescue is the right call
Rescue — stabilising, securing, and incrementally improving the existing system — makes sense when the core architecture is sound, even if the surface is messy. Specifically:
- The system does what the business needs, mostly. The pain is in specific broken features, missing integrations, or neglected maintenance — not in a fundamentally wrong design.
- Your data lives in the existing system and migrating it cleanly would be complex or risky.
- The business cannot afford several months of disruption while a new system is built and staff are retrained.
- The codebase is in a language or framework Netgen can work with (which covers most of what we encounter).
- A rewrite would cost significantly more than a structured programme of improvements.
Most systems we audit are worth rescuing. Businesses typically come to us thinking they need to rebuild everything, and after the audit we find that targeted stabilisation and a clear improvement roadmap is a better use of budget.
When a rewrite makes more sense
Sometimes the right answer genuinely is a rewrite. We will tell you this even though it means a larger project. However, if the technology is old and it would cost more in the long run to continue down that path, we also recommend rewrites — updating the frameworks and languages to give the system a viable future:
- The existing system is so poorly structured that every change breaks something else. The cost of maintaining it exceeds the cost of replacing it within a reasonable timeframe.
- The technology is end-of-life with no viable upgrade path — not just old, but truly unsupported with known, unfixable security vulnerabilities.
- The business requirements have changed significantly since the system was built. The original system was the right solution for a different business; it is not the right foundation for where you are going.
- The audit reveals that the system cannot be made secure without essentially rebuilding it.
We do not recommend rewrites lightly. A rewrite is disruptive, more expensive upfront, and carries its own risks. But if a rescue would cost more over three years than a replacement, we will say so.
The audit is where this question gets answered
Our paid audit (typically R25,000 to R45,000 depending on codebase size) exists precisely to answer this question with evidence rather than assumptions. You get a written report. You decide what to do with it. There is no pressure to continue with Netgen.
Why Netgen
- 25+ years in business, since 2000.
- 100% local team. Cape Town and Johannesburg, no offshoring.
- BBBEE Level 2 compliant.
- Transparent pricing. An audit typically runs R25,000 to R45,000 depending on codebase size and complexity.
- We integrate AI (GPT/RAG) into existing systems rather than forcing a rebuild.
How it works
- Free initial consult. Tell us what you have inherited.
- Paid audit. We review the code and give you a written risk report.
- You decide. Stabilise and continue with us, or walk away with a clear picture. No lock-in.
We are grateful to work with incredible clients
Common questions about software takeovers
My developer disappeared and I do not have the source code. Can you help?
Yes — this is one of the most common situations we deal with. The approach depends on what you do have. If the system is live and running, we can often reverse-engineer enough from the deployed application, database structure, and any partial documentation to establish a working baseline. If there is a compiled application but no source, we will be honest about what is and is not recoverable. In some cases we can work with what exists; in others, a controlled rebuild of specific components is the pragmatic answer. The starting point is always a conversation and, if there is enough to work with, a formal audit. Contact us and we will tell you plainly what your options are.
How much does it cost to take over an existing system?
The process starts with a paid audit, which typically costs R25,000 to R45,000, depending on the size and complexity of the codebase. The audit gives you a written risk report — security issues, structural problems, immediate versus deferred fixes — and a clear recommendation. From there, stabilisation work is scoped and priced based on what the audit finds. Ongoing development is billed on a retainer or project basis. We do not ask you to commit to anything beyond the audit upfront.
Can you fix a system you did not build?
Yes. This is a significant part of what we do. We work across a range of languages and frameworks — C#, .NET, Python, PHP, React, React Native, and others. We are not tied to a single stack, which means we can take over most established systems without forcing a rebuild. The first step is always understanding what you have, which is what the audit is for. If we encounter something outside our range, we will tell you that before you commit.
Rescue or rewrite — how do you decide?
We recommend whatever makes more sense commercially and technically for your situation — not whatever is the larger project for us. After the audit, we produce a written recommendation with the reasoning behind it. The key factors are whether the existing architecture can be made stable and secure at a reasonable cost, whether your data can be preserved, and whether the cost of maintaining the existing system over time would exceed a structured replacement. Most systems we audit are worth rescuing. Some are not, and we will say so.
How long does a software takeover typically take?
The initial audit takes one to three weeks, depending on codebase size. Following that, the time to stabilise a system varies considerably based on what the audit finds. A system with isolated issues — a few security vulnerabilities, some broken integrations, a missing deployment pipeline — can be stabilised in four to eight weeks. A system with deeper structural problems may require a longer programme of work, delivered in prioritised phases so the most critical issues are addressed first. We do not give timelines before the audit, because without seeing the code, any estimate would be guesswork. What we can commit to is a clear roadmap once we have completed the audit.
What our clients say
Take back control of your system
Netgen provides audits, stabilisation and ongoing ownership for inherited and legacy software systems.