Why we treat the CMS as a liability, not a shortcut
A CMS doesn't remove complexity from a project. It just moves it somewhere you can't see it as clearly.
Every client meeting eventually arrives at the same question: what CMS are you using. It's a reasonable thing to ask. It's also the wrong question, because it assumes the CMS is the hard part. It isn't. The hard part is everything the CMS doesn't do, and every CMS, no matter how good, doesn't do a lot.
We've watched teams pick a CMS in week one to feel like they've made progress, then spend the next six months fighting its data model instead of building the product. The CMS was supposed to be a shortcut. It became the roadblock nobody budgeted for.
This is why we treat every CMS as a liability we're choosing to take on, not a foundation we get for free. Liabilities have to be managed. That means isolating content structure from presentation logic, keeping the CMS replaceable rather than load-bearing, and never letting its admin panel define what the business is allowed to do. If swapping the CMS would require rewriting the application, the CMS was never really a tool. It was an architecture decision disguised as a convenience.
The complexity doesn't disappear when you outsource content management. It just moves into integration code, migration scripts, and workarounds for whatever the CMS assumed you'd never need. Someone still has to hold that complexity and understand it end to end. We'd rather that someone be us, on purpose, than a support ticket queue six months from now.
None of this means we avoid CMS platforms. We use them constantly, and some are excellent. But we choose them the way you'd choose a subcontractor, not a co-founder: useful, replaceable, and never in charge of the decisions that actually matter.