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

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 Actions

Example output

Example for: evaluation of user authentication and identity management for a B2B SaaS platform

Capability Assessment

User authentication, SSO, and session management are security-critical commodities rather than unique product value. Proprietary competitive advantage comes from workflow automations, not user credential databases.

Comparison Matrix
FactorBuild In-HouseBuy Vendor SolutionWinner
Time to Production4 to 6 months for base auth and SAML2 to 3 weeks for integrationBuy
Engineering Cost2 dedicated engineers full-time (~$350k/yr)$24k/year base tier SaaS feeBuy
Maintenance OverheadOngoing patch cycles, CVE triage, auditsOffloaded to vendor compliance teamBuy
CustomizationInfinite control over auth flowsRestricted to vendor webhooks and UI kitBuild
Vendor Lock-inZero lock-in, proprietary schemaHigh switching costs if user IDs couple to schemaBuild
Total Cost and Risk Analysis
  • Maintenance: In-house auth requires continuous SOC 2 audit readiness, SAML edge-case handling, and quarterly library updates.
  • Vendor Risk: Third-party outages halt login flows. Vendor pricing tiers can scale aggressively per monthly active user.
  • Migration Barriers: Vendor-managed password hashes make migrating away expensive without forcing password resets.
Final Recommendation and 90-Day Next Actions

Recommendation: Buy a managed identity provider via standard OIDC to launch customer enterprise tiers this quarter.

  • Next 30 days: Run proof-of-concept with Auth0 and WorkOS focusing strictly on enterprise SAML setup.
  • Next 60 days: Implement standard OIDC wrapper in your backend so switching providers does not break core data models.
  • Next 90 days: Ship enterprise SSO tier and audit vendor bill against user growth triggers.
Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management
Product Management

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.