Evaluate build versus buy trade-offs for a capability
Assess whether to engineer software in-house or purchase an external vendor solution. Use this before committing engineering quarters or vendor budgets.
You getCapability Assessment, comparison Matrix and total Cost and Risk Analysis
Prompt
Act as a principal product manager specializing in software architecture and technical procurement. Your goal is to run a rigorous build-versus-buy trade-off evaluation for a specific capability.
First, ask me these 3 numbered questions in one message and wait for my response:
1. What is the capability, and what primary user problem does it solve?
2. What is your team's core strategic differentiation, and does this capability directly create competitive advantage?
3. What are your estimated timeline constraints, engineering availability, and annual software budget for this area?
Once I reply, provide an objective comparative analysis using these rules:
- Distinguish clearly between core business logic and undifferentiated commodity scaffolding.
- Account for total cost of ownership including maintenance, compliance, vendor lock-in, and migration difficulty.
- Provide a clear recommendation with exit criteria if assumptions fail.
Output format:
- Capability Assessment (commodity vs. differentiator)
- Comparison Matrix (table with columns: Factor, Build In-House, Buy Vendor Solution, Winner)
- Total Cost and Risk Analysis (maintenance overhead, API dependency, switching barriers)
- Final Recommendation and 90-Day Next ActionsExample output
Paste this prompt into ChatGPT, Claude or Gemini. The model will prompt you with 3 specific scoping questions. After replying, ask it to draft a slide-ready executive summary for engineering leadership.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Classify onboarding drop-offs into cognitive and value friction
Audit user onboarding funnels by separating confusion from missing value motivation. Use it to prioritize growth experiments and UX redesigns.
Score beta readiness for general availability release
Evaluate qualitative feedback, bug logs, and usage stats to decide if a beta is ready for general availability. Use this to make unbiased release decisions.
Turn onboarding test notes into root causes
Extract recurring user drop-off triggers and identify root causes from raw usability notes. Use this to focus sprint priorities on true blockers.
Write a beta tester welcome and feedback guide
Generate a concise onboarding document for new beta testers. Use it to clarify software limitations, expected time commitment, and bug submission steps.
Break a product epic into vertical MVP slices
Slice large, horizontal engineering epics into thin, end-to-end user stories. Use this during backlog refinement to ship testable customer value every sprint.
Translate technical debt into business risk and ROI
Convert complex engineering refactoring proposals into commercial risks, cost savings, and strategic ROI. Use this to secure executive buy-in for critical architectural upgrades.
- Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
- Draft an Internal Launch FAQ and Enablement Brief for Sales and Support
- Create a quarterly win-loss brief for sales teams
- Define beta cohorts and launch exit metrics
- Draft a customer advisory board charter
- Extract win and loss drivers from CRM notes