Within one working day, I tell you for free, from the outside, which move to Drupal 11 easily and which need work.
You resell at a fixed price per site, known before you quote your client.
Drupal 10 security support ends on
After that, a client site still on Drupal 10 is open to the next published flaw. The client calls you, and nobody in house can take it. Waiting for the budget means migrating later at a higher price, or watching another provider take the account.
What your client gets under your name: careful work down to the detail, priorities understood, and a clear status at every step. No bad surprises, on the invoice or in production: no major incident since 2018.
What I take off your plate
Your portfolio, kept up to date.
Security and minor updates on every client site, a monthly report you send under your name, and the move to Drupal 11 at a fixed price per site. Run on your tooling and in your ticket system.
An inherited Drupal platform nobody wants to touch, a stalled upgrade, a backlog that keeps growing. The client stays with you, and the site gets fixed under your name.
“Highly dependable, Jo quickly and efficiently completed all tasks to a very high standard. I have already hired again for the next project.”
Spencer L., Crossbridges
You stay the single point of contact
I don’t appear in your client’s tickets, their invoices, or their inbox unless you put me there.
Some of the work below is described without naming the client, because my agreements require it. Yours would be handled the same way.
Example
[Your agency]
Monthly maintenance report
Site
[Your client’s site]
Month
October 2026
Prepared by
[Your agency]
Updated
Drupal core 11.4.9 to 11.4.11, and 6 modules.
Including the 14 October core security release, tested on staging.
Fixed
The contact form sent no confirmation e-mail.
A menu link pointed to the old events page.
Plan next
PHP 8.5 on the host before Drupal 12.
Small requests1 h 20 of 2 h
Example with made-up data. Your client gets this report from you. My name is not on it.
What my clients got out of it
Seventeen client sites, kept running under the same agency’s name since 2018.
The agency keeps the relationship: its clients only ever deal with it. I apply the security updates, fix what breaks and log every intervention. The clients run very different businesses: a professional order’s member portal, a trilingual cultural venue with ticketing, a social housing platform, a waste authority serving twelve municipalities, a certification body and a consumer brand’s 3,000-product catalogue. None of them has had a major incident. Ten are already on Drupal 11, ahead of the December deadline.
Same agency since
2018
Client sites
17
Already on Drupal 11
10
Interventions logged since 2021
573
of which security updates
292
Major incidents
0
A US agency’s lead developer took two weeks off, and the tickets kept moving.
I stepped in as acting lead developer, in the agency’s tickets and repository, under its name, on Drupal and WordPress. Work went on for ten client accounts, among them two universities, an art school, a senior community group, a medical imaging practice, a SaaS publisher, a real estate developer and a publisher. One multisite went live during those two weeks.
Tickets taken on
25
of which delivered or in review
18
Client accounts
10
Site launches
1
Cinequest Film Festival: a late project brought back on schedule.
The project had fallen behind. Donor and pass forms, ticketing and sponsor pages were ready for the festival’s traffic peaks. Their former IT manager had recommended me; three years later they called me back to move cinequest.org and picturethepossibilities.org to Drupal 11, done in October 2026.
The new site went live for the 2022 festival, on the date set.
“Johan was able to make up the time to get us back on schedule. He provides excellent status and understood the updates/changes to get the project to align with the goals. When we have more Drupal projects, Johan is the first person we will reach out to!”
Halfdan Hussey, Cinequest Inc.
A large US public research university: accessibility fixed on its medical sites.
I worked inside the central web team, on seven sites built on the university’s own design system. On the medical school and clinical practice sites, I ran the ADA remediation: text that low-vision visitors can read, menus that work with a screen reader. I also connected the university’s service platform to its IT sites, so a knowledge-base article is written once and shows up everywhere.
Contrast failures closed
3,431
Pages covered
1,587
Broken ARIA menus and references fixed
142
An art and design college moved to Drupal 11 and kept the same developer.
An American college, delivered this year. I still look after its sites, so nobody has to learn them again after the upgrade.
The earlier move from Drupal 9 to 10 on the same sites took sixteen hours of work.
Based in Antananarivo, Madagascar, on UTC+3. Two hours ahead of Paris and Brussels in winter, one in summer, so we share the full working day. For US teams, your mornings overlap with my afternoons.
I know what an agency’s week looks like when a client escalates on a Friday.
Async-first: I write things down. Composer-managed codebases, staging before production, and a regression check before anything ships.
You send the list of your Drupal sites. I tell you what I can see from outside, no charge.
The written audit, with the detail behind it, is paid.
You get a fixed quote, or an hourly block, whichever fits.
I work in your tracker, on your branch, to your review.
Each week
TuesdayYou send what needs doing.
WednesdaySecurity releases, if any: staging first, then production.
ThursdayDone in the morning, then kept for blockers.