Drupal suits organisations with complicated content and real permission requirements. It is a poor fit for a brochure site, and we will say so before you commit to it.
Drupal earns its place where content is genuinely structured — many content types with real relationships between them, editorial workflow with approval steps, and permissions that differ by role and by section. Universities, public bodies, membership organisations and large publishers tend to land there for good reasons.
It is heavier than the alternatives, and for a site that is essentially pages and a blog that weight buys nothing. The commonest Drupal problem we are asked to fix is not technical: it is a site that was built on Drupal when something simpler would have served, and now costs more to maintain than it needs to.
The other recurring job is version upgrades. Major Drupal versions are not incremental, and an installation left on an unsupported release accumulates risk quietly until the upgrade is a project rather than a task.
What we do
Working UK-wide — directly with businesses, and white label behind design and marketing agencies.
Discuss a projectMoving off an unsupported release. Planned on a copy first, because the contributed modules are usually what decides how hard it will be.
Functionality that no contributed module covers, written to Drupal conventions so the next developer recognises it.
Content types, fields and taxonomy arranged so editors can work without a developer. This is where most Drupal sites are won or lost.
Caching layers, query problems and the module stack. Drupal is quick when configured properly and slow when it is not.
Connecting to CRM, finance and single sign-on, which is often why Drupal was chosen in the first place.
Security releases applied promptly, which matters more on Drupal than on most platforms because advisories are public and specific.
For a marketing site with a handful of templates, a lighter CMS is cheaper to build and cheaper to run. We will tell you when that applies.
Major version moves involve contributed modules that may not have been ported. The assessment comes before the quote for that reason.
Most complaints about Drupal being awkward trace back to content modelling, not the software. Fixing that is usually cheaper than replacing it.
A lot of our work is delivered white label or under agreement, so these describe the problem and the approach rather than naming the client.
A multisite platform serving several regional websites from one build, each with its own content and language.
Web application · IntegrationAn API-connected membership platform handling publications, events and a two-way CRM sync — thousands of profiles and hundreds of transactions a week.
Migration · DevelopmentFive separate legacy CMS sites, five databases and five themes, consolidated into a single multilingual multisite CMS platform.
That, and roughly what the site does. We will tell you whether the right move is an upgrade, a rebuild or simply better support — and which modules are likely to decide it.