Headless CMS
When WordPress is enough (and when It isn't)
WordPress works for a lot of businesses, but not forever. Here's how to tell when it's still the right choice and when it's quietly holdi...
The Blog
The hidden cost of poor content modelling
Headless CMS
Content modelling is one of those things that sounds deeply technical and boring, until it starts costing you money.
It's the process of deciding how information is structured in your CMS. What types of content exist (pages, blog posts, case studies, team members, services). What fields each type has. How those types relate to each other. And how your team interacts with all of it when they need to publish, update, or reorganise content.
Get it right, and your CMS feels intuitive. Your team publishes confidently. Content goes where it needs to go. The platform grows without friction.
Get it wrong, and you'll feel it in every workaround, every "can you ask the developer to do this," and every redesign that takes three times longer than it should because the content is locked into a structure that doesn't flex.
What it looks like
What bad content modelling looks like
Bad content modelling doesn't announce itself. It accumulates quietly and by the time you notice, it's expensive to fix.
- 01Everything in one rich-text field
The most common pattern. Every page is a single block of formatted text with images dropped inline. It works at launch. Six months later, when you want to pull product features into a comparison table, or display team members on multiple pages, or restructure your services section, the content can't be separated from the page it lives on. It's trapped.
- 02Copy-pasted content instead of relationships
Your CEO's bio appears on the About page, the Team page, and three case studies. If it's stored as a relationship, one bio, referenced everywhere, updating it takes seconds. If it's copy-pasted into each page, updating it means finding every instance, editing each one, and hoping you didn't miss one.
- 03Fields that don't match how editors think
A content model designed by a developer who never talked to the content team. Fields named with technical terms. Structures that make sense in the database but confuse anyone trying to publish a blog post. The CMS becomes something people avoid rather than something they use.
- 04No separation between content and layout
Content tied to specific page templates — so adding a new section means developer involvement, moving content between pages means rebuilding, and the platform becomes rigid exactly when the business needs it to flex.
Why it matters
Why it matters commercially
Content modelling feels like a technical decision. It's actually a commercial one. Every content modelling shortcut creates a cost that shows up later.
- 01Editor dependency on developers
If your team can't publish a blog post, update a service description, or add a new team member without calling a developer, that's a content modelling problem. Every request that requires developer time for a routine content change is money spent on something that should cost nothing.
- 02Redesign costs multiply
When a business wants to refresh its website, the design and development cost depends heavily on how the content is structured. Well-modelled content can be reorganised, restyled, and extended with minimal migration work. Poorly modelled content, everything in rich-text fields, no relationships, no structure, means every page needs to be rebuilt from scratch.
- 03Multi-channel becomes impossible
Structured content can go anywhere, your website, your app, your email campaigns, your partner platforms. Content locked in page-specific rich-text fields can only go to one place. If your business ever needs to deliver content to a second channel, bad modelling means starting again.
- 04Content quality degrades
When a CMS is confusing or frustrating, content updates slow down. Blog posts stop getting published. Team pages go stale. Service descriptions stay outdated. The platform stops reflecting the business, not because nobody cares, but because the tool makes it too hard.
The platforms that age well are the ones where someone spent time getting the content model right at the start. The ones that don't are the ones where nobody thought it mattered.
Good modelling
What good content modelling looks like
Good content modelling starts with three questions.
Not just pages and posts, but services, team members, case studies, testimonials, FAQs, locations, products, events. Each distinct type of content should be its own content type in the CMS, with fields specific to what it needs.
A case study references a service and one or more team members. A blog post belongs to a category and links to related posts. A service page displays relevant case studies and FAQs. These relationships should be modelled explicitly, not recreated manually every time someone publishes.
The content model needs to make sense to the people using the CMS, not just the people who built it. Field names should be plain English. The editing interface should guide editors through what's required. Validation should prevent mistakes rather than allow them and hope for the best.
When to invest
When to invest in content modelling
- 01Before a new build
This is the cheapest time. Content modelling during discovery costs a few days of work. Fixing a bad content model after launch costs weeks, plus content migration, template rebuilds, and editorial retraining.
- 02When you're migrating platforms
If you're moving from WordPress to a headless CMS, the migration is an opportunity to restructure. Don't just copy the old structure into the new platform, design the model your business actually needs.
- 03When your team has stopped using the CMS
If content updates have stalled because the CMS is too confusing or too rigid, the content model is usually the root cause. A restructure can transform the editorial experience without rebuilding the entire platform.
The payoff
The investment pays for itself
Content modelling typically takes one to two weeks on a standard business website. For complex platforms with multiple content types and editorial workflows, two to four weeks.
That investment pays for itself the first time your team publishes a page without calling a developer. It pays for itself again when a redesign takes half the time because the content is already structured. And it keeps paying for itself every time your business needs content to go somewhere new.