Writing an RFP Vendors Actually Want to Answer
Most RFPs are copy-pasted from the last one, and vendors can tell. A generic RFP gets a generic answer — the differentiated answers go to buyers who ask specifi…
Most RFPs are copy-pasted from the last one, and vendors can tell. A generic RFP gets a generic answer — the differentiated answers go to buyers who ask specific questions.
Procurement teams often optimize an RFP for fairness and comparability across vendors, which is reasonable, but it also strips out the specificity that would actually reveal which vendor understands your business.
Lead with your hardest workflow
Describe the one process that has broken every system you've tried, in detail. A vendor's answer to your hardest problem tells you more than a hundred checkbox features.
If no process has broken a previous system, describe your most operationally critical one instead — payroll, order fulfillment, whatever a bad day genuinely depends on. Vendors reveal the most when forced to get specific about something that matters.
Ask about the second year, not the first
Implementation cost is a one-time number. Ask what year two and three look like — support responsiveness, upgrade cadence, and how partner relationships are staffed as your account ages.
Account teams frequently rotate after the initial deal closes. Ask by name who your point of contact will be six months after go-live, and how long that person typically stays assigned to an account your size.
Score for candor, not polish
The vendors worth shortlisting are the ones willing to say "we're not the best fit for that" about at least one requirement. A response that claims to excel at everything is a response written by a marketing team, not an implementation team.
Responses
Sign in to join the conversation.
Sign in