When Content Becomes a Commodity, Your CMS Becomes a Brand Decision

Paul Graham recently wrote about us entering the "Brand Age," a period where AI makes production so cheap and abundant that the differentiator shifts from what you make to who makes it. Taste, curation, and identity become the competitive edge.

He was talking about consumer goods. But the same logic applies to content.

When every company can generate a thousand blog posts overnight, what separates the signal from the noise? The answer is taste, editorial voice, and the craft behind how content gets made.

And that means your CMS, the thing most people treat as plumbing, suddenly matters in a way it never did before.

The plumbing era is over

For years, choosing a CMS was a technical decision. API flexibility. Framework support. Deployment options. The developer picked it, the content team lived with it. The assumption was that the hard part was delivery, not creation.

AI just flipped that assumption.

Creation is now trivially easy. Any tool can generate passable content. The valuable part is the editorial process: how you shape, refine, and publish. How your team collaborates on a piece. How the tool itself influences the quality of the output.

Your CMS is no longer invisible infrastructure. It's an editorial statement.

The editor is the brand

When content is abundant, the editing experience becomes both the bottleneck and the differentiator. A CMS that treats editing as an afterthought produces content that feels like an afterthought. One that prioritises the editorial experience produces content with intention.

This is why we built Strife as an editor-first CMS. Not because developer experience doesn't matter (it does), but because we saw where the puck was heading. The teams that win in a world of infinite content are the ones with the best editorial craft. And craft requires tools that respect the process.

A beautiful, responsive, collaborative editing experience isn't a nice-to-have. It's a brand decision. It signals that you take content seriously, that you value the people who create it, that your content isn't just generated but made.

Taste scales differently than technology

Taste doesn't come from your tech stack. It comes from your people and the environment they work in. The best writers and editors do their best work when the tools disappear, when the interface is so good it gets out of the way.

Most headless CMS platforms optimised for the developer. Clean APIs, flexible schemas, great SDKs. All important. But they left the content team staring at form fields and JSON previews, wondering why publishing feels like filing a tax return.

In the Brand Age, that's a strategic liability.

What this means for content teams

If you're choosing a CMS in 2026, ask yourself a different question. Not "which one has the best API?" but "which one makes our content team do their best work?"

In a world where AI handles the first draft, the competitive advantage is in the second draft. The third draft. The editorial judgment that turns generated text into something worth reading.

Your CMS is either helping that process or hindering it. There's no neutral ground anymore.