Architecture & Technology

How I Approach Choosing a New CMS Without Starting With Features

Every CMS looks great in a demo. I start with requirements from marketing, engineering and security, then ask which platform fits the operating model.

When evaluating a CMS, it’s easy to get distracted by demos.

Every platform looks impressive in a polished demo. The editor is smooth, the templates are beautiful, the integrations “just work.” Vendors are very good at showing their best features on their best day.

But a demo answers the question “What can this product do?” The question that actually matters is different: “What do we need it to do?”

Start with requirements, not features

I prefer starting with requirements, gathered from everyone who will live with the decision.

What does Marketing need? How quickly can they publish? Can they build pages without developers for routine work? How do campaigns, landing pages and experiments fit in?

What does Engineering need? How do we build custom components? How does it fit our development workflow, version control and CI/CD? How do we extend it when the out-of-the-box features aren’t enough?

What does Security require? How is access managed? How does SSO work? What are the platform’s security responsibilities versus ours?

How will integrations work? Search, forms, analytics, consent, events, careers, CRM: how does each connect, and what are the limits?

How will developers deploy applications? If parts of the website need custom application logic, where does it run and how is it released?

How will authors publish? What does the workflow look like, including reviews, approvals and scheduling?

How will localization work? How are languages and regions managed, and how much effort does each new locale require?

How will we test and recover from failures? Can we stage changes? Roll back? Monitor?

Those questions shift the evaluation from “Is this impressive?” to “Will this work for us?”

Validate with real scenarios

Requirements on a spreadsheet are a good start, but they’re not enough. Every vendor will say yes to most of them.

During our evaluation, we examined the platform against concrete areas, including:

  • publishing workflow,
  • component development,
  • customized forms,
  • API-driven search,
  • integration with a Next.js application layer,
  • and cloud deployment.

The evaluation included hands-on validation planning around those scenarios before a final decision. The point was to test the things that would actually matter in daily operation, not the features that look best in a sales presentation.

Hands-on validation surfaces the details demos skip: the workaround needed for a particular form behavior, the limit on how content can be structured, the extra step in a deployment process. Those details often decide whether a platform will feel like an accelerator or a constraint two years later.

Think in total cost, not just license cost

A CMS decision also needs to consider the full cost of ownership:

  • implementation effort,
  • integration work,
  • training for authors and developers,
  • ongoing maintenance,
  • partner or vendor dependency,
  • and the cost of the things the platform doesn’t do that you’ll have to build yourself.

A platform with a lower license cost can easily become more expensive if it requires significant custom work to meet core requirements.

The question that makes it easier

A technology decision becomes much easier when you stop asking, “Which product has more features?”

And start asking: “Which platform best supports the operating model we’re trying to build?”

That reframing changes the conversation. Features become relevant only to the extent they support how the organization wants to work: how quickly content moves, how safely changes are deployed, how integrations are owned and how the team will grow.

The best CMS for one organization can be the wrong one for another. The demo can’t tell you which one you are. Your requirements can.

Nita Yang Lee

Senior Software Engineering Manager in Atlanta, leading web operations, platform modernization and engineering teams. More about me · Get in touch

Keep reading