Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/map-value-chain-profit-pools
map-value-chain-profit-pools
UnverifiedProduces a paired Porter value-chain decomposition + Bain/Gadiesh-Gilbert profit-pool overlay for a defined industry. Output: value-chain-profit-pools.md with value-chain stages (inbound logistics through service + support activities), absolute EBIT/economic profit (not revenue margin) per stage, horizontal-bar profit-pool visualization in markdown, identification of which stage has structural profit concentration and why, plus V/C/A/I provenance tagging. The pairing is deliberate — value chain alone is incomplete; profit pool alone lacks structural context. Sub-skill of analyze-industry but invocable standalone. Triggers on 'value chain analysis for [industry]', 'profit pool analysis for [industry]', 'where does the money sit in [industry]', 'where do profits concentrate in [industry]', 'value chain and profit pools'. Do NOT activate for single-company P&L decomposition (use build-company-model), customer-level economics (use analyze-demand), or competitive share analysis (use map-competitive-arena).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.6 KB |
| assets/profit-pool-template.md | markdown | 5.2 KB |
| evals/evals.json | config | 5.9 KB |
| references/economic-profit.md | markdown | 5.0 KB |
| references/edge-cases.md | markdown | 136 B |
| references/learnings.md | markdown | 252 B |
| references/listed-comparable-triangulation.md | markdown | 5.4 KB |
| references/profit-pool-methodology.md | markdown | 8.3 KB |
| references/structural-protections.md | markdown | 6.0 KB |
| references/value-chain-templates.md | markdown | 6.0 KB |
| scripts/validate_profit_pools.pyexecutable | script | 15.7 KB |
references/structural-protections.md
View on GitHub# Structural Protections — Helmer's 7 Powers Mapping
The "why" question in a profit pool is non-negotiable. Profit concentrates where it is **structurally protected** — not where it "adds value," not where the work is "critical," not where the players are "differentiated." Those phrases are tautologies. A structural protection is a specific, named, durable mechanism that prevents competitors from arbitraging the profit away.
This skill uses Hamilton Helmer's **7 Powers** as the canonical vocabulary so the downstream `assess-moat-sources` sub-skill inherits the same taxonomy.
## The 7 Powers (Helmer, 2016)
| # | Power | One-line test | Common stage location |
|---|-------|---------------|----------------------|
| 1 | **Scale economies** | Does unit cost decline with volume such that a sub-scale entrant cannot match price at acceptable margin? | Manufacturing, infrastructure, distribution |
| 2 | **Network economies** | Does the value to each user increase as more users join, and does that effect compound? | Marketplaces, social platforms, payments |
| 3 | **Counter-positioning** | Has a new entrant adopted a business model the incumbent cannot copy without damaging its existing economics? | Disruptive new entrants vs. integrated incumbents |
| 4 | **Switching costs** | Is the customer's all-in cost of switching (financial, procedural, relational) materially higher than the price differential a competitor can offer? | Integration / implementation, vertical SaaS, ERP |
| 5 | **Branding** | Do customers ascribe higher value to an objectively-identical offering because of trust / safety / status associations built over years? | Consumer-facing, regulated trust-sensitive, luxury |
| 6 | **Cornered resource** | Does one player have preferential access (at attractive terms) to a coveted, hard-to-replicate asset — patent, license, deposit, talent, dataset? | R&D-driven, regulated, resource-based |
| 7 | **Process power** | Has an organizational capability evolved over years such that even a well-resourced rival cannot replicate it in a reasonable time? | Manufacturing excellence (Toyota), lithography (ASML), logistics (Amazon) |
## Regulatory barriers — sub-case of Cornered Resource
A regulatory licence, an exclusivity grant, a certified GxP facility, or a patent are all forms of **cornered resource** in Helmer's taxonomy. The skill accepts both "regulatory barrier" and "cornered resource — regulatory" as valid statements, but prefers the Helmer-canonical naming for downstream consistency.
## Diagnostic questions per power
When naming the protection for a stage, answer the matching diagnostic — do not just assert the label.
**Scale economies**
- What is the minimum efficient scale (MES) in this stage, in revenue or volume terms?
- What is the cost penalty for a player at half of MES?
- Why have new entrants over the last 5 years failed to reach MES?
**Network economies**
- What is the same-side or cross-side network effect? (Buyer-buyer, seller-seller, buyer-seller.)
- Is there evidence of winner-take-most concentration over time? (HHI rising? Share of #1 increasing?)
- Could a competitor seed liquidity in a narrow niche and grow out? (If yes, the network effect is weak.)
**Counter-positioning**
- Who is the incumbent that cannot copy? Why specifically — what asset would they cannibalise?
- Has the incumbent tried and failed (or visibly avoided)?
**Switching costs**
- Estimate the customer's switching cost in $ or hours per account. What is the typical contract length?
- What % of new revenue comes from net-new logos vs. expansion? (High expansion = lock-in.)
- What is the published / observed gross churn rate? (Below 5% annual usually signals real switching costs.)
**Branding**
- Is there a measurable price premium for the branded offering vs. unbranded equivalent? (Quantify.)
- How long did the brand take to build? (Decades signals durability; years signals fragility.)
- Is the brand category-defining or interchangeable with 2-3 peers?
**Cornered resource**
- Name the resource and the legal / contractual / geographical mechanism that corners it.
- How long does the cornering last? (Patent expiry, lease term, regulatory review cycle.)
- Could a well-funded competitor licence or acquire equivalent access?
**Process power**
- What is the specific process? (Not "operational excellence" — name the routine.)
- How long has the process compounded? (Decades signals process power; years signals replicable practice.)
- Has any competitor that hired senior leaders from the incumbent successfully replicated it? (If no, that is evidence.)
## Non-structural protections — REJECT
The validator rejects outputs that name any of the following as the protection:
| Anti-pattern phrase | Why it fails |
|---|---|
| "adds value" / "value-added" | Tautological — all stages add value, that is what "stage" means |
| "is critical" / "mission-critical" | Description, not mechanism |
| "is differentiated" / "differentiation" | Symptom of protection, not the protection itself |
| "high quality" / "superior product" | Quality is competitive, not structural |
| "first-mover advantage" | Not durable unless coupled with a named Helmer power |
| "expertise" / "know-how" | Vague — must be specified as process power or cornered resource (talent) |
| "relationships" / "trusted partner" | Not durable unless coupled with switching costs or branding |
| "complexity" / "hard to do" | Difficulty ≠ protection if competitors can also do it eventually |
## "Unstable concentration" — a valid finding
If after diligent analysis you cannot name a Helmer-style protection for the highest-EBIT stage, **do not invent one.** State explicitly: "Profit concentration at [stage] is not structurally protected — expect arbitrage by [named likely entrant] within [time horizon]." That is a load-bearing finding that flows into Five Forces and the moat-sources sub-skill.
## Cross-reference
This file maps 1:1 to `assess-moat-sources` (Phase 2) vocabulary. The structural-protection statement here is the seed of the moat thesis there. Use identical naming so the analytical chain compounds.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |