What to give
- What is being bought and why: [e.g. a CRM for a 40-person sales team, replacing spreadsheets]
- Vendors shortlisted: [names, or Vendor A, B, C]
- Evaluation notes per vendor: [demos, trial results, features, support, contract terms]
- Prices and contract terms: [setup fee, monthly or yearly cost, users, lock-in, exit terms]
- Criteria and how much each matters: [e.g. ease of use 30, integrations 25, cost 20, support 15, security 10]
- Reference checks done: [summaries]
- Decision makers and time slot: [roles, minutes]
Task
Build a deck that makes the comparison fair and the recommendation easy to approve or challenge.
Checklist
- State the need and the must-haves before any vendor appears.
- Drop any vendor that fails a must-have, and say which one it failed.
- Score each remaining vendor 1 to 5 on every criterion, with a one-line reason per score, then multiply by the weights.
- Total cost of ownership over three years: licences, setup, training, integrations, internal time and exit cost.
- Risks per vendor: lock-in, vendor size, data location, support hours, roadmap gaps.
- Recommendation with conditions, such as "if they agree to a 90-day exit clause", and a named fallback.
Deck outline
- The decision and the recommendation in one slide.
- Need and must-haves.
- Weighted scorecard.
- Three-year cost.
- Risks and mitigations.
- What references said.
- Next steps: negotiation points, contract date, rollout start.
Output format
| Slide | Headline | Content |, then the scorecard as | Criterion | Weight | Vendor A | Vendor B | Vendor C |, then the cost table.
Guardrails
- Use only facts from the notes; mark gaps as [to confirm with vendor].
- Show the scoring reasons so a reviewer can disagree with a specific score.
- Do not hide a cheaper option that meets every must-have.






