Skip to content
Digitice
Let's talk
Insights

Websites & e-commerce 6 min read

Waiting for a developer to change a sentence? How to choose a CMS your team can run

If every small website change waits in a developer's queue, the tool is the problem. Here is how to choose a CMS your own team can run with confidence.

By Digitice Admin

Your sales team spots an old price on the website. Your marketing lead wants a new case study live before a pitch. Both are small jobs, yet both go into a developer's queue. The change takes days, not minutes.

The cost adds up quietly. Buyers read out-of-date pages. Campaigns launch late. You pay for developer time on work your own staff could do. Over time, people stop asking for changes at all, and the website falls further behind the business.

The fix is usually not a better developer. It is a website built on a CMS your team can run. A CMS, or content management system, is the tool you log into to edit pages, add articles and upload images. This article explains why editing goes wrong, what good editing looks like, and how to choose well.

Why simple changes end up with a developer

Most businesses do not choose to depend on a developer. It happens for a few common reasons.

  • The content is locked inside the design. Text and layout are built together in code. Changing a heading means changing the code.
  • The editing screen is confusing. Staff can log in, but one wrong click breaks a page. So they stop trying.
  • Page builders get heavy. A page builder is a drag-and-drop tool added to a website. Each plugin adds features, but also adds weight. Pages slow down, and edits start causing odd problems.
  • Nobody planned the content. If the site was designed before anyone decided what pages and sections it needed, there is no clear place for new content to go.

Notice that only one of these is about the tool itself. The others are about how the site was planned and built.

What "easy to edit" really means

Almost every CMS claims to be easy. A better test is to ask what your team needs to do each month, then check the system against that list.

A CMS your team can run usually has:

  • Blocks. These are ready-made page sections, such as a text panel, a quote or a case study card. Editors add and reorder them without touching the design.
  • Clear content types. Case studies, articles, team members and services each have their own simple form. You fill in the fields and the site handles the layout.
  • Roles. Different people get different rights. A junior editor can draft a page. A manager approves and publishes it.
  • Previews. Editors see the page before it goes live.
  • Guard rails. Editors cannot break the layout, pick off-brand colours or upload huge images that slow the site.

The guard rails matter more than people expect. Freedom without limits is what makes many sites slow and messy after a year.

Your main options and their trade-offs

There is no single right choice. Each option suits a different stage and budget.

Option Good for Watch out for
Template with a page builder A quick start on a small budget Looks like other sites; gets slower as plugins are added
Hosted website builder Very simple sites with few pages Limited structure; harder to grow or move away from
Bespoke site on a standard CMS Businesses that need a site shaped around their buyers Needs proper planning up front
Headless CMS Content shared across several sites or apps More technical; needs developer support to change layouts

A headless CMS stores your content separately from the website that shows it. This is useful if one set of content feeds several brands or channels. For a single company website, it can add complexity you do not need.

The honest trade-off is this. Cheaper options are faster to start but often cost more in time later. Bespoke options cost more planning at the start but stay easier to run.

Plan the content before you pick the tool

Many teams choose a CMS first and plan the content second. It works better the other way round.

Start with your buyers. Who visits the site? What do they need to believe before they contact you? What must they be able to do on each page? The answers tell you which pages and sections you need.

Then list what your team will change often. For most firms it looks something like this:

  1. News and articles
  2. Case studies
  3. Service details and prices
  4. Team profiles
  5. Landing pages for campaigns

Each item on this list should become a simple form or block in the CMS. Anything you rarely change, such as the main navigation, can stay more fixed. This is the approach we take on bespoke websites: content structure and copy first, then design, then the build.

How to test a CMS before you commit

Do not judge a CMS from a sales demo. Judge it by letting your own people use it.

  • Run a real task. Ask the person who will edit the site to add a case study and publish it. Time it. Watch where they get stuck.
  • Try to break it. Paste in text from a Word file. Upload a very large photo. See what the system does.
  • Check the roles. Set up a draft-and-approve process and test it end to end.
  • Ask what happens to speed. Find out how images are handled and whether new features need extra plugins.
  • Ask about search basics. Can editors set page titles, descriptions and clean web addresses? Are sitemaps and structured data, the hidden labels that help search engines read a page, handled for you?
  • Ask about connections. If enquiries should go into your CRM or mailing list, check how that works. Our page on integration and automation covers this in more detail.

If your team can complete the real task alone, without notes, you have a strong sign the system will work for you.

A short checklist for your next website conversation

When you speak to any supplier, ask these questions:

  • Will we see the content structure before the visual design?
  • Which parts of the site can our team edit, and which parts are fixed?
  • What blocks and content types will we get?
  • Who will train our team, and how?
  • What happens to page speed as we add content?
  • If we leave, can we take our content with us?

Clear answers to these questions tell you more than any portfolio.

Next step

Pick one change your team asked for last month. Write down how long it took and who had to do it. If the answer is days and a developer, your CMS is costing you more than it should. If you would like a second opinion on your current site, get in touch and we will talk it through.

Questions

Frequently asked questions

What is a CMS?

A CMS, or content management system, is the tool you log into to edit your website's pages, articles and images. A good one lets your staff make everyday changes without writing code or asking a developer.

Can we switch CMS without rebuilding the whole website?

Usually not, because the design and the CMS are closely linked. Moving to a new CMS is normally part of a rebuild, and it should include redirects and content mapping so you keep your search rankings.

Is a page builder good enough for a small business?

It can be for a simple site at the start. The risk is that each added plugin makes pages heavier and slower, and editing can become fragile as the site grows.

How do we know our team will actually use the new CMS?

Test it with the people who will edit the site before you commit. Ask them to complete a real task, such as publishing a case study, and watch where they get stuck.

Keep reading

Next step

Tell us what you need to ship.

A 30-minute call with a senior lead. You leave with a clear scope, a realistic timeline and a fixed price, whether or not you work with us.