Why SitecoreAI - Getting into the shoes of the customer How to select right CMS

Hi Team,

Lately, I have been talking to lot of our customers / potential customers and having pre-sales demos where one question always comes is "Why Sitecore"? 

Now this question can be for any product which is out for sell.

And as a technician I always get into product technical features, but at the same time as a pre-sales guy, it also makes me think, surely all competitive products have same features, so definitely answer to this is not in the technicalities. 

If you step back and think, we are also a customer in our daily life and buy lot of things, what is that process we go through? When we buy, how can your customer decide if this is a right fit for you or not, why we select A over B? Is it price? is it service? Is it a brand? Is it about features? Is it about brand loyalty? 

When it is a technical product, I am sure it cannot start with the technicalities of the product or selecting product itself, 100% not, I feel decision is always business strategy first and then going for a selection of the right tool

If we talk in context of selecting CMS, we cannot start with the available CMSs out there and selecting one of it first and then think about fitting the business strategy or problem into it, It will backfire 100%

So, How to select right CMS?

Right path is first strategizing the digital transformation strategies by asking questions like

• What is the end goal?
• How can I give connected experience to my customer?
• How can we automate things?
• How easy it is for a business to go to marker fast?
• What is the marketing team is trying to do?
• Are we getting the right data, for right audience? and have right campaigns? 
• Is it future ready?

And lot more questions like these should be discussed first before any RFP (Request For Proposal) is out or you are getting into any discussions with any vendor

So crux is,

A customer can decide whether a CMS/DXP is the right fit by starting with business strategy and experience goals (not the tech), translating those into measurable requirements, and then evaluating platforms against a small set of “non‑negotiables” (security/compliance, performance, integration, and operability) plus “future-ready” capabilities (composability, omnichannel, scalability, and upgrade burden). The decision is typically made by a customer's DX team combined, so the evaluation must produce a clear business case with quantified impact, risk reduction, and total cost of ownership (including upgrade/maintenance effort).

Key Findings of how the decision should be made by a customer team

• Fit is determined by experience outcomes first: omnichannel cohesion, content discoverability, and connected customer journeys should be defined and measured before selecting technology.
• Buying is team decision-driven: success requires mapping stakeholder priorities (Marketing, IT, Security, Compliance, Product, Support, Finance) to a single decision scorecard and business case.
• The strongest decision drivers are operability + risk + scale: security/compliance, performance/reliability, integration flexibility, and the ability to evolve without heavy upgrades typically outweigh feature checklists.

Detailed Analysis

1) Start with Strategy and then translate to Experience Requirements

See the image above of three steps of Strategy, Experience , Technology - Please observe technology is always last.

A. Strategy (why)

• Growth goals: acquisition, conversion, retention, upsell
• Operating model: centralized vs federated content teams, global/local governance
• Time-to-market expectations: campaign velocity, experimentation cadence
• Risk posture: regulatory exposure, availability requirements, incident tolerance

B. Experience (what)

Define the experiences you want to deliver across channels:

• Omnichannel cohesion: same customer identity, consistent content and offers across web/mobile/email/in-store/portal/support
• Content findability: search, taxonomy, personalization rules, content reuse, localization
• Connected experience (CX in DX): journey continuity (handoffs across touchpoints), personalization, segmentation, integration with CRM/CDP/commerce

C. Technology (how)

Only after A and B, evaluate whether a platform can deliver those outcomes under your constraints:

• Architecture fit: monolith vs headless vs composable/hybrid
• Integration pattern: API-first, middleware compatibility
• Deployment/operations: cloud, SaaS, self-hosted, DevOps maturity

2) Core “Fit” Questions (presented in customer's language)

Use these questions as the platform fit gate:

Omnichannel experience

• Can the platform deliver content consistently to all current and planned channels (web, app, kiosk, partner portals, IoT, etc.)?
• Can it support reusable content models (structured content, components) rather than page-only authoring?

Content is easy to find

• Does it have strong content modeling, taxonomy, metadata, and search (both for editors and end users)?
• Can teams govern and locate assets quickly (DAM integration, tagging, workflows)?

Current setup: "good" vs "future-ready"

• Are you stuck spending most effort on upgrades and maintenance versus building new experiences?
• Can you add new channels/features without replatforming?
• Does the vendor roadmap align with your direction (AI tooling, composability, privacy changes, new channels)?

Ecosystem decision (not a single decision maker)

• Can you create a business case that different stakeholders will accept (Marketing speed, IT operability, Security risk reduction, Compliance readiness, Finance TCO)?

3) Key driving decision makers (who influences what)

A CMS/DXP choice typically has these decision-makers and drivers, It depends a lot on communication from customer's transformation team and vendor team to talk and have the decision makers aligned on all areas to be able to decide which platform and which tech. they should go.

Generally, following are the key points which different stakeholder would like to have in any CMS.

1) Marketing / Digital Experience

• Faster publishing, campaign velocity, personalization, experimentation
• Editorial UX, workflow, approvals, localization

2) Product / Business Owners

• Conversion rate, customer satisfaction, retention
•  Ability to launch new journeys/features quickly

3) IT / Architecture

• Integration, scalability, maintainability, DevOps fit
• API-first, modularity, observability, incident management

4) Security

• Identity/access control, secrets management, audit logging
• Vulnerability management, patching model, data protection

5) Compliance / Legal (Healthcare, Automotive, E-commerce implications)

• Regulatory alignment (HIPAA/PHI handling if applicable; PCI for payments; privacy laws)
• Data residency, retention, audit trails, accessibility requirements

6) Finance / Procurement for TCO calculations

• Total cost of ownership (licenses + hosting + implementation + ongoing ops)
• Vendor risk, contract terms, predictable costs

7) Customer Support / Operations

• Reduced content errors, fewer incidents, easier rollbacks
• Consistency across self-service and assisted channels

4) Decision Drivers (what typically “wins”)

Now that we have all of it covered, But customer team's influence will based majority on below points which could be key decision drivers for them.

 1) Performance & Reliability

• SLA/uptime, latency, global delivery, caching/CDN strategy
• Peak traffic handling (campaign spikes, seasonal events)
• Monitoring/observability (logs, metrics, tracing)

2) Security

• SSO (SAML/OIDC), RBAC/ABAC, MFA, least privilege
• Secure SDLC, penetration testing, vulnerability disclosure
• Encryption (at rest/in transit), key management, audit logs

3) Compliance

This is one of the important points, if there are domain specific requirements, how much compliant the CMS is, even if it does everything above but its not compliant, The decision will be not to use this until it becomes compliant.

• Industry-specific: HIPAA (health), PCI (payments), privacy regulations, accessibility (WCAG), records retention
• Data residency and vendor subprocessors

4) Future-ready (scale + adaptability + ease of use)

• Composable capabilities: ability to swap components (search, personalization, commerce) without replatforming
• Content reusability across channels
• Developer productivity (SDKs, APIs, CI/CD)
• Editor productivity (components, previews, approvals, localization)

5) “Upgrade effort” as a first-class KPI (how to reduce wasted effort)

Many organizations pick a platform that becomes an "upgrade loop." A fit check should explicitly score:

• Upgrade frequency and effort: hours per month/quarter spent on patching, regressions, re-testing
• Breaking-change risk: how often upgrades require rework
• Operational burden: hosting, scaling, security patching responsibilities

What reduces upgrade effort:

• SaaS-managed platform where patches and infra are handled by vendor (with clear release management)
• Strong backward compatibility and tooling (migration tools, deprecation policies)
• Automated testing and staging environments that mirror production

6) How to build the business case for a combined team decision

A good business case ties platform capabilities to measurable outcomes:

1) Value (revenue / growth)

• Faster launches → more campaigns → lift in conversion/lead volume
• Personalization/targeting → higher AOV/retention

2) Cost savings (operational)

• Reduced engineering time on upgrades/maintenance
• Fewer incidents and lower support burden
• Reduced vendor sprawl (consolidation)

3) Risk reduction

• Compliance exposure reduction (auditability, access controls)
• Security posture improvement (patching, logging, incident response)

7) Practical evaluation scorecard (use this to decide “right fit”)

Customer team (shown in above wheel diagram) should now put high level points on the board and start the evaluation process based on different BUs, Practical way would be to have a score card for every points and have the evaluations done in different categories, Some could be like below

1. Experience enablement -  (omnichannel, personalization, preview, workflows)
2. Content operations - (modeling, reuse, localization, governance, search)
3. Integration & architecture - (API-first, commerce/CRM/CDP, middleware)
4. Security & compliance - (SSO, audit logs, certifications, data controls)
5. Performance & reliability - (SLA, global delivery, DR, observability)
6. Operability & upgrade burden - (patching model, release cadence, migration effort)
7. Total cost of ownership - (license + implementation + run)
8. Vendor viability & roadmap - (support model, community, product direction)
9. Team fit - (editor usability + developer productivity)

NOTE: Here you can evaluate CMS too as well as different vendor too in the same score card.

8) "Latest offering" and "tech stack used" (how customer should interpret these)

Instead of "latest features" in isolation, customer should ask:

• Which features directly improve our KPIs (speed-to-market, conversion, operational cost, risk)?
• Are “latest offerings” stable, supported, and used by reference customers at our scale?
• Does the tech stack align with our talent pool and operating model (SaaS vs self-managed; frameworks, APIs, integration tooling)?
• As AI is everywhere, One of the criteria is definitely AI capabilities, How much of AI features are backed into CMS, how can it empower the CMS user or content authors.  

Summary

The whole exercises which i gave above is to help customer decide when they are going under digital transformation and want to select CMS from pool of different CMS available

I have had many experiences where if above exercises are not done, It creates friction among customer and vendor team, because customer is expecting things which the selected tool or vendor can not do

So, i really hope this extensive guide will all the customers out there and use it as a starting point 

NOTE: All of the above images are generated with google gemini.