Build Vs Buy Analyzer

Transform "gut feeling" into data-driven build-vs-buy decisions with TCO estimates and risk analysis.

Install
cmdop skills install agensi-build-vs-buy-analyzer

Build vs Buy Analyzer is a skill that walks an AI agent through a structured, 8-point evaluation framework to determine whether an engineering team should build a capability in-house, purchase a third-party service, or pursue a hybrid approach. Each of the eight criteria is scored from 1 to 5, covering dimensions such as core competency alignment, total cost of ownership, time-to-market, and vendor lock-in risk.

The skill produces a Decision Record as its output. That record includes a 3-year TCO model that accounts for engineering hours, maintenance overhead, infrastructure costs, and licensing fees. It also surfaces the top three risks for each path — for example, IP reputation concerns on the build side or vendor price increases on the buy side — and pairs each risk with a mitigation approach.

The Decision Record concludes with three concrete next steps to move from the decision to implementation. The format is designed to be inserted directly into Architecture Decision Records (ADRs), shared with stakeholders, or posted to a team communication channel.

This skill is appropriate when an engineering team needs a repeatable, documented rationale for a build-vs-buy choice rather than an informal discussion. It is not a general-purpose cost-estimation or procurement tool, and it does not integrate with external pricing APIs or vendor catalogs to fetch live cost data.

Use cases

  • Produce a scored Decision Record before committing engineering resources to building an internal email service vs. buying one
  • Generate a 3-year TCO comparison when evaluating whether to self-host a database or use a managed cloud service
  • Document a build-vs-buy rationale in ADR format for a forthcoming architecture review
  • Identify the top risks of vendor lock-in before signing a multi-year SaaS contract
  • Run a repeatable evaluation across multiple candidate tools to compare their weighted scores side by side
  • Prepare a structured summary to align engineering and product stakeholders on a make-or-buy direction

When to use it

  • An engineering team needs a documented, reproducible framework for a build-vs-buy decision
  • Stakeholder alignment requires a formal Decision Record rather than an informal recommendation
  • A project evaluation must account for multi-year TCO including maintenance and infrastructure
  • The team wants to surface and prioritize risks for both the build and buy paths before committing

When not to use it

  • Live vendor pricing or real-time procurement catalog data is required — this skill does not fetch external cost data
  • The decision involves non-engineering procurement categories outside software or infrastructure
  • A quick, informal gut-check is sufficient and formal documentation is not needed
  • The scope is a pure financial audit requiring integration with accounting or ERP systems