Strategic Bets Framework
A Strategic Bets Framework treats company strategy as a portfolio of explicit, time-boxed bets — each one is a hypothesis with a defined hypothesis, capital allocation, success criteria, and kill criteria. Instead of 'we're going to grow ARR 40%,' the strategy is: 'We're making 3 bets — Bet A: enterprise upmarket (12 months, $8M, succeeds if we land 5 logos > $250K); Bet B: AI features (9 months, $4M, succeeds if 30% of users adopt within 60 days); Bet C: international (18 months, $6M, succeeds if EMEA hits $10M ARR).' Each bet has a sponsor, a kill date, and a written 'we will stop if' clause. The framework forces leadership to admit they're guessing, which is the only honest place to start.
The Trap
The trap is calling everything a strategic bet. If the company has 14 'bets' running simultaneously, none of them are actually bets — they're a roadmap. A real bet has scarcity: capital, attention, and the company's narrative are concentrated. Companies that 'bet on AI, mobile, enterprise, SMB, international, and partnerships' simultaneously are placing 0 bets. The other trap: never killing a bet. If your kill criteria triggers and you keep going, you've converted strategy into religion.
What to Do
Limit yourself to 3-5 active bets per year. Write each on a one-page bet card with: Hypothesis, Sponsor, Capital, Success Criteria (measurable), Kill Criteria (measurable), Review Date. Allocate capital and headcount EXPLICITLY — if a bet doesn't have a budget line and named people, it's not a bet, it's a wish. Hold a quarterly bet review where each sponsor reports against the criteria. If kill criteria triggered, kill it — without a board fight.
Formula
In Practice
Microsoft under Satya Nadella runs a clear bets portfolio. When he took over in 2014, he killed Windows Phone (kill criteria triggered: < 3% market share), de-emphasized Windows as the strategic center, and made three explicit bets: Cloud (Azure), Productivity (Office 365 + Teams), and AI (eventually OpenAI partnership). Each bet had its own org, its own P&L, and its own success criteria. Azure had to hit $20B run rate. The framework let Microsoft go from a $300B market cap in 2014 to over $3T by 2024 because the bets were named, funded, and held accountable.
Pro Tips
- 01
The CEO must publicly defend each bet at the kickoff and publicly accept responsibility if it fails. Bets without an executive who's willing to be wrong on the record become orphaned mid-year.
- 02
Pre-mortem every bet: assume it's 12 months later and the bet failed — write down WHY. The most common failure modes (couldn't hire the team, market moved faster than us, technical assumption was wrong) can usually be designed against in advance.
- 03
Reserve 60-70% of capital for a small number of large bets, 20-30% for adjacent experiments, and 10% for true wildcards. The reverse — many small bets, no large bets — is the death by 1,000 paper cuts that kills mid-stage companies.
Myth vs Reality
Myth
“Strategic bets are mainly about big M&A or new product lines.”
Reality
Some of the highest-ROI bets are operational: 'we will rebuild our checkout' or 'we will move from on-prem to cloud.' What makes something a bet isn't the topic — it's the binary commitment, capital allocation, and named kill criteria. A boring infrastructure bet that hits is more valuable than a sexy product bet that misses.
Myth
“If a bet is failing, you should pivot it rather than kill it.”
Reality
Pivoting a failed bet is usually a face-saving rebrand of 'we won't admit this didn't work.' Real pivots are rare. Far more common: a bet hits its kill criteria, the team rewrites the success criteria to make it look like the bet is on track, and the company burns another 12 months on a bet that should have been killed.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Scenario Challenge
You're the CEO of a $80M ARR SaaS company. Last year you made a 'big bet' on launching an SMB self-serve product. Capital allocated: $5M. Kill criteria: 1,000 paying SMB customers within 12 months. It's now month 11. You have 240 SMB customers. Your VP of Product proposes 'redefining' the bet to focus on PLG-led mid-market expansion (not SMB), arguing the underlying motion is sound but the segment was wrong.
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Active Strategic Bets per Year
Mid-to-late-stage companies running an explicit bets frameworkFocused
3-5 bets
Acceptable
6-8 bets
Spread Too Thin
9-15 bets
No Strategy (Roadmap)
> 15 bets
Source: Hamilton Helmer 7 Powers; Patrick Pichette (former Google CFO) on capital allocation
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Microsoft
2014-2024 (Nadella era)
When Satya Nadella became CEO in February 2014, Microsoft's market cap was around $300B and the company was widely considered to have missed mobile and lost its way. Nadella made three explicit strategic bets: (1) Cloud (Azure), (2) Productivity-as-a-service (Office 365, Teams), (3) AI (eventually anchored by the OpenAI partnership). He killed Windows Phone — kill criteria triggered when Lumia couldn't crack 3% global share. He restructured the company so each bet had its own org, its own P&L, and its own success criteria. Azure went from a $4B run rate in 2014 to over $80B by 2024.
Market Cap (2014)
~$300B
Market Cap (2024)
~$3.1T
Number of named strategic bets
3
Bets killed (Windows Phone)
1 major
The 10x stock performance came from concentration, not diversification. Nadella's discipline to NAME 3 bets and kill the strategic distractions (phones, Bing as a standalone bet) is what made the framework work. A list of 12 'priorities' would have produced the previous decade.
Amazon (AWS)
2003-2010
AWS started as an internal infrastructure project that Jeff Bezos converted into an explicit strategic bet around 2003. The bet had clear hypotheses: (1) compute and storage will become utilities; (2) Amazon's retail-scale infrastructure was a unique starting point; (3) developers would adopt before enterprises. Bezos personally championed it through years of skepticism — Wall Street hated AWS because it depressed margins. Andy Jassy got named sponsor. The bet's success criteria were product adoption metrics, not revenue, for the first 5 years. By 2010, AWS was clearly winning. By 2024, AWS generated over $100B in annual revenue.
Bet origin
~2003 internal
Years before profitability proof
~5-7
Revenue (2024)
$100B+
Operating margin (2024)
~30%
Real strategic bets often need 5-7 years and a CEO willing to absorb public market pressure. AWS would have been killed at 3 different points by a CFO-driven culture. Bezos's 'Day 1' framing was, in essence, a defense of long-duration bets against short-term metrics.
Hypothetical: $200M ARR vertical SaaS company
FY 2023-2024
A $200M ARR vertical SaaS company entered 2023 with 11 'strategic initiatives.' By Q3, the CEO realized none were resourced enough to win. He restructured into 3 bets: enterprise upmarket ($6M, 18 months), platform API ($4M, 12 months), and international expansion ($3M, 24 months). The other 8 initiatives moved to roadmap or were killed. ARR growth re-accelerated from 18% to 31% the following year because teams stopped context-switching across 11 priorities.
Initiatives (before)
11
Bets (after)
3
ARR Growth (before)
18%
ARR Growth (after)
31%
The largest unlock for a mid-stage company is often subtraction. Going from 11 'priorities' to 3 named bets felt like losing optionality but actually concentrated the org's attention enough to win.
Decision scenario
The Bet That Wouldn't Die
You're the CEO of a 600-person company. 14 months ago, you made a strategic bet on a new vertical (legal-tech) — $8M capital, kill criteria of $5M ARR by month 18. You're at month 14 with $1.2M ARR and a slowing pipeline. The Bet Sponsor (your VP of Vertical Strategy) is requesting a budget extension and a revised target of $5M ARR by month 30.
Bet Capital Allocated
$8M
Capital Spent to Date
$6.5M
Original Kill Criteria
$5M ARR by month 18
Current ARR
$1.2M
Sponsor's Request
+$4M, target moved to month 30
Decision 1
Your VP argues that the legal-tech market is real but the sales cycle was longer than expected. Your CFO wants the bet killed immediately to redirect capital to a new bet on AI features. Your board chair is neutral but says 'whatever you do, don't half-measure it.'
Grant the extension and the additional $4M. The sponsor has institutional knowledge and walking away wastes the $6.5M sunk cost.Reveal
Kill the bet on the original schedule. Reassign the team. Run a written post-mortem. Redirect $3M of the remaining capital to the AI bet. Keep $1M as a small follow-on if any of the legal-tech logos warrant retention work.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Strategic Bets Framework into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Strategic Bets Framework into a live operating decision.
Use Strategic Bets Framework as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.