If you have a continuing need for testing, hiring your own people is often the better answer. If you have a specific problem you need diagnosed, challenged or stabilised, consultancy can make more sense.
The mistake is treating those as the same decision. Hiring permanent staff to solve a six-week problem is one way to turn a temporary bottleneck into an onboarding programme.
If you are about to recruit a whole test team because delivery feels chaotic, we can look at what capability you actually need before you spend months hiring into the wrong shape.
Hire when the capability belongs with you
Permanent testers build product knowledge, relationships and context. They can influence design early, understand historical failures and become part of the engineering system rather than a service arriving at the end.
That matters when testing is a normal, ongoing part of delivery. If every sprint, release and product change needs independent challenge, you probably need internal capability somewhere. If the answer is still unclear, start with whether you need a consultant or more testers rather than assuming the largest team wins.
Use consultancy for a defined problem or change
Consultancy earns its keep when you need experience you do not need forever: reviewing a failing test function, challenging a supplier, assessing a major release, redesigning a test approach, sorting out automation strategy or helping recover a programme.
It can also provide independence where an internal team is too close to the issue. A supplier marking its own homework is obvious. An internal function defending the model it designed can be harder to spot but produces the same problem.
Do not build permanent dependency by accident
External support can quietly become the organisation. Six months later nobody internally understands the automation framework, the test data, the environments or why the strategy says what it says. The consultancy has become both indispensable and the only party qualified to confirm that it remains indispensable.
Consultancy is also not magic dust. A consultant cannot independently review an environment they are not allowed to access, although they can put the access issue in 28-point font.
If you use external help, keep enough internal knowledge to be an intelligent customer. Know the risks, understand the evidence and retain ownership of decisions.
The best answer may be mixed: a small strong internal capability, specialist external support when needed, and independent consultancy for the occasional problem that deserves a fresh view. What matters is choosing deliberately rather than inheriting whatever structure the last procurement happened to create.
Think about what you want to own in two years
A short-term decision can create a long-term operating model by accident. If every important test capability lives outside the organisation, you may save recruitment effort today and discover later that nobody internally can challenge the supplier, maintain the tooling or judge the evidence.
The opposite can also happen. Organisations recruit permanent specialists for peaks that occur once every few years, then spend the rest of the time inventing work to keep the structure busy.
Decide which knowledge is strategically useful to retain and which capability is genuinely occasional. Product knowledge, risk ownership and the ability to be an intelligent customer usually deserve an internal home even when a lot of execution remains external.
Use external help to accelerate learning, not avoid it
If consultancy is brought in, make knowledge transfer part of normal work rather than a final workshop nobody attends. Internal staff should understand why the approach changed, how the evidence is produced and what decisions sit behind the tooling. Choose the model that leaves you with the capability you need, not the org chart that looks most reassuring in PowerPoint.
That way the organisation can keep the useful parts after the consultants leave. External expertise should leave you more capable of judging your own testing, not more dependent on the people who introduced it.