Why the platforms your company bought are working exactly as designed, and why adoption still stalls one person at a time. A kickoff hour is a talk, not a workshop. It can change how a room thinks about using these tools. It cannot build anything, and anyone promising otherwise is selling you a demonstration.
Scan the published 2027 kickoff themes and the pattern is immediate. Assisted not automated. Human first, AI ready. The human edge. The instinct behind all of them is sound, because it is the real change in the work.
The common complaint about the resulting sessions, in the same planning guides that recommend the themes, is that they stay abstract. A talk about what AI will mean for the profession, a demonstration of a platform, a slide about the future of the role. Interesting for an hour, and then the quarter starts.
A keynote cannot fix that by becoming a workshop. It fixes it by being about the right thing.
It is worth being precise here, because the usual version of this argument is unfair to the tools.
The platforms companies are buying do the job they were built for. Point of view tracking, stakeholder updates, response and proposal drafting, utilisation and capacity, pipeline hygiene. That layer works, and in most organisations it is the only thing standing between the team and a spreadsheet.
What they do not do is address one engineer’s own gaps, and that is a question of what they were built to do, not a failure. Nobody built a stakeholder update tool to fix somebody’s discovery. It was never the brief.
The engineer who builds something for themselves on top of your platform is the engineer who actually logs into your platform.
Which makes the individual layer additive rather than competitive. Adoption is the hardest problem every vendor in this category has, and the thing that moves it is a person having a reason of their own to open the thing.
An organisation buys at the organisation level, which is correct, because that is where the budget and the standards live. Then adoption is measured one person at a time, which is a different unit entirely.
A tool that is excellent at the company’s problem and indifferent to mine gets opened when somebody asks me to open it. A tool shaped around how I actually work gets opened because it saves me something today. The gap between those two sentences is most of the adoption curve.
Companies with a genuine sales play system grow revenue at 2.2 times the rate of those without one. Only 21 percent of the companies that say they run one realise the full value. Source: Bain and Company, B2B Growth Divide: Commercial Excellence Agenda 2025, based on roughly 1,300 senior commercial executives.
Buying the system and realising it are different events, separated by whether individual people changed what they do on a Tuesday. AI has not altered that, it has raised the stakes.
The room leaves understanding why the tools they have been given are not being used, without blaming the tools or the people. That is a more useful hour than it sounds, because the usual explanations are that the platform is bad or the team is resistant, and neither is true.
It also covers what has to happen next for any of it to stick: that the thing somebody uses daily is almost always the thing shaped around their own work, and what that implies for how a company rolls out anything.
A main stage keynote. Thirty to sixty minutes, mixed room of sellers, engineers and leadership. Nothing for anyone to install, prepare or bring. It sits comfortably against an AI readiness theme without being a product demonstration.
A workshop. Nobody is building a working tool in a kickoff slot, and a session that promises it will deliver a demonstration instead. Building something of your own takes repetition against real deals, which is a different engagement entirely.
In the training engagement this is not a separate session bolted on at the end. It runs through the whole thing. At the end of every module, each person extends their own AI coach with the capability they just learned, tuned to how they work, on their own account. They finish the programme owning it and they keep changing it as their process changes.
That is why it cannot be compressed into a kickoff hour. The coach is worth something because it was built against real deals over months, by the person who uses it.
It is the first question a good enablement lead asks, and the keynote answers it rather than avoiding it.
The guardrails get set collectively, before anybody builds anything. What varies is the fit, not the method. Two engineers can end up with differently shaped tools that ask the same questions in the same order, and that is a healthier outcome than thirty people issued identical tools that four of them open.
The benchmark is blunt about which risk is real. Under two percent of sales engineers say their team already runs deals the same way. Inconsistency is the starting condition, not something this introduces.
Because a platform bought at the organisation level is built to solve organisation level problems, and adoption is measured one person at a time. That is a question of what the platform was built to do rather than a product failure.
No. An hour is enough to change how a room thinks about adoption, and not enough to build anything that works. Building a coach of your own happens over a programme, not in a kickoff slot.
Thirty minutes on what your team already has, what the hour is supposed to produce, and whether this talk or one of the others fits the room better. If your platform vendor is better placed to run the session, I will say so.