Purpose
Surface the specific digital forces that could erode a business model, score each threat by likelihood and time horizon, and map a strategic response — so leadership stops debating whether disruption is coming and starts deciding where to defend, where to attack, and what to ignore. Replaces vague "we need to be more digital" anxiety with a ranked, defensible threat map.
When to Use
Invoke this skill when the user asks to:
- Assess how digital disruption could threaten their industry or business model
- Identify which new entrants, platforms, or AI capabilities pose the biggest risk
- Build the threat case to justify a transformation investment or board discussion
- Prioritize where disruption will hit first versus what is overhyped
- Pressure-test whether their current strategy survives a platform or AI shift
- Understand changing customer behavior and what it means for their model
Inputs Required
Before starting, collect:
- Industry/sector: The specific market the business operates in
- Business model: How the company creates and captures value — what they sell, to whom, how they make money
- Revenue structure: Primary revenue streams and rough share of each
- Current digital maturity: Where they are today (legacy/transitioning/digital-native)
- Key assets/moats: What currently protects the business (scale, data, distribution, brand, regulation, switching costs)
- Known threats: Any disruptors or shifts already on their radar
- Time horizon of concern: Are they planning 18 months, 3 years, or 5+ years out?
If digital maturity or moats are not provided, infer them from the business model and note the assumption explicitly.
Instructions
Step 1: Baseline the Value Chain and Moats
Decompose the business model into its value-creation steps (e.g., acquisition → production → distribution → service → monetization). For each step, identify what currently makes it defensible. Disruption almost always attacks a specific link — name the links before naming the threats.
Step 2: Scan the Four Disruption Vectors
For each vector, identify 2–4 concrete threats specific to this business — not generic industry trends.
Vector 1 — New Entrants & Business Model Disruption Players attacking with a structurally different model: unbundlers, low-end disruptors, aggregators, vertically integrated digital-natives, marketplace intermediaries.
- Ask: Who can serve our most profitable customers more cheaply, or our least profitable customers "good enough"?
- Pattern check: unbundling, low-end disruption, jobs-to-be-done substitution
Vector 2 — Platform & Ecosystem Shifts A platform inserting itself between the business and its customers, or a shift in where value accrues.
- Ask: Could a platform own the customer relationship and reduce us to a commoditized supplier? Are we becoming a feature of someone else's product?
- Pattern check: disintermediation, platform envelopment, ecosystem lock-in, channel power shift
Vector 3 — AI & Automation Threats Capabilities that automate the work the business charges for, or collapse the cost structure a competitor could exploit.
- Ask: Which part of our value is "expertise or labor we sell" that AI can now replicate at near-zero marginal cost? Where does AI let a smaller competitor operate at our scale?
- Pattern check: cost-structure collapse, expertise commoditization, self-service substitution, AI-native re-architecture
Vector 4 — Changing Customer Behavior & Expectations Demand-side shifts in how customers buy, trust, and switch.
- Ask: What do customers now expect (instant, transparent, personalized, self-serve) that our model can't deliver? Are switching costs falling?
- Pattern check: experience expectation inflation, declining loyalty, generational substitution, transparency-driven price compression
Step 3: Apply the Five Forces Overlay
Re-read each threat through Porter's Five Forces and note which force it intensifies:
- Threat of new entrants (falling barriers from digital/AI)
- Bargaining power of buyers (transparency, switching ease)
- Bargaining power of suppliers (platform consolidation)
- Threat of substitutes (new ways to get the job done)
- Rivalry intensity (digital-natives compressing margins)
This converts a trend list into a structural argument about where competitive advantage is leaking.
Step 4: Score Each Threat
Build a threat table. For every identified threat, assign:
- Likelihood: High / Medium / Low — with one sentence of reasoning
- Time horizon: Now (0–18 mo) / Near (18 mo–3 yr) / Far (3 yr+)
- Impact if realized: Severe (model-breaking) / Significant (margin/share erosion) / Moderate
- Which moat it attacks: from Step 1
- Five Forces driver: from Step 3
Step 5: Prioritize with a Threat Matrix
Rank threats by combining likelihood × impact, weighted toward nearer horizons. Sort into three tiers:
- Act now — high likelihood, near horizon, severe/significant impact
- Prepare — credible but further out, or medium likelihood
- Monitor — low likelihood or overhyped relative to evidence
Explicitly name 1–2 threats that are overhyped and should be deprioritized — credibility comes from saying what not to chase.
Step 6: Recommend Strategic Responses
For each "Act now" and "Prepare" threat, recommend a response using the appropriate posture:
- Defend — reinforce the attacked moat (deepen data advantage, raise switching costs, secure exclusivity)
- Disrupt yourself — launch or acquire the disrupting model before an entrant does
- Partner/platform — join or build the ecosystem rather than fight it
- Reposition — move up or down the value chain to where value is migrating
- Exit/harvest — manage a structurally declining segment for cash
State the posture, the specific first move, and the signal that would confirm the threat is materializing (so the team knows when to escalate).
Output Format
- Structure: Value-chain baseline → four-vector threat scan → Five Forces overlay → scored threat table → prioritization tiers → response recommendations
- Length: 1,100–1,500 words
- Format: Structured document with a markdown table for the scored threats; prose for analysis; bulleted responses
- Sections: Value Chain & Moats / Disruption Vector Scan / Five Forces Overlay / Threat Scoring Table / Prioritization (Act Now / Prepare / Monitor) / Strategic Responses / Watch Signals
- Tone: Chief strategy officer briefing — structural, evidence-led, decisive. No hype, no doom; treats disruption as a portfolio of probabilities, not a single inevitability.
Quality Checklist
Before delivering output, verify:
- [ ] All four disruption vectors are covered with at least 2 threats each, specific to this business — not generic trends
- [ ] Every threat in the table has a likelihood, time horizon, impact rating, moat attacked, and Five Forces driver
- [ ] Threats are sorted into Act Now / Prepare / Monitor tiers — not left as a flat list
- [ ] At least one threat is explicitly named as overhyped and deprioritized
- [ ] Each Act Now and Prepare threat has a named strategic posture, a specific first move, and a watch signal
- [ ] The analysis ties each threat back to a specific link in the value chain from Step 1
Notes
- The most common error is listing trends instead of threats — a trend becomes a threat only when it attacks a specific moat or value-chain link. Anchor every item to Step 1.
- Disruption rarely kills a business via the obvious frontal threat; it usually arrives through unbundling the most profitable customer segment or commoditizing the highest-margin step. Probe those first.
- Time horizon matters more than likelihood for prioritization — a severe but distant threat may justify monitoring, while a moderate near-term threat may demand action now.
- If the business is already digital-native, shift emphasis toward platform envelopment and AI-native re-architecture, where even digital incumbents get displaced.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills