How to choose a CMS for your business: questions to ask before you decide
"Which CMS is best?" is the wrong question. The right one is: which CMS best fits what your business will actually do with it a year from now, and five years from now.
Start with questions, not system names.
CMS rankings answer a question nobody asked. Before any system's name comes up, answer a few concrete questions:
- How many pages, and how complex a content structure, will I have in 2 years?
- Do I need multiple language versions?
- Who will be editing the content — one person, or a whole team with different permission levels?
- Am I planning integrations with other systems (ERP, CRM, payments)?
- Will the same developer maintain the site for years, or will different people take turns?
The answers usually narrow the choice down to one of the groups of solutions described below.
Website builders and subscription platforms — when the site should stay simple.
Wix and similar builders serve very simple brochure sites well, and Shopify works for stores without extensive editorial content. You pay a monthly subscription in exchange for ready-made infrastructure and no hosting worries. The limitation shows up once the site needs to grow: content structure, integrations, and the ability to move your data elsewhere all depend on what the platform allows. I cover this in more depth in website builder vs CMS.
Plugin-based CMS — a fast start, more parts to keep an eye on.
The most popular systems in this group rely on ready-made themes and thousands of plugins that you assemble the features you need from. It's a sensible choice for simpler business sites and blogs, where launching quickly matters more than precise control over data structure. The price of that simplicity: security and performance depend heavily on the quality of the plugins installed, and it's easy to end up with too many of them — each one being a separate thing to update and keep an eye on.
Drupal — more work up front, more control later.
Drupal requires more planning at the implementation stage, but in return gives you a solid data architecture, built-in multilingual support, and permission mechanisms that simpler systems need extra plugins to add. It's a solution that holds up well on large, multilingual sites, or ones meant to grow over years rather than just survive until the end of the year. It's worth remembering, though, that this solidity comes at a price: Drupal — like any CMS — needs regular upkeep afterward, which is covered in more detail in the piece about why updates matter.
Headless CMS — only when there's a real need.
Headless solutions (a CMS separated from the visual layer) make sense for unusual projects — for example, a single content base feeding a website, a mobile app, and a point-of-sale screen at the same time. But that's a level of complexity worth reaching for only when there's a real need, not "just in case."
Implementation cost and maintenance cost — two different numbers.
When comparing offers, it's easy to focus only on the cost of the implementation itself. Meanwhile, a simpler, cheaper start on a system assembled from many plugins can end up costing more in upkeep over time — more parts to watch, more risk that one of them breaks after an update. Drupal tends to be pricier up front, but at the right scale (a large number of pages, several languages, a team of editors) its maintenance cost grows more slowly. So the question worth asking a provider isn't just "how much does the build cost," but also "how much will maintaining this really cost over the next three years." I break that bill down in how much Drupal maintenance costs.
Migrating from one CMS to another a year in costs more than an extra week of thinking it through before you start.
Frequently asked questions.
Can I switch CMS later? Yes, but it's a separate project, not a simple export-import — content has to be moved over, and the data structure often needs to be redesigned around what the new system can do. It's cheaper to think the choice through properly at the start than to migrate a year later.
Is a CMS with lots of plugins secure? The core of popular systems is regularly updated. The risk grows with the number of installed plugins — each one is an extra potential point of attack that needs to be tracked and updated separately.
How much does a Drupal website cost to build? Usually more than a simple site assembled from a ready-made theme and plugins — Drupal requires more development work up front. The difference pays off on sites meant to grow: more pages, languages, or permission levels down the line, without an expensive rebuild.
Can you build an online store on Drupal? Yes, although a dedicated e-commerce platform can be a faster start for a simple store. Drupal works well for stores integrated with a large content system or multiple languages.
Summary.
The right answer depends on your specific situation, not on rankings you find online — and that's where the conversation with a developer should start, before any particular technology's name even comes up. Also see what the whole website development process looks like, so you know what to expect once you've picked a CMS.