CMS platforms we build on
The CMS decides who can update the site, how content is structured, and how easily it feeds everything else you run. We build on a small, opinionated set — chosen by the job in front of us, not by habit.
What a CMS is — and what actually matters to you
A content management system is where your website's words, images and structure live, and where your team goes to change them. On the surface every CMS does the same job. In practice the differences decide how quickly your team can publish, how the content scales across channels, and how much developer time it costs you every year.
The questions that matter are rarely about features. They are: can the people who own the content actually run it without us? Will the model still make sense when the site is three times bigger? And does the CMS help performance and SEO, or quietly work against them? Those answers point to very different platforms.
The two kinds of CMS, and how they differ
Almost every CMS is one of two shapes. Getting this choice right is more important than the specific brand — it shapes performance, flexibility and cost for years.
Traditional (coupled)
- Content and the front end are one system — e.g. classic WordPress.
- Fast to stand up; a familiar all-in-one admin.
- The theme layer and plugins can drag on performance and security.
- Best for content-led marketing sites with a single web front end.
Headless (decoupled)
- Content lives in an API; the front end is built separately in a framework like Next.js.
- Faster, more secure, and future-proof — one content source feeds site, app and more.
- Needs a considered content model and a developer to build the front end.
- Best for performance-critical sites, design systems and multi-channel content.
How we decide with you
We do not lead with a brand. We work through a short set of questions and let the answers choose the platform.
Who owns the content?
A hands-on marketing team that wants to build pages visually points one way; a content team that wants a tailored, guard-railed editor points another.
How structured is it?
Product-like, reusable content rewards a structured headless model. A handful of straightforward pages does not need one.
Where does it need to go?
If the same content must feed a site, an app and other channels, headless earns its keep. One web front end may not need it.
What is the performance bar?
When Core Web Vitals and SEO are non-negotiable, a decoupled front end gives us the most headroom.
Our chosen CMS
Sanity
A structured-content platform you shape like code.
Sanity is our default when content is product-like and the editing experience matters. It treats content as structured data, not pages, and lets us design the Studio around how the team actually works.
Storyblok
Headless content with genuine visual editing.
Storyblok is our pick when marketing wants to build and rearrange pages visually without a developer in the loop, but the build still needs to be headless and fast.
WordPress
Fully custom WordPress — no page builders, no bloat.
We still build on WordPress — but properly. Bespoke themes, clean custom fields and only the plugins a project genuinely needs. No Elementor, no off-the-shelf themes.
Headless WordPress
Keep the CMS your team knows, replace the front end.
Headless WordPress keeps the editor your team is comfortable with and swaps the ageing front end for a fast, modern one built in Next.js — the best of both.
Contentful
The enterprise incumbent — and where we sit on it.
Contentful is the API-first CMS procurement teams often already know. We build on it happily, and we are equally happy to tell you when Sanity is the better call.
Not sure which stack fits?
Tell us about the build and we will recommend the platforms — a reasoned recommendation, not a ranking. No jargon, no lock-in.