Skip to content

Vibe App Launch Check · £497

You vibe-coded the app. I'll try to break it before your customers do.

Independent human and automated QA for apps built with Lovable, Replit, Bolt, Cursor, Claude Code and ChatGPT. I test the workflows, edge cases and failure points you haven't had time to check. Before real customers find them for you.

£497. Fixed price. One report. A clear go / no-go before you launch.

launch-check-report — sample

Launch Readiness

AMBER

Fix before launch
  • CriticalCheckout fails after session expiry
  • HighMobile navigation traps user
  • MediumValidation message disappears after refresh
Automated smoke tests8 passed1 failed
Illustrative example — not a real customer report

It working for you doesn't mean it's ready for customers.

You built this fast, and you tested it as you went. You know the login flow because you wrote it. You know which button to click first because you put it there.

That's the problem. You're the worst possible person to find the bugs in your own app, because you already know how to avoid them.

Real users don't know your app's unwritten rules. They'll refresh mid-checkout. They'll hit the back button after paying. They'll paste an emoji into a name field. They'll upload the wrong file type, or open your onboarding flow in three tabs at once because they got distracted.

None of that is unusual. It's just what people do. The question isn't whether your users will do something you didn't expect, it's whether your app survives it.

When did someone who isn't you last try to break your app on purpose?

You know the happy path

Sign up → create the thing → pay → done. Clicked in the order you built it, with the data you designed it for.

Real users don't

  • They'll refresh mid-checkout.
  • They'll hit the back button after paying.
  • They'll paste an emoji into a name field.
  • They'll upload the wrong file type.
  • They'll open your onboarding flow in three tabs at once because they got distracted.

Where the cracks usually are.

Every AI-built app has a shape: the parts that got tested because they were fun to build, and the parts that got skipped because they weren't. This is where I go looking first.

  • Signup and onboarding
  • Login, logout and session handling
  • Forms and validation, especially the inputs you didn't plan for
  • Payments and checkout
  • Your three most important user journeys, end to end
  • Mobile and responsive layouts
  • Error states and empty states
  • Data persistence — does it actually save what it says it saved
  • Navigation, back-button and refresh behaviour
  • Basic cross-browser behaviour

If it's a workflow a paying customer will rely on, it's fair game.

Two different jobs. Both matter.

Good QA isn't one technique, it's two, working together.

Human exploratory testing

This is me, in your app, actively trying to break it.

The testing isn't limited to a pre-written script or checklist. I deliberately click the wrong things, enter the wrong data, challenge assumptions and follow paths a real customer might take instead of only the one you designed.

This is how genuinely unexpected problems get found.

Playwright automation

Once we know which journeys matter most, I build automated smoke tests around them — typically five to ten. These re-run your critical paths automatically, so if a future change quietly breaks signup or checkout, you'll know before your customers do.

$ npx playwright test smoke

✓ signup → verify → first login

✓ checkout → payment → receipt

✕ session expiry → resume checkout

8 passed · 1 failed · illustrative example

Human judgement finds the blind spots. Automation protects the journeys you can't afford to break again.

What a finding actually looks like.

You don't need to imagine what you're paying for. Here's the format every issue in your report follows, using a placeholder example to show the shape of it.

Example finding — illustrative

KF-LC-014
Severity
High
Area
Checkout
Issue
Clicking the browser back button after a successful payment returns the user to the payment form, which is still active and can be resubmitted.
Steps to reproduce
Complete checkout → click browser back → click "Pay" again.
Evidence
Screen recording attached, with console and network logs.
Status
Open

Automated Smoke Tests

  • Pass 8 passed
  • Fail 1 failed

Launch Readiness

AMBER

Launch blocked on one critical issue and one high-severity issue.

Illustrative example — sample data, not customer results

Every issue in your report is rated Critical, High, Medium or Low. Each one comes with clear reproduction steps and evidence attached. No guessing between "there's a bug somewhere" and "here's exactly what's broken."

What lands in your inbox.

  • A prioritised bug report, ranked by severity
  • Clear reproduction steps for every issue
  • Screenshot and video evidence
  • Automated Playwright test results for your critical journeys
  • A RED / AMBER / GREEN launch-readiness assessment
  • Practical recommendations, not just a list of problems
  • A short walkthrough of the results

You'll know exactly what's broken, how bad it is, and what to fix first.

Four steps. Clear from start to finish.

  1. 01

    Send access

    You give me access to your staging app and a test account. No production access needed.

  2. 02

    Define what matters

    We agree on the three critical workflows that absolutely have to work, plus anything you're already worried about.

  3. 03

    I try to break it

    Manual exploratory testing across your app, backed by targeted Playwright automation on your critical journeys.

  4. 04

    You get the report

    A prioritised bug report, test evidence, and a clear launch-readiness call.

Built the right way to need this.

  • Solo founders and non-technical founders shipping an AI-built app
  • Small SaaS teams without dedicated QA
  • Apps built with Lovable, Replit, Bolt, Cursor, Claude Code or ChatGPT
  • Micro-SaaS approaching launch
  • Founders about to charge real customers real money
  • AI-development freelancers and small agencies who want to QA a build before handover, instead of marking their own homework

Where this isn't the right fit.

  • You want a formal security audit or penetration test
  • You need enterprise-scale load testing
  • You need regulatory or compliance certification
  • You're testing a native mobile app
  • You want unlimited, ongoing testing rather than a fixed pre-launch check
  • You're not planning to charge customers or put real users through the app yet

If any of that's you, this isn't the right service, and I'd rather tell you now than after you've paid.

£497. One check. One clear answer.

Vibe App Launch Check

£497

Fixed price. One report. Delivered once, before you launch.

What's included

  • A short discovery briefing to understand your app and priorities
  • Manual exploratory QA across signup, forms, navigation, sessions, mobile and error states
  • Testing of your three critical user journeys, end to end
  • Five to ten automated Playwright smoke tests on your most important workflows
  • Basic technical investigation: browser console, network requests, failed API calls
  • A prioritised bug report with reproduction steps and evidence
  • A RED / AMBER / GREEN launch-readiness assessment
  • A short results walkthrough

One fixed price. No hourly rate to negotiate, no scope creep, no surprise invoice.

Book Your £497 Launch Check

Questions before you book.

You already know it mostly works. Find out what "mostly" is hiding.

You built this fast, and it works — for you. Before you find out what it does for everyone else, get someone independent to try and break it first.