Skip to content

borghei/Claude-Skills / project-management/strategy-frameworks/ansoff-matrix

ansoff-matrix

Verified

Classifies growth bets into the four Ansoff quadrants and checks the investment mix against the company's stage. Use when prioritising growth bets, allocating a growth budget or testing a pitched "adjacent" move.

references/ansoff-matrix-deep.md

View on GitHub
# Ansoff Matrix — Deep Reference

## The 4 quadrants — tactics + examples

### Q1: Market Penetration (existing product × existing market)

**Goal:** sell more of what we have to people we know.

**Tactics:**
- **Increase frequency:** Starbucks rewards program; Netflix daily push
- **Increase basket size:** Amazon "frequently bought together"
- **Take competitor share:** sales win-back campaigns; competitor migrate offers
- **Improve conversion:** funnel optimization (signup, activation, upsell)
- **Pricing optimization:** A/B test tier structures
- **Loyalty + retention:** customer success investments
- **Geographic density:** more stores in same region
- **Improve product** (subtle Q1 — same market, "better" product is still Q1)

**Risk profile:** Lowest. Known product, known buyer.

**Common KPIs:** market share, share of wallet, NRR, frequency, ARPU.

**Examples:**
- Uber expanding from rideshare to UberX everywhere = Q1
- Netflix adding new content for existing subscribers = Q1
- Salesforce launching CRM tier upgrades to existing accounts = Q1
- Stripe adding payment volume from existing customers = Q1

### Q2: Market Development (existing product × new market)

**Goal:** take what works to a new market.

**Tactics:**
- **New geography:** US → Europe; SF → NYC retail
- **New industry vertical:** general SaaS → healthcare vertical
- **New segment:** SMB → mid-market → enterprise
- **New buyer persona:** IT-led sale → business-line sale
- **New use case:** PM tool used for engineering teams too
- **New channel:** direct sales → channel partners
- **Localization:** language + pricing + payment for new market

**Risk profile:** Medium. Product known; market discovery needed.

**Common KPIs:** market penetration in new segment, time-to-first-customer
in new market, ramp curve vs initial market.

**Examples:**
- Uber → UberEats in same cities (same buyer, new use case = Q1 leaning Q3)
- Netflix US → Netflix international expansion = Q2
- Slack SMB → Slack enterprise = Q2 (different motion)
- Stripe online → Stripe in-person retail = Q2 (different channel)

### Q3: Product Development (new product × existing market)

**Goal:** build something new for people we know.

**Tactics:**
- **Adjacent product:** ERP vendor adds HR module
- **Platform extension:** developer platform adds new service
- **Add-on:** main product gets paid add-ons
- **Vertical-specific feature line:** general product → industry-specific bundle
- **Re-build for new context:** desktop → mobile; web → API

**Risk profile:** Medium. Market known; product discovery needed.

**Common KPIs:** attach rate, cross-sell rate, ARPU lift, time-to-adoption.

**Examples:**
- Apple iPhone → Apple Watch (same audience, new product) = Q3
- Amazon Retail → Kindle (same audience, new product) = Q3
- Salesforce Sales Cloud → Service Cloud = Q3
- Notion docs → Notion AI = Q3

### Q4: Diversification (new product × new market)

**Goal:** new thing for new people.

**Types:**
- **Related/adjacent diversification:** shared capability or audience
  (Amazon → AWS; shared infra capability)
- **Concentric diversification:** related but separate product+market
  (Disney → consumer products)
- **Conglomerate diversification:** unrelated
  (1990s conglomerates; mostly out of favor)
- **Horizontal diversification:** similar buyer; different product
  (sometimes; often actually Q3)

**Risk profile:** Highest. Both axes need discovery.

**Common KPIs:** time-to-revenue, capital efficiency, vs other-quadrant alternatives.

