Skip to content

Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/assess-moat-sources

assess-moat-sources

Unverified

Assesses which of Helmer's 7 Powers (scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, process power) protect incumbents in a defined industry, how durable each is over the analysis horizon, and which Power combination the winning archetype must hold. Output: moat-sources.md with per-Power present/absent + intensity, benefit + barrier decomposition for each present Power, durability rating (erosion timeframe + vector), buildability for a new entrant or roll-up, winner-archetype Power profile, durability risks, and reconciliation against value-chain-profit-pools.md if present. Sub-skill of analyze-industry; invocable standalone. Triggers on 'assess moat for [industry]', '7 powers analysis of [industry]', 'how durable is the moat in [industry]', 'moat durability [industry]', 'will the moat hold'. Do NOT use for single-company moat (use build-company-model), customer-lock-in only (use analyze-demand), or share analysis (use map-competitive-arena).

references/buildability-assessment.md

View on GitHub
# Buildability — Can a New Entrant or Roll-Up Build This Power?

Per-Power assessment of whether a well-resourced new entrant or roll-up platform can build the Power within the analysis horizon. Load-bearing for the orchestrator's "roll-up archetype" question.

## Output format per Power

```
- Power: scale economies
- Buildable by new entrant: NO within 5y horizon — MES is ~$2B revenue [C: peer benchmark]; reaching MES requires ~$800M cumulative investment with payback >7y at current industry growth [I: triangulation].
- Buildable by roll-up: YES — consolidating 4-5 top-10 players reaches MES at ~$1.5B aggregate; integration risk is the binding constraint, not capital.
- Required conditions: control of distribution + ability to rationalise overlapping capacity within 18 months of close.
- Capital required: $1.0-1.4B equity + ~$2B debt [I: comparable industrial roll-ups 2020-2024].
```

## Per-Power buildability heuristics

### Scale Economies
- **New entrant:** rarely buildable from zero in mature industries within 5y. Possible if (a) MES is small relative to entrant capital, or (b) a step-change technology resets the cost curve in entrant's favour.
- **Roll-up:** typically yes — consolidation is the canonical scale-build strategy. Binding constraints: antitrust, integration friction, working-capital release.
- **Required:** capital + distribution control + a credible integration playbook.

### Network Economies
- **New entrant:** difficult — requires breaking incumbent tipping. Possible via (a) narrow vertical seed → grow out, (b) cross-side bootstrapping with a subsidised side, (c) regulatory unbundling that opens interop.
- **Roll-up:** generally NO. Acquiring users does not equal acquiring network value; the network's incumbent already holds the tipping.
- **Required:** liquidity-side subsidy + a defensible niche to start.

### Counter-Positioning
- **New entrant:** by definition YES — Counter-Positioning is a new-entrant Power.
- **Roll-up:** NO. A roll-up is a scale play, not a counter-positioning play. Roll-ups inherit incumbent economics.
- **Required:** a structurally different model + incumbent cannot copy without cannibalisation.

### Switching Costs
- **New entrant:** YES, if the entrant gets to the customer first AND embeds deep workflow integration. Window closes once an incumbent owns the install base.
- **Roll-up:** acquires the switching-cost Power along with the install base.
- **Required:** workflow-embedded product OR multi-year contract structures.

### Branding
- **New entrant:** rarely within 5y — brand requires hysteresis. Possible in (a) emerging categories with no incumbent brand, (b) brand-acquisition (M&A of a smaller branded player).
- **Roll-up:** YES via acquisition of branded targets — but post-acquisition brand dilution is the binding risk.
- **Required:** decades of consistent action OR M&A path.

### Cornered Resource
- **New entrant:** depends on the resource. Patents → file early. Regulatory exclusivity → first-mover gets it. Talent → poach. Data → access the supply.
- **Roll-up:** YES if the target holds the resource; acquisition transfers it (subject to change-of-control clauses).
- **Required:** specific to resource type; assess per case.

### Process Power
- **New entrant:** NO within 5y. Process Power requires multi-year compounding. New entrants build the precursor (a disciplined operating model) but not the Power.
- **Roll-up:** NO — acquiring a process-power-holder typically loses the Power post-close (senior-leader exits, culture dilution).
- **Required:** multi-year operational discipline; cannot be bought.

## Winner-archetype Power profile

The output's step-5 statement names the minimum Power combination the winner must hold. Combine:

- **Anchor Power:** typically Cornered Resource, Network Economies, or Process Power (long-duration).
- **Reinforcer Power(s):** Scale, Switching Costs, or Branding (medium-duration).
- **Entry Power:** Counter-Positioning (transition-only, expires at scale).

Example for a vertical-SaaS roll-up:
> Winner archetype must hold: (1) Switching Costs (workflow-embedded vertical product, durable in core install base); (2) Scale Economies in customer-support and R&D allocation across the install base; OPTIONAL (3) Process Power in onboarding playbook after 5+ years of compounding. Network Economies NOT available in this segment (no buyer-buyer or seller-buyer linkage).

## Power Progression filter

A roll-up at industry stability stage typically cannot build Counter-Positioning (window closed) but CAN build Scale + Process Power. A new entrant at origination stage typically CAN build Counter-Positioning + Cornered Resource (talent/data) but NOT yet Scale or Network. Cross-check buildability against the industry's S-curve stage from `analyze-trajectory`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall