A reference-check playbook for government software buyers
Reference checks are where shortlists get decided — here's how to run one that surfaces the truth instead of a vendor's three happiest customers.
Every vendor hands you three references who love them. That's not intelligence — it's a testimonial. A real reference check is designed to get past the curated list to the verified peer experience the GTM thesis is built on: what comparable agencies actually picked, paid, and regretted. Run correctly, it's the single highest-signal step in a procurement.
Find your own references, not just the vendor's
Start from public award records: jurisdictions your size that bought this product in the last few years, found through council minutes and bid portals rather than the vendor's reference sheet. A buyer who calls a peer the vendor didn't pre-coach gets a candor that no managed reference will ever match. The vendor's list is still worth calling — just treat it as the optimistic bound.
Ask questions that can't be answered with a brochure
Skip 'are you happy with the product.' Ask: what slipped in the implementation timeline and why; what did you pay in change orders beyond the contract; what would you scope differently if you started over; how responsive is support once you're no longer a new logo; and would you buy it again. The gap between the contract timeline and the actual go-live date is one of the most honest numbers in the entire process.
Weight what you hear by how comparable the peer is
A glowing reference from an agency a tenth your size, or in a far simpler regulatory environment, is weak evidence for your decision. Weight each reference by population band, complexity, and recency, and write down what you learned in the same scoring rubric you used for the demos — so the reference check informs the decision instead of just confirming a preference you already had.