Founding pilot open — first 10 teams
Real people break your app before your users do.
You shipped fast. Nobody has tried an emoji in the postcode field yet. Five vetted testers hammer your app for three days on real devices — you get a ranked bug report with screen recordings, not a shrug.
Checkout total shows "£NaN" when the quantity field is left empty
Steps to reproduce
- Add any item to the basket
- Clear the quantity field, tap Checkout
Expected
Quantity required, button disabled
Actual
Total = £NaN, payment sheet opens
VALID · £25 PAID
How a Launch Sprint works
No sales call, no annual contract. Book a sprint, tell us what you're shipping, and get out of the way.
Day 0 — Brief
You set the scope
A short brief: what the app does, what's in scope, what's already known-broken, which devices matter. You authorise the testing — nothing happens without it.
Days 1–3 — Break
Five testers, real devices
Vetted human testers use your app the way real users do: impatiently, on a train, with an empty battery and a comma in the price field. Every bug is filed with repro steps and a screen recording.
Day 4 — Report
Ranked, deduplicated, honest
We triage every report: duplicates merged, invalid ones binned, the rest ranked by severity. You get one document your team can work through top to bottom.
The Launch Sprint — founding price
First 10 teams · price locked before we launch the platform
- 5 vetted human testers, 3-day sprint
- Real devices — iOS, Android, desktop & mobile web
- Every bug: repro steps + screen recording
- Triaged & ranked by severity, duplicates removed
- Functional & input QA — forms, flows, edge cases
- Report delivered as a doc + export to GitHub Issues
Reserve a founding slot
No payment now. We'll email you a short brief and a payment link when a sprint slot opens — usually within a week.
Get paid to break things
A sprint takes two to three hours of focused testing on devices you already own. File clear bugs with recordings, get paid per valid find — from a budget the client has already committed.
| Severity | What it means | Payout |
|---|---|---|
| P0 | Crash, data loss, payment broken | up to £25 |
| P1 | Feature unusable, ugly workaround | up to £12 |
| P2 | Cosmetic, copy, minor friction | up to £5 |
Every sprint pays from a guaranteed pool, split by contribution — serious bugs earn the biggest share, and if the app is very buggy the pool divides proportionally. First valid reporter wins a bug; duplicates earn nothing. Typical founding sprint: £20–35 per tester. Rates rise with your track record.
Join the mob
The mob starts small and vetted: you'll get a short paid trial task first. Good reports get you into founding sprints.
Questions you should ask
Is this security testing?
No. Sprints are functional and input QA — broken flows, crashes, edge cases, things users actually hit. Testing only happens on products you own or are authorised to test, within the scope you set in the brief. No penetration testing, no third-party targets.
Who decides whether a bug is valid?
We do — not the tester, not the client. A bug is valid if it's reproducible from the filed steps, in scope, not on your known-issues list, and not a duplicate. Every valid bug comes with a recording, so there's nothing to argue about. Payouts come from the sprint fee, which is committed before testing starts.
What can I put through a sprint?
iOS and Android apps (TestFlight or APK), web apps, and SaaS products. Pre-launch or already live. If it has forms, flows, and users, it qualifies.
Why so cheap? What's the catch?
The founding price is under-priced on purpose: we're proving the model before building the full platform, and the first ten teams pay for that with feedback and a testimonial. The catch is the queue — sprints run one at a time for now.
When does the full platform launch?
Founding sprints run hands-on now. The self-serve platform — post a brief, escrow a budget, testers worldwide — ships once ten founding sprints are done and the model has earned it.