QA Health Check & Audit

You can't fix what
you haven't diagnosed.

An independent, scored assessment of your test coverage, tooling, and processes. Delivered in 1–2 weeks as a prioritised action plan. The lowest-risk way to start.

The problem

Most teams don't know
what they're not testing.

Coverage metrics tell you what percentage of your code has a test touching it. They don't tell you whether those tests would catch a real failure. They don't tell you which untested paths carry the most business risk. And they don't tell you whether the QA process will hold under the pressure of a fast release.

Most engineering leaders know something is off — releases feel riskier than they should, incidents surface in production that feel like they should have been caught, or the team has accumulated tooling that nobody fully trusts. The problem is they don't have a clear picture of where the gaps actually are.

The QA Audit produces that picture. An independent, structured assessment with a risk score attached to every finding and a prioritised action plan so you know exactly what to do next — whether you do it alone or with PrsnQA.

What the audit covers

Four areas. One scored report.

01

Coverage gap analysis

What's being tested, what isn't, and where the business risk sits in the gaps. Not just which files have tests, but which user journeys, integration points, and edge cases are uncovered — and how much that matters for this product.

02

Tooling assessment

What's in use, what's redundant, and what's missing. Test management, automation frameworks, CI pipeline, defect tracking — reviewed for fitness for purpose and whether the investment is actually paying off.

03

Process review

How testing is integrated into the development and release cycle. Where QA sits in the process, how defects are triaged, what the release criteria are, and whether the process survives pressure — or only works when there's no urgency.

04

Prioritised action plan

Every finding scored Critical / High / Medium by business impact. A prioritised list of what to fix first, what to fix next, and what to consciously defer. Written so you can act on it independently — or use it as the brief for a follow-on engagement.

How it works

Five steps. 1–2 weeks. Fully remote.

01

Scoping call

30 minutes. Understand the team size, tech stack, and what's worrying you. Confirm the exact price.

02

Access & review

Read-only access to your test repository, CI pipeline, and any existing QA documentation. No installation required.

03

Assessment

1–2 weeks of structured remote analysis across the four audit areas. No disruption to your team's workflow.

04

Report delivered

Written scored report with every finding rated by business impact and a prioritised action plan you can act on immediately.

05

Readout session

Optional 60-minute walkthrough of the findings with your engineering and product leadership. Questions, decisions, next steps.

Why this works

An honest assessment is worth more
than a reassuring one.

The value of an audit isn't the document — it's the independence. An internal team reviewing its own QA practice will miss the things they've normalised. An external assessment surfaces what's been invisible, scores it objectively, and gives you a plan that isn't shaped by internal politics.

Independent

No vested interest in the findings

The report reflects the actual state — not what the team hopes it is or what would justify a larger engagement.

Scored

Risk-rated, not just listed

Every finding is rated by business impact. You know which gaps matter and which can wait — so you can make a decision, not just a to-do list.

Actionable

A plan, not just an assessment

The report tells you what to do next. You can act on it with your existing team or use it as the brief for a follow-on engagement.

This is right for you if...
✓  A production incident has made you question your test coverage
✓  You're about to invest in QA tooling and want to know what you actually need
✓  You can't answer basic questions about your quality risk
✓  You're scaling and want a quality baseline before you grow
✓  You want an independent view before hiring for QA
✓  You've inherited a codebase and don't know what state the testing is in
Investment

Fixed-price. No surprises.

QA Health Check & Audit
£1,200–£2,000
fixed price, ex-VAT · confirmed after scoping call
  • Scored report with every finding risk-rated
  • Prioritised action plan
  • Optional readout session included
  • Delivered in 1–2 weeks, fully remote
  • Fee offset against any follow-on engagement within 60 days

Price is within this range based on team size and codebase complexity. Confirmed on the scoping call — no surprises after that.

Common questions

What people ask before they book the call.

How much does a QA audit cost?
Between £1,200 and £2,000, fixed-price and confirmed after a free scoping call. Price is driven by team size and codebase complexity — confirmed before work begins, with no variable costs after that.
How long does a QA audit take?
1–2 weeks, conducted fully remotely with read-only access to the test repository and CI pipeline. No disruption to the engineering team's workflow.
What does a QA audit cover?
Coverage gap analysis, tooling assessment, process review, and a prioritised action plan with every finding risk-rated Critical, High, or Medium by business impact. Delivered as a written report, with an optional 60-minute readout session.
Do I need to commit to further work after the audit?
No. The audit is a standalone engagement. You receive a prioritised action plan you can act on with your existing team. The audit fee is offset against any follow-on engagement contracted within 60 days, but there is no obligation to proceed.
Start here

The lowest-risk way to begin
is also the most useful.

Book a free 30-minute scoping call. You'll leave with a fixed price, a clear scope, and a start date. No commitment beyond that.