Run Your AI Bets Like a VC Portfolio
Sam Gaddis
Sign up for our newsletter to get Runpoint's latest articles, interviews, and more.
Venture capitalists have known something for decades that enterprise leaders are just now figuring out: the best way to find winners is to place a lot of bets and accept that most of them will fail.
This is not how most companies approach AI.
The Enterprise AI Failure Mode
Here's what typically happens when a large organization decides to "do AI":
- A committee is formed
- A strategy is written
- A vendor is selected
- A pilot is scoped (carefully, to minimize risk)
- The pilot runs for six months
- The pilot produces ambiguous results
- A new committee is formed to evaluate the results
- Repeat
By the time the organization has completed one cycle, the technology has moved two generations forward. The pilot was testing yesterday's capabilities against today's problems. The results are meaningless.
This is not a technology problem. It's a portfolio management problem.
The VC Model
A good VC fund operates on a simple principle: invest in many promising opportunities, knowing that most will fail, some will break even, and a few will return 10-100x.
The math works because the winners more than compensate for the losers. A $100M fund that makes 30 investments will see 20 fail, 7 return 1-3x, and 3 return 10x+. Those three winners generate the entire fund's returns.
Apply this to AI initiatives:
| VC Concept | AI Translation | |---|---| | Fund size | Annual AI budget | | Portfolio companies | Individual AI experiments | | Due diligence | Rapid feasibility assessment | | Board seat | Executive sponsor | | Follow-on funding | Scale successful experiments | | Write-off | Kill failed experiments fast |
The Portfolio In Practice
We work with a mid-market PE firm that runs AI experiments across their portfolio companies. Here's their approach:
Quarterly allocation: $200K per quarter across all portfolio companies.
Experiment structure: Each experiment gets $5-15K and 2-4 weeks. No more. If it can't demonstrate value in that window, it's killed.
Success rate target: 20-30%. They explicitly expect 70-80% of experiments to fail. If the success rate is higher, they're not being ambitious enough.
Kill criteria: Clear, pre-defined metrics. "Did this reduce processing time by 40%?" is a kill criterion. "Did stakeholders feel positive about the AI experience?" is not.
Scale criteria: Successful experiments get 5-10x follow-on investment and a dedicated team.
In the last 12 months, they've run 47 experiments. 13 succeeded. Of those 13, 4 have been scaled to production. Those 4 are generating an estimated $3.2M in annual value against a total experimental spend of $800K.
Why Most Companies Can't Do This
The portfolio approach requires three things that most organizations lack:
1. Tolerance for Failure
Most corporate cultures punish failure. If you run 10 AI experiments and 7 fail, you get called into a meeting about your 70% failure rate. Nobody talks about the 3 that worked.
This has to change at the leadership level. If your CEO doesn't explicitly celebrate failed experiments (because they generated learning), your portfolio approach will collapse into risk-averse incrementalism.
2. Speed of Execution
You can't run a portfolio if each experiment takes six months. The math doesn't work. You need to be able to spin up experiments in days, evaluate them in weeks, and kill or scale them in a single decision meeting.
This is where Operator Engineers (see page 12) become critical. They can go from idea to working prototype fast enough to make the portfolio model viable.
3. Honest Evaluation
The experiments that "kind of worked" are the most dangerous. They consume resources, generate hope, and never deliver. You need evaluation criteria that are binary: it hit the target or it didn't.
"The model achieved 73% accuracy" sounds impressive until you realize that 73% accuracy in a financial reconciliation process means 27% of your transactions are wrong. That's not a success. That's a lawsuit.
Building Your Portfolio
If you're starting from zero, here's the playbook:
Month 1: Inventory. Catalog every manual, repetitive, or data-heavy process in your organization. Score them on two axes: business impact and technical feasibility. You'll typically find 30-50 candidates.
Month 2: First batch. Pick 5-8 experiments from the top of your list. Allocate budget and assign an Operator Engineer (or a team with equivalent capability) to each one. Set 2-week checkpoints.
Month 3: Evaluate and iterate. Kill the failures. Double down on the wins. Start the next batch. Publish results internally—including the failures.
Quarter 2 onwards: Scale what works. Successful experiments get productionized. Failed experiments get documented (what didn't work and why). New experiments start every two weeks.
The Compound Effect
The real power of the portfolio approach isn't any single experiment. It's the organizational muscle you build by running many experiments fast.
After six months, your team has developed:
- Pattern recognition for which types of AI applications work in your specific context
- Technical infrastructure (APIs, data pipelines, monitoring) that makes each subsequent experiment cheaper and faster
- Cultural comfort with experimentation and failure
- A track record of delivered value that funds the next round of experiments
This compounds. The organizations that started running AI portfolios 12 months ago aren't just ahead—they're accelerating away from the ones still writing strategy decks.
The only question is whether you start now or keep committee-ing your way to irrelevance.
Get the magazine delivered to your door.
Issue 01: Technology Strategy for the Agentic Era. $12 + free US shipping.