Vendor evaluation and RFPs: the 6-step process that prevents buyer's remorse
Most vendor decisions are made by the loudest stakeholder and re-litigated 18 months later. A structured 6-step process — needs, shortlist, RFP, demos…
On this page▾
- Define needs before you talk to a vendor. Vendor pitches reshape needs in 30 minutes.
- RFP is a filter, not a love letter. Keep it short, scoreable, and honest.
- Reference calls matter more than demos. Two calls beats six demos.
- Decision in writing, against the rubric. No 'we just clicked'.
Vendor selection is one of the costliest decisions HR makes — and one of the least disciplined. The 6-step process below moves the centre of gravity from sales-led to buyer-led.
The 6 steps
- 1Step 1 — NeedsWrite a 1-page brief: problem, must-haves, nice-to-haves, budget, timeline. Sign-off before any vendor call.
- 2Step 2 — Shortlist3-5 vendors from analyst reports, peer recommendations, and the brief. Not 12.
- 3Step 3 — RFPSend a short, scoreable RFP. 10-15 questions, not 200.
- 4Step 4 — DemosReal scenarios from YOUR data, not the vendor's polished script.
- 5Step 5 — References2 references per finalist, including 1 that churned.
- 6Step 6 — DecisionScored against rubric. Documented. Signed.
RFP design
- Company + product overview (1 question).
- How they meet each must-have (1 per must-have).
- Implementation timeline + customer responsibilities.
- Pricing model + total cost over 3 years.
- Security + privacy posture (SOC 2, GDPR, sub-processors).
- Data export + exit support.
- Three customer references at similar company size.
Reference calls
'What's broken about the product?' 'What would have to be true for you to leave?' 'How long was real implementation vs the sales pitch?' 'What surprised you in year 2?'
Decision rubric
- Score each vendor 1-5 on the must-haves. Weighted by importance.
- Score 1-5 on operational fit (implementation, support, references).
- Compute total. The highest score isn't always the choice — but a different choice requires written rationale.
- Lock the decision in the log.
Read next
All playbooksHR tech RFPs have specific traps — payroll edge cases, role-based access at scale, data residency, integration debt.
A decision log captures what was decided, by whom, why, and what alternatives were considered. Two hours a week to maintain — and it pays back the first time…
Lattice, 15Five, Leapsome, Culture Amp, Peakon — what each one is really for, and how to avoid buying a tool to fix a practice you haven’t built.