Business system takeovers and maintenance

We take over business systems that have become slow, error-prone or left without a developer, find the causes of the problems and get work running normally again. We work with Laravel, Statamic, Drupal and other PHP projects, and after the takeover we maintain the system, build integrations and develop new features. On esfondi.lv, the Ministry of Finance's portal, for example, pages that took about five seconds to load now open instantly.

What the service covers

Fast diagnostics
We first find out why the system is slow, throws errors or stops, and fix whatever disrupts your work the most.
Access and knowledge transfer
We sort out access to the server, repository, database and external services, and gather what is known about the system in one place.
Performance and stability
We optimise queries, caching, queues and server settings so the system stays fast even with large volumes of data.
Integrations
We maintain and fix connections to accounting, warehouse, payment and government information systems.
Updates and security
We upgrade the framework, PHP and libraries to supported versions and install security fixes, testing everything in a staging environment first.
Further development
Once the system is stable, we keep developing it with new features and process automation.

How the takeover works

Conversation and access

We find out what is happening with the system, who depends on it and what access is available.

Staging and diagnostics

We set up a copy of the system in a staging environment and reproduce the problems there, so nothing changes in production before we know the cause.

Urgent fixes

We fix the errors that stop work or put data at risk, testing them in staging before release.

Plan

We prepare a change plan with priorities, risks and scope of work.

Maintenance

We agree on the scope of maintenance, response times and further development.

We'll take over your system and put it in order

Tell us what's holding up your work and attach an error example if you have one. We'll tackle the problem itself first. We reply within one working day.

Request a takeover

When a system needs taking over

We take over CRMs, ERPs, client portals and other business systems when the previous developer is no longer available, the system slows down as data grows, the framework version has reached end of support, or errors keep recurring and nobody knows why. Often the system doesn't need rebuilding, because finding and removing the causes is enough.

Getting to the root cause

We analyse the code, database queries, logs, queues, the server and the integrations. We trace each error back to its source and fix the cause, not just the symptoms. That is how we also resolve problems that earlier one-off fixes only ever patched for a while.

esfondi.lv takeover and optimisation

We took over esfondi.lv, the Ministry of Finance's portal built on Statamic and Laravel, from another developer when its pages took about five seconds to load. We simplified the data queries, moved the cache and sessions to Redis and put the server in order. Pages now open instantly, even without a cache, and we keep working on the integrations and further development of the portal. Read about the project

Keep the value of what you've built

We keep the parts of the system that work well and rework whatever holds back your operations and further development. We set up a staging environment and an orderly release process, so new features can go live regularly and with less risk to your daily work.

One team for maintenance and development

After the takeover we look after updates, error monitoring, the database and the server, document how the system is built and develop new features. Even when your needs become more complex, you don't have to look for a new developer.

For public sector institutions

We work with staging environments, documented changes and handover reports, as the maintenance of public information systems requires.

Frequently asked questions

Can you take over a system if the previous developer is gone and there's no documentation?
Yes, that's a common situation. As long as there is access to the server or the code repository, we study the code, database, server settings and integrations ourselves and document them during the takeover.
Will the system need to be rebuilt?
Not always. We first assess what can be fixed. If a rebuild makes more sense, we compare both routes by cost and risk.
How quickly can you start?
Urgent problems come first. We agree when to start after the first conversation, once we know what has happened and what access is available.
What does the price depend on?
On the size of the system, the state of the code and server, the number of integrations and how many urgent fixes are needed. We give you the scope of work after the diagnosis.

Related services