Build, buy or combine? Put time and total cost to a successful replacement on the map, then inspect the operating evidence behind the answer.
CONSTRAINTS
Cost to successTime to success
EVIDENCE GATES
What must be true before this counts as a replacement?
Critical regression tests
Required integrations, data contracts and backward compatibility pass.
Pass
Service restoration
Recovery is rehearsed against a defined operating target.
Pass
Security and dependency review
The option has reviewable supply-chain and vulnerability evidence.
Pass
Audit evidence package
Required compliance records can be produced, not merely promised.
Pass
Target load exercised
Peak workload, latency and degradation behavior have been tested.
Pass
Documented internal maintainers
Knowledge is discoverable and owned by more than one person.
Pass
OpenTelemetry trace coverage
Portable traces, structured logs and metrics cover critical paths.
Pass
Observed time to mitigation
Response time is measured rather than inferred from an SLA or staffing chart.
Pass
Exit and rollback rehearsal
Data export, switching and rollback assumptions have been exercised.
Pass
Add organization-specific measures
Custom measures stay in this browser session and do not change the supplied evidence gates.
Why these measures?
Subscription price and payroll are not enough. A successful replacement also has to survive integration and backward-compatibility testing, preserve domain knowledge, handle incidents, produce audit evidence, meet the workload and preserve a tested exit.