Learn · Module detail
how to run a vendor evaluation
Evaluate vendors against the programme you must operate, not the feature list they present. Require evidence for ledger accuracy, integrations, member experience, cost, ownership, and exit before choosing a platform.
## The mechanism
Turn requirements into observable tests. The vendor should show an earn event, reversal, redemption, balance correction, support workflow, data export, and settlement report. Record the result against the same acceptance rule for every supplier.
## Worked example
A member earning 2 points per dollar on 400 dollars of spend holds 800 points. At a 1 cent point value, that balance represents 8 dollars of liability. Ask each vendor to show how the transaction creates the balance, how a reversal removes it, and where the 8 dollar exposure appears.
## Do it
Define the target workflow and failure cases. Give every vendor identical test data. Score evidence, implementation ownership, recurring cost, contract controls, and the export path. Speak with the people who will operate exceptions.
## Common mistakes
- Scoring demonstrations instead of evidence. Require a repeatable test. - Comparing features without operating cost. Include implementation and support ownership. - Leaving data exit until negotiation. Test the export before selection. - Accepting a custom promise. Put acceptance criteria in the contract.