Build Vs Buy
Systematically evaluate whether to build a solution or buy/use existing product. Use when evaluating tooling, services, or frameworks.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill build-vs-buygit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/decision-making/skills/build-vs-buy ~/.claude/skills/build-vs-buyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Build vs Buy Systematically compare building custom solutions vs using off-the-shelf products or services. ## Context You are deciding between building custom or buying existing. Establish clear decision criteria and cost models. ## Domain Context Based on make-vs-buy decision frameworks: - **Build**: Full control, learning investment, ongoing maintenance cost - **Buy**: Faster time-to-market, but less control, vendor lock-in risk - **Hybrid**: Use product but customize parts ## Instructions 1. **List Requirements**: Functional and non-functional needs 2. **Compare Options**: Build custom, Product A, Product B, Open source 3. **Cost Model**: Development time, licensing, ops, migration, training 4. **Risk Assessment**: Vendor risk, technical risk, team capacity risk 5. **Decide**: Option with best total cost of ownership wins ## Anti-Patterns - **Build Anything**: "We can build it faster!" Result: years and millions later, still building. **Guard**: Honestly assess dev time vs buying. - **Vendor Lock-In Ignored**: Buy product without exit strategy. Result: stuck. **Guard**: Evaluate switching cost before committing. ## Further Reading - *Make vs Buy Decision Frameworks* - *Open Source Business Models*
Details
- Skill name
build-vs-buy- Repository
- sethdford/claude-skills
- Path
architect/decision-making/skills/build-vs-buy/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Build Vs Buy skill do?
Systematically evaluate whether to build a solution or buy/use existing product. Use when evaluating tooling, services, or frameworks.
How do I install the Build Vs Buy skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Build Vs Buy popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Card Sort Analysis
48sethdford/claude-skills
Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.
Bug Bounty Program
48sethdford/claude-skills
Establish and manage bug bounty programs to leverage external researchers for vulnerability discovery.
Clean Code Review
48sethdford/claude-skills
Systematic code review checklist for readability, maintainability, and correctness. Use when reviewing pull requests or assessing existing code.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.