How it works

From brief to report

No meetings unless you want one. Everything is written down, because that is the product.

1. You tell us about the product What it does, who it is for, what you are worried about, and how a tester gets in — a link, a build, or a Play closed-testing invitation.
2. We agree the package and you pay half Recruitment does not begin until the deposit is in. That is not a formality: we are committing real people's time.
3. We recruit and brief testers Matched on the devices they actually own. If you need Android 15 on a mid-range phone, that is who tests it.
4. Testing runs Each tester works through a checklist daily and submits a screenshot as proof. You get updates as we go, and anything critical the day we find it.
5. You ship a fix, we check it Give us an updated build inside the testing window and the same testers verify whether the problems you fixed are actually gone.
6. You get the report and pay the balance Findings by severity, reproduction steps, screenshots, tester feedback and what we verified.

What a 7-day week actually looks like

The seven days are a testing window, not unlimited rounds. A typical Standard week runs something like this:

Day 1	Testers start. Setup and first-run problems surface immediately.
Day 2	Eight defects found. We send a preliminary report.
Day 3	You fix five of them.
Day 4	You give us the new build and ask for a retest.
Day 5	Testers verify those five fixes.
Day 6	Deeper use turns up more.
Day 7	Final pass and the consolidated report.

What a fix-verification cycle means

Testers check whether problems we already reported appear to be corrected. It is not the whole product tested again from the beginning.

Your testers never see your users

And you never see our testers. Reports label them "Tester 1", "Tester 2" and so on — you get the device make and model, the findings, and which days each covered. Names, contact details and payment details stay with us. It is in our privacy policy, not just our intentions.