Service 02

Software takeover and modernisation

We take over knowledge of the existing solution, name the risks and propose a path to stabilise the system, modernise it and develop it predictably again.

We do not start with a rewrite by default. We look for changes that have a real impact on further development, operation and costs.

Discuss an existing application

Where you are

Typical situations we help with

01
A supplier or key developer is leaving and the knowledge of the system lives only in the code.
02
Every change takes longer and breaks something it should not.
03
The system runs on outdated technology that is hard to operate and secure.
04
You need to move the application to the cloud or a new database without downtime.
05
You are considering a rewrite from scratch and want to know whether it is really necessary.

What you get

Outputs that stay with you

a technical audit: the state of the code, architecture, operation and security
named risks ordered by impact
a step-by-step modernisation plan that can be deployed continuously
takeover of development and operation as agreed
documentation the system did not have before

OutcomeA system that can be operated safely and developed further.

How we work together

From the first conversation to a validated outcome

First conversation

We find out what the system does, who depends on it and what troubles you most.

Output: audit scope

Technical audit

We review the code, architecture, operation and security and order the risks by their impact on development, operation and costs.

Output: a report with risks and a recommendation

Modernisation plan

We propose steps that can be deployed gradually and without downtime. We recommend a rewrite only where it pays off.

Output: plan, schedule and price

Takeover and delivery

We take over development, stabilise the system and modernise it in verifiable steps.

Output: a system that can be operated and developed safely

Good to know before we start

01Does the old system have to be rewritten?

Usually not. A rewrite is expensive and risky. We first look for the changes with the biggest impact and recommend a full rewrite only where it really pays off.

02Will you take over a system from another supplier?

Yes. We start a takeover with an audit so we know what we are taking over, and gradually move the knowledge of the system into documentation and the team.

03Can modernisation happen without downtime?

That is what we design it for. Examples are a zero-downtime SaaS migration and replacing a NoSQL layer in production.

04How much do the audit and modernisation cost?

The audit has a fixed scope. We set the price of modernisation from the plan that comes out of the audit.

Next step

When an application works, but developing it further keeps getting harder.

Describe your situation in a few sentences. We will get back to you and arrange a first conversation after which you will know how to proceed.

Discuss an existing application

Other services