Free scoring matrix · score each vendor, then see the ranking
AI Vendor Evaluation Matrix
For procurement and technology leads comparing AI vendors. Score each vendor on identical criteria, adjust the weights to your case, and see how they rank and why.
Built by XONIK. Nothing you enter leaves this page.

In brief
This matrix helps you compare AI vendors fairly. You score each vendor on the same criteria, from fit to your task and where your data goes to exit and the cost of running, and you change the weights to match your case. It ranks the vendors, explains the leader against the runner-up and runs in your browser.
Please correct the highlighted fields.
Score each from 0 to 5. Leave a name empty to leave that column out.
| Criterion | Weight | |||||
|---|---|---|---|---|---|---|
Fit to the taskHow to score thisJudge it on your own cases, the awkward ones included, and not on a demonstration. Lowest score: it fails on your real cases, or you have not been able to try it on them. Middle score: it handles the usual cases and misses some awkward ones. Highest score: it handles your awkward cases correctly and you kept the results. | ||||||
Data handling and where data goesHow to score thisLowest score: the vendor will not say where your data is stored or processed, or keeps the right to train on it. Middle score: location and use are stated, but only in a policy that the contract does not bind. Highest score: the contract says where data goes, which subprocessors see it, that it is not used for training without your written consent, and how it is deleted. | ||||||
Ability to inspect and exportHow to score thisCan you see what it did on one case, and take your data and settings out? Lowest score: you see only the final answer, and nothing can be exported. Middle score: logs or step records exist but only on request, or export is limited to part of what you hold. Highest score: step records for each case, your settings and your data export in documented formats, and you control the access. | ||||||
Security evidence offeredHow to score thisJudge what the vendor shows you before you sign, not what it says. Lowest score: a statement that it is secure and nothing more. Middle score: summaries of independent assurance are shared, but not the reports, or they cover a different product from the one you would use. Highest score: independent assurance reports, results of recent security testing and a named route for reporting a weakness are shared first, and they cover the product you would use. | ||||||
How change and model updates are announcedHow to score thisLowest score: models and terms change without notice and no version history is kept. Middle score: changes are announced after release, in release notes you have to look for. Highest score: changes, including model updates, are announced in advance in writing, you can test or pin a version before it reaches you, and the contract commits to the notice. | ||||||
Integration effortHow to score thisScore high when the effort is low. Lowest score: connecting to your systems needs custom work no one has scoped, and credentials with wide access. Middle score: standard connectors exist for some of your systems and the rest need work you have estimated. Highest score: it connects through documented interfaces with credentials limited to the task, and your own team has tried it. | ||||||
Support and escalationHow to score thisLowest score: a shared inbox with no stated response time. Middle score: stated hours and response times, but no named contact and no route for a serious fault. Highest score: a named contact, response times set by severity, and an escalation route that reaches people who can change the product, all written in the contract. | ||||||
Exit and portabilityHow to score thisLowest score: no way to take your data or configuration out, or exit terms that are silent. Middle score: data exports, but in a format only the vendor's tools read, or service stops the day you give notice. Highest score: your data, prompts, rules and configuration export in documented formats, the contract sets a period of continued access after notice, and you have tried an export. | ||||||
Documentation for your own obligationsHow to score thisWhat you would need to show a customer, an auditor or a regulator. Lowest score: no instructions for use and no statement of intended purpose. Middle score: general documents exist, but not the logs, the fault-reporting route or the way to stop it that your role needs. Highest score: instructions for use, a stated purpose, access to the logs you control, a route to report a fault and a way to stop the system, all in writing before you sign. | ||||||
Total cost of runningHow to score thisScore high for lower cost over time. Lowest score: usage charges can grow without a limit you set, and integration, review time and the cost of leaving are unknown. Middle score: usage charges are understood and the other costs are estimated roughly. Highest score: usage is capped or predictable, and you have counted integration, the people who run and review it, and the cost of leaving. |
Your result
| Rank | Vendor | Score |
|---|
Want to talk through what this means for your organization?
Talk through your shortlist with usOn this page
What a fair comparison of AI vendors takes, and what this matrix cannot supply
Vendor selections drift toward the best demonstration. A well-handled awkward question, a reference call the vendor arranged and a low quoted cost on the first page all leave a stronger impression than a clause about where data is processed. The matrix puts every vendor on the same criteria, with the same evidence expected for each.
It holds no information about any vendor and recommends none. It cannot check that a claim is true. It makes your own judgments visible and puts them in an order that can be argued over.
| Criterion | Evidence to collect before you score it |
|---|---|
| Fit to the task | The vendor's results on your own awkward cases, kept in a file |
| Data handling | The contract clauses on location, subprocessors, training and deletion |
| Inspection and export | A record of the steps taken on one case, and an export you ran |
| Security evidence | The independent assurance reports and test results, not a summary |
| Change notice | The written commitment on notice, and the option to hold a version |
| Integration effort | A trial by your own engineers against one real system |
| Support and exit | Response times and escalation in the contract, and a test export |
| Documentation and cost | Instructions for use, the fault route, and a usage model on your volumes |
Who scores, in what order, and how long does it take?
Collecting the evidence takes the time and runs through the whole evaluation. Scoring takes about a working session per vendor once the evidence is in the file. Ask the procurement lead, the security lead, the technology lead and the business owner of the task to score separately, then compare their sheets. Where scorers differ widely on one criterion, one of them has seen evidence the others have not.
Scoring as one group in a room drifts toward the most confident person. Separate scoring, then a short meeting to settle the differences, keeps the ranking sound.
How do you read the ranking, the margin and the weakest cell?
The ranking puts the vendors in order and explains the leader against the runner-up: the margin, where it is ahead and where the runner-up is ahead. A narrow margin is not a decision. The evidence has not yet separated the two, and the criteria where each leads are the questions to put to them next.
Look at the lowest score of the vendor that ranks first. A weighted average can hide a failure. A vendor with the best total and the lowest possible score on data handling, exit or documentation has a problem to resolve before signing. A good score elsewhere does not pay for it.
After the ranking, before the contract
- 01
Write to the leading vendors
List the criteria on which each scored low, and ask for answers in writing.
- 02
Move the answers into the contract
A promise made on a call is not a term. Have legal check that the data, notice and exit clauses match the sales material.
- 03
Score again with what came back
The second pass matters most, since it rests on evidence the vendors gave when asked.
- 04
Keep the sheet
Filed with the contract, the scores and weights show later why the choice was made and what was knowingly accepted.
When the matrix fits, and when it does not
It fits when
- You have a shortlist and each vendor has been tried on your own cases
- More than one function has a say, and the criteria must be agreed
- An auditor or a customer may review the decision later
Look elsewhere when
- You have not yet decided whether to buy; use the build, buy or agent decision tool first
- You expect it to rank vendors from marketing material alone
- One condition, such as a data location, should simply exclude vendors
A weighted matrix trades nuance for comparability. It is the right tool for putting vendors in order and the wrong one for finding the single fact that rules a vendor out.
What do people ask before using the AI vendor evaluation matrix?
Does the matrix recommend a vendor or check what vendors claim?
No. It holds no information about any vendor and recommends none, and it cannot check that a claim is true. It puts every vendor on the same criteria with the same evidence expected, and it makes your own judgments visible in an order that can be argued over.
Why agree the weights before scoring any vendor?
Weights set after the scores are in tend to move toward the vendor somebody already prefers. Fix them first with the sponsor and write down why each criterion counts as much as it does. Any weight can change, down to zero, but change it while no vendor is yet ahead.
Is the vendor with the highest total always the safe choice?
No, because a weighted average can hide a failure. A vendor with the best total and the lowest possible score on data handling, exit or documentation has a problem to resolve before signing, and a good score elsewhere does not offset it. A narrow margin is no decision.
Should we score the vendors together in one meeting?
Score separately first. Procurement, security, technology and the task's business owner each fill in a sheet, then meet to settle the differences. Scoring as one group drifts toward whoever sounds surest. Collect evidence beforehand, such as results on your own awkward cases and the contract clauses.
Related
Want a second opinion on your shortlist?
Describe what you are weighing in a few lines. A senior practitioner replies with a suggested first conversation.