ManagedQA PartnersSee plans

Onboarding, cadence, reporting, escalation

How it works

One person to ask, a checklist every release runs against, a suite that grows in your repository, and a report you can forward. Here is the month, the release, and the escalation path.

Termscritical flow (a path a user takes that costs money or trust if it breaks: sign-up, checkout, invite, export) · verdict (a one-word release result (pass, pass with findings, fail) with the findings and the checklist version behind it) · CI (the pipeline that builds and tests every change before it can be merged or deployed) · Playwright (an open-source framework that drives a real browser through your product's flows) · flaky test (a test that fails without a code change; it gets a written cause and a fix, never a mute)

The first month

  1. Day 1

    Access and cadence

    Read access to the repository, a staging environment, your release cadence, and the named contact on your side. Nothing to install.

  2. Day 2-3

    Flow map and first run

    We map the critical user flows, run the checklist against the current build and send the first list of findings by severity.

  3. Day 4-7

    First verdict, suite scaffold

    The first release gets a written verdict. The automated suite is scaffolded in your CI, in your repository, under your ownership.

  4. Week 2 to month 2

    Coverage to the plan limit

    Automated coverage grows each week and reaches the plan's flow limit by the end of month 2. From week 2 every release runs the checklist and the suite, and the monthly report starts.

The first two steps are the same for every plan. The plan sets the flow limit that step four grows toward and the surfaces it covers. Limits side by side.

Every release

You tell us a release candidate is ready (or CI does). We run the checklist items your plan includes and the automated suite, and write a verdict, signed by the tester, naming the build and the checklist version.

A written verdict per release: pass, pass with findings, or fail, with findings listed by severity and the checklist version used.

  • Pass No findings at critical or high severity.
  • Pass with findings Findings at high or below; ships with the findings scheduled and re-tested next run.
  • Fail A critical finding. The release is held until the item passes; re-test the same day where the fix allows.

Escalation

A critical finding reaches your named contact within 4 business hours of us confirming it.

Tooling

Playwright for web (browser flows), Appium or Detox for mobile (device flows), k6 for performance smoke (load in your CI). Everything runs in your CI and lives in your repository.

No agents of ours hold write credentials to your production. That is checklist item DR-03 and it applies to us too.

Every month

A monthly report by the 5th business day: releases tested, verdicts, findings by severity, coverage growth against the plan limit, flaky-test handling, and next month's plan.

Coverage is counted in critical flows automated against the plan limit (30, 80 or 200 by month 2), never as a percentage of code. Flaky tests are never silenced: each gets a written cause and an action and stays in the report until it has run clean for a month. A synthetic sample shows the format.

Growth includes a biweekly call and Scale a weekly one; Starter is async. Every plan has one named QA lead who reads your product for as long as you are a customer.

What changes when you leave

Cancel with 30 days' notice. The suite, the scripts and every report are already in your repository and your inbox. Nothing is hosted by us that you would lose. The checklist stays public.

Guarantees, written and shown on every plan

  1. 01A named QA lead within 3 business days of start
  2. 02First release verdict within 7 days of onboarding
  3. 03Every release tested against the published checklist version in force
  4. 04Monthly report delivered by the 5th business day
  5. 05If a release ships with a critical finding we marked as passed, the next month is free

Exit terms. Monthly. Cancel with 30 days' notice. No setup fee. The coverage audit fee is credited to the first month of any plan started within 60 days.

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.

Read the full list

Questions

What is managed QA?
A service that owns testing for your product on a flat monthly fee: a published checklist run on every release, an automated suite in your repository that we write and maintain, a written verdict per release, a monthly report, and a named QA lead you can ask. The scope is the plan's limits.
Done for you QA testing
That is the model, with two differences from the phrase: the checklist is public, so you can see exactly what is done, and the suite lives in your CI under your ownership, so nothing is done for you that you could not keep.
What does a monthly QA report include?
Releases tested with verdicts, findings by severity, coverage growth in flows against the plan limit, flaky-test handling with causes and actions, and next month's plan. A synthetic sample is on the sample report page.
What should a release checklist include?
For AI-assisted code: secrets, access control, auth, payments, LLM features, error handling, performance, migrations, deploy and rollback, and mobile gates. Ours has 53 items with pass criteria and is published in full.

Start with the audit

5 business days, $1,200, credited to the first month. Or email about a plan directly.

Start with the auditSee plans