Drupal delivery with release criteria and a controlled module set
We take Drupal when content models, roles, or migrations need a written plan. Upgrades and greenfield installs share one rule: scope first, modules second.
- Migrations and major-version upgrades with cutover plans
- Content types and roles locked before theme work
- GDPR and hosting listed in the same brief
CMS engineering, against a release
Drupal projects stall when every stakeholder adds modules without an owner. We agree content types, permissions, and the success metric before the first custom module lands.
If WordPress covers the publishing job, we say so early. For enterprise peers see TYPO3 and Pimcore; for lighter sites see WordPress.
Config management and deployment discipline come before theme polish. Unexported config is how staging and production drift.
What we check before a Drupal engagement
- Module and custom code mapContrib vs custom modules that touch auth, forms, and content types are listed with risk notes.
- Content modelContent types, paragraphs, and media are checked against what editors need next quarter.
- Security updatesCore and module update lag, staging practice, and who applies patches are confirmed.
- Search and viewsHeavy Views and search configs on money pages are profiled before new features land.
Selected work with commercial stakes
Relaunch study before vendor lock-in
Requirements, localisation, and vendor-scope advice for a multi-market manufacturer relaunch.
Four-market stack under one TechOps lead
Fractional CTO across vegconomist markets plus Cultivated-X: updates, adops, performance, and incident response.
Discovery and launch on a production stack
User interviews ran in parallel with the build so the site matched what buyers asked for.
From brief to a Drupal release you can run
Audit and outcomes
Version, modules, content volume, and the metric that decides whether the cycle succeeded.
Content and ownership map
Content types, roles, hosting, and who maintains Drupal after launch written down.
Engineering cycle
Build against release criteria. Custom modules stay documented; unused contrib leaves the stack.
Integrations and GDPR
SSO, forms, and processors with consent behaviour and a written data map.
Launch and handover
Staging QA, redirect plan, backup check, and a short editor runbook.
Drupal work we take on
Major upgrades
Plan Drupal upgrades with module triage, content migration, and a cutover window ops can own.
Content model work
Rebuild content types and permissions so editors publish without developer tickets.
Greenfield Drupal installs
New sites with written scope for roles, GDPR, and hosting before the first contrib module.
Migrations onto or off Drupal
Move content and URLs with redirects when Drupal stays or when WordPress is the better fit.
When Drupal is the right call
- You already run Drupal and need a scoped upgrade or modernisation
- Complex roles, workflows, or multi-site publishing justify the investment
- You want GDPR and hosting decisions in the same written brief
- You need a simple brochure site with no Drupal ownership after launch
- You expect unlimited hourly module installs without release criteria
- You want market-share claims instead of a migration or greenfield plan
Drupal questions
Do you migrate Drupal 7 or 9 sites to a supported version?
Yes. We audit modules, plan content migration, and keep redirects in scope. Open-ended upgrade retainers without exit criteria are a poor fit.
Drupal, TYPO3, or WordPress?
Do you build greenfield Drupal sites?
Yes, when roles and content complexity justify Drupal. For many marketing sites we recommend WordPress and say so before you fund a greenfield install.
How do you handle GDPR on Drupal?
Consent, processors, and cookie behaviour belong in the build scope. We document vendors and keep marketing tags behind consent where required.
Where are you based?
Registered in Wiesbaden. Discovery and reviews can happen in person in the Rhein-Main region; delivery runs in structured cycles.
What do you finish in week one on Drupal?
Config management discipline, content type ownership, deploy path, and which modules are abandoned risk.
Do you theme before fixing config drift?
No. Unexported config between staging and production gets fixed before polish.
Nearby stacks and services
Technologies: WordPress, Shopify, WooCommerce, Webflow, TYPO3, Pimcore, Next.js, React, Frontend engineering, Laravel, PHP, Angular. All technologies →
Services: Websites & WordPress, WordPress agency, SEO for B2B, AEO & GEO for AI search, Website relaunch, Technical compliance, AI & automations.
Office in Wiesbaden
Hans-Böckler-Str. 76
65199 Wiesbaden
Ready to talk.Book a short diagnostic.
Tell us what needs fixing
We read every brief and reply within one business day.
Prefer to talk first?or request a tech stack audit →or email us directly →
Not sure where to start? Send the stuck decision, workflow, or page. We will say whether you need a diagnostic call, a tech stack audit, or a different first step.