Most CEOs approach AI adoption the way they approach most technology initiatives: delegate it.
Find the right person, give them budget, hold them accountable for results, and wait for the update at the next leadership meeting.
That works for a lot of technology projects. It doesn’t work for this one.
Why this one is different
AI-era revenue transformation is not a technology project with a commercial outcome attached. It is a commercial operating model change that happens to be enabled by technology. That distinction matters enormously, because commercial operating model change requires decisions that cannot be delegated.
What are we willing to change about how we go to market? What are we willing to stop doing? What does success look like and on what timeline? How do we communicate this to a team that is, understandably, nervous about what AI means for their roles?
These are not questions a Head of Revenue Operations can answer with authority. They are not questions a Chief of Staff can own. They require the CEO — not as a sponsor who blesses the programme in a kick-off meeting and disappears, but as an active participant who holds the commercial thread throughout.
The decisions only you can make
The strategic frame is yours. Is this initiative primarily about efficiency — producing the same with less — or capability — doing things the team couldn’t do before? The answer changes everything about how the work gets designed, communicated, and measured. Nobody below you can make that call credibly.
The pace is yours to set. Fast, focused change with visible results in 90 days creates momentum and evidence that compounds. Slow, careful, comprehensive change creates committees, drift, and a programme that’s out of date before it’s finished. Most CEOs say they want the first and create conditions for the second. This is a CEO decision that gets made, often unconsciously, in the first few weeks.
The accountability structure is yours to define. Who is responsible for the new workflows actually being adopted — not introduced, adopted, measured, and enforced as the new standard? If the answer is “the team will figure it out,” the initiative will stall. Every time.
What the CEO’s job actually looks like in practice
It is not running the project. It is not attending every working session. It is not becoming an AI expert — though genuine curiosity about what AI specifically changes in your commercial motion is more useful than most CEOs realise.
It is setting the commercial ambition clearly enough that everyone below it knows what good looks like. It is making the three or four structural decisions that unlock everything else. It is staying close enough to the real data — not the filtered version — to know whether it’s working. And it is naming the resistance when it appears, because it will appear, and the only person with sufficient authority to push through it is you.
Every AI initiative that stalls does so for the same reason: the change required was larger than the organisation was prepared for, and nobody with enough authority decided to push through. That is a CEO failure, not an implementation failure. The programme didn’t run out of ideas. It ran out of courage.
The CEO who gets this right
They treat the commercial operating model as their direct responsibility, not something that happens two levels below them. They stay genuinely curious about what AI changes — not in abstract terms but in the specific terms of their own revenue motion. They measure the right things and ask uncomfortable questions when the numbers don’t move.
And they find someone who will tell them the truth about what’s working and what isn’t — because inside the organisation, the incentives for complete honesty are complicated in ways that don’t serve the CEO’s interests.
That conversation is worth having. Most CEOs aren’t having it yet.
Still here? Good. You might be exactly my kind of client.
