How to write an RFP for QA and software testing services

Updated 2026-09-24

A useful RFP for software testing or development work describes your product, your current testing and the outcome you need in enough detail that vendors can answer specifically, and asks every vendor the same questions in the same format so answers can be compared. State the engagement model, the evaluation criteria and their weights, the pricing structure you want, and the contract terms you will insist on. Most of the effort goes into the context section: vendors cannot propose a sensible approach to a product they cannot see.

What to check

  1. Describe your product, architecture, release frequency and current test state honestly, including what is not working.
  2. State the engagement model you want, or ask vendors to propose one against stated constraints.
  3. Publish the evaluation criteria and their weights in the RFP itself.
  4. Give a fixed response format with question numbers and word limits, and a pricing template every vendor must use.
  5. List the contract terms you will require, such as code ownership and key personnel, so vendors price them in.
  6. Set a clarification deadline and share every answer with all bidders.

Ask the vendor

  • Who, by name and role, will work on our account in the first three months? Please attach CVs.
  • How would you decide what to test first on our product, and what would you leave out?
  • Please price the scope using our pricing template, and list every assumption the price depends on.
  • Where will the test code live, and who will own it from the first commit?
  • What would you produce in the first 30 days, and how would we know onboarding has worked?

What an RFP is for

An RFP has one job: to get answers from several vendors that you can compare fairly. Everything in it should serve that. Vague context produces generic proposals; open questions without a format produce answers that cannot be lined up; hidden criteria produce proposals aimed at the wrong things.

Public procurement rules show the discipline that makes this work. EU procurement law requires the award criteria and their relative weighting (or, where weighting is not possible, their order of importance) to be stated in the procurement documents, and US federal rules keep the instructions to offerors and the evaluation factors as defined sections of a solicitation. You are not bound by either, but the principle holds: tell vendors how you will judge them.

The RFP builder assembles the sections below from your answers and the framework's question bank, and exports Markdown, CSV and DOCX.

Section by section

Section What to include Why it matters
About you Company, product, users, team size, where people work Lets vendors size the team and overlap hours
Current testing Who tests today, what is automated, in which framework, what is not working The honest part; drives a realistic proposal
Architecture and tools Platforms, languages, CI, issue tracker, test management, environments Shows whether vendors can work in your setup
Release process Frequency, branching, who decides to release Sets turnaround and service levels
Scope In scope, out of scope, test types, non-functional needs, standards Stops proposals that price the wrong thing
Engagement model Staff, team, managed service or project, or ask for a proposal Makes prices comparable
Questions Numbered, with word limits Makes answers comparable
Attachments CVs, sample reports, anonymised test strategy, certificates Evidence rather than claims
Pricing A template: roles, rates, management, tools, changes, increases Stops hidden costs
Contract terms Non-negotiables such as code ownership, key personnel, data terms, exit Vendors price them in now, not later
Evaluation Criteria, weights, stages, pilot Tells vendors what matters
Timeline and rules Dates, clarification process, confidentiality Keeps the process fair

The context section is where RFPs fail

Buyers often under-describe their current state, sometimes out of embarrassment. That produces proposals for an ideal product you do not have. Be specific:

Weak: "We are a fast-growing SaaS company looking for a QA partner to improve quality."

Stronger: "Web application and two mobile apps, released weekly from a single main branch. About [N] automated end-to-end tests exist in Playwright, of which a large share fail intermittently and are ignored. No dedicated testers; developers test their own work. Main risks: payments, permissions and data export. Staging is shared and often unavailable on Mondays."

The second version lets a vendor propose a real approach, and it lets you see which vendors actually read it. Use your own facts, not these.

Questions that make vendors reveal how they work

Ask for specifics and evidence, not claims. Good RFP questions ask for names, examples and commitments:

  • the named team with CVs, and the share of each person's time;
  • an anonymised test strategy and a real status report from another client;
  • how they would assess risk on your product and what they would not test;
  • where the code lives and who owns it;
  • which service levels they would accept, with remedies;
  • what they would deliver in the first 30 days.

The questionnaire has the full question bank with what strong and weak answers look like. For the strategy you are asking for, see what a test strategy document should contain.

Pricing: give a template

If each vendor prices in its own format, you will spend days rebuilding the numbers. Provide a template with roles, levels, rates, management, onboarding, tools, out-of-hours rates, change request rates and rate increases, and require every vendor to use it. See rate cards and what they hide for the lines that matter.

Criteria and weights

Publish the criteria and weights you will use, and use them. The scorecard starts from the framework's criteria and adjusts weights by situation, for example more weight on security and audit rights for a regulated product, or on code ownership for an automation build-out. Decide the weights before responses arrive, so you are not tempted to fit them to a favourite.

Timeline and fair process

Set a clarification deadline and share every question and answer with all bidders without naming who asked. Allow enough time to answer well; rushed RFPs get template responses. Plan the stages after submission: shortlist, presentations with the named team, references, a paid pilot, and contract. The selection path sets these out end to end, and the engagement models guide helps you decide the model before you write.

Tools for this

Questions buyers ask

Should I use an RFI before the RFP?
If you do not yet know which engagement model or kind of vendor fits, a short request for information helps you learn and build a shortlist. If you already know what you need, go straight to a focused RFP with a small number of vendors.
How many vendors should receive the RFP?
Few enough that you can read every response properly and run reference checks and pilots on the shortlist. Sending an RFP widely creates reading work without improving the decision.
Should I share my budget?
Sharing a range can stop proposals that are far outside it and helps vendors size the team. The risk is that bids cluster at the upper end of the range. Either way, require a price breakdown so you can see what the money buys.

Sources

  1. The Sourcing and Consultancy Playbooks, UK Cabinet Office
  2. FAR Part 15: Contracting by Negotiation (source selection), US Federal Acquisition Regulation
  3. Directive 2014/24/EU on public procurement, European Union
  4. ISO/IEC/IEEE 29119-3:2021 Software testing, Part 3: Test documentation, ISO/IEC/IEEE
  5. The Digital, Data and Technology Playbook, UK Cabinet Office