RedHub AIRedHub AI
Tool Gate · How it works

How the gate works

How the AI Vendor Reliability & Spend-Justification Scorecard works

This tool grades each AI / SaaS vendor on reliability and whether the spend is justified at renewal. It scores 6 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.

The 6 weighted controls

01Reliability (uptime/SLA)gate · reliability floorwt 22
02Incident load (inverted)reliability lanewt 16
03Support responsivenessreliability lanewt 14
04Adoption & usagewt 16
05Value vs costwt 20
06Alternative / switch costwt 12
RENEW
score 75+
RENEGOTIATE
score 50+
DO NOT RENEW
below floor
Reliability floor · worsen-only

On a business-critical vendor, any reliability-lane signal — reliability, incident load, or support — at or below 1 forces DO NOT RENEW regardless of the justification score. You can't justify renewing a core dependency you can't rely on, no matter how good the price looks; the gate only ranks against renewal, it never grants it.

75/100
DO NOT RENEW

Why: This core LLM API is well-adopted, priced right, and has no easy alternative — the justification score is 75, which alone reads RENEW. But it's business-critical and its reliability signal is at 1: below the floor. The reliability-floor gate forces DO NOT RENEW. A 75 can't justify renewing a core dependency you can't rely on.

Fix firstReliability (uptime/SLA) is at 1 on a business-critical vendor — demand an SLA with credits, or plan migration off this dependency, before the renewal call. The score can't clear until the reliability problem is fixed.

A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. A planning aid that grades the vendor relationship from your own inputs, not people. It applies no industry multiplier and is not financial or legal advice. Confirm renewal, contract, and budget decisions with the relevant owners.