We’ve written enough RFPs to know better. A Playbook from IQ4hire on IT sourcing.

Insights

We’ve written enough RFPs to know better

For most technology purchases, the request for proposal is the slowest route to a decision you could have made sooner. Here is what we do instead, and when you still need one.

For most technology purchases, the request for proposal (RFP) is the slowest route to a decision you could have made sooner, and it rarely produces a better one. Use one only when the decision really requires it.

We have written them, scored them and sat on both sides of the table. Here is what we learned, and what we do instead.

Why the RFP falls short

  • It rewards the vendor best at answering RFPs. The strongest response is often written by the team with the most practice, not the one that best fits your situation.
  • The requirements tend to be written after the demos, so by then they quietly favor whoever you saw first.
  • It costs months of time from IT, procurement and the business, and the answers still have to be interpreted.
  • It rarely surfaces the risks you care about most: how the contract works at renewal, who owns the product next year, and what happens when you leave.

What works instead

  • Start from a shortlist of suppliers that have already been vetted for your category.
  • Test each one against your actual situation, not a generic checklist.
  • Run a focused proof of the thing that worries you most.
  • Negotiate with a real alternative in hand.

When you still need an RFP

Public-sector purchasing rules sometimes require one, and a very large or regulated purchase may need a formal process for governance. In those cases we help you write a short one, with requirements drawn from your situation instead of a vendor’s feature list, and we keep the shortlist small.

Where to start

If you have a decision on your desk, send it to us. We will tell you whether it needs an RFP, and if it does not, we will get you to a shortlist. See how we work.

← All Insights