Hidden costs of outsourcing software testing

Why the rate is not the cost

When you compare testing vendors, the first number you see is a rate: per hour, per tester per month, or per release. It is tempting to compare those rates and pick the lower one. The UK Sourcing Playbook requires central government to produce a "should cost model" of the whole life cost for complex outsourcing projects, treats it as good practice elsewhere, and presents it as a protection against "low cost bid bias". ISO 37500, the guidance standard on outsourcing, likewise treats transition and ongoing governance as phases of the outsourcing life cycle, not as free extras.

For testing, the gap between rate and total cost comes from a small number of predictable sources. None of them is exotic. Each can be estimated with numbers you already have.

The cost lines to add

Cost line	Who pays	How to estimate it
Your management and briefing time	You, in staff hours	Hours per week from engineering, product and QA leads, multiplied by internal cost
Onboarding and knowledge transfer in	Often both	Vendor days for ramp-up plus your hours to explain the product
Test management and defect tools	Varies	Licences per seat, whether in your accounts or theirs
Devices and browsers	Varies	Real devices, emulators or a cloud device service, and who holds the subscription
Test environments	You	Extra environments, data refreshes, cloud spend for parallel test runs
Automation maintenance	Usually you, through the rate	Hours per sprint to fix broken tests after product changes
Change requests	You	Past frequency of scope change, multiplied by the agreed change rate
Rework from missed defects	You	Production incidents that testing should have caught, and the cost to fix and release again
Exit and knowledge transfer out	Often both	Days of exit assistance plus your time to take over or brief the next supplier

Put each line into the cost model with your own figures. The model does not hold market rates on purpose: your quotes and your internal costs are the only numbers that mean anything for your decision.

Your own team's time

The vendor cannot test what nobody has explained. Someone on your side will attend stand-ups, clarify requirements, triage defects, approve test plans and review reports. In the first weeks this can be a large share of a lead's week. Later it usually falls but rarely disappears.

Estimate it honestly. Ask your engineering and product leads how many hours a week they expect to spend, then multiply by your internal cost per hour. If that number is large compared with the vendor's fee, it is a signal to look at how the vendor will work inside your team, not a reason to stop.

Tools, devices and environments

Testing depends on tools: a test management system, a defect tracker, automation frameworks, device farms, accessibility checkers, performance tools. Some vendors include their own licences in the rate; others bill them separately; others expect you to provide them. Ask directly, and ask what happens to any vendor-held licence at exit. If your test history lives in the vendor's tool account, getting it back can become a cost of its own. See test automation vendor lock-in for the related risk.

Environments are almost always yours. A vendor that runs more tests in parallel may need more environments or more cloud capacity. Price that before you sign.

Rework and change requests

Two costs appear only after the contract starts.

Rework is what you pay when a defect escapes to production: the incident, the fix, the extra release, and sometimes customer credits. You cannot know this in advance, but you can make it visible. Agree how escaped defects will be counted, as described in defect leakage as a vendor metric, so you can see the trend.

Change requests are what you pay when scope moves. A narrow scope definition with everything else priced as a change is a known pattern. Read the change control clause, agree a rate and a process, and estimate how often your own scope has changed in recent releases.

Exit

Every contract ends. The US Government Accountability Office report on HealthCare.gov describes how ineffective planning and oversight of contractors contributed to rising costs and delays. Planning for the end of the contract is part of that planning. Price exit up front: the days of assistance, the handover of test assets and data, and your own time to take over or brief the next supplier. Put exit terms in the contract from the start, not at renewal.

Putting it together

Once every line has a number, compare vendors on total cost across the term, and compare outsourcing with hiring on the same basis. The in-house vs outsourced cost guide shows that comparison. Use the cost tool to keep all lines in one sheet you can share with finance, and check where the cost model sits in the selection path.