Here it is:
The Request for Proposal is supposed to be a filtering mechanism. You define what you need, vendors respond with their best case for why they can deliver it, and you select the partner most likely to succeed. In theory, it's an elegant process. In practice, most IT outsourcing RFPs are broken in ways that undermine their very purpose.
They filter by price rather than capability. They attract vendors who are good at writing proposals rather than vendors who are good at delivering results. They ask the wrong questions, invite the wrong responses, and leave the most important variables — culture, accountability, long-term fit — completely unexamined.
The result is a selection process that feels rigorous but isn't. Companies end up choosing vendors based on polished presentations and competitive pricing, then wonder why the relationship looks so different six months into delivery.
Writing a better RFP won't guarantee a perfect vendor relationship. But it will dramatically improve your odds of finding a partner worth having. Here's how to do it.
The most common RFP mistake is describing what you want a vendor to do rather than what you need them to achieve. Activity-based RFPs attract vendors who are skilled at executing defined tasks. Outcome-based RFPs attract vendors who are invested in your actual results.
Instead of writing "vendor will provide 24/7 helpdesk support with a maximum response time of four hours," write "vendor will maintain end-user productivity by ensuring IT issues are resolved with minimal business disruption, with resolution metrics to be agreed upon during contract negotiation." The first invites compliance. The second invites partnership.
Outcome-based framing also filters out vendors who can hit narrow technical metrics while completely missing the point. A vendor who resolves 95% of tickets within SLA but leaves users working around broken systems has technically performed. An outcome-based RFP makes clear that this isn't acceptable.
Many companies present an idealized version of their IT environment in RFPs — clean, well-documented, straightforward. The actual environment is messier: legacy systems held together with institutional knowledge, undocumented configurations, and technical debt accumulated over years of rapid growth.
Vendors who price against the idealized version will be surprised by the real one. That surprise translates directly into scope disputes, change orders, and an adversarial relationship. The vendors you actually want — experienced, realistic, honest — will appreciate transparency about complexity. It demonstrates maturity on your side and lets them price and plan accurately.
Include a frank description of your current environment, including its challenges. The vendors who respond thoughtfully to that honesty are the ones worth talking to. The ones who gloss over it in their response are showing you exactly how they'll handle complexity once the engagement begins.
Most RFPs ask vendors to describe their capabilities, their processes, and their experience. Those questions are necessary but insufficient. The questions that actually differentiate great vendors from mediocre ones are the ones that reveal how they think and behave under pressure.
Add questions like these to your RFP:
Describe a client engagement that didn't go as planned. What happened, what caused it, and what did you do about it? A vendor who can answer this honestly — with specifics, clear ownership of what went wrong, and demonstrable learning — is showing you something valuable. A vendor who can't think of a single example, or who describes every challenge as entirely the client's fault, is showing you something too.
How do you handle a situation where a client's requested approach conflicts with what your team believes is the right technical solution? This reveals how the vendor balances service with expertise — whether they'll tell you what you want to hear or what you need to know.
What does a successful first 90 days look like from your perspective, and how do you measure it? The answer tells you how thoughtfully they approach onboarding, and whether their definition of success aligns with yours.
One of the most common ways RFP processes go wrong is that evaluation criteria shift based on what vendors happen to offer. A particularly impressive capability gets added to the mental scorecard mid-process. Price starts to carry more weight when the budget conversation gets tense. The criteria drift, and with them, the integrity of the selection.
Before you open a single response, write down your evaluation criteria with explicit weightings. Decide in advance what percentage of the decision is technical capability, what percentage is cultural fit, what percentage is price, what percentage is relevant experience, and what percentage is the quality of their proposed approach. Then hold yourself to it.
This discipline protects you from being dazzled by a vendor's great presentation that doesn't actually fit your needs — and from unconsciously letting budget pressure override factors that will matter far more to the success of the engagement than the monthly invoice.
An RFP scope that is too narrow will get you precise bids on the wrong problem. A scope that is too broad will get you wildly inconsistent responses that are impossible to compare. The goal is a scope that is specific enough to get comparable, meaningful responses while honest enough to reflect the reality that your needs will evolve.
Include a core scope that is well-defined, a description of anticipated growth or change in the next 12 to 24 months, and a question asking vendors how they would approach scope changes as your business evolves. The last piece is important: it tells you whether the vendor's commercial model encourages partnership or nickel-and-diming.
A vendor whose entire growth strategy depends on change orders has a fundamental conflict of interest with your cost management goals. A vendor whose model includes built-in flexibility and transparent mechanisms for handling scope evolution is structurally aligned with you.
Reference checks are almost universally performed badly. Most consist of a call to a reference the vendor provided — someone who is, by definition, likely to say positive things — with questions like "were you happy with the service?" and "would you recommend them?"
Make reference checks count by asking specific, behavioral questions. Ask the reference to describe the worst moment in the engagement and how the vendor handled it. Ask whether the vendor ever delivered bad news proactively, or whether problems only surfaced when the client discovered them. Ask what they would do differently in the contract if they were starting over.
And don't limit yourself to the vendor's references. Use LinkedIn to find other clients — particularly former ones — and reach out directly. Former clients who chose not to renew will tell you things that current satisfied clients won't.
Even the best RFP process will only get you so far. A written proposal is a vendor's best effort at self-presentation, not a demonstration of actual delivery capability. Use the RFP to create a shortlist, then invest serious time in finalist conversations, working sessions, and due diligence before making a final decision.
The vendors worth choosing will welcome that scrutiny. They'll bring their actual delivery team to finalist meetings, not just their sales team. They'll engage substantively with your hard questions rather than deflecting them. They'll treat the selection process as the beginning of a working relationship — because for them, it is.
An RFP that asks the right questions will attract vendors who have the right answers. What you do with those answers from there is up to you.