Back to prompts
Decision MakingPremiumadvanced
4.8

Buy vs. Build Decision Framework

Make systematic build-vs-buy decisions for technology solutions with total cost analysis and risk assessment.

Copy & Paste this prompt
You are a seasoned CTO who has made dozens of build-vs-buy decisions. You combine technical depth with business pragmatism.

Help me decide whether to **build** or **buy** a solution:

- **What I need:** [DESCRIBE THE CAPABILITY/TOOL/SYSTEM]
- **Problem it solves:** [WHAT PAIN POINT OR NEED]
- **Company size:** [e.g., 5 people startup, 200-person scaleup, enterprise]
- **Engineering team size:** [NUMBER OF DEVELOPERS]
- **Budget range:** [MONTHLY OR ANNUAL BUDGET]
- **Timeline pressure:** [WHEN DO YOU NEED THIS WORKING]
- **Candidate buy options:** [SPECIFIC TOOLS/VENDORS CONSIDERED]
- **Core vs. context:** [IS THIS CORE TO YOUR COMPETITIVE ADVANTAGE OR SUPPORTING INFRASTRUCTURE]
- **Integration requirements:** [WHAT MUST THIS CONNECT TO]

Provide:

1. **Strategic Assessment** — Core vs context, Wardley Map lens
2. **Total Cost of Ownership (5-year)** — Build vs buy with all hidden costs
3. **Technical Fit Analysis** — Score each buy option on key criteria
4. **Risk Matrix** — Build risks vs buy risks
5. **Hidden Costs Checklist** — Costs people always forget
6. **Decision Framework** — Scored across 8 weighted criteria
7. **Hybrid Option** — Buy-and-extend or build-on-top approach
8. **Reversal Cost** — If you choose wrong, how hard is it to switch?
#build-vs-buy#technology#strategy#CTO#architecture

Works with

chatgptclaudegemini

💡 Pro Tips

  • •Be honest about your team's available bandwidth — maintenance is forever
  • •The 'Core vs. Context' question is the most important filter
  • •Run this analysis again in 12 months — the equation changes as your company grows

🧠 Why This Works

Build vs. buy decisions are among the most consequential in technology—wrong choices create years of technical debt or vendor lock-in. This prompt applies systematic evaluation criteria (cost, time, customization, maintenance, risk) that prevent the common bias toward building everything in-house.

📅 When to Use This Prompt

Use when evaluating whether to build internal tools, adopt SaaS platforms, or purchase off-the-shelf solutions. Essential for CTOs, engineering managers, and technical founders facing decisions about infrastructure, internal tools, or platform components where both options are viable.

🎯 What You'll Get

You'll receive a structured comparison covering total cost of ownership (build + maintain vs. license), time-to-value analysis, customization requirements scoring, vendor risk assessment, and a clear recommendation with decision criteria weights. Ready to present to leadership for approval.

🔗 Related Prompts

Coding & DevelopmentPremium

System Design Interview Simulator

Practice system design interviews with a realistic AI interviewer — get architecture feedback, follow-up questions, and…

system-designinterviewarchitecture
★4.9
advanced