Service · Web development

Custom website development.

A code-first website for organisations that can't get by with WordPress, Wix or Squarespace. A fully custom design system, the headless CMS of your choice, server-side rendering and native multi-language support. Built for enterprises, SaaS companies, publishers and government.

Astro & Next.jsHeadless CMSWCAG 2.2 AAMulti-language

When an off-the-shelf CMS no longer fits.

WordPress powers roughly 43% of the internet and is a perfectly good choice for most small and medium-sized sites. Wix, Squarespace and Webflow are similar — drag-and-drop platforms that deliver quick results within fixed limits. For many organisations, those limits are fine.

But not for everyone. We build custom websites when an off-the-shelf CMS can no longer cope with the scale, performance, accessibility or content architecture. Think of an enterprise corporate site with multiple divisions, a SaaS company that wants its marketing website and product app to connect seamlessly, a university with multi-faculty content, a government organisation that must strictly follow WCAG and BIO, or a publisher with daily content volumes that an off-the-shelf CMS buckles under.

Custom means we start from your requirements, not from the limitations of an existing platform. Code-first, with a headless CMS for your editors and a dedicated frontend that does exactly what your brand and technology require.

Since 2015 we have been building custom websites for a wide range of clients — from industrial groups and SaaS companies to publishers, ministries and international agencies that build white-label client websites. What they have in common is that an off-the-shelf CMS no longer fits, and that they want to take back control of performance, accessibility, content architecture and integrations. For clients with a broader application landscape, we also connect the website to our enterprise software development, so that the marketing website and core systems reinforce each other rather than grow apart.

Three flavours of custom website.

Which one fits depends on the scale, the content architecture and the degree of integration with your existing systems. We'll advise on the right flavour in our first conversation.

Compact project · fixed sprint budget

Brand site with headless CMS

A marketing or corporate site for an organisation that wants to move away from WordPress but still needs a simple content flow. An Astro or Next.js frontend, a headless CMS of your choice, server-side rendering and a clean SEO foundation. A good fit for scale-ups and B2B companies that want to strengthen their website foundation without immediately embarking on an enterprise project.

AstroDirectusSanitySEO-ready
Mid-sized project · fixed sprint budget

Multi-language enterprise site

For groups and internationally operating organisations with multiple languages, regions and audiences. Native i18n in the routing, geo-IP detection for content variants, and a content model that editors can maintain in several languages in parallel. Well suited to industrial groups, universities with international students and international media titles.

i18n routingGeo-targetingContent variantsMulti-tenant
Larger project · fixed sprint budget

Mission-critical platform website

A website that is more than content presentation: portal integrations, calendar and booking flows, a headless commerce component, personalisation by visitor segment and deep integrations with your CRM and ERP. For SaaS companies that want their marketing site and product app to connect seamlessly, media houses with daily publishing streams, and public-sector organisations with strict compliance requirements.

CRM integrationPersonalisationBooking flowA/B testing

What you get at the end.

A production-ready website, with everything around it to manage and extend it independently.

  • The website itself, with a staging environmentA server-side rendered frontend on the hosting of your choice (Vercel, Netlify, Cloudflare Pages or your own Hetzner server), plus a separate staging environment for editors and QA.
  • Your own design systemComponents, tokens and guidelines in code, linked to a design system in Figma that your brand team maintains itself.
  • Headless CMS, set up for your teamDirectus, Strapi, Sanity or Contentful, chosen to fit your editorial workflow. Content models, roles and publishing workflow are set up so your editors can publish on their own without needing us.
  • SEO foundation built into the codeServer-side rendering, structured data (JSON-LD), sitemap generation, robots.txt, canonicals, Open Graph and Core Web Vitals optimisation included as standard.
  • Accessibility and complianceWCAG 2.2 AA in line with the European Accessibility Act, axe-core in the CI pipeline, a GDPR-compliant flow for cookies and analytics, and a Content Security Policy locked down as tightly as necessary.
  • Documentation and knowledge transferAn architecture overview, a hosting runbook, an editorial guide for your content team, and a live walkthrough in which your IT and editorial teams take part.
  • Maintenance contract (optional)Ongoing monitoring, security updates, performance checks and minor further development. Fixed monthly price, with a specified response time per incident level.

When custom is the right choice.

Four patterns that tell us an organisation is ready for a custom website. If you recognise one, we'd be glad to talk further.

Scale & architecture

A standard CMS is buckling

Your editors publish daily, the content model has ten types with relations between them, and the WordPress database is clogged with plugins that get in each other's way. A headless CMS with a custom frontend keeps things manageable that would turn messy in a standard CMS.

Performance

Core Web Vitals are critical

Your site is a conversion funnel or an acquisition channel where every 100 milliseconds counts. Lighthouse scores of 95 or higher on LCP, CLS and INP are achievable with a custom frontend; with most plugin-heavy WordPress sites they are not.

