borghei/Claude-Skills / project-management/strategy-frameworks/porters-five-forces
porters-five-forces
VerifiedRates the five competitive forces of one precisely defined industry with evidence and turns the dominant forces into moves. Use when weighing market entry, diagnosing margin pressure or auditing industry positioning.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| assets/five_forces_template.md | markdown | 3.0 KB |
| assets/sample_forces.json | config | 2.0 KB |
| assets/sample_forces_flawed.json | config | 393 B |
| references/five-forces-and-strategy.md | markdown | 6.9 KB |
| references/five-forces-deep.md | markdown | 8.6 KB |
| scripts/five_forces_scorer.py | script | 8.8 KB |
references/five-forces-and-strategy.md
View on GitHub# Five Forces → Strategy Translation
Strategy doesn't fall out of the analysis automatically. This reference
maps each force to candidate strategic moves.
## 1. Threat of new entrants HIGH → build barriers
| Barrier to build | How |
|------------------|-----|
| **Brand** | Sustained marketing + reputation; lighthouse customers; analyst positioning |
| **Scale** | Achieve cost advantages competitors can't match (Amazon-style infra) |
| **Network effects** | Two-sided platform design; user-to-user value; viral loops |
| **Switching cost** | Deep integration; proprietary data; workflow lock-in (sticky onboarding) |
| **Regulatory** | Become deeply compliant; help shape the rules; certification moats |
| **IP** | Patents on critical processes; trade secrets; copyright; trademarks |
| **Distribution** | Lock up channels; partnerships; exclusive arrangements |
| **Talent moat** | Hire the top of a specialized field |
## 2. Supplier power HIGH → reduce dependency
| Move | When |
|------|------|
| **Diversify suppliers** | When one supplier is critical (single-vendor cloud, single chip) |
| **Standardize on commodity inputs** | When you can substitute without quality loss |
| **Backward integrate** | When supplier is extracting too much margin and you have scale to justify |
| **Long-term contracts** | When you can lock in pricing before further consolidation |
| **Help suppliers' competitors** | Promote a #2 vendor to compete with #1 |
| **Become the dominant customer** | If you can grow to where you matter |
| **Open source the layer** | If supplier is software, fund open alternative |
### Example
- OpenAI / Anthropic concentration on foundation models → strategy:
multi-vendor adapter; open-source local models for low-stakes use cases;
fine-tune to reduce switching cost; multi-cloud deployment.
## 3. Buyer power HIGH → reduce dependency on each
| Move | When |
|------|------|
| **Diversify customer base** | When customer concentration > 20% in one buyer |
| **Differentiate** | Reduce buyers' ability to commoditize you |
| **Raise switching costs** | Deep integrations, custom workflows, data lock-in |
| **Improve information asymmetry** | Charge for transparency they need |
| **Forward integrate** | Serve customer's customer; bypass intermediary |
| **Vertical specialization** | Become irreplaceable in specific industries |
### Example
- Enterprise SaaS with 2-3 mega-customers extracting heavy discounts →
strategy: targeted mid-market expansion; differentiation on vertical
features; multi-year contracts with switching cost; per-tier pricing
with upfront commits.
## 4. Threat of substitutes HIGH → defend value prop
| Move | When |
|------|------|
| **Reframe value** | What can we deliver substitute can't? |
| **Bundle adjacent value** | Move from product → solution |
| **Lower switching cost from us to us** | Match substitute on the dimension they win on |
| **Acquire substitute** | If you have capital and they have IP |
| **Build the substitute yourself** | Cannibalize before they do (digital cameras, e.g.) |
| **Differentiate emotionally** | Brand, identity, community (e.g., Apple vs Android) |
### Example
- Movie theaters threatened by streaming → strategy: premium experience
(IMAX, recliners, food), exclusive windows, social experience
positioning. Some succeeded; many didn't.
## 5. Competitive rivalry HIGH → exit, niche, or consolidate
| Move | When |
|------|------|
| **Differentiate aggressively** | Standout positioning to escape commodity competition |
| **Niche down** | Pick a specific segment / vertical to dominate |
| **Acquire competitors** | If you have scale to consolidate |
| **Exit segments** | Cede unprofitable subsegments |
| **Strategic restraint** | Don't match every move; preserve margin |
| **Build switching cost** | Make customer retention harder for others to steal |
| **Vertical integrate** | Own more of the value chain |
### Example
- Airlines (chronically high rivalry) → strategy: low-cost-carrier model
(Southwest, Ryanair); premium positioning (Singapore, Emirates);
alliance + frequent-flyer lock-in.
## 6. The 4-quadrant strategy guide
Combine force intensity to identify strategy patterns:
| Industry pattern | Strategy |
|-------------------|----------|
| Low forces (attractive) | Defend + capture share before forces intensify |
| High new entrant + low rivalry | Build barriers fast |
| High buyer power + low rivalry | Differentiate + segment |
| High rivalry + low buyer power | Consolidate; vertical integration |
| All forces high | Exit, or find unique sub-niche |
| Forces shifting | Reposition early; first-mover advantage |
## 7. Strategy by company stage
### Startup (entering)
- Pick an industry with at least 1-2 favorable forces
- Build initial moat (network effect, switching cost, brand)
- Don't enter "all forces high" markets — most startups die there
### Growth-stage
- Reinforce the moat that worked
- Watch for force shifts (consolidation, new entrants)
- Consider expansion into adjacent industries
### Mature
- Defend moats; M&A to consolidate
- Identify substitute risk; acquire or build
- Selectively exit high-rivalry segments
### Declining
- Harvest cash flow; exit responsibly
- Don't reinvest in unfavorable industries
## 8. Translating Five Forces to OKRs
Five Forces analysis should drive specific OKRs:
| Force diagnosis | OKR theme |
|------------------|-----------|
| High buyer power | "Reduce top-10 customer revenue concentration from X to Y" |
| High rivalry | "Increase win rate vs Competitor Z from X to Y in segment A" |
| High substitute threat | "Launch [substitute-blocking feature] by Q3" |
| High new entrant threat | "Achieve [moat metric: certifications, integrations, etc.]" |
| High supplier power | "Reduce dependency on [supplier] from X% to Y%" |
If your Five Forces analysis produces no OKR delta, it was decorative.
## 9. Sustaining vs disruptive shifts
Force shifts come in two flavors:
**Sustaining** — incumbent can respond:
- New competitor in known segment
- Buyer demanding lower prices in known way
- Existing substitute getting cheaper
**Disruptive** (Christensen) — incumbent often can't respond:
- Substitute serving overshot customers at lower price (mini-mills vs integrated steel)
- New competitor with structurally different cost model (cloud vs on-prem)
- New buyer segment with different needs (low-end disruption)
Five Forces sees both. Strategy differs:
- Sustaining: incremental response
- Disruptive: structural response (often = separate org / spin-out)
## 10. Common strategy errors after Five Forces
- **Analyzing without acting.** Five Forces becomes a deck, not decisions.
- **Generic responses.** "Differentiate more" without specifics.
- **Picking too many strategic moves.** Pick 2-3.
- **Strategy without resources.** Move chosen; no headcount/$ allocated.
- **No measurement.** Strategy progress not tracked.
- **Static — done once.** Refresh annually + on major industry events.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |