Back to Skills
Strategy/build-vs-buy-analyzer

Build vs. Buy Analyzer

Analyzes whether to build internally or buy an existing solution

Time Saved

4-6 hrs → 15 min

Compared to doing it manually

Slash Command

/build-vs-buy-analyzer

Type this in Claude to run the skill

The Problem

Engineering wants to build, finance wants to buy, leadership wants a recommendation by Friday. Without structured analysis, the decision becomes political.

What You Get

  • ✓Requirements list (must-have vs. nice-to-have)
  • ✓Build option analysis
  • ✓Buy option analysis (per vendor)
  • ✓Comparison matrix with weighted scores
  • ✓Clear recommendation
  • ✓When to reconsider triggers

How to use this skill

  1. 1Download the skill file using the button on this page
  2. 2Add the file to your .claude/skills/ folder in your project
  3. 3Type /build-vs-buy-analyzer in Claude to run the skill

Best For

New capability decisionsVendor evaluationsArchitecture decisions

Related Skills

Strategic Roadmap Review

/strategic-roadmap-review

A facilitated thinking exercise: look back at what happened, then look forward to set strategic direction — before building the tactical roadmap.

Prioritization Engine

/prioritization-engine

Score and rank features using RICE, ICE, or weighted scoring with clear documentation.

North Star Finder

/north-star-finder

Identify and validate your product's North Star metric with supporting input metrics.

Go-to-Market Strategy

/go-to-market-strategy

Creates a complete GTM plan with channels, messaging, timeline, and success metrics

Frequently Asked Questions

Build when: it's core to your differentiation, you need full control, or existing solutions don't fit. Buy when: it's commodity functionality, speed matters more than customization, or maintenance cost exceeds license cost.

Consider: total cost of ownership (not just license), integration complexity, vendor risk, customization needs, and strategic importance. Build costs are often underestimated by 2-3x.