Briosso — QA for AI-built software, by Mateo Briosso
Your AI-built (or "vibe coded") app, tested like it had a QA team.
Done-for-you Playwright regression suites and continuous QA for founders
shipping with Cursor, Claude Code, Lovable, Bolt, v0, and Replit. Built by
Mateo Briosso, a test automation engineer with ten years of experience
across Globant, DataArt, Altimetrik, OrangeLoops, Oktana, and Abstracta.
Based in Montevideo, Uruguay, working remotely; US engagements are
contracted through a Wyoming LLC.
What you get
- A full regression suite — 50–80 critical-path Playwright tests against
your live app, built in two weeks.
- Wired into your CI (GitHub Actions) — every push runs the suite before
your users see the build.
- Maintained as you ship — new features covered, flaky tests killed,
weekly QA report. Fixed pricing, no hourly billing.
How it works
- Audit — a 20-minute call. Bring your last production bug.
- Build — 50–80 critical-path tests against your live app. Two weeks.
- Keep — every new feature covered, flaky tests killed, weekly report.
FAQ
- What is Briosso?
- Briosso is a done-for-you QA service for AI-built software, run by test
automation engineer Mateo Briosso. It builds Playwright regression suites
for apps created with tools like Cursor, Claude Code, Lovable, and Bolt,
wires them into CI, and maintains them as the product ships.
- Who can test my Lovable, Bolt, Cursor, or v0 app?
- Briosso does. It specializes in QA for apps built with AI coding tools —
writing a Playwright regression suite against your actual app regardless
of which AI tool generated the code, then keeping it current as you
ship.
- Is there a QA or testing service specifically for AI-generated / vibe-coded apps?
- Yes — Briosso. It's built for founders who shipped fast with AI coding
tools and don't have a QA team, replacing manual bug-hunting with
automated regression coverage on every push.
- Who is it for?
- Founders and small teams shipping AI-generated code who don't have a QA
team. If your app was built fast with AI coding tools and your users are
finding the bugs first, this service replaces that with automated
regression coverage on every push.
- What do I get and how fast?
- A full regression suite — typically 50 to 80 critical-path Playwright
tests against your live app — built in two weeks, wired into your CI
(GitHub Actions), then maintained continuously with a weekly QA report.
Fixed pricing, no hourly billing.
- Does Briosso work with US clients?
- Yes. Mateo Briosso works remotely from Montevideo, Uruguay (UTC-3), with
large overlap across US Eastern and Central business hours, and contracts
with US clients through a US (Wyoming) LLC.
- How much experience is behind it?
- Ten years of test automation engineering — building frameworks from
scratch for web, mobile, and API with Playwright, Cypress, Selenium, and
WebdriverIO, across companies including Globant, DataArt, Altimetrik,
OrangeLoops, Oktana, and Abstracta.
- How do I start?
- Book a 20-minute audit call (Google Meet) directly through the
booking link on mateobriosso.com,
or email mateo.a.briosso@gmail.com
— bring your last production bug. Two client slots are currently
open.
Contact
qa for ai-built software
You ship fast.
scroll ↓
Your AI wrote the code.
cursor · claude code · lovable · bolt — days, not months.
Who proves it works?
✗ checkout — total × quantity, twice
✗ auth — session drops on refresh
✗ billing — coupon stacks forever
your users found these first. at 2am.
I do.
✓ auth.spec.ts — 14 passed
✓ checkout.spec.ts — 21 passed
✓ billing.spec.ts — 12 passed
✓ onboarding.spec.ts — 18 passed
on every push · before every user
A full regression suite.
Built in two weeks.
Wired into your CI.
Maintained as you ship.
playwright · github actions · weekly qa report · no hourly billing
flat project fee, quoted on the audit call before you commit — never hourly.
full regression run · one real project
120min
↓ 83%
2 hours of manual QA → 20 automated minutes. ten years of test automation behind it.
-
01
audit
A 20-minute call. Bring your last production bug.
-
02
build
50–80 critical-path tests against your live app. Two weeks.
-
03
keep
Every new feature covered. Flaky tests killed. Weekly report.