I remember the first time a client told me they were ‘going headless.’
They were beaming. They had a roadmap, a new agency, and a budget that would make a small country jealous. On paper, it was a dream: total frontend control, lightning-fast page loads, and a ‘modern’ stack.
Six months later, they called me in a panic.
The site was fast, sure. But their operational workflows were in shambai. Now, instead of changing a banner in 30 seconds, their marketing team had to open a Jira ticket and wait three days for a developer to push a commit.
They hadn’t upgraded their store. They’d just built a high-tech wall between their business and their customers.
The industry loves to talk about the ‘conversion lift’ of headless commerce. Shopify’s data pushes it, and the agencies sell it as a silver bullet. But here is the truth they don’t put in the pitch deck: Headless is a massive organizational tax.
If you don’t have a world-class DevOps pipeline, headless is just a way to make your site crash in more sophisticated ways.
Most brands don’t need a decoupled frontend. They need a process that doesn’t require a computer science degree to change a discount code.
I’m starting to think we’ve replaced the problem of ‘slow sites’ with the problem of ’too much complexity to move at all.’
Maybe the real goal isn’t a ‘modern stack.’ Maybe it’s just a store that actually works.