**Examples (mixed track record):**
- Amazon → AWS = successful Q4 (shared capability)
- Apple → Apple Car = aborted; Q4 too far from core
- Google → Alphabet bets = mixed; portfolio approach to Q4
- Tesla → Energy = Q4; shared capability (batteries)

## Risk ladder

Risk increases moving from Q1 to Q4:

| Quadrant | Why risky | Failure rate (rough) |
|----------|-----------|----------------------|
| Q1 — Market Penetration | Limited if at all (commodity competition only) | 10% |
| Q2 — Market Development | New market unknowns | 30% |
| Q3 — Product Development | New product unknowns | 35% |
| Q4 — Diversification | Both axes unknown | 50-70% |

Failure rates are illustrative; real numbers depend on execution and adjacency.

## Investment mix by stage

### Early-stage (pre-PMF or just-after)
- Q1: 70-80%
- Q2: 10%
- Q3: 10-20%
- Q4: 0%

Reason: focus or die.

### Growth-stage
- Q1: 50-60%
- Q2: 20-25%
- Q3: 15-20%
- Q4: 0-5%

Reason: deepen + expand on proven base.

### Mature
- Q1: 30-40%
- Q2: 25-30%
- Q3: 25-30%
- Q4: 5-15%

Reason: portfolio approach; reinvest cash from Q1 into other quadrants.

### Declining core
- Q1: 20-30%
- Q2: 20-30%
- Q3: 30-40%
- Q4: 10-20%

Reason: need to replace declining core; higher risk acceptable.

## Misclassification patterns

### Q3 dressed as Q1
"We're adding [completely new product] to our existing customers."

Probably actually Q3 (or Q4 if the customer isn't natural buyer of new product).

Q1 is genuine more-of-the-same: more usage, more conversion, more
geography density, more tier upsell.

### Q2 dressed as Q1
"We're expanding to mid-market with our SMB product."

Different motion = different market = Q2.

### Q4 dressed as Q3 or Q2
"Adjacent" diversification often hides Q4.

Test: would the new initiative succeed/fail independent of the core?
If yes → Q4. If no (shares meaningful capability) → Q3.

### Q1 hidden as Q3
"We're building a new product feature." Often it's just feature
investment in existing product = Q1.

A "new product" needs:
- Distinct value prop
- Distinct success metric
- Often distinct go-to-market
- Capable of being killed without killing the core

## Strategic principles

### Principle 1: Q1 first
Most companies under-invest in Q1. The boring penetration moves
(better onboarding, retention, conversion) often outperform the
exciting expansion moves.

### Principle 2: Earn the right to expand
Don't move to Q2/Q3/Q4 until Q1 is reliably executed. Companies that
expand prematurely spread thin and fail in multiple quadrants.

### Principle 3: Adjacency matters
Closer to core = lower risk. "Adjacent" Q3/Q4 (shared capability, shared
audience) far outperforms unrelated diversification.

### Principle 4: Stage-mix discipline
Refresh your quadrant mix annually. Drifting too high in Q4 = high
failure rate. Drifting too low in Q3/Q2 = stagnation.

### Principle 5: Honest classification
Q4 disguised as Q2 is a failure waiting. Be honest.

## Combining Ansoff with other frameworks

- **Ansoff + Five Forces:** assess industry attractiveness per quadrant
- **Ansoff + SWOT:** which strengths support which quadrant bets?
- **Ansoff + BMC:** new BMC per quadrant (changes more than people think)
- **Ansoff + Lean Canvas:** Q4 needs its own Lean Canvas (it's a new startup)
- **Ansoff + portfolio/RAR:** risk-adjusted return per quadrant initiative

## Common mistakes

- Misclassifying for political reasons (Q4 hidden as Q2 to get approved)
- Over-investment in Q4 to look "innovative"
- Under-investment in Q1 because "boring"
- Static mix; no annual refresh
- Strategy = "all four quadrants" = unfocused
- Diversification without shared capability or audience
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall