QA tester hourly rates and what rate cards hide

Why the headline rate misleads

Rate cards are built to be compared on one number. The cost of a testing engagement is made of several, and the ones that move the total most are often not on the rate card.

The UK Sourcing Playbook asks public buyers to build a "should cost" model of the whole life cost, so they understand what the service ought to cost and are protected from "low cost bid bias". US federal rules describe cost realism analysis for a related purpose: checking whether proposed costs are realistic for the work and reflect a clear understanding of the requirements. A price that does not match the work proposed is a risk, not a saving. The cost model is a simple version of this. It holds no market rates; you enter the quotes you receive.

Seven things a rate card hides

1. The seniority mix. A blended rate averages senior and junior people. If the proposal assumed a senior-heavy team and the delivery team is mostly junior, you pay the same rate for less experience. Ask for individual rates by role and the planned number of people at each level.

2. Utilisation assumptions. A low rate with slow delivery costs more than a higher rate with fast delivery. The question is how many billed hours it takes to test a release, not what one hour costs. A pilot gives you real numbers. See how to run a paid pilot.

3. Roles outside the rate. Test leads, delivery managers, account managers, automation architects and performance specialists are often billed separately, or added part-time. List every role that will touch your account and check where each is paid for.

4. What counts as billable. Onboarding, knowledge transfer, internal vendor meetings, travel, and time spent waiting for environments may all be billed. Agree what is billable in writing.

5. Overtime and urgent work. Release weekends and hotfix testing are common in QA. Check the multiplier for out-of-hours work and who must approve it before it is billed.

6. Change requests. A narrow scope at a low price, with anything outside it priced as a change request, can raise the effective cost well above the quoted price. Check how change requests are estimated, at what rates, and that no work starts before you approve it in writing.

7. Tools and licences. Device clouds, test management tools and proprietary accelerators can be charged directly or folded into the rate. If folded in, you may lose access when the contract ends.

Build a like-for-like comparison

Give every vendor the same scope and the same assumptions in the RFP, and ask for pricing in the same structure:

Line	What to ask for
Roles	Each role, level, number of people, share of time
Rates	Rate per role per day or hour, and the currency
Management	Any lead, delivery or account management charged
Onboarding	Cost and duration of ramp-up
Tooling	Every tool or licence charged, and who owns the account
Out of hours	Multiplier and approval rule
Changes	Rate and process for change requests
Expenses	Travel and other expenses, and any cap
Increases	Rate lock period, index and cap

Then compare the total over the term, including your own management time. A vendor whose model needs more direction from you costs you more in internal time, even at the same rate. See QA engagement models explained.

Price signals worth checking

The red flags checker looks for pricing patterns in proposal text, including:

• hours billed with no outcome measures at all;
• change requests billed without agreed rates or process;
• automatic renewal with a fixed annual rate increase;
• a rate far below the other bids with no explanation of how the work will be done at that price.

A very low bid is worth a direct question: which assumptions make this price possible? The answer often shows a smaller team, a more junior mix or a narrower scope than you asked for.

Contract terms that protect the rate

Put the pricing structure into the contract, not only the proposal. The contract clause builder has clauses for:

• Rate lock. Rates fixed for an initial period, with later changes limited to once a year, with notice, and capped by a named index.
• Timesheets. Hours recorded by person and activity, visible to you, and approved before invoicing.
• Change control. No change and no extra charge until both sides sign.
• Team mix. The seniority mix in the proposal as a commitment, with changes needing your approval.

For how staffing changes affect cost after signature, see how QA vendors staff projects.