Pilots without owners die
Lucas Val Eggers · Partner, Foundry IX · 2 min read
Lucas Val EggersPartner, Foundry IXMost AI pilots die a quiet death. Not because the technology didn't work, but because nobody owned them once the demo was over.
The pattern repeats across organisations: a team builds something promising, everyone nods at the showcase, and three months later the project is gone. Nobody decided to kill it. There was simply no one with the mandate to take it further.
How a pilot dies
It rarely dies in a meeting. The demo gets applause, someone says 'we should roll this out', and the room moves on. But the rollout never gets a budget line. The developer who built it goes back to their day job. The champion changes roles. Six months later, the login has expired and nobody notices.
The most expensive part isn't the wasted pilot. It's the conclusion the organisation quietly draws: 'we tried AI, and it didn't stick.' That conclusion is wrong. Nothing was tried, only demonstrated. But it hardens into culture and makes the next attempt harder.
It's a leadership problem, not a technical one
A pilot without an owner, a budget and a deadline isn't an initiative. It's a postponement.
The technology is rarely the bottleneck. What's missing is the decision infrastructure around it: who owns the outcome, what it may cost, and when it must prove itself.
What successful organisations do from day one
- Appoint one owner with the mandate to make decisions.
- Set a budget that reaches past the demo and into operations.
- Set a deadline and a measurable KPI that decides life or death.
- Treat the decision with the same discipline as any other strategic investment.
Ninety days is enough
The discipline doesn't require a transformation programme. It requires treating one initiative the way you'd treat any other investment: a named owner with real mandate, a budget that covers operations rather than just the build, and a date on which the KPI decides whether it scales or stops. Ninety days is enough to know, if someone owns the answer.
The difference between a pilot and a change isn't the code. It's whether someone has been made responsible for getting it into operation. And keeping it there.
What we think. What we build.
StrategyAI is moving competitive advantage now
4 min readThe question is not whether AI hits your market. It's who turns it into operations first.
GovernanceThe EU AI Act holds leadership accountable. Not your vendor
2 min readResponsibility for classifying, governing and understanding AI systems sits with the organisation itself.