How QA vendors staff projects, and how to keep your team
Updated 2026-09-24
A bait and switch happens when the senior people you meet during selection are not the people who do the work after signature. You prevent it by asking for named individuals with CVs, interviewing them, running a pilot with the same people, and writing those names into the contract as key personnel with notice, approval and overlap terms for any replacement.
What to check
- Check that the proposal names every person in the first three months of the team, with a CV for each, not only roles and headcount.
- Interview the proposed lead and at least one tester, and note who from the vendor attended the sales meetings.
- Confirm in writing which named people are employees and which are contractors or subcontractors.
- Ask how much of the lead's time is allocated to you, as a share of a working week, and whether they lead other clients too.
- Put the named people into a key personnel schedule, with the replacement terms, before signature.
- In reference calls, ask whether the people met during the sale were the people who did the work.
Ask the vendor
- Who, by name and role, will work on our account in the first three months, and are these the people who will start on day one?
- Which of the people we met during this process will work on our account, and for what share of their time?
- If a named team member leaves or is moved to another client, how much notice do we get, who approves the replacement, and who pays for the overlap?
- Are any of the proposed people not yet employed by you, or currently assigned to another client?
- Can we run a short paid pilot with exactly the people named in this proposal?
How staffing usually works at a testing vendor
Testing vendors sell people's time, so their economics depend on keeping people billable. Three practices follow from that, and none of them is wrong in itself. They only become a problem when you do not know they are happening.
The bench. People between client assignments sit on the bench. When a deal closes, the vendor staffs it from whoever is on the bench at that moment, which may not be who was available when the proposal was written.
Sales-stage seniors. Senior engineers, architects or practice heads often join pitches and workshops because they present well and understand the problem quickly. Their role after signature may be a few hours of oversight a month.
Shadow resources. Some vendors add junior people to an account, sometimes unbilled at first, to train them on your product. That can be a fair way to build a pipeline of cover, or a way to replace the seniors you are paying for with cheaper staff over time.
Your goal is not to stop these practices. It is to know which people will do your work, for how much of their time, and what happens when that changes.
Signs in the proposal
The red flags checker looks for these patterns in proposal text:
| What you read | What it can mean |
|---|---|
| "Team to be confirmed on contract signature" | Nobody is assigned yet; you are buying from the bench |
| Roles and headcount with no names or CVs | You cannot judge seniority |
| "Access to our pool of certified testers" | People shared across clients, no time commitment |
| A named lead with no stated allocation | The lead may be spread over several accounts |
| Seniority argued by the number of certificates | Knowledge of terms, not practice on products like yours |
US federal source selection rules list personnel qualifications among the non-price factors a buyer can evaluate (FAR 15.304). You can only evaluate people you can see. A proposal that names nobody gives you nothing to evaluate.
Before signature: pin the team down
Ask for names and CVs. For each person in the first three months: name, role, years of testing experience, products worked on, employing entity, and the share of their time allocated to you. Use the questionnaire to send this as a standard question to every vendor, so the answers are comparable.
Interview the people, not the presenters. Ask the proposed lead and at least one tester to walk through how they would test a feature of your product. Note who attended the sales meetings and who will actually work on the account. If they are different, ask directly why.
Run the pilot with the same people. A short paid pilot is the most reliable way to see the team at work. Write into the pilot terms that the named people will do it. See how to run a paid pilot.
Check employment status. Ask which people are employees and which are freelancers or employees of a subcontractor. A subcontractor you have not checked is a different company doing your work.
In the contract: key personnel and replacement terms
The UK Model Services Contract, used for central government services, has a key personnel mechanism: named roles that the supplier cannot change without the buyer's consent, except for events outside its control. You can adapt the same idea to a testing contract. The contract clause builder includes two clauses for this.
Key personnel. Name the lead and any specialists who were part of your decision. Wording to adapt:
The individuals listed in Schedule X are Key Personnel. Supplier will not remove or reassign Key Personnel during the first [12] months without Customer's prior written consent, except for resignation, illness or dismissal.
Replacement terms. For everyone else on the team, agree:
- written notice before any planned change, in business days;
- a replacement with equal or higher skills and experience, whose CV you see first;
- the right to interview and reject a replacement;
- an overlap period, at the vendor's cost, while the new person learns your product;
- a statement that repeated unapproved changes are a breach.
The point of the overlap at the vendor's cost is simple: the party that causes the change carries its cost. Without it, you pay for every new person to learn your product.
After signature: watch for drift
Staffing changes gradually. Keep a simple team register with the names and allocations from the contract, and compare it with timesheets or invoices each month. Watch for:
- new names on timesheets that were never introduced to you;
- the lead's hours falling month by month;
- questions from the team that show they have not read earlier decisions or defects;
- a rise in the time it takes to test a normal release.
Raise changes at your regular service review, not only when a problem appears. If you are also measuring the service, staffing continuity can be one of the service levels. See SLA metrics that matter.
Confirm with references
References are a strong check on staffing because they have lived through it. Ask them whether the people from the sale were the people who did the work, whether the original team is still there, and how replacements were handled. See how to check references properly.
Tools for this
Vendor questionnaire
81 questions by theme, each with why it matters and what strong and weak answers sound like.
Contract clauses
Clauses to insist on, with plain-English rationale, as a checklist and a DOCX.
Proposal red-flag checker
Paste a proposal or tick what you saw; get flagged patterns and what to ask next.
Questions buyers ask
- Is it unreasonable to ask for named people before signing?
- No. The vendor may not be able to hold people indefinitely, so agree a validity period for the proposal and ask the vendor to confirm availability for your start date. If it cannot name anyone, treat the team as unknown when you score it.
- What if a named person really does resign?
- Resignation, illness and dismissal are normal exceptions in a key personnel clause. The replacement terms should still apply: you see the replacement's CV, can interview them, and the vendor covers the handover overlap.
- Are testing certificates a good proxy for seniority?
- Only partly. Entry-level certification shows knowledge of terms and techniques, not years of practice on products like yours. Ask for the projects each person has worked on and test them in the interview.
Sources
- Model Services Contract, UK Cabinet Office
- ISO 37500:2014 Guidance on outsourcing, ISO
- The Sourcing and Consultancy Playbooks, UK Cabinet Office
- FAR Part 15: Contracting by Negotiation (source selection), US Federal Acquisition Regulation
- ISTQB certification scheme, International Software Testing Qualifications Board