What Headless Operations Actually Means
Headless commerce decoupled storefronts from backends. Headless operations does the same to the running of a company. This is what changes for owners now.
Section 3 of 9 · By Mike Birtwistle
The word “headless” will get thrown around a lot in the next two years. Most of it will be lazy. Before the term gets diluted, here is what it actually means, and what changes when you apply it to operations instead of architecture.
Where “headless” comes from
In software architecture, “headless” means the backend and the frontend have been decoupled. The engine still runs. The dashboard is just one way to see it.
The term was coined in 2012 by Dirk Hoerig, the founder of commercetools, to describe a new kind of e-commerce platform: one whose backend ran stores it never rendered. Within a decade, the idea had a name, a category, and a generation of platforms built around it. Shopify launched its own headless framework, Hydrogen, at Shopify Unite in 2021. Today, every serious enterprise commerce stack has a headless option.
Content management followed the same arc. Contentful launched in 2013 out of Berlin and built the same idea for words: a content backend whose stories appeared on websites, mobile apps, kiosks, and smartwatches that Contentful itself had never seen. WordPress was the dashboard. Contentful was the engine that ran without one.
In both cases, the visible interface became optional. The real value moved underneath. The store ran without the storefront. The article ran without the page.
The same shift, applied to a business
Headless Operations is the same shift, applied to the running of a company.
The CRM stops being the place your business runs through. It becomes a record store. A well-organized filing cabinet that exposes its contents through APIs. ServiceTitan, Jobber, Housecall Pro, Salesforce, HubSpot, whichever one you picked, the role is the same: hold the truth about who the customer is, what job is on the calendar, what got invoiced, what got paid.
The actual operating of the business moves to a layer above the CRM.
The routing of the next call. The follow-up on the unsigned estimate. The collection on the past-due invoice. The review request after the job closes. The reschedule when the customer pushes back. The reporting at the end of the week. All of it lifts off the screen and moves into a fabric that sits on top of the record store.
The fabric does not care which CRM you use. It reads from the record store, applies the policy, makes the decision, takes the action, writes the result back. It runs on agents instead of employees. It improves itself with every exception it encounters. It runs at three in the morning. It runs while you are on a roof. It runs while you are sleeping.
The dashboard becomes optional. The office becomes optional. The office manager becomes optional. None of them disappear by force. They become things the business no longer needs in order to function.
What “optional” actually means
This is the part that gets misread. “Optional” is not the same as “gone.” The dashboard is still there if you want to look at it, the same way Shopify’s storefront is still there if you want to use it. What changes is the requirement that a human sit in front of the dashboard for the work to happen.
That is the entire shift, in one sentence. Not “no more screens.” Not “no more humans.” But: the work no longer requires a human at a screen.
A trade business owner who grasps this shift early will, within a year, look around their office and ask a hard question: which of these chairs needs to be filled, and which of these chairs was only ever filled because the software could not yet do the job?
The headless commerce companies asked that question about storefront developers a decade ago. The headless CMS companies asked it about web teams. What happens when a trades owner asks it about the office is the rest of this manifesto.
That is what Headless Operations actually means.