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/growth-strategy-patterns.md

View on GitHub
# Ansoff — Growth Strategy Patterns

Common patterns observed across successful (and failed) growth strategies.

## Pattern 1: The Q1 default that wins
"We thought we needed to expand, but turned out Q1 was the answer."

Most common in growth-stage companies. Symptoms:
- Customer retention < 90%
- Sales win rate < 25%
- ARPU well below ceiling
- Geographic / segment density below saturation

**Move:** Pour 70% into Q1 for 2-3 quarters. Reassess after improvement.

**Example:** Many SaaS startups think they need to enter new verticals
when they actually have churn problems in their first vertical.

## Pattern 2: Q2 international expansion
Existing product → new geography.

**Costs:**
- Localization (product, marketing, support)
- Legal entity / regulatory
- Local hiring (sales, CS)
- Cultural fit (sometimes the model doesn't translate)

**Common failures:**
- Pricing not localized
- Sales motion that worked in US doesn't work in EU/APAC
- Channel doesn't exist in new market
- Compliance unexpectedly heavy

**Successful playbook:**
1. Pilot in 1 country (closest cultural/language to home)
2. Hire 1 local lead + 1-2 ICs
3. Localize the bare minimum (pricing, language, currency, basic legal)
4. 6-month checkpoint; refine model
5. Scale to 2-3 more countries

## Pattern 3: Q2 segment expansion (SMB → ENT)
"We're going up-market."

**Costs:**
- Different sales motion (PLG → enterprise sales)
- New compliance posture (SOC 2, ISO 27001)
- Enterprise features (SSO, audit logs, role-based access)
- Different ICP
- Longer sales cycles → cash burn

**Common failures:**
- Don't adjust sales comp model
- Underestimate enterprise procurement timeline
- Try to serve both SMB and ENT with one product roadmap (impossible)
- Pricing not engineered for enterprise

**Successful playbook:**
1. Hire enterprise AE + SE
2. Separate enterprise tier (price, features, support)
3. Get 3-5 lighthouse enterprise customers
4. Build the enterprise PLG → sales transition flow
5. Decide: do we keep SMB? (often the answer is yes, with separate motion)

## Pattern 4: Q3 platform extension
"We're adding a module."

**Costs:**
- Engineering on new product
- Sales/marketing to drive adoption
- Risk of cannibalizing existing
- Brand confusion ("what does this company do?")

**Common failures:**
- New module isn't actually wanted by existing customers (built in vacuum)
- Stretches sales motion (different buyer in same account)
- Same engineers thinly spread on both
- Pricing power eroded (bundled discount)

**Successful playbook:**
1. Validate demand with 10+ customer conversations
2. Sell pilot to 5-10 customers BEFORE building
3. Dedicated team (not shared)
4. Clear pricing (add-on, not free bundle)
5. Independent metrics (adoption, attach rate, revenue)

## Pattern 5: Q4 disguised as Q3
"It's an adjacent product for our existing customers."

Often actually Q4 because:
- The "existing customers" don't really buy the new product (different DM)
- Capability isn't actually shared (engineering different)
- Sales motion different

**Test:**
- If the new product needed its own go-to-market team, it's likely Q4
- If existing customers' buying committee isn't the buyer, it's Q4
- If shared capability is "we're good at startups," it's Q4

**Treat as Q4:**
- Apply Q4 risk assessment
- Separate funding decision (might not pass)
- Separate team if approved
- Distinct success criteria

## Pattern 6: Q4 acquisition
"We're buying this company to enter X market."

**Risk axes:**
- Integration risk
- Cultural fit
- Product technical debt absorbed
- Customer retention through transition
- Brand/positioning consistency

**Common failures:**
- Synergies don't materialize
- Acquired culture clashes
- Customers churn during integration
- Founders / key talent leave 12-18 months later
- Combined entity worse than sum of parts

**Successful playbook:**
1. Clear strategic rationale (not "good price")
2. Pre-LOI alignment with founders on cultural fit + future
3. Detailed integration plan + day-1, day-30, day-90, day-365 milestones
4. Customer comms + retention focus
5. Talent retention packages
6. 18-month integration commitment

## Pattern 7: Q4 internal moonshot
"We're starting an internal new business."

Examples: Google X, Amazon Devices, Meta Reality Labs, X.AI internal projects.

**Risk axes:**
- Resource competition with core
- Culture mismatch (startup feel inside big co)
- Different metrics; different leadership profile needed
- Risk of being killed in a downturn

**Common failures:**
- Treated as project, not company
- Killed before validation
- Founders / leads frustrated; leave to start outside
- Synergies overstated

**Successful playbook:**
1. Separate legal entity or division
2. Different leadership (entrepreneurial profile)
3. Different success metrics (not core KPIs)
4. Multi-year capital commitment (3+ years)
5. Clear independence + handoff rules
6. Honest about acquired-skill gaps; hire externally

## Stage-by-stage growth mix

### Pre-PMF
- Q1 100% (find PMF first)

### Just after PMF
- Q1 80% (pour fuel)
- Q2 10% (start exploring next market)
- Q3 10% (start exploring product extension)
- Q4 0%

### Growth stage
- Q1 50%
- Q2 25%
- Q3 20%
- Q4 5%

### Mature
- Q1 35%
- Q2 25%
- Q3 25%
- Q4 15%

### Pre-decline
- Q1 25% (extract cash)
- Q2 25% (extend life)
- Q3 30% (replace product line)
- Q4 20% (find next business)

## Common cross-pattern mistakes

- **All Q1.** No future-proofing.
- **All Q4.** Bet-the-company quarterly.
- **Q1 starved.** Core erodes while building "innovations."
- **Q3 with shared team.** Both products mediocre.
- **Q4 without shared capability.** Random walk.
- **"Adjacency" as cover.** Q4 dressed as Q2/Q3.
- **No mix discipline.** Drift over time.
- **No measurement per quadrant.** Can't tell what's working.

## Refresh cadence

- Annual: full quadrant mix review
- Quarterly: per-initiative checkpoint
- On material event: M&A, market shift, competitor exit
- Don't refresh more often (oscillation = no strategy)
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