When custom, and when WordPress?
If your site is small or medium-sized and you can manage perfectly well with existing WordPress themes and plugins, WordPress is almost always the smartest choice. Custom becomes interesting once you hit WordPress's limits: a complex content model, daily publishing volumes, performance requirements for Core Web Vitals, strict WCAG requirements, native multi-language support, or integrations with CRM, ERP and custom backends. We don't replace WordPress for budget reasons, only when the standard route is genuinely holding you back.
What exactly is a headless CMS?
A headless CMS separates content storage from presentation. Your editors work in an admin interface (Directus, Strapi, Sanity, Contentful), which delivers content to the frontend via an API. Your own frontend then decides how content is displayed — on the website, in a mobile app, in a product portal or in all three at once. You are no longer tied to the templates and plugins of a traditional CMS, yet you still get a pleasant editing environment. For a more detailed explanation, see the page on
building a headless CMS.
WCAG 2.2 AA and the EAA — is it really mandatory?
Yes. The European Accessibility Act (EAA) has applied since June 2025 and requires many commercial and public websites to meet WCAG 2.2 AA. For government sites this has applied for longer. With a custom website, we make sure WCAG requirements are built in from the design system onwards: contrast, focus states, keyboard navigation, ARIA labels, and axe-core checks in the CI pipeline. For existing sites we also carry out standalone accessibility audits.
Multi-language — how do you handle that technically?
In a custom website we build i18n natively into the routing: /nl/, /en/, /de/ and so on, with SEO-correct hreflang tags and language detection at visitor level. The CMS gets a content model with language variants that your editorial team maintains in parallel, and we can connect DeepL or another translation system for a first-pass translation. For multi-region setups with geographic content variations, we build geo-IP detection and region-specific flows on top.
Does SEO go hand in hand with custom development?
Better than with most standard CMS installations, provided it's built properly. Server-side rendering or static generation ensures Googlebot receives HTML immediately; structured data (JSON-LD) is built in per content type; the sitemap, robots.txt, canonicals and Open Graph are generated from the content model; and Core Web Vitals are much easier to achieve with a dedicated frontend than with a WordPress site weighed down by plugins. We deliver an SEO foundation that is stronger than what most templates offer out of the box.
Which tech choices do you make by default?
Frontend is usually Astro or Next.js, depending on the level of interactivity and personalisation. Astro for content-heavy sites with many static pages, Next.js when server-side personalisation or complex app functionality comes into play. We choose the headless CMS per project: Directus for flexible content models, Sanity for strong real-time collaboration, Strapi for self-hosted control, Contentful for enterprise projects. Hosting on Vercel, Netlify, Cloudflare Pages or our own Hetzner — whatever best fits your IT policy.
What determines the cost?
The biggest factors are the size of the content model, the number of templates, the level of personalisation, the number of integrations (CRM, ERP, payments, search, analytics) and whether multi-language or multi-region is involved. A brand site with a handful of templates is a different scale from a media company with a daily content pipeline. In the first conversation we outline the scope and attach a suitable sprint budget to it, with no surprises afterwards.
And maintenance after launch?
You decide. Your IT team can continue development itself — you get the full codebase, documentation and a runbook. Or we handle it under a maintenance contract: ongoing monitoring, security patches, performance checks and minor development, with a fixed monthly price and specified response times per incident level. Many clients opt for a hybrid: you handle the editorial flow and small content changes, we handle the technology and further development.
What about migrating from WordPress or another CMS?
An important part of the project. We map your existing content types to the new CMS, write a one-off import script for your existing articles, pages and media, and set up 301 redirects for all old URLs to preserve SEO value. For sites with a lot of content, we often use a staging environment where your editorial team can check the migration before go-live. We handle image optimisation and alt-text checks in the same pass.
Do you host it yourselves, or do we?
Either works. For most custom projects, we initially host on Vercel, Netlify or Cloudflare Pages, which gives the best developer experience and the strongest edge performance. For clients with a data residency requirement or their own IT policy, we run the website on a dedicated Hetzner or GCP server within Europe. The same choice applies to the CMS: SaaS or self-hosted, depending on what your IT allows.