Maintenance and evolution

We take care of corrections, updates, and functional evolution of your applications with agreed priorities and visibility on what is being done. The goal is for your platform to remain stable and secure, and for technical debt to decrease over time instead of growing.

What problems do we solve

• Obsolete versions and pending updates. Keeping the core, modules, and dependencies up to date avoids security risks and forced migrations at the worst time. If your platform uses Drupal 10, which reaches end of life in December 2026, we explain what to do in our action plan for Drupal 10.
• Recurring errors that no one resolves. We look for the cause, not just the symptom, so the same problem doesn't come back in the next campaign.
• A platform that no longer evolves at the pace of the business. We combine maintenance with planned evolutionary improvements. When the leap is greater, we address it as a legacy application modernization and migrations project.
• Dependency on the person who developed the system. If no one else knows your application, we document it and organize its knowledge so that it stops being a black box. This includes digital platforms and e-commerce that we did not build ourselves.

Two modalities

Hour package. You hire a number of hours that are consumed according to your requests: corrections, adjustments, or small improvements. It fits when needs are variable or occasional.

Fee. A periodic amount with an agreed scope, which can include updates, corrective maintenance, and a commitment to evolution that we plan with you. It fits when the platform is critical and you want continuity and predictability.

The details of each modality are specified in the proposal, according to the state of your application and what you need.

In both modalities, you know how each hour has been invested and what the next priorities are.

What is included and what is not

Includes:

• Corrective maintenance: diagnosis and correction of errors.
• Security and version updates of the software: core, modules, libraries, and dependencies.
• Planned evolutionary improvements and new functionalities.
• Progressive reduction of technical debt.
• Technical documentation and the decisions we make.

Generally does not include:

• Server administration, hosting, or cloud infrastructure.
• System operations, DevOps, and 24/7 on-call support.
• Cybersecurity as an independent service (infrastructure security audits or penetration testing).

We focus on software. When an update requires changes to the server, we usually coordinate with your hosting provider or your systems team, who are the ones who apply them. Large evolutionary projects are budgeted separately, as a custom software development project.

How we work

1. Startup. If we did not develop the application ourselves, we always start with an initial review of the code, the environment, and the available documentation, to understand what we receive and what risks it has. It is an essential step before committing to maintain it.
2. Agreed priorities. We define with you how changes are requested, how they are prioritized, and what is considered urgent.
3. Visible work. Each intervention is recorded and documented. We periodically review the status of the platform and the priorities.
4. Planned evolution. We propose improvements and reduction of technical debt before they become a problem.

Related case: FastBill

FastBill is one of the leading European solutions for online invoicing. Since 2019, we have been taking care of the continuous evolution of its web platform in Drupal. The collaboration, initially focused on evolutionary changes, has become a sustained transformation: a content architecture based on reusable components, technical SEO, performance improvements, the evolution to Drupal 10, and strengthening security. The result is a more stable platform and an editorial team with more autonomy.

Frequently asked questions

Do you maintain applications that you did not develop?

Yes, as long as we start with an initial review of the code and the environment to understand its state and risks. With that information, we agree on how to maintain it.

What is the difference between the hour package and the fee?

The hour package is consumed according to your requests and fits variable needs. The fee has an agreed scope and a stable commitment, and fits critical platforms that need continuity.

Do you also take care of the servers?

In general, no. We focus on software, and when it is necessary to touch the server, we coordinate with your hosting provider or your systems team, who manage it.

What happens if an urgent problem arises?

At the start, we agree with you on what is considered urgent and how it is communicated, so that those incidents take precedence over the rest of the work.

Can we combine maintenance with new developments?

Yes. Small improvements can be included in the maintenance modality itself, and larger developments are proposed as a separate project.