Sometimes you genuinely need more testers. A programme can simply have more work than the current team can reasonably cover.
But “we need more people” is also the easiest diagnosis in delivery because it avoids fixing whatever is wasting the people you already have. If you want an independent capacity review, we can help.
Ask what one more tester would actually do
Make the supplier describe the work the additional person will pick up. “Increase capacity” is not an answer. Will they cover a specific product area, remove a known bottleneck, build automation that pays back, own an integration or reduce a queue that is genuinely delaying releases?
If the request cannot be tied to identifiable work and a clear constraint, you are being asked to approve a number rather than solve a problem. Sometimes that number is still right. At least make them earn it.
Find the waiting
How much time disappears into unavailable environments, late builds, broken test data, access requests, defect re-testing, meetings and waiting for other suppliers? Adding ten people to a team that spends half its week blocked gives you ten more blocked people. If the response to every problem is more people, question why your contract keeps buying more bodies.
Check the scope
Test teams grow because nobody ever stops testing anything. Every release adds functionality and the regression pack only gets larger. Legacy checks remain because removing them feels risky. Eventually the supplier needs more people simply to repeat history.
Ask what could be removed, combined or automated sensibly. Ask whether low-risk areas receive the same attention as critical ones. Capacity problems are often prioritisation problems wearing a resource-plan hat.
Understand the commercial incentive
If your supplier makes more money when it supplies more testers, that does not mean every resource request is dishonest. It does mean you should expect the business case to be slightly enthusiastic.
A strong supplier should also suggest ways to reduce demand. If the only lever is headcount, you may have bought a very expensive recruitment agency with defect templates.
Check whether the team shape is wrong
A request for more testers can hide a capability gap. The team may have plenty of people but nobody comfortable with performance, automation, data, integration or a particular platform. Adding another generalist will increase capacity without fixing the constraint.
Ask whether the missing thing is genuinely another pair of hands or a different skill, stronger leadership or access to someone elsewhere in the organisation. Resource plans count people very well and capabilities rather badly.
If you want us to look at the workload before approving another wave of people, get onto us. We can separate genuine capacity needs from blocked time, duplicated effort and testing that no longer earns its keep.