What to ask about editing, content structures, integrations and ownership before you commit to a platform
Most of the pressure around choosing a CMS lands in the weeks before a site goes live, when the demo looks sharp and the shortlist is short. The decision you are actually making, though, is about the two or three years after that: who updates the pricing page, how a new service gets added, what happens when the CRM changes hands. A platform that is pleasant to build on and awkward to live with costs you in small, repeated ways, usually in time your team does not have. This article sets out the questions worth asking before you commit, and how to judge which answers matter for your business rather than someone else’s.
Why choosing a CMS is a decision about the years after launch
A website build has an end date. The way the business uses it does not. Six months on, the questions change: can we publish a new service page without a developer, does the event form reach the CRM, why does the layout break when someone pastes from Word. Those are platform questions, and they decide whether the site keeps earning its keep.
That is why choosing a CMS out of habit, because the last agency used it or a competitor did, so often disappoints. The platform is rarely wrong in itself; it was chosen for someone else’s operation. An established business with twelve service pages, a news section nobody updates and one form that matters has different needs from a membership body publishing weekly to three audiences. So the honest version of this decision starts with how your business runs, then asks which platform suits that.
The editing experience is the part you live with
Ask who will log in, and be realistic about it. In most established businesses the person who updates the site is doing it between other work, not as their job. If a simple change requires remembering which of four page builders was used on that template, the change does not get made, and the site slowly drifts out of date.
Sit with a demo and try the dull tasks rather than the impressive ones. Add a staff member to the team page. Reorder three items. Change an image and see whether the layout holds. Check whether you can preview before publishing, revert a mistake, and give someone permission to draft without permission to publish. A platform that handles those five things calmly will serve you better than one with a longer feature list.
Content structure decides how much manual work you keep
Websites get expensive to maintain when content is stored as free-form pages. If each service page is a blank canvas, then every update is manual and every listing of services has to be edited separately. Defined content types change that: a service has fields, and the hub page, the related links and the navigation draw on the same record.
Good structure also supports the things that are easy to neglect. Heading levels, image alternative text and consistent link labels are part of meeting the Web Content Accessibility Guidelines, and a CMS that builds those into its templates makes compliance a default rather than a project. For example, when the template sets the heading order, an editor cannot accidentally break the page outline while making a Tuesday afternoon edit.
What has to connect, and who will look after it
List what the site must do beyond publishing pages: enquiry forms reaching a CRM, bookings, payments, gated documents, member logins, a feed from another system. Then ask how each connection is made and what happens when it fails. Feasibility depends on the platforms involved, their APIs, your access and your licences, so a confident “yes, that integrates” deserves a follow-up question about who tests it and who fixes it.
Ownership belongs in the same conversation. Somebody has to apply updates, hold the backups, watch the security and answer the phone when a plugin conflicts with a theme. That may be your internal team, your developer or an agreed care arrangement, but it should be named before launch rather than discovered afterwards. The same thinking applies to what happens between a visit and an enquiry: the platform is only useful if the path through it works.
Where WordPress fits, and when a bespoke platform earns its cost
WordPress suits many established businesses. It handles content types, editorial workflow, forms and common integrations well, and the editing experience can be shaped around the way a particular team works rather than left generic. Our WordPress development work covers the CMS and the editing experience as well as the visitor-facing site, because the two are the same decision.
A bespoke platform suits requirements a standard website cannot meet. Learning programs, member participation, self-service portals and operational reporting often involve permissions, data models and workflows that a content system was never built to carry. Where that is the case, a custom digital platform is the honest answer, scoped around users, workflows and functional requirements.
Plenty of other platforms serve their users well, and the right question is never which is best in the abstract. It is which one matches your publishing pace, your workflows and the people who will run it.
A practical way to go about choosing a CMS
Work from the operation outwards. Before anyone demonstrates a platform, write down the answers to a handful of questions and take them into every conversation:
- Who updates the site, how often, and what do they change most?
- Which content repeats across pages and should be stored once?
- What must connect to another system, and who owns that system?
- Which approvals apply before something goes live?
- Who maintains, updates and backs up the site after launch?
- What might the business need the site to do within the next year?
Those answers do most of the deciding. However, they only help if you insist on specifics in return: ask to see the editing screen for your hardest content type, not a brochure page, and ask what a typical change costs in effort. If the shortlist still feels even after that, talk the requirement through with someone before the build starts rather than after it.
Frequently asked questions about choosing a CMS
WordPress suits many established businesses, particularly when the build is shaped around their content types, editorial workflow and the systems they already use. It is a weaker fit where the requirement is really an application rather than a website.
When the core requirement involves user permissions, structured data and workflows that a content system was not designed to manage, such as learning delivery, member self-service or operational reporting. A standard site with one unusual feature usually does not warrant it.
The platform affects what you can control: page structure, metadata, internal linking, redirects and site speed. No platform guarantees rankings, so judge a CMS on whether it lets you implement search work without fighting it.
It depends on the volume of content, how structured it is now, and how many integrations have to be rebuilt and tested. Content preparation and redirect mapping are generally the parts that take longer than expected.
Not necessarily, but someone must own updates, backups, monitoring and recovery. Agree where that responsibility sits before launch, in writing, whoever holds it.
A website your team can actually run
The point of this decision is not the platform. It is a site your people can keep current, that holds your content in a sensible shape, and that passes information to the systems behind it without anyone retyping anything. Get those right and the website stops being a project you survive every few years.
Redfox Digital is a Sydney-based digital growth agency working with established businesses whose digital presence is not doing justice to what they do. We bring strategy, marketing, technology and execution together under one roof, so businesses don’t have to coordinate five different specialists just to solve one problem, and we recommend a platform based on the requirement rather than our habits.
If you are weighing platforms now, bring your requirement and your constraints and we will tell you what we would build on and why. Book a discovery call.
