vendor-evaluation

Score vendors against build options to generate weighted build-versus-buy recommendations.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill vendor-evaluation-camilooscargbaptista
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendor-evaluation
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/vendor-evaluation
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill vendor-evaluation-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, repeatable framework to decide between building in-house or buying a vendor solution, reducing subjective procurement decisions and surfacing lock-in, SLA, security, and cost risks.

Core Features & Use Cases

  • Build vs Buy scorecard: Multi-dimension scoring (technical fit, security, business viability, support) with weighted totals and tie-breaker rules.
  • Vendor evaluation checklist: Actionable checks for APIs, data export, compliance, and business continuity to assess lock-in and operational risk.
  • SLA negotiation & exit planning: Ready checklist for uptime, response times, credits, data return timelines, and contract termination clauses.
  • Output templates: Markdown report template for recommendation, weighted scores, key risks, lock-in assessment, and a 3-year cost comparison for stakeholders.

Quick Start

Compare two vendor options or a vendor versus a build plan by scoring technical fit, security/compliance, business viability, and support to produce a recommendation, confidence level, and a three-year cost comparison.

Frequently Asked Questions about vendor-evaluation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate vendors for a build-versus-buy decision?

To evaluate vendors for a build-versus-buy decision, score functional fit, security/compliance evidence, business viability, SLA terms, and three-year cost estimates to generate weighted recommendations and identify potential lock-in risks.

What is the best way to compare SaaS options against in-house development?

The best way to compare SaaS options against in-house development is using a multi-dimension scorecard that applies weighted totals to technical fit, security, business viability, and support, alongside a three-year cost comparison.

How do I assess vendor lock-in risk during procurement?

Assess vendor lock-in risk during procurement by running actionable checks on APIs, data export capabilities, compliance evidence, and business continuity to determine operational dependency and exit planning difficulty.

What SLA terms should I check when negotiating with software vendors?

Check SLA terms for uptime guarantees, response times, service credits, data return timelines, and contract termination clauses to ensure clear operational boundaries and establish a secure exit planning strategy.

Can I use a vendor evaluation scorecard for architecture reviews?

Yes, you can use a vendor evaluation scorecard for architecture reviews to systematically compare third-party options against internal builds, surfacing security, SLA, and cost risks before finalizing procurement decisions.

What should be included in a build vs buy recommendation report?

A build vs buy recommendation report should include weighted scores across technical and business dimensions, key risk assessments, vendor lock-in analysis, a three-year cost comparison, and a final confidence level for stakeholders.