We're not going to hand you our entire playbook — matching logic and QA scoring are how we keep quality consistent, and that's the part we keep to ourselves. But here's exactly what happens between your brief and your report.
Category, package size, and what you actually want to learn — a specific flow, a build, a set of videos or posts, whatever applies.
We pull from our vetted pool based on device, platform, and audience fit for your category. We don't publish our exact matching criteria, but we do screen for reliability and past report quality before anyone is invited to a job.
Every tester works from the same category-specific framework, so a report from tester #1 and tester #12 are actually comparable.
Submissions are checked for completeness and specificity. Vague or low-effort reports get sent back for revision or replaced — they never reach you as-is.
Every tester's report, plus a summary that rolls up the patterns that showed up more than once.
Growth and Scale packages include a follow-up round if you want testers to clarify or dig into something specific.