A Drupal site without maintenance ends up with leaks.

AI writes a first draft, but I decide the architecture and review every change before delivering it. It works like a very fast team with a senior supervising everything, and I stand behind the result just like I always have.

Because an hour of mine fits a lot more work than it used to. What counts in the end is the total cost of the project, and there I usually come out below what a traditional team would cost.

I work with prepaid hour banks, with no minimum. When I don't know your project or its code yet, a fixed price forces me to inflate the quote to cover the unknown. I prefer to start with a small bank to analyze what you need and give you an honest opinion of what it would cost. After that, in the same bank or a new one, I do the work and only the real hours are deducted. Whatever is left stays available for one year and is not refunded.

Yes. It's a fixed monthly fee that depends on what you need, such as security updates, frequency, included hours or monitoring with DruScan. You can work out yours in the maintenance configurator.

Yes. I can join your team using your repositories, workflows and tools, or take on complete projects that you manage afterwards.

Yes, and it's what I do most. Agencies that need backup or companies with an inherited Drupal that nobody wants to touch. I always start with a diagnosis to know exactly where the project stands.

All of them, from Drupal 7 to Drupal 11, including migrations from Drupal 7 and upgrades between major versions. I only work with Drupal, so it's what I spend all my time on.

I work in my local environment with a sanitized copy of the database. Sensitive data, like users' emails, is anonymized beforehand, so the AI never gets to see it. If you need it, we sign a non-disclosure agreement. For projects where privacy is critical I also have my own local AI server, so nothing goes out to companies like OpenAI or Anthropic. That said, if you let me use those services the work moves a lot faster.