Accessibility

WCAG 2.2 AA is mandatory

Now that the European Accessibility Act applies, public websites and many commercial services must meet WCAG 2.2 AA. A custom frontend with axe-core in the pipeline gives you far more control than wrestling with themes on a standard CMS.

International

Multi-language and multi-region

You have multiple languages, regions and domains, and want to manage content variants per country without endless URL patchwork. Native i18n in the routing and a content model that understands variants is far cleaner out of the box than a multilingual plugin.

Tech stack and architecture choices.

The stack we use by default, and why. We choose on fit with your situation, not on dogma: frontend, CMS, hosting and everything around them.

Frontend

Astro, Next.js or Nuxt

Astro for content-heavy sites with lots of static pages and little client-side interactivity: less JavaScript sent to the browser and faster Core Web Vitals. Next.js when you also need server-side personalisation, dashboards or complex application features. Nuxt for teams already in the Vue ecosystem who want to stay there.

Headless CMS

Directus, Sanity, Strapi or Contentful

Directus when you need a lot of flexibility in the content model and want to stay self-hosted. Sanity for real-time collaboration and a strong editor UX. Strapi for maximum self-hosted control. Contentful for enterprise projects with strict SLA requirements.

Hosting

Vercel, Netlify, Cloudflare or your own cloud

Vercel and Netlify for maximum convenience with Next.js and Astro projects. Cloudflare Pages for low costs at scale and a strong edge network. Your own Hetzner or GCP server when you want to keep data within Europe on principle, or when your IT policy requires your own environment.

Search & integrations

Algolia, Typesense, HubSpot, Salesforce

Site search with Algolia, Typesense or Meilisearch, depending on scale and budget. Form flows and lead routing to HubSpot, Salesforce or your own CRM. Analytics in GA4 or in privacy-friendly alternatives such as Plausible or Matomo. Cookie consent via TCF 2.2 or Klaro.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Compliance and privacy from A to Z.

A custom website is also a legal product. Since 2025, far more regulation has converged at website level. We build compliance in from the architecture up, not as a patch afterwards.

  • GDPR and cookie consentCookie-free analytics where possible, otherwise consent-by-design via TCF 2.2-compliant banners. Data processing agreements and DPIAs where needed.
  • WCAG 2.2 AA and EAAAccessibility built into the design system. Axe-core checks in the CI pipeline, manual screen reader tests in the final sprint.
  • EU Digital Services ActFor sites with user-generated content or advertising flows: notice-and-action procedures, transparent content moderation and the right user-facing documentation.
  • CSRD and sustainability reportingFor organisations with a sustainability reporting obligation: a content architecture that makes ESG reports, due diligence overviews and CO2 data accessible.
  • PSD2 for paymentsIf you process payments on the site: strong customer authentication, PCI DSS compliance and correct delegation to the payment provider.
  • BIO and Common GroundFor government organisations: building blocks that respect Common Ground and follow the Baseline Informatiebeveiliging Overheid (BIO), the Dutch government information security baseline.
  • Content Security PolicyStrict CSP headers, subresource integrity and HSTS as standard. No third-party scripts that can run unnoticed.

How a custom website project works.

1

Introduction and scope sign-off

A conversation in which we learn which organisation you are, which brand you run, which editorial team is involved and which integrations are really needed. We check whether a custom build is indeed the right fit, or whether a lighter platform would be more practical.

2

Content architecture and design

Workshops with your editorial and brand teams. We model the content types, map the site architecture and set up the design system. At the end: a prototype with the key templates and a configured CMS environment.

3

Building in sprints

A working build every two weeks that you can test. Your editorial team fills the CMS in parallel, your brand team validates the design system and your IT team tests the integrations. The MVP is ready after a few sprints; after that comes fine-tuning, a performance pass and an accessibility pass.

4

Launch and further development

A controlled go-live, with monitoring and redirects from the old site. After that you choose whether to carry on building yourself or have us keep doing it under a maintenance contract. Both are possible, and the codebase remains yours.

5

Continuous evolution

A custom website is not a one-off delivery but a platform that grows with your organisation. New markets, new languages, new content types and additional integrations almost always follow. We plan quarterly cycles in which we prioritise together what the website needs to be able to do next quarter, and we carry that through in the same sprint rhythm in which we built it.

Frequently asked questions.

What clients usually want to know before we start.

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.

Talk to us about your custom website.

A no-obligation introductory call of half an hour. We listen to what your organisation needs, ask questions about your content architecture and integrations, and give you direction you can actually use, even if custom turns out not to be the smartest option.

On applatenmaken.com, our platform about custom software development, you'll find a deeper look at Custom software by sector.

Edit content