RFI vs RFP for QA services: which to send first
Updated 2026-09-24
An RFI (request for information) asks the market what it can do so you can plan and shortlist; responses are not offers. An RFP (request for proposal) asks shortlisted vendors for a priced proposal against your defined scope, so you can compare and choose. Send an RFI first when you are unsure of scope, model or who can deliver; go straight to an RFP when you already know what you need and have a shortlist.
What to check
- Write one paragraph describing what you need. If you cannot, you are not ready for an RFP.
- Decide whether you know the engagement model you want. If not, use the RFI to learn how vendors would approach it.
- Count your candidates. If you have more than you can evaluate properly, use a short RFI to cut the list.
- Keep the RFI short: a few pages and a response limit, so you get answers you can read in one sitting.
- State in the RFI that responses are not offers and that a later RFP will follow for shortlisted vendors.
- Set a date by which you will tell RFI respondents whether they are invited to the RFP.
Ask the vendor
- Based on this summary, which engagement model would you propose and why?
- Which parts of this scope would you not take on, or would you subcontract?
- What information would you need from us to give a firm price in an RFP?
- Can you share one anonymised example of a similar engagement: product type, team shape and duration?
The short answer
An RFI is for learning. An RFP is for choosing.
The US Federal Acquisition Regulation, at FAR 15.201(e), describes RFIs as a tool for when a buyer does not yet intend to award a contract but wants price, delivery, market or capability information for planning, and states that responses are not offers. The same logic works for a private company hiring a QA vendor: an RFI helps you shape the requirement and the shortlist; an RFP asks for proposals you will score.
When to send an RFI first
Use an RFI when one or more of these is true:
- You do not know what model you need. You are unsure between a dedicated team, a fixed-scope project or a mix, and want to see how vendors would approach your situation. The engagement models guide helps you frame the options.
- Your candidate list is long. Scoring full proposals takes hours each. A short RFI lets you cut a long list to a shortlist you can evaluate properly.
- The scope is new to you. For example, you have never bought performance or accessibility testing and want to learn what the scope should include before you write it.
- You need budget information for planning. Rough price ranges from an RFI help you set a budget band for the RFP. Treat them as indicative only.
When to go straight to an RFP
Skip the RFI when:
- You can describe the scope, deliverables and timeline in a page.
- You know the engagement model you want.
- You already have a shortlist from referrals or past work.
- Your timeline is tight. An RFI round adds time for writing, responses and review.
If you have only a few weeks between deciding to outsource and signing a contract, going straight to an RFP is reasonable as long as the scope is clear.
What each document contains
| Section | RFI | RFP |
|---|---|---|
| Background on your product | Short summary | Full context, stack, current test state |
| Scope | Problem statement | Defined scope with in and out lists |
| Engagement model | Ask vendors to propose | State what you want, or ask for options priced separately |
| Questions | Few, open | Structured, with a response template |
| Pricing | Indicative ranges, optional | Firm price with build-up |
| Evaluation criteria | Shortlisting criteria | Criteria with weights |
| Length of response | Strict page limit | Structured, fuller |
| Status | Not an offer | A proposal you will score and negotiate |
A short RFI that works
Keep it to a few pages. Include:
- One paragraph on your product and users.
- One paragraph on the problem you want solved.
- Five to eight questions, such as how they would approach the work, a comparable engagement, team shape, where people are based, and how they handle ownership of test code.
- A page limit and a deadline.
- A statement that responses are not offers, that you will invite a shortlist to an RFP, and when you will tell respondents.
The UK Cabinet Office Sourcing Playbook recommends early market engagement before a formal procurement to test the requirement. Your RFI is a light version of that.
From RFI to RFP
Use what you learned:
- Tighten the scope where responses showed confusion.
- Pick the engagement model, or ask for two priced options.
- Add questions where RFI answers were vague.
- Set the evaluation criteria and weights before you send the RFP, not after proposals arrive.
The RFP generator builds the document with scope, deliverables, weighted criteria and a response template. Set the weights with the scorecard before release. The selection path shows where each step sits in the timeline, and how to write a QA RFP covers the document section by section. When responses arrive, follow how to evaluate RFP responses.
Fairness and courtesy
Send the same documents to every candidate, answer questions in writing and share the answers with all respondents, and tell unsuccessful vendors promptly. Vendors spend real time on responses; a clear, short process gets you better answers.
Tools for this
Questions buyers ask
- Is an RFI binding?
- No. An RFI gathers information for planning. US federal rules, for example, state that RFI responses are not offers. Say this in your RFI so vendors do not treat it as a bid.
- What about an RFQ?
- A request for quotation asks for a price against a fully defined requirement. It suits commodity purchases. QA services usually need the vendor to explain approach and staffing, which is what an RFP asks for.
- Can I skip both and just talk to vendors?
- You can, but without a written request each vendor answers a different question. A short, identical document to every candidate is what makes answers comparable.
Sources
- FAR Part 15: Contracting by Negotiation (source selection), US Federal Acquisition Regulation
- The Sourcing and Consultancy Playbooks, UK Cabinet Office
- TechFAR Hub, US Digital Service
- FAR 15.201 Exchanges with industry before receipt of proposals, US Federal Acquisition Regulation