Your Tech Club
ADC logo

ADC: from a redesign to a Strapi headless CMS with Next.js

Why a redesign for ADC became a Strapi headless CMS: a content model for cases and insights, a Next.js front end and HubSpot built in.

Strapi headless CMS with a Next.js front end for ADC, on a laptop and a phone

For ADC we built a Strapi headless CMS with a Next.js front end on top. ADC is a European data and AI consultancy. Its credibility rests on proof, and that proof lives in content: cases, insights and sector knowledge.

The request that came in was a redesign. What we delivered was a new platform. This is the story of why it went that way, and why I now think it was the best decision of the project.

The project in brief

Client
ADC, a European data and AI consultancy.
Sector
consultancy, data and AI.
What we did
UI/UX design (in part), custom web development, content modelling and migration.
Technology
Next.js, React and GSAP on the front end, Strapi (open-source headless CMS) with MySQL on the back end, HubSpot and GA4 for marketing.

What was the challenge at ADC?

The brief started as a redesign, but the bottleneck wasn't the design. The technical discovery showed that the existing CMS setup was hitting its limits. The content structure didn't scale, performance lagged behind and maintenance got heavier every quarter. A fresh coat of paint would have changed none of that.

The discovery turned up five concrete limitations: scalability, content structure, performance, maintenance and an SEO risk. That last one weighed heavily. If you only renew the design in a redesign, a later migration will still hit your search rankings. Then you pay twice: now for the design and later for the foundation.

For a consultancy that grows on authority, that's no detail. Every week that publishing a new insight is a struggle is a week in which the proof doesn't grow.

ADC's homepage on a laptop: the heading "Leading the most impactful AI transformation", a row of client logos and the start of the Industries section.

Why did the redesign become a headless CMS with Strapi?

Because a new design on the same foundation wouldn't solve the real problems. So instead of building on the old setup, we chose a headless approach. Strapi manages the content, a Next.js front end displays it. That way the content can grow without the site getting slower or harder to maintain.

There was a clear reason for choosing Strapi: it's open source. That means ADC keeps control of its content structure, can host and extend the platform itself, and isn't tied to a single vendor. There are also no licence fees per user or per API call.

My view on this is simple. If content is your most important proof, you don't want it in a system you don't control yourself. For a rough idea of what a platform like this costs, read about the cost of a website.

Is your CMS hitting its limits too? We first look at whether the problem is the design or the foundation.

See Strapi development

What is a headless CMS, and when should you choose one?

The Industries page on tablet and phone, with the heading "Find inspiration, gain valuable insights, and discover effective solutions" and cards for each sector.

A headless CMS only manages content and makes it available through an API, without displaying the website itself. The front end is a separate system. That lets you use the same content across several channels, and replace the front end without touching the content. It gives you freedom, but it also takes more build work up front.

Headless is the right choice if you publish a lot of content, serve several channels or have high demands on performance and structure. For a ten-page site that rarely changes, a traditional CMS is actually cheaper and faster. I say that honestly to clients who ask for headless because it sounds modern.

Torn between custom and off the shelf? Then custom software or an off-the-shelf package will help you decide.

How did we build the platform?

We started with the content model, not the pages. In Strapi we designed relational content types for cases, insights, sector pages, news, events and campaigns with gated assets. Those entries are linked to each other. As a result, internal links and topic clusters follow from the structure, instead of someone maintaining them by hand.

Two phone screens: the contact details of the office in Denmark and the Latest insights overview with an article about the EU AI Act.

Rendering by page type

The platform generates static pages in advance. Dynamic pages are rendered server-side, with caching and optimised image delivery. The SEO basics also live in Strapi: metadata fields, canonical control, a clean URL structure and a sitemap that moves with the content. Read more about this front end under Next.js development.

Marketing keeps running

HubSpot is built into the new front end, with forms, UTM tracking and lead routing. So the existing workflows simply kept working. GA4 also records clicks on calls to action, form submissions, interaction with content and navigation behaviour. We didn't want a migration where marketing flies blind for a month.

What does the design look like?

We did part of the UI/UX design, within ADC's existing brand identity. The homepage opens with the headline "Leading the most impactful AI transformation", followed by a row of client logos and a block on Industries. The green pattern from the brand identity returns in several places, on mobile too.

ADC's mobile homepage next to an article page about financial services, framed by the green pattern from the brand identity.

The Industries page shows cards per sector, on tablet and phone. ADC works in financial services, life sciences and transport, among others. The Latest insights overview shows the newest articles, such as a piece on the EU AI Act. The contact details for each office, including Denmark, are also neatly stacked on mobile. For animation we used GSAP.

What did the Strapi headless CMS deliver?

Publishing a new case or insight is now a matter of filling in Strapi rather than a development task. New content types and pages can be added without rebuilding the existing content. That means ADC's proof can grow with the company again.

We built a similar headless project, with Strapi, Next.js and an MCP server, for Sprints & Sneakers.

Not sure whether headless suits your site? In an intro call we'll tell you honestly whether it's worth it.

Book an intro call

Updated

Questions or an intro call

Get in touch with us directly. We'll get back to you as soon as we can

Joey van VlietYassine SeghrouchniThe team at the officeYour message goes straight to our team in Amsterdam.

We'll get in touch as soon as we can.

Frequently asked questions

Who built the ADC website?

Your Tech Club. We did part of the UI/UX design, modelled and migrated the content and built the platform: Strapi as a headless CMS with a Next.js front end.

What technology does the ADC website run on?

Next.js and React on the front end, with GSAP for animation, and Strapi with MySQL on the back end. HubSpot handles forms and lead routing, GA4 the analytics.

What exactly is a headless CMS?

A CMS that only manages content and makes it available through an API, without rendering the website itself. The front end is a separate system. That lets you use the same content across several channels and replace the front end without touching the content.

When is headless the right choice?

When you publish a lot of content, serve several channels or have high demands on performance and structure. For a ten-page site that rarely changes, a traditional CMS is cheaper and faster.

Why Strapi rather than a commercial headless platform?

Strapi is open source, so there are no licence fees per user or per API call and no vendor lock-in. You can host it yourself, model the content types yourself and set up role-based access rights.