Two weeks ago I wrote that our sellers were already practising and we just gave it a home. Beth and I told that story at Seismic Shift in Carlsbad. The room was generous, the questions were sharp, and the sellers who practised really did perform differently from the ones who didn't.
But the thing I keep thinking about isn't our session. It's a word that came up in almost every keynote and half the hallway conversations.
Headless.
What headless means for enablement
For years, enablement has been a destination. You built a place: a portal, a learning platform, a content hub. You made it good. You taught people to go there. You measured whether they did.
Headless turns that inside out. The content, the guidance, the coaching, the permissions and the governance still live in one trusted system. But the front door moves to wherever the seller already is: their CRM, their inbox, their meeting notes, and increasingly a general-purpose assistant that knows nothing about enablement until your system hands it the context.
Seismic made that concrete on stage. Its agents and content can now be reached through an MCP server from assistants built by Anthropic, OpenAI and Google, and the demo showed a seller preparing for a meeting, practising it, running it and following it up without once opening Seismic itself. Add the Highspot merger that closed in August and you have a very clear statement of direction from the biggest vendor in the category: the platform is becoming infrastructure. The experience is going wherever the work is.
I think this is the most important shift in enablement since content management moved to the cloud. And I think most of us are not ready for it, for reasons that have nothing to do with technology.
Three camps, same vendor
Here is what struck me most, walking the floor. Almost everyone in that room is a customer of the same vendor. Same roadmap, same demos, same ambition. The outcomes could not have been more different, and they sorted into three camps.
The first camp is still building the basics. No field operations or enablement function to speak of, content that is more of a library than a system, no clear path to agentic workflows. This camp includes some very large, very successful companies. Scale is not the same as readiness.
The second camp is established and personalising. Mature workflows, serious measurement, early experiments in hyper-personalised guidance: the right nudge to the right seller at the right time. This is where most established enablement teams sit. It is good, hard-won work. It is also, if we're honest, still the middle of the pack.
The third camp has one front door. A single seller entry point that joins CRM, meeting preparation, in-call coaching and follow-up, with enablement flowing through it rather than sitting next to it. IBM and Oracle were among the companies showing this, and what they showed wasn't a demo of a product. It was a redesigned job.
Same tools. Different outcomes. The vendor sells the tools; only you can build the third camp.
My admiration, and what sits behind it
I want to say plainly that I admire the leaders in that third camp, and not because they bought earlier or bigger.
What they did was harder. They decided that the seller's day was the unit of design, not the enablement platform. They put a product manager's mindset on their own function and asked what it would take for a seller to never have to go looking. They treated trust, permissions and data quality as the first workstream, because an agent that confidently serves the wrong deck to the wrong seller destroys adoption faster than any portal ever did. And they accepted that the enablement team's job changes: less building the destination, more governing the flow.
Those are organisational decisions, taken by people who were willing to be uncomfortable for a while. The technology followed.
The numbers say the same thing
Gartner expects ten AI agents for every seller by 2028, and fewer than forty percent of sellers to say those agents improved their productivity. McKinsey finds that eighty percent of companies feel more productive with AI, thirty-seven percent see an impact on the bottom line, and six percent are genuine high performers. The thing the six percent do differently is unglamorous: about three quarters of them redesigned the workflow, against about a quarter of everyone else.
BCG puts it as a rule of thumb I've started quoting in every meeting. Ten percent of the value of AI is in the algorithms, twenty percent in the technology and data, seventy percent in people and process.
Headless is the ten and the twenty arriving on schedule. The seventy is us.
Why the next two years matter more than the last ten
When the front door was yours, a slow enablement team cost you adoption. When the front door is an assistant any seller can open, a slow enablement team costs you the seller's attention, and attention does not come back.
Think about what headless does to volume. Every team with a message for the field can now reach a seller personally, in the flow of work, at any hour. Today that is a signal. Without a rule about who can ask, what qualifies and who says yes, next quarter it is noise, and the channel our sellers open first becomes the one they mute. The teams that win the next two years will treat attention as a budget and govern it like one.
It also changes what we measure. Portal logins and course completions were always a proxy. In a headless world they aren't even that. What matters is whether the guidance reached the conversation and whether the conversation went better, which means our evidence has to come from call signals, pipeline behaviour and outcomes, not from our own dashboards.
And it changes who we are for. If agents produce the signal and track the outcome, the human half of the loop, the judgement, the conversation and the follow-through, is where enablement lives now. That was always the part that mattered. Headless just removes the excuses for spending our time anywhere else.
What I'm taking home
Three things, none of them a product.
Design from the seller's day backwards. Map where our sellers actually spend their hours and make sure trusted guidance can reach every one of those places before we build another destination.
Write the governance rule before we need it. Who can ask for a seller's attention, what qualifies, what the default channel is, and who says no. A rule written now is a habit; a rule written after the noise starts is a cleanup.
Baseline the human measures. Conversation quality, time to productivity, win rate by behaviour. If we can't show that practice changed outcomes, we have no business asking for a front door.
Our sellers were already practising. We gave it a home. The lesson of Shift is that the home is about to stop being a place, and the job of enablement is about to get a lot more honest about what it was always for.
---
Beth Potter and I spoke at Seismic Shift 2026 on how AI role play turns enablement into repeatable sales practice. The preview is here. Sources: Seismic Shift 2026 announcements (October 2026); Permira on the Seismic–Highspot merger (August 2026); Gartner (July 2026); McKinsey, The State of AI (August 2026); BCG, the 10-20-70 rule.