How to choose the right CMS: a practical guide
To choose the right CMS, start with your business goals, not a feature list. Involve the people who'll use the system, turn your needs into weighted requirements, and test a shortlist with your own editors and content. Then look beyond the licence: total cost of ownership, lock-in, the implementation partner and long-term maintenance decide whether the choice still feels right in five years.
This guide is based on our webinar and white paper How to choose the right CMS for your organization. In it, leaders from four Umbraco partner agencies, who between them have taken part in many CMS selections, discussed the process with two people from Umbraco's product team. Prefer to watch? Jump to the recording.
In this guide
The 8 steps
- Start with your goals, not features
- Involve the right people early
- Understand the types of CMS
- Turn your goals into weighted requirements
- Shortlist and test with your own editors
- Calculate the total cost of ownership, and check for lock-in
- Choose the right implementation partner
- Plan for maintenance from day one
Also in this guide
Watch the webinar
Prefer to watch? Four partner agencies and Umbraco's product team discuss how to choose a CMS.
Why choosing a CMS has become harder
The CMS market moves fast. Bolette Kern, Product Manager for the CMS at Umbraco, describes how quickly the conversation has shifted. A few years ago the industry was focused on MACH (microservices, API-first, cloud-native, headless). Then traditional CMSs added headless capabilities, and the debate became headless versus hybrid. She sums up the market as fast-moving, crowded, competitive and noisy.
Part of the noise comes from rankings. Analyst reports can give you an overview, but different reports measure different things and don't always include the same products, so it's easy to end up comparing apples and oranges. Emiliano Bottaioli, CTO at Sampson May, puts it this way: being named a leader in a category is great for marketing, but it doesn't necessarily mean that CMS is the right fit for you.
That's why the steps below start with your organisation, not with the market.
Step 1: Start with your goals, not features
"You don't wake up one morning and instinctively know exactly what you need from a CMS."
Rune Strand, Product Communications Manager, Umbraco
Before you look at any product, ask why you're changing at all. Niels Brinkø, CTO at Kruso, suggests checking whether it's really the CMS you need to replace, or a website or digital experience that no longer supports the business. He's seen many organisations point at a product and say "we need a site on that platform", when what they need is a digital experience that supports their business and tools that support their editors.
Write down what the new CMS should make possible, for example:
publishing campaigns without waiting for a developer
launching new markets and languages faster
clearer governance and approval flows
delivering content to apps, screens or other channels
connecting content with commerce, CRM or marketing automation
Run a pre-mortem in reverse. Imagine the launch is over and the site is a success. What are people saying internally? That publishing is quick? That sales are up? Those answers become your goals.
Keep the "why" on file. Niels Brinkø's advice: write your reasons down and keep them visible through the project. When someone asks months later why you chose this system, you'll have the answer, and it's your best defence against scope creep.
Step 2: Involve the right people early
A CMS affects more people than most software. If only IT or only marketing decides, you'll find the gaps after launch.
Bring in:
Content editors, who'll use the system every day
Developers, who'll build, extend and maintain it
Marketing, who care about speed, campaigns and analytics
IT and security, who own hosting, access and integrations
Legal or compliance, especially in regulated sectors, for data protection (GDPR), accessibility and industry rules
You don't need everyone in every meeting. You need their requirements on the table before you shortlist.
Step 3: Understand the types of CMS
Emiliano Bottaioli sees a common mistake: clients putting an enterprise CMS, an open source CMS and a simple website builder side by side, as if they did the same job. Know which category fits before you compare products.
Type | What it is | Good fit when |
|---|---|---|
No-code website builder | Hosted, all-in-one tool with templates; no development needed | You need a simple site quickly, or a temporary presence |
Low-code builder | Visual, designer-led building with limited custom code | Design matters most and integration needs are small |
Open source CMS | Source code you can use, adapt and host where you want, with a developer community behind it | You want flexibility and control, with developers or a partner |
Enterprise CMS or DXP | Licensed platform, often with many built-in marketing tools | You'll use those tools and can carry the licence and complexity |
Headless CMS | Content delivered through APIs to any frontend | You serve several channels or build your frontend in JavaScript |
Two things to check:
For open source, check the community. Look at how big and active the community is, since that's where much of your help and extensions will come from. It's also worth checking whether the project is commercially backed, so there's a company to turn to if you need support or a new partner.
For enterprise platforms, check what you'll actually use. Emiliano's experience is that few clients use most of the extra tools they pay for, and those tools can make the backoffice heavier for editors.
Many CMSs now span more than one type, for example an open source CMS that also works headless. Read more: What is a CMS? · What is a headless CMS? · CMS vs DXP
Step 4: Turn your goals into weighted requirements
"Organizations often get caught up in feature comparisons without considering whether they actually need those capabilities."
Jason Prothero, President, ProWorks Corporation
Jason Prothero's point: if you buy an enterprise CMS with a thousand features and only use ten of them, you're paying for complexity you don't need.
Turn your goals from step 1 into requirements, grouped into areas like these:
Content workflow and governance: how content is created, reviewed, approved and published
Editor experience: how quickly editors can build and change pages without help
Integrations: CRM, commerce, search, marketing automation and other systems
Multilingual and multi-site: languages, markets and brands
Scalability: growth in traffic, content and teams
Security and compliance: your organisation's and your industry's requirements
Developer experience: technology stack, documentation, community and available skills
Cost and return on investment: whether the system's complexity matches how you'll actually use it
Ask "why" two or three times. For each major feature, ask why you need it. If there's still a good business reason after a few rounds, keep it. If the answer ends with "because a competitor has it" or "someone said it's a good idea", look again, since every feature costs something.
Give non-negotiables a measurable target. For example, don't just write "accessible", write which WCAG level. Don't just write "always available", write the uptime you need. Each step up costs more, so be precise about what regulation or your business really requires.
Use the CMS as a hub, not a do-everything tool. Jason describes CMSs being stretched into document management systems with heavy approval chains. A CMS can do light work in neighbouring areas like product information or digital assets, but past a certain point it's better to integrate a specialist system and let the CMS bring the content together.
Then weight everything in a scorecard. Mark each requirement as a must-have or a nice-to-have, give each area a weight, and score every shortlisted CMS against it. If everything is marked critical, you haven't prioritised yet.
Copy our free CMS scorecard template (Google Sheets)
Plan in phases. Nik Wahlberg's experience is that most RFPs contain "the kitchen sink". Decide what you need at launch and what can follow in a second or third phase. It's easier to hit the mark first time with a tight scope.
Step 5: Shortlist and test with your own editors
"A CMS might look great in a demo, but how does it perform when your actual content editors start using it?"
Nik Wahlberg, Founder & CEO, Scandia
Narrow the field with what you already know. Jason Prothero suggests starting from your team. Which technology stack does your IT department work with, for example Microsoft or Linux? Who'll help maintain and develop the site, and which technologies do they know?
Shortlist three or four options, ideally of different types, so you see real alternatives. Then test them yourself. A sales demo shows the best path through the product; your editors will meet all the other paths.
Give your editors real tasks, with your own content:
Create a new page with text, images and a form, and publish it.
Reuse a content block on several pages, then change it once.
Translate a page into a second language.
Schedule a page and send it for approval.
Roll back to an earlier version of a page.
Watch whether the editing experience suits your team. Jason noted that experienced editors can handle a lot of design freedom, while others get overwhelmed by too many options and work better with a more controlled setup.
Ask to see the backoffice of real, live sites, as well as the demo environment. Emiliano Bottaioli recommends asking agencies to show how they implemented earlier projects. Few buyers ask to see the backoffice, even though editors will live in it every day.
If you write an RFP, describe scenarios and keep it focused.
"Our marketing team needs to launch a campaign page in three languages without developer help" tells you far more than "Multilingual: yes/no".
Emiliano's warning: when an RFP lists everything, agencies have to price everything, and you pay for capabilities you may never use.
Nik's advice: aim for a handful of quality responses rather than fifteen, and talk to the bidders instead of judging on price alone.
Step 6: Calculate the total cost of ownership, and check for lock-in
The licence is rarely the whole story. Work out what the CMS will cost over at least three to five years:
licence or subscription
implementation and development
hosting and infrastructure
support and service levels
upgrades and ongoing maintenance
integrations and their upkeep
training and onboarding
your own team's time
the cost of leaving again, if you ever need to
Know how the costs arrive. Neither SaaS nor self-hosted is free to run. With SaaS, you pay a subscription continuously and the platform is upgraded for you. With a self-hosted CMS, upgrade and maintenance costs come in larger chunks at intervals, so you need to save up for them.
Check for lock-in before you sign. Jason Prothero's red flags were about ownership and exit: who owns the code, and can you leave a vendor or partner without starting over? Ask:
Can we export all our content and data in a usable format?
Do we own the code that's built for us?
Can we change implementation partner without changing platform?
Can we choose where and how the solution is hosted?
Can we connect the tools we already use through open APIs?
Do the licence terms or contracts make it hard to leave?
Check your price tag with Umbraco
Step 7: Choose the right implementation partner
"A CMS is a tool, but how it's implemented makes all the difference."
Emiliano Bottaioli, CTO, Sampson May
The same CMS can deliver very different results depending on who builds it, so the partner deserves as much attention as the platform. A good partner helps you turn business requirements into a technical solution, set up workflows, train editors and keep the solution healthy after launch.
When to bring in a partner. Niels Brinkø's rule of thumb: if you don't have the skills in-house, if it's a long time since you last did this, or if the project starts to feel too big, bring someone in. Even a short consultation early on can help you narrow the field. He also suggests being honest about whether your team's experience is recent, because the market moves fast.
Some partners will also help you write the RFP, which helps you ask the right questions from the start.
"Find someone that matches your industry or understands your challenges."
Niels Brinkø, CTO, Kruso
Questions to ask a potential partner:
Have you worked with organisations like ours, in size, sector and technology?
Can we see the backoffice of a site you've built and still maintain?
Can we speak to references?
What happens after the site goes live? Some partners hand over and leave; others stay for the long run.
How do you handle upgrades, security updates and incidents?
Who from your team will we actually work with?
You can choose the CMS first and then the partner, or let a partner guide the selection. Either way, keep the requirements and the final decision in your own hands.
Step 8: Plan for maintenance from day one
"A CMS isn't a one-time investment - it's an ongoing commitment."
Niels Brinkø, CTO, Kruso
A CMS needs regular updates, security patches and performance work. Nik Wahlberg shares an example: a client postponed CMS updates for years to save money, until security vulnerabilities forced an emergency migration that cost more than planned upgrades would have.
Nik's advice is to expect the site to keep evolving after launch, since no project ships with every requirement. Agree a regular rhythm with your partner, review analytics and feedback together, and set aside a maintenance budget or retainer that fits your volume.
Before you decide:
Check the vendor's release cadence and support periods. How often are new versions released, and how long is each version supported?
Budget for maintenance as a running cost, not a one-off.
Plan for growth in traffic, content, languages and integrations.
Leave room for new technology, such as AI-assisted editing or personalisation, without needing a rebuild.
Common mistakes when choosing a CMS
Choosing on trends or rankings instead of your own requirements
Letting the feature list grow until scope and budget get out of hand
Buying for features you won't use, and paying for the complexity
Forcing the CMS to do another system's job, instead of integrating
Letting one department decide for everyone who'll use the system
Trusting the demo instead of testing with your own editors
Comparing licence prices only, and ignoring total cost of ownership and lock-in
Treating launch as the finish line, with no plan or budget for maintenance
"A CMS should empower your organization, not complicate it."
Jason Prothero, President, ProWorks Corporation
Why the CMS decision matters even more with AI
With AI, creating content has become easier for everyone, so there's more of it and more competition for attention. Rune Strand argues that this makes how you plan, update, schedule and publish content more important, not less. A CMS that supports your content strategy and connects to the rest of your stack is a big part of standing out.
Where Umbraco fits
Umbraco is an open source CMS built on .NET and MIT-licensed, developed by Umbraco HQ together with a global community. It's a strong fit for organisations that want control and flexibility, with a backoffice editors can work in without developer help and an architecture developers can extend and integrate.
The partner agencies highlighted a few things from their own projects:
No licence fee for the core CMS, so more of the budget can go into the solution itself. You pay for add-ons, such as personalisation, only when you need them. You still need to budget for hosting, development and maintenance.
Flexibility to fit the business: one panellist describes Umbraco as a blank slate, which is both the most daunting and the best thing about it, because you build what the business needs instead of bending a bundled tool to fit.
Room to grow: Emiliano Bottaioli described clients that started small and grew to listed companies on the same platform.
You can host Umbraco yourself or use Umbraco Cloud for managed hosting, and work with one of our partners. Umbraco publishes its release cadence and long-term support periods, so you can plan maintenance from the start.
It isn't the right fit for every project, and that's the point of a structured selection: let your requirements decide.
Frequently asked questions
How do I choose the right CMS?
Start with your business goals, involve the people who'll use the system, turn your needs into weighted requirements, and test three or four options with your own editors. Then compare total cost of ownership, lock-in risk, implementation partners and long-term maintenance before you decide.
What factors should be considered when choosing a CMS?
The most important are:
how well it supports your business goals
the editor experience
content workflow and governance
integrations
multilingual needs
scalability
security and compliance
developer experience
total cost of ownership
how easy it is to leave if you need to
Should we let an agency choose the CMS for us?
An experienced partner brings valuable knowledge and can help write the requirements. Define your own business goals first, though, so you can judge the recommendation and stay in control of the decision.
How much does a CMS cost?
It depends on the type of CMS, the licence model, the size of the implementation, hosting and maintenance. Compare the total cost of ownership over several years, which covers far more than the licence or subscription.
Do I need a developer to manage a CMS?
Not for day-to-day content work, since a good CMS lets editors create and publish without code. You'll usually need developers or a partner to set up the CMS, build templates and integrations, and keep it updated.
When is it time to change CMS?
Common signs:
editors depend on developers for simple changes
the platform is hard or expensive to upgrade
integrations you need are missing
the system can't support new channels, markets or languages
Is an open source CMS secure?
An open source CMS can be very secure, provided it's kept up to date and well configured. Look at how security fixes and supported versions are handled, whether the project is commercially backed, and plan updates as part of your maintenance.
What's the difference between a CMS and a DXP?
A CMS manages and publishes content. A DXP adds personalisation, customer data and analytics across channels. Read more: CMS vs DXP: what's the difference?
Next steps
Get the full white paper: How to choose the right CMS for your organization
Weigh your options: Copy the CMS scorecard template
Comparing specific platforms? See Umbraco vs Sitecore, Umbraco vs Optimizely and Umbraco vs Kentico
Need help? Find an Umbraco partner or book a discovery call