Analyzing Vertical Integration Economics

Evaluates vertical integration decisions with make-vs-buy analysis, supply chain control benefits, and margin capture opportunity…

You say
Install this skill Read the source first Free Written by lev-os · unverified publisher
Context cost
1.6k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 6.5 kBtext throughout, nothing executable
Licence
free to use
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Evaluates vertical integration decisions with make-vs-buy analysis, supply chain control benefits, and margin capture opportunity assessment. Use when analyzing vertical integration, evaluating supply chain strategy, or assessing integration economics.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

analysis

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md6.5 kB · 96 lines
--- name: analyzing-vertical-integration-economics description: Evaluates vertical integration decisions with make-vs-buy analysis, supply chain control benefits, and margin capture opportunity assessment. Use when analyzing vertical integration, evaluating supply chain strategy, or assessing integration economics. tags: - analysis - capital-allocation-and-corporate-strategy metadata: author: casemark practice_areas: - Corporate Strategy - Capital Allocation - Shareholder Value document_types: - Analysis Report skill_modes: - Analysis ---
18# Analyzing Vertical Integration Economics
19
20Evaluates vertical integration decisions by quantifying the economic trade-offs between internal control and external procurement across the value chain.
21
22## When To Use
23
24- A company is considering acquiring or building a supplier or distributor
25- Management wants to compare make-vs-buy economics for a critical input or process step
26- A portfolio company is evaluating backward integration (into raw materials/components) or forward integration (into distribution/retail)
27- Supply chain disruptions have exposed dependency risks that integration might mitigate
28- An existing integration is under review for potential divestiture or outsourcing
29
30## Inputs To Gather
31
32- **Current cost structure**: Fully-loaded unit economics for the process step under consideration — external purchase price, internal COGS estimates, freight/logistics, quality costs
33- **Volume data**: Current and projected volumes for the input or output being evaluated; minimum efficient scale for in-house operations
34- **Supplier/channel landscape**: Number of qualified suppliers or distributors, switching costs, concentration risk, contract terms and renewal timelines
35- **Margin stack**: Gross and operating margins at each value chain stage; identify where margin pools sit and who captures them today
36- **Capital requirements**: Estimated CapEx for building or acquiring the capability, ongoing maintenance CapEx, working capital impact
37- **Strategic context**: Competitive dynamics (are peers integrated?), regulatory constraints on integration [VERIFY], customer/channel conflict risks
38
39## Workflow
40
411. **Map the value chain** — Diagram each stage from raw input to end customer. Identify the specific stage(s) under integration consideration. Note current ownership boundaries and transaction interfaces.
42
432. **Quantify the make-vs-buy spread**
44 - Calculate fully-loaded internal production cost (direct materials, labor, overhead, allocated SG&A, depreciation on required CapEx)
45 - Compare against current external procurement cost (unit price + freight + quality inspection + inventory carrying cost + contract management overhead)
46 - Compute the per-unit and annual cost differential at current volume and at projected scale
47
483. **Assess margin capture opportunity**
49 - Identify the gross margin earned by the current external provider on the company's business
50 - Estimate how much of that margin is capturable after accounting for the company's likely cost structure at relevant scale
51 - Model margin impact at 80%, 100%, and 120% of projected volume to stress-test the economics
52
534. **Evaluate supply chain control benefits**
54 - **Quality**: Quantify cost-of-quality improvements (defect rates, rework, warranty claims) from tighter process control
55 - **Lead time**: Estimate working capital savings from shorter, more predictable lead times
56 - **Security of supply**: Value the option of avoiding disruption — use historical disruption frequency and cost data where available
57 - **IP protection**: Assess whether integration reduces leakage of proprietary processes or specifications
58
595. **Model the investment return**
60 - Build a 5–7 year DCF of the integration investment using the company's WACC or hurdle rate
61 - Include acquisition premium or build cost, ramp-up timeline, integration expenses, and incremental working capital
62 - Calculate NPV, IRR, and payback period
63 - Compare risk-adjusted returns against alternative uses of the same capital (share repurchases, organic growth, other M&A)
64
656. **Identify dis-integration risks**
66 - Loss of supplier innovation and competitive benchmarking
67 - Fixed cost absorption risk if volumes decline
68 - Management distraction and organizational complexity
69 - Customer or channel conflict if forward-integrating into a space served by current partners
70 - Regulatory or antitrust constraints on vertical combinations [VERIFY — jurisdiction-specific thresholds and review standards]
71
727. **Synthesize recommendation** — Frame the integration decision as a capital allocation choice. State whether the economics justify integration, partial integration (e.g., dual-sourcing with internal capability), or continued outsourcing.
73
74## Output
75
76Deliver a structured analysis report containing:
77
78- **Executive summary**: Integration recommendation with key economic rationale (2–3 sentences)
79- **Value chain map**: Visual or tabular depiction of current vs. proposed ownership boundaries
80- **Make-vs-buy economics table**: Side-by-side unit cost comparison with assumptions stated
81- **Margin capture analysis**: Quantified margin currently earned by external party and estimated capturable portion
82- **Supply chain benefit valuation**: Monetized control benefits (quality, lead time, security of supply)
83- **Investment return summary**: NPV, IRR, and payback under base, upside, and downside scenarios
84- **Risk register**: Key dis-integration risks with likelihood and mitigation options
85- **Recommendation**: Integrate, partially integrate, or maintain outsourcing — with conditions or triggers for revisiting
86
87## Quality Checks
88
89- All cost comparisons use the same basis (fully-loaded, same accounting treatment for overhead allocation)
90- Volume assumptions are consistent across make-vs-buy, margin capture, and DCF sections
91- Capturable margin estimates reflect the company's realistic cost position at scale, not the supplier's margin structure applied wholesale
92- CapEx and ramp-up timeline assumptions are benchmarked against comparable integration projects where data is available
93- Dis-integration risks are addressed with equal rigor as integration benefits — avoid confirmation bias toward the integration thesis
94- Antitrust and regulatory review requirements are flagged with [VERIFY] for jurisdiction-specific analysis
95- Sensitivity analysis covers volume shortfall, cost overrun, and delayed ramp scenarios
96
In the file
SKILL.md851 words
Files1
Licence
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈140
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,485
on trigger
The instruction body, read only when the skill fires.
0.81%
of a 200k window
Ten skills this size would take about 8% of the window before you open a file.
050k100k150k200k context window

1.6k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 6.5 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md6.5 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Analyzing Vertical Integration Economics · 1.6k tokens when loaded npx mcprush@latest skill add lev-os/analyzing-vertical-integration-economics

Writes to .claude/skills/analyzing-vertical-integration-economics/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencelev-os/analyzing-vertical-integration-economics

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0
Claim this skill