Seven Powers

Concept of the skill

What it is: Seven Powers is Hamilton Helmer's framework for identifying durable firm-level sources of Power: scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, and process power.

Mental model: Power is not a compliment. It is a mechanism. A valid power creates a benefit for the company and a barrier that prevents rivals from fully copying, neutralizing, or bidding away that benefit.

Why it exists: Agents often call every strong company, growing product, sticky workflow, or differentiated feature a moat. Seven Powers forces the moat claim to name its source, economic benefit, competitive barrier, timing, and failure mode.

What it is NOT: It is not industry attractiveness, a generic competitor list, a strategy cascade, a financial valuation, or a claim that execution alone is durable Power.

Adjacent concepts: porters-five-forces owns industry structure; playing-to-win owns integrated strategy choices; blue-ocean-strategy owns value-curve creation; vrio owns resource/capability advantage tests; swot-tows owns factor-to-option work; expected-value and prioritization own choice ranking.

One-line analogy: Seven Powers is a lock-and-key test: the benefit is the key that opens economic value, and the barrier is the lock that keeps competitors from using the same key.

Common misconception: A company can have a strong product, high growth, or a large market without having Power. Growth may reveal an opportunity; it does not by itself prove durable Power.

Seven Powers

Coverage

This skill teaches agents to:

1. Name all seven powers accurately.
2. Separate firm-level Power from industry attractiveness.
3. Test every power claim for both benefit and barrier.
4. Distinguish real network economies from ordinary user growth.
5. Distinguish branding power from awareness, taste, or short-term marketing.
6. Distinguish process power from ordinary execution competence.
7. Map likely powers to company phase and timing.
8. Translate power diagnosis into strategic implications and evidence requests.

Philosophy of the skill

Seven Powers is useful because it makes competitive advantage falsifiable. A vague moat claim can survive almost any critique: "we have data," "we have brand," "we are better," "we move faster." A power claim has to survive a sharper question: what exact mechanism lets this company earn better economics, and why can competitors not close the gap?

The framework should make an agent slower and stricter. Do not reward a confident-sounding moat story. Look for the economic effect, the barrier, the time horizon, the rival response, and the evidence that would disconfirm the claim.

Core Equation

Treat a candidate power as valid only when both sides are present.

If the analysis cannot state the benefit and barrier, report "candidate power, not proven power."

The Seven Powers

Workflow

1. Scope the business and arena

State what business, product, segment, geography, and time horizon you are analyzing.

Business:
Arena:
Stage: origination / takeoff / stability / unclear
Time horizon:
Competitors or substitutes:
Power claim being tested:

Do not diagnose power for "the company" in the abstract when the power may apply only to one product, segment, geography, or channel.

2. Extract the candidate power claims

List every claim in the source material that sounds like durable advantage.

Claim:
Possible power:
Evidence offered:
Missing evidence:
Immediate false-positive risk:

Translate vague claims into the nearest power. For example, "our community grows by itself" might be network economies, "customers never leave" might be switching costs, and "incumbents cannot respond" might be counter-positioning.

3. Test benefit and barrier separately

For each candidate power, fill both columns.

If either benefit or barrier is missing, the verdict cannot be "proven."

4. Check timing and phase

Different powers tend to become available at different moments. Use phase as a diagnostic, not as a rigid rule.

Do not assume a startup has process power or branding just because it wants them. Do not assume an incumbent has power just because it is large.

5. Rank the power diagnosis

Use four verdicts.

Prefer "plausible candidate" over overclaiming when evidence is thin.

6. Translate into strategy implications

End with action, not just classification.

Most likely power:
Confidence:
Evidence that supports it:
Evidence still needed:
Competitor response to watch:
Strategic implication:
What would strengthen the power:
What would weaken or destroy it:

Strong implications usually change where the company invests. For example: deepen the network loop, protect the resource, make switching safer for current customers but harder for rivals to dislodge, or avoid a market where no plausible power exists.

Diagnostic Prompts

Use these prompts to pressure-test common claims.

Scale Economies

• Which costs decline with cumulative volume or current scale?
• What minimum efficient scale matters in this arena?
• Could a well-funded rival subsidize its way to equivalent scale?
• Does scale improve unit economics, distribution, procurement, data quality, or utilization?

Network Economies

• Who creates value for whom as the network grows?
• Is the network same-side, cross-side, data-driven, protocol-driven, or complement-driven?
• What makes a cold-start rival hard to bootstrap?
• Are participants multi-homing, and does that weaken the barrier?

Counter-Positioning

• What incumbent profit pool, asset, channel, metric, culture, or incentive would be harmed by copying?
• Is the entrant model truly superior for a chosen segment?
• Could incumbents respond with a separate brand, acquisition, price cut, or regulation?
• Is the advantage temporary until incumbents accept cannibalization?

Switching Costs

• What exactly makes switching expensive: data, workflow, integrations, contracts, risk, training, compliance, identity, or relationships?
• Are costs borne by users, buyers, admins, developers, or partners?
• Can a rival automate migration or offer guarantees?
• Are customers retained because of value or trapped despite weak value?

Branding

• Would customers pay more or choose faster for an objectively similar offering?
• Is the brand tied to trust, identity, status, safety, taste, or assurance?
• How long did the perception take to build?
• Can rivals buy similar awareness, or is the perception historically accumulated?

Cornered Resource

• What scarce resource is controlled?
• Is control exclusive, preferential, contractual, regulatory, geographic, relational, or capability-based?
• Does the resource independently enhance value or economics?
• Can rivals substitute, bid it away, lobby around it, or develop an alternative?

Process Power

• What activity system produces lower cost, higher quality, faster cycle time, or superior reliability?
• How much is codified versus tacit?
• How long would a competent rival need to replicate it?
• Is the process embedded across people, tooling, routines, metrics, culture, and suppliers?

Output Template

## Seven Powers Diagnosis

Business and arena:
Time horizon:
Stage:

### Candidate Powers
| Power | Verdict | Benefit | Barrier | Evidence | Missing evidence |
| --- | --- | --- | --- | --- | --- |

### Strongest Claim
- Power:
- Confidence:
- Why it creates benefit:
- Why competitors face a barrier:
- Key false-positive risk:

### Strategy Implications
- Invest in:
- Protect:
- Watch:
- Evidence to collect next:
- What would change the verdict:

Failure Modes

• Growth confused with power: Fast adoption may be demand discovery, not defensibility.
• Benefit without barrier: The business has an edge, but rivals can copy it.
• Barrier without benefit: The company has something hard to copy, but it does not improve economics.
• Network effects claimed from usage: More users is not enough; users must increase value for other users or participants.
• Brand awareness confused with branding power: Recognition is not the same as durable willingness to pay.
• Process power claimed too early: Good execution is not a hard-to-copy activity system.
• Industry attractiveness confused with firm power: A good industry can still lack firm-specific power, and a tough industry can contain a powerful firm.

Boundaries

• Use Porter's Five Forces when the question is whether an industry structure lets participants keep profits.
• Use Playing to Win when the question is which arena to choose, how to win, what capabilities are required, and what management systems support the choice.
• Use Blue Ocean Strategy when the question is how to create differentiated value and reduce direct rivalry.
• Use VRIO when the question is whether a resource or capability is valuable, rare, inimitable, and organized.
• Use SWOT/TOWS when the question is how to inventory internal/external factors and convert them into options.
• Use Seven Powers when the question is whether the company has or can build a durable moat mechanism.
• Use expected value when the question is which action has the best probability-weighted payoff.
• Use prioritization when the question is how to rank a queue of work.
• Use framework-fit-analysis when the question is which method should be used at all.

Quality Bar

A good Seven Powers answer:

1. Names the relevant power precisely.
2. Tests benefit and barrier separately.
3. Explains why rival imitation is hard.
4. Labels weak evidence and false positives.
5. Distinguishes company power from industry structure.
6. Connects the diagnosis to strategy implications.
7. Avoids calling every advantage a moat.

References

• skills/skills/reasoning-strategy/seven-powers/references/seven-powers-sources.md
• skills/skills/reasoning-strategy/seven-powers/references/upstream-displacement-2026-05-26.md

Verification

After applying this skill, verify:

• The task matches the declared scope, coverage, or positive examples.
• The response follows this skill's workflow or checks instead of generic advice.
• The exclusions in ## Do NOT Use When do not point to a better skill.

Do NOT Use When

Use another skill when the task falls outside the declared scope, matches an anti_examples prompt, or is owned by a more specific related skill.