Where Xperience by Kentico fits in a mid-market platform shortlist

Distinction is a Kentico implementation partner. That relationship gives us practical experience of the platform and a commercial interest readers should know about. It does not make Xperience by Kentico the right answer for every project.

The useful case for the platform is narrower than “enterprise capability without enterprise complexity”. Mid-market firms vary too much for that slogan to help. Xperience deserves consideration when its combination of content management, digital marketing and Microsoft-aligned development matches the organisation’s operating model. It is a poor choice when a simpler content system would meet the real need.

The gap it can fill

Some firms have outgrown a basic publishing setup. They run several sites or brands, need controlled workflows, want reusable structured content and need marketing activity to connect with the web experience. Their current stack may consist of a CMS, email platform, form tool, personalisation product and several fragile integrations.

At the other end of the market are broad enterprise suites with substantial licence, implementation and operating demands. A mid-market organisation can buy that power and still lack the team required to use it.

Xperience by Kentico can sit between those positions. As of August 2026, Kentico’s current documentation describes website channels built with ASP.NET Core, content workflows, reusable content, role-based administration and deployment to its SaaS environment. Its digital marketing capabilities include contact activity, forms, email, automation, campaigns and personalisation. Headless channels expose content through GraphQL and require the relevant licence tier.

Those details matter because “Kentico” can refer to different generations of the product. Procurement should assess the current Xperience by Kentico service and the exact licence under consideration, not rely on a feature remembered from Kentico Xperience 13 or an old implementation.

Where the unified approach helps

A unified platform can reduce the number of boundaries a team must operate. An editor may create web content, forms and emails in related tools. Marketers can build automation around known activities without first joining several products. Governance can be applied through common roles and workflows.

That does not eliminate integration. CRM, analytics, identity, data warehouse and line-of-business systems may still sit elsewhere. It changes the amount and type of integration the organisation owns.

This can be valuable when the digital team is large enough to use the connected features but too lean to operate a highly composable estate. It can also make accountability clearer: there are fewer suppliers to blame when data stops moving, and fewer contracts to reconcile when planning a change.

The trade-off is coupling. Choosing more capability in one platform means accepting its product direction, licence model and implementation conventions. The question is whether the operating simplicity is worth that dependency for your firm.

Technical fit comes first

Xperience by Kentico is built for .NET development. Kentico’s current system requirements list supported .NET versions and Microsoft SQL Server requirements, while its configuration guidance uses ASP.NET Core MVC for website channels. That makes it a natural shortlist candidate for organisations or partners already comfortable in the Microsoft ecosystem.

It requires professional development. Marketers can manage content and campaigns once the system has been implemented. Developers still need to model content, build components, integrate other systems and operate the solution.

That distinction affects total cost. A buyer should assess the team required after launch, not only the project team presented in the proposal. Who will build new components? Who will manage releases? How quickly can the firm obtain specialist support? What happens if the implementation partner changes?

A platform can be affordable to license and expensive to change. It can also cost more initially and reduce future integration work. The answer depends on the roadmap and operating model, not a universal ranking.

Marketing capability must have an owner

Built-in marketing features are valuable only if people will use them. Before treating automation, personalisation or campaign management as benefits, identify the team, content and data needed to run them.

Personalisation is a good example. Kentico’s current documentation notes that some website and email personalisation features depend on the Advanced licence tier and configuration by developers. The organisation still needs a meaningful audience definition, appropriate data, enough traffic to learn from and editorial capacity to maintain variants.

The same applies to automation. A visual workflow does not decide which communication is useful, who may receive it or how consent and objections are handled. In the UK, storing or accessing information on a user’s device and processing personal data require careful assessment. The ICO’s guidance on storage and access technologies is relevant when planning tracking and personalisation.

Buy the capability because there is a credible operating plan, not because it made the demonstration memorable.

Strong-fit conditions

Xperience is more likely to fit when several of these conditions are present:

• the organisation has reliable .NET capability internally or through a long-term partner;
• multiple sites, brands, languages or content channels need shared governance;
• content, forms, email and automation would benefit from closer operation;
• editorial roles and approval workflows are more complex than a basic CMS supports;
• a SaaS deployment model fits the organisation’s security and service requirements;
• the team wants headless delivery for specific channels without assembling the whole platform from separate products;
• the three-to-five-year roadmap justifies the implementation and ongoing specialist support.

Firm size alone is a weak criterion. A 1,000-person firm with one simple publishing site may need less. A 150-person regulated business with several audiences, systems and approval paths may need more.

Weak-fit conditions

The platform is less persuasive when the requirement is primarily to publish a modest brochure site and a small article library. In that case, much of the value would remain unused.

It may also be a weak fit where the organisation has no intention of maintaining .NET capability, where speed and low operating overhead dominate the decision, or where the architecture strategy deliberately favours independent best-of-breed services.

A complex platform will not repair weak content governance. If nobody owns expired pages, campaign data or editorial standards, more features can make the neglect harder to see.

Finally, Xperience should not be selected solely because an incumbent agency recommends it. Every implementation partner has experience, delivery economics and preferences that shape a shortlist. Ask the partner to name the circumstances in which it would recommend a different platform.

Questions for the selection process

A useful evaluation moves beyond a feature matrix.

Ask editors to complete representative tasks in the product, including awkward ones such as updating reused content, handling an approval rejection and finding an old campaign asset. Ask developers to explain how a new content type, integration and channel would be delivered. Ask operations how environments, updates, backups, monitoring and incident responsibilities work under the proposed deployment.

Then test the commercial assumptions:

• Which features require a different licence tier?
• What is included in SaaS and what remains the customer’s responsibility?
• Which custom components will the implementation create?
• How will content and data be exported if the firm leaves?
• What does a routine change cost after launch?
• Which roadmap items depend on capability the team does not yet have?
• How many separate tools and contracts would genuinely be retired?

The collection’s guide to comparing platform total cost of ownership provides a broader framework for this exercise.

A conditional recommendation

Xperience by Kentico can be a strong mid-market choice when a firm needs governed content and marketing capability, has the right technical support and wants to limit the integration overhead of a fragmented stack. Its current product supports a broader operating model than a simple CMS.

That same breadth creates cost and complexity. A firm that needs only publishing, or lacks the people to operate the marketing capability, should choose something smaller.

The sound recommendation is therefore conditional: shortlist Xperience when its architecture and integrated features answer requirements the organisation has agreed to fund and own. Eliminate it when they do not. A platform decision improves when the buyer is willing to hear both conclusions.

Budget fit. Can you absorb both the implementation cost and the ongoing licensing? Get a realistic total cost of ownership estimate, not just the Year 1 number. I've written a companion piece on how to compare digital platforms on TCO honestly - worth reading before any platform decision, not just this one.

If you want to assess whether it fits your specific requirements, we've put together a mid-market CMS/DXP decision checklist that covers the five criteria that matter most - including where Kentico fits, where it doesn't, and where other platforms might serve you better. It's designed to be something you can share with your managing partner or CFO before committing to anything.