Entry product
Coverage audit: what is tested, what is not, and what to do first
In 5 business days you get a map of your critical user flows with their current coverage, a risk list from the AI-code failure catalogue in priority order, a recommended plan with a 30-day coverage plan, and a 45-minute walkthrough. The fee is credited to the first month of any plan started within 60 days.
$1,200 one-time
Termscritical flow (a path a user takes that costs money or trust if it breaks: sign-up, checkout, invite, export) · row-level security (database rules that decide which rows each signed-in user may read or write) · CI (the pipeline that builds and tests every change before it can be merged or deployed)
What you receive
Included
- Map of critical user flows and their current coverage
- Risk list from the AI-code failure catalogue, prioritised
- Recommended plan and 30-day coverage plan
- 45-minute walkthrough
Not included
- Automated tests written for you
- A release verdict on a specific build
- Ongoing monthly reporting
Terms. One-time fee, invoiced on delivery. Delivered within 5 business days of access being granted. Credited to the first month of any plan started within 60 days.
Five business days
- Day 1
Access
Read access to the repository and a staging environment. A 30-minute call to list the flows that matter to revenue and to trust.
- Day 2-3
Map and scan
We map the critical flows, record what covers each one today (tests, monitoring, nothing), and run the catalogue patterns against the codebase and the running app.
- Day 4
Risk list
Findings ordered by severity, each mapped to a pattern and to the checklist item that would catch it on every release.
- Day 5
Walkthrough
45 minutes: the map, the risks, the recommended plan and a 30-day coverage plan you can run yourselves or with us.
Who it is for
A team whose codebase is now mostly AI-assisted and whose last visible break made someone ask what is actually tested. A founder moving an app built with Lovable or Bolt to a real team. A CTO who has been sent an enterprise security questionnaire with a testing section and needs a true answer.
The risk list starts from documented failure patterns, not from a generic template. In one scan of 5,600 apps built with prompt-to-app platforms, researchers found more than 2,000 vulnerabilities and over 400 exposed secrets (Source: Escape, 2025-10-29 · verified 2026-09-21). The audit tells you which of those patterns apply to your code and which checklist item would catch each one.
Guarantees, written and shown on every plan
- 01A named QA lead within 3 business days of start
- 02First release verdict within 7 days of onboarding
- 03Every release tested against the published checklist version in force
- 04Monthly report delivered by the 5th business day
- 05If a release ships with a critical finding we marked as passed, the next month is free
What we cannot do
We test against a defined scope and report what we find. We do not guarantee bug-free releases. We do not write your product code. We are not a certified penetration-testing firm and do not issue compliance attestations. Coverage limits per plan are explicit and apply.
The five guarantees apply to plans. For the audit, the commitment is the five-business-day turnaround and the credit.
Questions
QA coverage audit
Is QA as a service worth it?
Testing vibe coded apps
Email about the audit
Tell us team size, release cadence, stacks and AI tools. We reply within 24 hours on business days.