Netpower WEB Solutions AS · Further development and takeover
We take over your system. Whoever built it.
Custom solutions in Visual Basic, C#, Java, PHP, .NET, Python or something else entirely. The supplier is gone, or nobody dares to touch the code. With Claude Code, Codex or Grok in the hands of senior developers, we get an overview of an unfamiliar codebase in days, not months.
Visual Basic · C# · Java · PHP · .NET · Python · and more
Sound familiar?
The system still does its job. The problem is everything around it: no documentation, no tests, nobody who knows the code. We take over where the previous supplier stopped.
A good fit if you …
- Lost the supplier that built the solution
- Lost the key person who was the only one who knew the code
- Have no up-to-date documentation
- Avoid changing anything, in case something else breaks
- Are years behind on security updates
- Have built spreadsheets and manual routines around the system
What you get
What you buy is control over a system nobody dares to touch today.
- A written map of your own codebase — you know what you own, and what has to be dealt with first.
- Security updates running again — dependencies are lifted, and the gaps closed in priority order.
- An agreed response time on faults — in writing, with named people behind it.
- Maintenance we can estimate — after the mapping you get an hour estimate per change. Tests and documentation make that estimate checkable.
- Code and hosting in the same group — WEB Solutions extends the code. IT Solutions can run it in Stavanger.
Proof: we have maintained and developed iQbank.
Customers we have done this for: iQbank Kolumbus
Two routes: take over or rewrite
After the mapping we recommend the route that pays off for you. Usually the answer is takeover first, and a rewrite only when the numbers justify it.
Route 1 · Takeover
Takeover and maintenance
First we read the code with AI tools and senior developers, and write down how the solution actually fits together: functions, integrations, data model, dependencies and risks. Then we take responsibility for it.
- Security updates for frameworks, packages and platform
- Bug fixing within an agreed response time
- New functionality at a steady pace
- Automated tests around today’s behaviour
- Hosting in Netpower’s own data centre in Stavanger if you want it
The tests are written around the behaviour the solution has today, before we change anything. That way a new feature cannot break what worked yesterday, or open a hole that was not there before.
Route 2 · Rewrite
A full rewrite in months, not years
AI tools read the old application and produce a map of functions, screens and rules. We check that map against the code and with you — a starting point, not a promise that everything has been found. The team then rebuilds the solution on a modern platform, using Claude Code, Codex or Grok. What took years before 2025 now takes months.
- A mapping we walk through with you before the first line of code
- Data migration from the old database to the new one
- Parallel running until you trust the new system
- An hour estimate for ongoing maintenance after the mapping
- Changes without tearing at old spaghetti code
Cost-efficient, because the mapping and much of the coding is done with AI, steered by developers who have done this before.
How we do it
The same approach whether we take the solution over or rebuild it.
1. Mapping with AI
We read the code and map functions, integrations, data model and risks. It takes days, not months, and you get the overview in writing.
2. A test net around today’s behaviour
Before we change anything, automated tests pin down how the solution behaves right now. That is the safety net the rest of the work rests on.
3. Takeover or rebuild
We take over maintenance, support and hosting, or we start the rewrite. The choice rests on the mapping, not on a gut feeling.
4. Further development at a steady pace
New features ship regularly, with tests and a developer review before every release. You deal with one team.
Security and testing
An old system is rarely insecure on purpose. It is simply a long time since anyone looked.
- AI-driven review of the codebase and every dependency
- Known vulnerabilities in old packages are found and closed
- Tests run before every change reaches production
- Everything the AI proposes is reviewed by a developer
- Access control, logging and backup are reviewed at the same time
What customers ask first
“The code is 15 years old and undocumented”
That is the norm in this kind of work. The AI tools read the whole codebase and give us a map in days. The documentation gets written as we go.
“Do we have to rewrite everything?”
No. We start with a takeover. We recommend a rewrite only when it pays off, and then we say plainly why.
“How long does a rewrite take?”
Months, not years. How many depends on the size of the solution, and you get that answer after the mapping.
“What does maintenance cost afterwards?”
It depends on the solution. After the mapping you get an hour estimate. Tests and documentation make the next change checkable — not a promise that it will cost less.
Other services within development
Custom development · Integrations · Mobile development · DevTeam for hire · Netpower data centre · All development services
Next step
Do you have a system nobody dares to touch?
We look at the code, map what it actually does, and tell you what should happen next. No obligation, and you are left with a concrete overview.