The hidden costs of a CMS: 6 things to calculate TCO

There's lots to consider when evaluating the Total Cost of Ownership (TCO) of a Content Management System (CMS), including developer costs, build and implementation, knock-on costs, licences, hosting, and maintenance. Embarking on a new CMS project? Here's what to remember...

by Rich Fairbairn

Published: 17:41, 16 January 2023

Last updated: 22:51, 11 September 2024

Implementation and customisation costs

In standard form, a generic headless CMS is unlikely to be a good toolset for a serious publishing business, so remember to factor in budget to customise the basic set of tools and technology to meet publishing demands, and ensure that plan accounts for how long that will take. 

If you need to engage a team of developers and project managers, or a 3rd party supplier, to build and implement a CMS and integrate it into your ecosystem, remember to consider the full system lifespan costs of those engagements - bespoke CMSs are not 'install and forget'.

Another consideration is that you may need to modify any internal or 3rd party systems with which the CMS must integrate or communicate, such as other CMSs, paywalls, Identity and Access Management, DAMs, websites and apps: budget for those changes, and for full testing of those systems after any modifications.

Maintenance and support costs

Any CMS will need ongoing maintenance and support to keep it fit and healthy, keep up with security updates, and to introduce any new features it may need over time - publishing doesn't stand still. 

An enterprise CMS should have provisions for enterprise-level support with a choice of SLAs to suit your needs. Glide provides Essential, Premier, and Premier+ support packages which include proactive monitoring of both platform and the costs for example. 

If your internal teams have completed all its customisations make sure to budget for round-the-clock cover as they may be the only people who know the system sufficiently to support it. 

Consider outsourcing this role to an external partner should your internal teams not be the right fit for these demands.

Training and onboarding costs

These costs can be explicit such as utilising a formal training provider, or less transparent - does the system take a long time to learn, and mean that users are slow in becoming truly productive?

Another shameless Glide plug - we offer unlimited baseline editorial training as part of the service. 

Content creation costs

Not all CMSs are equal in the basics of how long it takes to actually produce content and pages. The variations in time-to-site for content can be vast between systems.

A poorly designed system that doesn't think about its users or what it is being used for becomes a bottleneck for output and editorial responsiveness. Magnify those delays by hundreds or thousands of users, and the hidden costs of inefficient workflows become enormous. The lack of good editorial guardrails can cause massive damage. Is your team equipped to design these workflows and guardrails, and more to the point - should your team spend time on those tasks rather than focusing on what makes you unique - your customer facing product?

All of this adds up to a lot of hard to quantify costs.

Migration costs

If you are switching from one CMS to another, there will be costs associated with migrating your content and data to the new platform. Depending on the condition of your legacy content, this migration cost can be highly volatile and take place over highly variable timescales.

This is true in particular if you are using CMSs such as Wordpress that don't naturally have good meta data management rules and where information architecture is likely to be poor.

Hosting and usage costs

A headless CMS will need to be hosted somewhere, be that in the cloud or (very rarely now) on-premises at a site of your own. 

Cloud hosting can be managed by your own personnel if they have suitable expertise, or outsourced to a 3rd party or the CMS provider if they offer that service. In either case, be certain to check service and support levels to ensure they can match your needs: a fixed hosting cost might look attractive, but be more costly in the long run if your sites are slow or you incur severe penalty costs for exceeding traffic figures.

Costs will typically comprise of usage-based elements - broadly a measure of how much data is in the system, how it gets moved about, and how many users the CMS has -  and traffic-based elements linked to your various consumer-facing outlets. Requested improvements such as beefed up security or better global availability can add extra costs. 

Should you be trying to manage hosting on-premises, then account for hardware purchase and maintenance costs, associated licences, personnel to manage your tech stack, on-call and out of hours support and site access, power and cooling costs and the square-footage costs of floorspace. Self-managed hosting of your data and systems may also incur significant additional site security and disaster recovery costs/protocols.

There is clearly only one winner when it comes to Total Cost of Ownership and that is a specialised vertical SaaS platform. Overall, it's important to carefully evaluate all of these costs to get a complete picture of the TCO of a CMS for your business.