It’s Halloween week, and the new concept of a headless CRM is out there again, galloping through LinkedIn ads with its cloak flapping and its eyes glowing.

I kind of get it, though, and can see why VCs are dumping money into this “new” model. The pitch is clean and modern: it’s AI-native, it auto-builds and updates records from your email, calendar, meetings, and Slack. The agents handle a lot of the busywork. No more reps logging every call by hand. It sounds like the thing that finally ends the Salesforce, HubSpot, Dynamics, etc., grind – i.e. less manual effort, more intelligence, basically a system that mostly runs itself. The promise of a smarter, lighter alternative to the old enterprise stacks is certainly appealing.

Except it’s still headless. You get the body: the data layer, the capture engine, the open flexibility to supposedly fit any company or situation, but the brain is missing. There are no ready-made workflows that match how your team actually sells, supports, or reports. No built-in opinion on how the data should move through your process or what “done” looks like for your organization. It starts utterly generic / formless on purpose so it can claim to work anywhere. Which also means it doesn’t arrive ready for you.

You’re handed a big box of parts and told good luck building your Ikea office desk. The box shows up with tons of pieces, the high upside promise, and some tools (how many allen wrenches do you need?). It can look slick once someone puts the pieces together: auto-captured data, agent drafts, natural-language queries. 

But someone (or a team of someone’s) still has to decide the workflows, shape the logic, customize the objects, connect the moving parts, train the team, and put in the energy to make it useful for your specific business. That work doesn’t disappear just because the system auto-captures data. It just shifts to setup, configuration, and ongoing care. And it is not remotely cheap once you count up all the time required to make it truly useful.

That’s why consultants love these platforms. “Don’t stick with your current CRM. Go headless. We’ll put the head on for you.” Then the project starts: mapping processes, building the custom logic, wiring everything up, handling the edge cases, training people, and charging for the ongoing care and feeding. They get to play hero while the company still carries the ongoing cost, maintenance, customizations, maintenance, and complexity. 

The license might look reasonable next to a full enterprise stack, but it’s the effort to get it working (and keep it working) is the part that really adds up. Same underlying problem, new costume. You still end up needing dedicated people, or outside help, just to make the system useful day to day, instead of having a solution that simply does the job you need done.

The headless horseman keeps riding because the alternative still requires you (or someone you pay) to finish the job and to keep doing the job.

It certainly looks modern, and feels flexible, and it can even auto-update records without anyone typing. But the head, the brain – i.e. the finished, usable system that fits how you actually operate, is still something you have to build and attach yourself. 

Companies that want something that works without the costume party of consultants, custom builds, and constant internal effort are still looking for the version that arrives with the head already attached. Until then, the rider keeps circling, and the consultants stay busy.

If you want to learn how you can get the best of both worlds, I’ll show you. Let’s chat: Schedule a Meeting