Skip to main content

Agentic QA with an engineer in the loop.

Playwright tests for your web app’s critical flows in one month, in a repository you own.

Most bugs are still found by customers.

  • Manual QA can’t keep pace

    Checking every flow by hand before a release takes days, so when you ship weekly or daily, most releases go out without a full regression pass.

  • Tests go stale

    AI tools write tests fast, but after a redesign some of them fail every run and nobody fixes them.

  • Hiring takes months

    Finding a QA automation engineer takes months, and building a suite from zero takes longer.

Both bugs were in critical flows that had no tests, so customers found them first.

What is agentic QA?

Agentic QA, also called agentic testing, is software testing where AI agents write the tests and an engineer reviews every one.

QA agents explore your app, draft Playwright tests for your critical flows and update them when your product changes.

A senior QA engineer decides what to test, reviews every change before it’s merged and checks each failed run for a real bug.

Built in a month, then kept up to date every month.

We start by understanding your workflows, data architecture, and release cadence. Before any work begins, you receive a detailed roadmap with guaranteed, fixed pricing.

QA Care

Monthly

We keep the tests in step with your product.

  • Specs updated when your product changes
  • Every failed run checked within 1 business day
  • Real bugs filed in Linear, Jira or GitHub Issues, with steps, video and trace
  • Up to 2 new critical flows a month
  • A short monthly report

Billed monthly, and you can cancel any month and keep the tests.

From first call to a working test suite in a month.

The month starts once staging and test accounts are ready, and ends with the suite handed over to your team.

  1. 01

    First call

    Scoping call

    You name up to ten flows and get a fixed price within two business days.

  2. 02

    Before day 1

    Staging and test accounts

    The month starts when staging, test accounts and sandboxes are ready.

  3. 03

    Week 1

    Flow map

    We walk each flow on staging and write it down step by step.

  4. 04

    Weeks 1–4

    Write the specs

    Agents draft a Playwright spec for each flow, and a senior QA engineer reviews it before it’s merged.

  5. 05

    Week 4

    Handover

    You get the finished suite and a README for your team.

  6. 06

    Every month

    Keep them current

    We update the specs as your product changes and check every failed run.

Only real bugs reach your team.

With QA Care, we look at every failed run within one business day, before you hear about it. If it’s a real bug, you get a ticket with the steps, the browser, a video and the Playwright trace, and if the test is out of date, we fix the test.

WEB-117 · sampleBlocks release

Checkout rejects names with an apostrophe

  1. Add any item to the cart
  2. Enter “Siobhán O’Neill” as the cardholder name
  3. Press Pay → “Please enter a valid name”
Expected
Payment goes through
Where
Safari · iPhone · also WebKit in CI
Evidence
Video 0:14 · Playwright trace
Checked by a senior QA engineer

Agents do the typing, but a senior QA engineer is responsible for your tests.

Many teams build end-to-end tests themselves with AI agents, then find that writing them was the easy part and the real work is test data, flaky runs and checking every failure.

Quick BrainsHire a QA engineerDIY with AI agentsQA platform
Critical flows testedWithin one monthMonths to hire, then the buildWhen someone has timeDays to weeks
Who decides what to testA senior QA engineer, with youYour hireWhoever writes the promptThe vendor’s engineer
Test data, logins, sandboxesSet up in month oneYour hire builds themYour developers build themThe vendor sets them up
Flaky testsFixed before HandoverUp to your hireFixed when someone has timeThe vendor handles them
Failed runs checkedWithin 1 business day, with QA CareWhen your hire is inWhen someone noticesBy the vendor
Where the tests liveYour repository, plain PlaywrightYour repositoryYour repositoryThe vendor’s platform
If you stopThe tests keep running in your CIYou hire againThe tests go staleDepends on the vendor’s export
CostFixed price, then an optional monthly feeA full salaryYour developers’ timeA monthly subscription

Scroll the table sideways to compare all four.

Questions teams ask on the call

Are the tests written by AI?

Drafted by AI, then run, corrected and reviewed by a senior QA engineer before they reach your repo. You get plain Playwright code your developers can read and change.

Will flaky tests block our releases?

No. The tests run in your CI, but from their own repository, so a failing test never blocks your app’s pipeline. They run on a schedule and after each deploy to staging, and results go to a shared Slack channel. Once they’ve proven stable, you can make them a required check before merging if you want to.

Do we own the tests?

Yes. They’re plain Playwright in a new repository in your GitHub organisation from the first commit. Nothing depends on our tools, so you can stop after the first month and keep everything.

Is this QA outsourcing?

Yes, we do the testing work for you. Unlike most QA outsourcing, the tests are yours: they live in your repo and you can take them over at any time.

What access do you need?

A staging URL, a test account for each role, and sandbox mode for payments and email. Read access to your code helps the agents learn your product, but it’s optional. We never need production data or passwords.

What does it cost?

It depends on how many critical flows you need covered. After a 30-minute call, you get a fixed price for QA Launch within two business days. QA Care is a flat monthly fee.

What if it takes longer than a month?

We keep working at no extra cost. The month starts once staging and test accounts are ready, and if the suite isn’t finished by the end of it, we carry on until it is.

QA services

A month from now, your critical flows are tested.

Book 30 minutes and bring a staging URL and the flow you worry about most, and you get a fixed price within two business days.