Nobody owns the number: why AI plans fail

A company decides it needs an AI plan. It pays for one and gets a deck. Then nobody stays to build it.
Six months later the plan is partly built, by different people. The number the deck promised to move has not moved. Nobody can say why, because nobody was watching it.
This is not bad work. Every party did their job. The chain has no one holding the end of it.
Key points in 30 seconds
- Three hands, no owner. A deck, a vendor and an integrator each finish their task. The business result belongs to none of them.
- AI makes it worse. Plans go old fast, the hard work starts after launch, and people must change how they work.
- The fix is one owner. One named person is responsible for the business number, from plan to build to hand-over.
- Ask five questions before you buy. Use the checklist below.
How does an AI plan lose its owner?
An AI project in a small or mid-sized company usually passes through three sets of hands. Tap each one.
A strategy firm or an internal working group
Looks at your business from the outside in. Talks to people, reviews processes, checks the market, and writes down where AI could help.
- Knows
- Why a workflow matters.
- Does not know
- How the tool really behaves.
The job ends when the deck is presented.
Someone who sells a tool that matches a slide
A support bot, a sales assistant or a document platform. Makes the tool work as a product.
- Knows
- The tool.
- Does not know
- Your workflow.
Whether it changes your business is outside the contract.
A development shop or your IT team
Connects the tool to your systems and ships the work to spec. The spec came from the vendor guide and the deck slide. Nobody who wrote them is still there.
- Knows
- Your systems.
- Does not know
- The reason for the project.
The job ends when the integration ships.
Each handoff loses something. The deck knows why, but not how. The vendor knows the tool, but not your work. The integrator knows your systems, but not the reason. The thing that was meant to change (hours, reply time, error rate, cost) belongs to nobody.
Why does AI make the handoff worse?
This chain is old. AI makes it weaker in three ways.
- The plan gets old fast. Models, prices and abilities change every few months. A plan from spring can be wrong by autumn. A deck is a snapshot, so someone must update the plan.
- The hard part is after the build. Normal software works the same on day 300 as on day one. An AI workflow does not. Its inputs change, its model is updated, and it can get quietly worse with no error. Someone must check the output and fix it. That work starts after the integrator leaves.
- People must change how they work. The support team reviews drafts instead of writing replies. Finance approves exceptions instead of checking every line. If nobody owns this change (training, who decides what, a new idea of a good day's work), people avoid the tool. It sits unused while the licence renews.
None of these three is anyone's job in the chain. They are exactly the owner's jobs.
What does it mean to own the number?
One named person is responsible for the business result, not for a deliverable along the way. In practice that person does five things the chain does not. Tap each step.
Five jobs of the owner
Before anything is bought. Not "deploy a support bot" but "halve the time to first reply on routine tickets without lowering satisfaction". A deliverable can be finished while the number stays flat. A number cannot.
The tool follows the job, not the other way round. Sometimes it is an open-source part, sometimes a paid product, sometimes neither.
The person who made the plan is in the standups. When reality disagrees with the slide, the plan changes that week, not at the next review.
Output checks, spend caps, an owner for every agent, and a regular look at whether the number is moving.
Train the people whose work changed. Write down who decides what. Leave the business able to run it alone.
None of this is unusual. A good CTO or head of operations does it already. But most companies with 20 to 200 people do not have that person and cannot pay for one full time. So they buy the three parts separately and hope the handoffs hold.
What is the alternative to three handoffs?
Not a bigger firm that does all three steps. It is one senior person, inside your team, who owns the plan, the build and the hand-over, and who is still there when the number is measured.
That is the idea behind a Forward Deployed CTO. The role sits inside your team: in standups, in planning, in decisions. It writes the plan, builds it with your people, then hands it over. The plan and the build are the same person's work, so nothing is lost in the handoff.
When the question is the whole business, not one product (AI across sales, support, finance and operations), the same seat is a Fractional CAIO.
We describe our way in three words: Embed. Equip. Hand over. The first word matters most here: inside the team, not looking in from outside.
What should you ask before you buy?
Before you commission an AI plan, buy a tool or hire an integrator, check these five questions. They are useful with any partner.
Tick each question that has a clear answer
0 of 5
No clear answers yet. Without them, a plan is only a deck.
A plan with good answers to all five will usually work, whoever writes it. A plan without them is a deck.
Working with us
If this chain sounds familiar, the Forward Deployed CTO page explains how the embedded role works and what it installs. It is a longer read, and it will tell you if the role is not what you need.
Frequently asked questions
Why do AI plans fail in small companies?
Usually not because the plan was wrong or the technology failed, but because nobody owned the result. The plan is written by one party, the tool is sold by another and the integration is done by a third. Each does its part properly, and each hands over to the next. The outcome the business wanted — fewer hours on a task, faster replies, lower cost — belongs to none of them, so nobody is measuring it and nobody changes course when it slips.
What does it mean to own the number?
It means one named person is accountable for the business outcome an AI project was meant to change, not for a deliverable along the way. They agree the number up front, they can see it every week, and they have the authority to change the plan, the tool or the process when it is not moving. Without that person, a project can deliver everything it promised and still change nothing.
Is an embedded CTO or CAIO better than hiring a strategy firm?
They solve different problems. An outside-in review can be useful when you need a fresh view of the market or a one-off decision. It is a poor fit for AI adoption, where the plan changes every few months as models change, and where the hard part is the building and the change in how people work. An embedded owner stays through the plan, the build and the hand-over, so the person who made the promise is the one who has to keep it.