Drupal 10 and 11 builds, Drupal 7 end-of-life migrations, security and accessibility work for government, higher education and large editorial teams. A good share of these clients cannot be named at all. Here is what we can show you instead.
Search "drupal case studies" and every result on the first page is a grid: a logo, one sentence, a percentage with no denominator. None of them mention what the project cost or how long it ran over.
We have a second problem on top of that one. Drupal clients skew towards government agencies, universities and regulated enterprises, and those organisations often cannot be named in a vendor's marketing at all. Procurement rules, security policy, or simply a communications team that says no. So this page will always understate the work.
What follows is what our Drupal projects involve, what a published case contains when a client does clear one, and what you can verify today. Our WordPress cases are already up with real numbers in them, and the headless build with Next.js and the multilingual newsroom are the two closest reads for anyone weighing a structured-content project.
No Drupal cases published yet. Check back soon — we ship multiple per month.
Drupal 7 reached end of life in January 2025, and a surprising number of organisations are still running it. That is where most of the demand sits right now: migrations to Drupal 10 or 11, usually on sites with a decade of content model drift, custom D7 modules with no D10 equivalent, and a Views layer nobody has documented. The rest is accessibility and security work, integration projects, and content modelling for editorial teams who have outgrown a flat page structure.
We are not evangelists about it. Plenty of the sites people ask us to build in Drupal would be cheaper and easier in WordPress, and we say so on the first call. Drupal earns its cost when content has real structure, when permissions are complicated, or when the site has to clear a security or accessibility bar that an off-the-shelf build will not clear.
The brief and the constraint behind it. Core version, PHP version, hosting, and the contrib modules we leaned on, named. The content model, because on Drupal that is the project. Migration source and row counts where a migration was involved. Real budget band and real calendar time, with the overruns stated. Post-launch Core Web Vitals and Search Console data from the client's own property. Accessibility audit results against WCAG 2.2 AA where the client was working to that standard. Then what we would do differently.
When a client cannot be named, we sometimes publish the engineering with the brand and the URL removed. The architecture is usually more useful to you than the logo anyway. When we cannot publish even that, the case stays off the site.
Read across platforms. The headless WordPress and Next.js build shows how we handle a decoupled front end and keep editors in a familiar admin, which is the same argument that comes up on every headless Drupal project. The multilingual newsroom covers translation workflow and publishing speed with a three-language editorial team.
Ask for a reference call. Thirty minutes with a past client, arranged before you sign anything. Some of our public-sector clients will take that call even though they will not appear on this page.
Commission a review. A paid architecture and security review of your existing Drupal site gives you a written report and a prioritised remediation list, and it tells you more about how we work than any case study would.
Drupal services lists scope and pricing per service. Packaged solutions covers the fixed-price versions, including the D7 migration pack. If you are still deciding between platforms, the scoping call is free and we will tell you when WordPress is the cheaper, better call.
Two reasons. We publish a case only once the client has approved the figures, and a large share of our Drupal clients are public sector or regulated organisations that cannot appear in vendor marketing at all. Write-ups go up as approvals come through, and some projects will never get one. We would rather say that than invent a case.
Often, yes. On a call we can walk through the content model, the migration mapping, custom module code, performance and accessibility reports, and the deployment pipeline, with the brand and URL withheld. Some clients also let us publish the engineering write-up anonymously, which is what we do where permitted.
Yes. We set up 30 minute reference calls before contracts are signed and try to match you to a project like yours. We ask the client first. Public-sector clients who decline a published case study will often still take a peer call, especially from another agency or university.
Yes, and it is the segment where Drupal makes the most sense: structured content, complex editorial permissions, multi-site, and an accessibility standard the organisation is actually audited against. We have dedicated pages for government and education that go into the specifics of each.
Drupal 7 stopped receiving official support in January 2025, so you are running unpatched code on a platform attackers know well. It is not an emergency on day one, but it becomes one the moment a serious vulnerability lands. The realistic path is a migration to Drupal 10 or 11, and the cost is driven by how much of your D7 custom code has no modern equivalent. We scope that in an audit before quoting.
A content-heavy but structurally simple D7 site is usually six to ten weeks. Sites with heavy custom modules, complex Views, or a content model that needs rebuilding run longer, and we say so before you commit rather than after. The audit produces a fixed scope and a fixed price.
30 minutes with a senior engineer. No salespeople. We respond within one business day with a brief outline.
Send a project brief →
