Custom Build or CMS? You Are Asking the Wrong Question.

Libby Day • May 13, 2026

There is a persistent assumption in agency-world that goes roughly like this: a custom-built site signals quality, expertise, and investment. A CMS signals speed, cost-cutting, and a client who did not want to spend properly.

It is an assumption worth challenging directly.

Over years of consulting with businesses across sectors, one of the most consistent pain points we encounter is not that a brand chose a CMS. It is that they were handed one that was never properly configured, or worse, they were talked out of one entirely and landed with a bespoke site they cannot touch without raising a support ticket.

What the CMS conversation is usually missing

When agencies position the CMS option as the more affordable tier, the implied message is that something is being compromised. Design fidelity. Flexibility. Capability. In practice, for the majority of marketing teams operating at the pace real businesses require, the opposite tends to be true.

The question worth asking is not "custom or CMS?" It is: who will own this site once it goes live, and what do they need to be able to do with it?

A marketing team that can update landing pages, publish blog content, swap out offer banners, and test new copy without waiting for a developer is not cutting corners. It is operating efficiently. That operational independence has real value, and it rarely comes from a fully custom build.

Notebook with wireframe sketches and pens beside a smartphone on a desk

The design control argument is a build quality argument

The concern we hear most often from design and brand stakeholders is legitimate: CMS platforms can produce inconsistent output if they are not set up carefully. Page layouts that drift. Spacing that varies between editors. Typography that breaks when someone pastes in the wrong block type.

These are not CMS problems. They are configuration problems. And they are entirely solvable.

A well-built CMS implementation does exactly what good design systems do: it defines what is locked and what is flexible. Spacing, type scale, grid structure, component proportions, brand colour usage can all be constrained at the build level. A content editor working within that system cannot accidentally break what has been designed. They can only work within the parameters set for them.

What they can do is update the headline on a service page, add a new case study, change a date, publish a post. That is the right division of labour.

Integration matters more than most briefs acknowledge

Modern marketing stacks involve more than a website. Analytics, CRM, marketing automation, booking tools, event platforms, form handlers. A CMS that integrates cleanly with these systems is not a nice-to-have. It is a practical requirement.

Custom builds can achieve this, but they require ongoing developer involvement every time an integration changes or a new tool is added. A well-supported CMS platform typically handles a significant proportion of these connections natively, and the ecosystem around major platforms continues to expand.

For a marketing team handling a campaign launch, a conference season, or a product update cycle, the ability to move without a three-week development queue is not a luxury. It is table stakes.

The honest case for knowing when custom is right

None of this is to say custom builds are not the right answer for certain projects. They are, where the functional requirements genuinely exceed what any CMS can provide, or where the product experience is itself the differentiator and demands complete control over every interaction.

But that describes a narrower set of projects than the way the choice is typically framed. For most businesses with active marketing functions, a CMS implemented with real care and proper design guardrails will outperform a custom build that requires a developer for every content update.

The budget question is worth reframing too. A custom site that becomes a maintenance dependency is not a premium investment. A CMS built properly, with constrained design and intuitive content management, is.

What good looks like

From a strategic and build perspective, a CMS done well means: a backend that is intuitive enough for non-technical team members to navigate confidently; design elements and page structure that are protected at the component level; integration points that are stable and maintained; and the ability to grow the site without rebuilding it.

That is not a fallback. That is a brief worth taking seriously.

Person working at a desk with dual monitors in a bright office, with a coworker and plants in the background

Ready to talk about your website?

If you are reviewing your current setup or scoping a new build, we are happy to have an honest conversation about what approach would actually serve your team.

Get in Touch

< Older Post