01 / Development teams

Taking over and further developing existing software.

For stalled projects, departing suppliers, technical debt and software without a clear owner. We first map the software, make it stable and then develop it further.

02 / Familiar situations

Software you run on, but nobody looks after any more.

A takeover usually starts not as a plan, but as a problem.

  • The supplier stops

    Your supplier stops or terminates the contract, and the software has to keep running.

  • The developer leaves

    The only person who knows the software is leaving, and little has been documented.

  • The project is stuck

    A lot has been invested, but delivery keeps slipping and trust is missing.

03 / What you get from us

Stable first, then onwards.

We take nothing over blindly. First we want to know what is there and what it can bear.

What we do

  • mapping the codebase, architecture and hosting;
  • identifying risks and immediate bottlenecks;
  • making the software stable and manageable;
  • filling gaps in the documentation;
  • drawing up a plan for further development.

What you notice

  • an honest picture of the state of your software;
  • less dependence on one person or party;
  • a well-founded choice between building on and replacing;
  • software that can be changed safely again;
  • a party that takes responsibility.

04 / Our approach

From uncertainty to control.

We carry out a takeover in clear steps, so you always know where you stand.

  1. Step 1

    Inventory

    Arranging access to code, servers and documentation, and gathering knowledge from whoever is still around.

  2. Step 2

    Assessment

    We assess the code, architecture and technical debt and report what we find.

  3. Step 3

    Stabilise

    We tackle the biggest risks and make sure the software is manageable.

  4. Step 4

    Further development

    After that we keep building, or help prepare a replacement if that is the wiser course.

05 / Good to know

Questions about takeovers.

Can't find your question? Feel free to send us a message.

What if the code is of poor quality?

We will tell you honestly, with our reasoning. Sometimes improving step by step is sensible, sometimes rebuilding is cheaper. We discuss that together.

Do you need access to the old supplier?

It helps, but it is not a requirement. With access to the code and servers we can reconstruct a lot.

Which technology do you work with?

Preferably TypeScript and Vue.js on the frontend and C# / .NET with PostgreSQL on the backend. We also have experience with React/Next.js, Angular and Node.js, and check in the intake whether we are a good fit.

Which software needs to be in good hands?

Tell us what is going on and how urgent it is. We will let you know how we would approach the takeover.