Buy vs Build Decision Matrix

Evaluates build-vs-buy decisions across seven weighted dimensions with a 3-year TCO calculator.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sparkst/sparkry-claude-skills --skill buy-vs-build-decision-matrix-sparkst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Buy vs Build Decision Matrix
Source: https://github.com/sparkst/sparkry-claude-skills/tree/main/plugins/strategy-workflow/skills/cos/buy-vs-build
Command: npx skills add https://github.com/sparkst/sparkry-claude-skills --skill buy-vs-build-decision-matrix-sparkst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Teams often make build-vs-buy decisions based on gut feel or cost alone, ignoring strategic fit, opportunity cost, risk, and reversibility. This Skill provides a structured framework that scores both options across seven dimensions and produces a defensible, documented decision. ## Core Features & Use Cases - 7-Dimension Decision Matrix: Scores strategic fit, 3-year TCO, time to market, risk, control, learning value, and ecosystem on a 1-10 scale with configurable weights. - 3-Year TCO Calculator: The tco_3y_calc.py script models development, maintenance, infrastructure, subscription, and opportunity costs to compare total ownership cost. - Learning Weights System: The decision_tracker.py script logs decisions to CSV, analyzes override patterns, and suggests weight adjustments based on your actual decision history. - Use Case: A solo founder deciding whether to build authentication or use Supabase runs the matrix, gets a weighted BUY recommendation (8.75 vs 3.85), and logs the decision with reversal triggers for future revisiting. ## Quick Start Ask the assistant to evaluate whether to build or buy a specific capability, such as "evaluate build vs buy for our authentication system using the decision matrix."

Frequently Asked Questions about Buy vs Build Decision Matrix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate a build vs buy decision systematically?▼

Score both options across seven dimensions: strategic fit, 3-year TCO, time to market, risk, control, learning value, and ecosystem. Apply weights to each dimension, compute weighted totals, and document assumptions, reversibility, and reversal triggers in a decision record.

How do I calculate 3-year total cost of ownership for build vs buy?▼

Run the tco_3y_calc.py script with your build story points, engineering hourly rate, and vendor monthly subscription cost. It outputs a JSON breakdown covering development, maintenance, infrastructure, opportunity cost, integration, and subscriptions over three years.

What factors matter most in a build vs buy decision?▼

Strategic fit typically carries the highest default weight (0.25), followed by TCO and time to market (0.20 each). Core differentiators should be built, while commodities like email delivery or payment processing should be bought.

Can the decision matrix weights be customized over time?▼

Yes. The decision_tracker.py script logs each decision to a CSV file and analyzes override patterns after at least five decisions. It suggests adjusted weights when you consistently override the matrix for specific dimensions.

When should you build instead of buy software?▼

Build when the capability is a core competitive differentiator, when you need full control over data and behavior, or when building develops strategically valuable team skills. Avoid building commodities where vendors offer mature, low-cost solutions.