
For your company
Money & Vendors
Module · The pitch is not the product
The AI Procurement Discipline Check
AI vendors sell a demo, and a demo is a magic trick: rehearsed data, cherry-picked prompts, no edge cases. Your normal procurement muscle was built for software that either works or does not, but AI fails softly and expensively in the gap between the demo and your data. This module checks the five habits that let you buy on evidence instead of vibes: written requirements before demos, a proof of value on your own data, security and compliance gates, an exit that actually works, and sign-off from the people who will live with it.
What the five levels look like
Every dimension in this assessment is scored 1 to 5. This is what the levels mean, dimension by dimension. The graded report diagnoses where your own answers land and what to do about it.
Requirements before demos
- 1No requirements
- 2Vague wish list
- 3Requirements after demos
- 4Written first
- 5Written and weighted
At the low end: Buying AI with no written requirements means the best demo wins, not the best fit. Write down the problem, the must-haves and the deal-breakers before you book the next call. What good looks like: Weighted requirements defined up front are exactly how you stay in control of the evaluation. Keep them honest by scoring every vendor against the same sheet, not against each other.
Proof on your data
- 1Demo only
- 2Reference calls
- 3Trial, generic data
- 4Pilot on real data
- 5Scored pilot, real data
At the low end: A decision made on the vendor demo alone is a decision made on their best day. Before you sign, run the tool on a real sample of your own data and see what actually happens. What good looks like: A scored pilot on your real data is the single strongest signal you can get before buying. Keep the scoring criteria fixed in advance so the pilot proves something instead of flattering the tool.
Security gate exists
- 1No review
- 2Review if remembered
- 3Review for big deals
- 4Standard gate
- 5Gate plus data mapping
At the low end: Buying AI with no security review means you learn where your data went after it has already gone. Put a mandatory review in the path before any tool touches real data. What good looks like: A standard gate with data mapping tells you exactly what leaves the building and where it lands. Keep the map current as vendors change their subprocessors; the answer expires.
Exit clause works
- 1Locked in
- 2No exit terms
- 3Exit on paper
- 4Exit with data export
- 5Tested exit path
At the low end: A vendor you cannot leave sets your price at renewal, not the market. Negotiate a data export and a clean exit now, while you still have a signature they want. What good looks like: A tested exit path with real data portability keeps every renewal a negotiation instead of a ransom. Re-check it when the vendor changes their platform; portability quietly rots.
The users sign off
- 1One person decides
- 2Rubber-stamp only
- 3Users consulted late
- 4Users sign off
- 5Cross-functional sign-off
At the low end: A tool chosen by one person and handed down is a tool the users will route around. Bring the people who do the work into the evaluation before the shortlist, not after. What good looks like: Cross-functional sign-off means the tool arrives with the users, security and legal already behind it. Keep the group small enough to decide; a sign-off that never converges is its own failure.