The Vendor Procurement Playbook helps a company choose technology vendors with less risk and more accountability.
Selection Pipeline
| Selection | Entry |
|---|
| Owner | |
| Target date | |
| Define | |
| Source | |
| Score | |
| Check | |
| Decide | |
| Hold accountable | |
| Shortlist | |
| Leading candidate | |
| Key risks | |
Requirements Brief and RFP
| Field | Entry |
|---|
| Problem we are solving | |
| Must-have capabilities | |
| Nice-to-have capabilities | |
| Users and volume | |
| Budget range | |
| Questions for vendors | |
Vendor Scorecard
| Criterion | Vendor A | Vendor B | Vendor C |
|---|
| Fit to requirements | | | |
| Track record and references | | | |
| Total cost (setup and recurring) | | | |
| Implementation and support | | | |
| Security and data handling | | | |
| Contract and exit terms | | | |
| Cultural fit and responsiveness | | | |
| Overall score and notes | | | |
Contract Red-Flag Checklist
| Red flag | Present? | Notes for reviewer |
|---|
| No clear data-export or exit clause | | |
| Auto-renewal with long notice window | | |
| Large price increases with little notice | | |
| Weak or missing security and privacy terms | | |
| Ownership of data or custom work unclear | | |
| No service levels or remedies for downtime | | |
| Liability heavily one-sided | | |
Selection Record and Accountability Plan
| Field | Entry |
|---|
| Chosen vendor | |
| Why chosen | |
| Red flags resolved | |
| Internal owner | |
| Service levels to track | |
| First review date | |
