In-house vs outsourced QA cost: building a fair comparison

Why headline comparisons mislead

The most common version of this comparison sets one tester's salary against a vendor's monthly fee for one tester. It leaves out most of what either option costs. Salaries miss employer on-costs, recruitment, ramp-up and the manager. Vendor fees miss your time managing the vendor, onboarding, tooling passed through to you, change requests and the cost of leaving.

The UK government's sourcing guidance asks public bodies to build a "should cost" model of what a service would cost to deliver, including in house, before deciding how to procure it. The same approach works for a product company: model each option fully, with your own numbers, and compare like with like.

This site does not publish market rates or salaries. Published averages rarely match your location, seniority needs and hiring market, and they go stale quickly. The cost model asks you for your own figures and your vendors' quotes.

The in-house side

Component	What to include	Where the number comes from
Salaries	Base pay for each tester role at the seniority you need	Your salary bands
Employer on-costs	Taxes, pension, benefits and other employment costs	Your finance team's standard rate
Recruitment	Agency fees or internal recruiting time per hire	Recent hires or recruiter quotes
Ramp-up	Months before a new hire is fully productive	Your experience with past hires
Attrition and backfill	Share of the team you expect to replace each year, and the recruitment and ramp-up each replacement costs	Your people data
Tools and licences	Test management, device access, other test tools	Current invoices or quotes
Equipment	Laptops, test devices, workspace	Your standard per-person cost
Management	Share of a manager's time spent managing testing	The manager's salary and your estimate of time

Two items tend to change the result most. Ramp-up delays the point at which you get value from each hire. Attrition repeats recruitment and ramp-up every time someone leaves, and it lands on a small team hard.

The outsourced side

Component	What to include	Where the number comes from
Vendor fees	Rate times hours, monthly fee per person, fixed price per release, or base plus variable fee	The written quote
Tools billed by the vendor	Licences or device services inside or added to the rate	The quote; ask directly
Change requests	Work outside the agreed scope	Your estimate of scope change, and the change control terms
Rate review	Increases after the initial term	The rate lock and review clause
Onboarding	Your team's time to onboard the vendor, plus any setup fee	Your estimate and the quote
Your management time	Reviews, meetings, triage, reporting and escalations	Hours per month times the internal hourly cost of the person doing it
Tools you pay for to support the vendor	Extra seats in your own tools	Your invoices
Exit and knowledge transfer	Exit assistance fees plus your team's time to take over or move to a successor	The exit clause and your estimate

Ask each vendor for a price build-up by role and seniority, not only a total. Rate cards and what they hide explains what to look for in that build-up, and hidden costs of outsourcing testing lists the items that appear after signature.

Compare over 12 and 24 months

One-off costs fall at different times on each side. Hiring front-loads recruitment and ramp-up. Outsourcing front-loads onboarding and back-loads exit. A 12-month view shows the cost of getting started; a 24-month view shows the cost of running.

Put both options side by side at both horizons. If the answer flips between the two, the decision depends on how long you need the capacity, which is a question for your roadmap rather than your spreadsheet.

Test your assumptions

A cost comparison is only as good as its inputs. Before you share the result, change each of the following and see whether the answer moves:

• ramp-up months for a new hire;
• expected attrition;
• management hours per month for the vendor;
• the share of hours that will fall outside the agreed scope;
• the rate after the initial term.

Note which assumptions change the conclusion. Those are the ones to check with your finance team, your hiring manager or the vendor before deciding.

Cost is one criterion, not the decision

A lower total does not settle the question. The framework weighs pricing transparency alongside team, process, code ownership and exit terms. A vendor option that is cheaper but leaves you without the test code at the end may cost more later. Once you have the numbers, score the vendors on the scorecard and read pros and cons of outsourcing software testing for the non-financial side.