See exactly what a buyer receives, how tester identity and payouts work, and which assets are sample, public, redacted, or permission-gated.
Human contact: Chat on WhatsApp · [email protected]
Review the structure before buying: session evidence, AI summary, tester context, invoice format, and what a founder can forward to finance.
The pack should answer the basic procurement question: who are we contracting with, and how is Nigerian personal data handled?
9jatesters' moat is verified, paid contributors. The proof pack makes the controls visible without leaking personal data.
The network proof page separates what is public today from what must be confirmed per buyer before payment.
For Google Play closed testing, buyers need proof that the right users were enrolled and stayed active.
Publish only what is verifiable: turnaround, task completion, rejection rates, and tester coverage once the dataset is available.
Every public pack starts with brief review. Once cohort, SLA, and acceptance criteria are confirmed, the buyer receives a Flutterwave link or invoice.
No client-logo wall until logos are permissioned. No inflated tester counts. No synthetic case studies. Trust is stronger when the claims are smaller and provable.
Verifiable now: RC number, public security/DPA summary, checkout/order flow, network-proof status board, and sample report format. Available under request/NDA: redacted real customer evidence when permission exists. Not claimed yet: customer-logo wall, production case studies, or a real Play Console gallery.
Open the proof pack now, or email your checklist. We clearly label sample/redacted assets and never imply a client logo or case study is permissioned before it is.
Want to see the report format first? View a sample usability report →