Markdown

AI Build vs Buy Scorecard

Define the evidence, meaning, and weight for each score before evaluating options. The directions below are hypotheses to test, not a formula that determines “buy” or “build.” Security, privacy, legal, safety, accessibility, data-residency, and operational vetoes override any total.

Mandatory gates before scoring

RequirementCandidate evidencePass/fail/unresolvedRemediation owner
Data, privacy, legal and safety boundary
Core task quality and accessibility
Permissions, duplicate/unknown-result recovery
Records, export and deletion
Funded operational ownership

For candidates that pass, compare workflow fit, user effort, integration/change burden, complete cost and strategic value with predeclared meanings and weights. Data sensitivity is not a score pointing automatically toward custom development.

Candidate interpretation to validate

Full-Cost Check

Representative-slice trial

Decision

Illustrative hold decisions

Vendor A lacks required source/version export; extension B duplicates a ticket on retry; build C lacks an operations owner. Each remains on hold for a different mandatory gap. Keep the manual baseline while resolving and retesting those gaps. No weighted total cancels a veto.