It earns its place when several people publish regularly, content is reused across pages, or more than one thing consumes it. It does not earn its place by being modern.
If none of them apply, the answer is usually no.
A headless CMS adds a subscription, a modelling exercise, a second system to keep current and a dependency the site cannot render without. It is worth all of that in specific circumstances, and it is worth none of it as a default.
The first justification is people. More than one person publishes, they are not developers, and they need to do it without waiting for a release. That is the common case and the strongest argument.
The second is reuse. The same content appears in several places: a service description on a service page, a landing page and a sector page. Holding it once and referencing it three times is the difference between a content system and three copies that drift apart.
The third is more than one consumer. A website, an application and an email system all reading the same content. That is genuinely a headless requirement rather than a preference about editing.
Where a site is updated a few times a year by the person who commissioned it, content in the repository is faster to build, cheaper to run and has nothing to keep current. Recommending a CMS there is selling complexity.
Selected against the requirement, not against a preference.
| Approach | Suits | What it costs you |
|---|---|---|
| Content in the repository | Small sites, developer-maintained content, complete version history | Non-technical editing, which effectively does not exist |
| Managed headless CMS | Marketing teams publishing regularly, structured reuse, several consumers | A subscription, a modelling exercise and a second system to maintain |
| Git-backed editor | Small teams wanting an editor without a separate platform | A weaker editing experience than a managed platform, and less structure |
| Traditional CMS such as WordPress | Teams already running one well, with an established publishing habit | Plugin dependency, hosting and maintenance the team has to own |
We select the platform against your requirement and tell you the licence cost before it is committed. It is your subscription, not an absorbed line in our invoice.
Almost always in the model, rarely in the technology.
A model with one type called Page and a free-form block field is a page builder with extra steps. Model the things that exist, services, sectors, people, case studies, and let pages compose them.
If an editor can put anything anywhere, they eventually will, and the design system stops meaning anything. Constrained composition produces better pages and fewer support requests.
Unlabelled fields, no preview, no explanation of where something appears. The CMS gets abandoned quietly and the site goes stale, which is the exact failure it was bought to prevent.
A statically built site needs a publish step, and the team needs to know how long it takes and how to tell whether it worked. Without that, a content change that has not appeared feels like a fault.
Model the content, constrain the composition, then choose the platform.
The modelling and the training, not just the connection.
Connecting a site to a CMS is a small part of the work. The parts that decide whether it is used are these.
Requiring alternative text at the point of upload does more for accessibility than any audit run six months later.
Published starting figures in GBP and USD, excluding VAT.
CMS work sits inside a build or a defined project
Lead generation
From £4,000From $5,200
A complete marketing and lead-generation website: the messaging, the structure and the enquiry routes a qualified buyer needs to make a decision.
Starting price
Up to 20 pages
From £2,000From $2,600
A compact marketing site or one focused lead-generation system, on a defined page and component scope of up to twenty pages.
Starting price
One bounded piece
£1,500$2,000
One bounded improvement: landing pages, a template rebuild, an analytics implementation, or a build-readiness review credited against a larger project.
Fixed price
CMS licence costs are yours, stated in the scope rather than absorbed. Where a managed platform’s free tier genuinely covers the requirement, we will say so instead of specifying a paid plan.
It depends on who edits, how structured the content is and what the budget for licences is. We shortlist against the requirement and explain the trade-offs. A supplier who always recommends the same platform is telling you about their habits rather than your needs.
The delivered site usually is, because it is statically built. But that is a property of the architecture rather than of the CMS, and a well-run WordPress site with a small plugin set can be perfectly fast. The stronger arguments are structure and reuse.
Content should be exportable, and that is worth checking before committing rather than afterwards. Because content and presentation are separate, moving to another platform is a re-import and a re-integration rather than a rebuild.
Yes, and it is often the sensible order. Content in the repository at launch, with the model designed as though a CMS were coming, means the migration later is an import rather than a redesign.
Those two answers decide whether a CMS is worth its subscription, and which kind is worth it.
