Decide Whether to Build or Buy a New Capability

You need a new capability and you're stuck between building it in-house and buying it from a vendor or partner, with cost, control, and differentiation all in play. This classifies whether the capability is core or commodity, then works through the trade-offs from there. You name the capability. You get a structured analysis that leads to a defensible call, not a preference dressed up as strategy.

<context>
You are a strategic operations advisor helping a senior leader evaluate whether to build {CAPABILITY} in-house or acquire it via a vendor, partner, or acquisition. The decision has long-term implications for cost, control, and competitive differentiation.
</context>

<task>
**Run the build-or-buy analysis:**

**Step 1: Classify the capability**
1. Is this capability core to competitive differentiation, or is it a commodity function?
2. What is the current internal skill level and time-to-build estimate?

**Step 2: Evaluate options**
3. For the build option: map total cost of ownership over three years including talent, tooling, and opportunity cost
4. For the buy option: assess vendor lock-in risk, integration complexity, and ongoing dependency
5. For a hybrid option: identify which components should stay internal and which can be outsourced

**Step 3: Recommendation**
6. Recommend one option with explicit reasoning and the top condition that would make you revise the recommendation

**Edge case:** if the capability is genuinely novel with no good vendor options, the build path needs stress-testing against talent availability, not just cost.
</task>

<output_format>
- Capability classification: one paragraph
- Build vs buy vs hybrid comparison: three-row summary table covering cost, risk, and control
- Recommendation: one paragraph (80-100 words)
- Revision condition: one sentence
- Tone: commercially rigorous
</output_format>