Who Edits Your Content? Choosing a CMS Honestly

"I want to be able to update it myself" is in almost every brief we receive. It is a reasonable thing to want and it is also the requirement that most often turns out to be untrue.

Here is how to work out what you will genuinely edit, and what to pick once you know.

Be specific about what "update it myself" means

The phrase covers four quite different things, and they cost different amounts:

Changing existing text. Fixing a typo, updating a price, changing opening hours. Easy in every system, and this is what most people actually mean.

Adding items to a list that already exists. A new blog post, a new team member, a new project in the portfolio. Straightforward if the site was built with that list in mind, and awkward if it was not.

Adding a whole new page. A new service, a new location. Needs a page template, or you are building a layout.

Changing how a page is laid out. Moving sections around, adding a new kind of block. This is design work, and this is where page builders come from — and where they cost you.

Most businesses need the first two, occasionally the third, and almost never the fourth. But the fourth is what drives people towards heavy page builders, and the weight of those is what makes sites slow and hard to maintain.

The honest question

Before choosing anything, answer this: how often will you actually change something?

Not how often you intend to. How often you have, on your current site, in the past year.

• A few times a year. You do not need a CMS. You need a developer or agency you can email, and a sensible arrangement for small changes. Paying for and maintaining an admin system you log into twice a year is a cost with no return, and it is an attack surface.
• Monthly. A simple CMS for the parts that change, with the rest of the site as fixed pages.
• Weekly or more. A proper CMS, properly set up, with the content model designed around what you publish.

There is no shame in the first answer, and a lot of money wasted pretending it is the third.

The options, plainly

No CMS, content in the code. Fast, secure, nothing to update, nothing to break. The site loads quickly because there is no database query and no admin layer. The trade is that changes go through whoever maintains the code. Good for brochure sites that rarely change, and this is more sites than the industry likes to admit.

A traditional CMS such as WordPress. Enormous ecosystem, everyone knows it, an answer to every question already exists on the internet. The costs are real: plugins to maintain, security updates that must actually be applied, and performance that takes work to keep good. Fine when it is looked after, a liability when it is not.

A headless CMS. The content lives in a service with a good editing interface; your site pulls it in and renders it. You get a fast modern site and a genuinely pleasant editor. The trade is a monthly fee and a slightly more involved setup. This is often the right answer for a business that publishes regularly and cares about speed.

Git-based content. Content in files alongside the code, edited through a simple web interface. Free, versioned, no database. Excellent for technical teams and confusing for people who just want to fix a typo.

What to insist on, whatever you pick

Editing must be simpler than the thing it replaces. If updating a price means logging into an admin panel, finding the right block, understanding a layout system and remembering to clear a cache, you will email your agency instead, and the whole system was for nothing.

Preview before publishing. Non-negotiable for anyone who has ever published a half-finished sentence to the front page.

It should be hard to break the design. A good setup lets you change the words and not the layout. A page builder that lets you do anything also lets you make a mess, and the person who makes the mess is usually the one who then has to pay someone to fix it.

Your content must be exportable. If you cannot get your text and images out in a usable format, you do not own your content — you are renting access to it.

It must not make the site slow. Ask to see a real site the agency built on the system, and test it on your phone.

A pattern that works well

For most small businesses: the parts that change often go in a CMS, and everything else is a fixed page.

Your blog, your team, your portfolio, your prices — content, edited by you. Your homepage layout, your service page structure, your navigation — code, changed by whoever maintains the site.

This gives you control where you actually want it and keeps the complexity out of everywhere else. It is faster, safer and cheaper to maintain than putting the entire site behind a builder so you can, in theory, rearrange the homepage — something you will do once, in the first month, and never again.

The question to ask an agency

Not "does it have a CMS", but: "show me exactly how I would change a price on the services page."

Make them do it in front of you. If it takes more than a minute and does not look obvious, you are not going to do it, and you should know that before you pay for it rather than a year later.