Free tool

See what your tests cost each year

Enter four numbers to see the hours and dollars your team spends on testing and test maintenance, and what you could get back. The results update as you type.

Runs in your browserNo sign-upNothing saved or sent

Everyone who runs or fixes tests: QA engineers, SDETs and developers.

One person's salary, benefits and overhead, per hour.

Per person: running tests by hand, like regression and smoke passes.

Per person: fixing broken selectors, updating scripts and chasing flaky tests.

What your tests cost each year

$124,800in team cost
1,560team hours

Maintenance alone is 780 hours and $62,400 of that.

Each person's 40-hour week

  • 5 hours on maintenance
  • 5 hours testing
  • 30 hours on everything else

Of course it's a pie chart.

That's 25% of each person's week.

What you could get back

$93,600a year
1,170team hours a year

Estimate: 75% of your testing and maintenance hours, the cut in manual testing effort Fi got with Pie. That's one customer's result, so yours will differ.

How Fi cut manual testing effort by 75%

Release validation at Fi went from two to three days to a few hours.

How the math works

Four numbers and one formula, so you can check it by hand or rebuild it in a budget sheet.

Count the hours

team size × (testing + maintenance hours) × 52 gives your team's hours for the year.

Price them

hours × loaded hourly cost gives what those hours cost.

Apply Fi's rate

hours and cost × 75% gives the estimate of what you could get back.

What it counts

  • Running tests by hand, like regression and smoke passes
  • Fixing broken selectors and updating scripts after a UI change
  • Chasing flaky tests

What it leaves out

  • Bugs that reach your users, and releases that wait on testing
  • Test tools, device labs and CI minutes
  • What Pie costs, so weigh that against the estimate

FAQ

Did we miss a question?
Email us directly →

How do I work out my weekly maintenance hours?
Count the time your team spends fixing broken selectors, updating scripts after a UI change and chasing flaky tests, then divide by the number of people. Our guide to the cost of test maintenance walks through it in five steps.
What is a loaded hourly cost?
What one person costs your company per hour, with salary, benefits and overhead included. The box starts at $80 as an example, so replace it with your own figure.
Where does the 75% come from?
From Fi, which makes smart GPS collars for dogs and cats. Fi reduced manual testing effort by 75% with Pie. That is one customer's result, so your number will differ.
Can I price test maintenance on its own?
Yes. Set weekly testing hours to 0, and every number on the page counts maintenance alone.
Does the estimate include what Pie costs?
No. It shows the hours and dollars your team could get back, before any tool cost. The calculator is free, and Pie itself is a paid product.
Is what I enter saved or sent anywhere?
No. The math runs in your browser, and nothing you type is saved or sent to Pie or anyone else.

Give your team those hours back.

Pie runs your tests like a real user on every build or pull request and reports what broke.