Email and profile gate
Tester accounts start with email/profile creation, then demographic, language, device, and network details used for matching.
Verified Nigerian network proof
How we prove supply without inflating the panel.
The honest proof standard is simple: no fake tester counts, no borrowed logos, no synthetic case studies dressed up as traction. Buyers get cohort fit confirmed before payment; public metrics are published only when they are backed by real permissioned data.
Last reviewed 25 June 2026 · Evidence requests: [email protected]
5
Language lanes: English, Pidgin, Yoruba, Igbo, Hausa
0
Fake tester-count claims or borrowed logo walls
Pre-pay
Cohort fit confirmed before payment link
Qualification
Paid-work testers pass gates before buyer delivery.
This is the control path a buyer is paying for: not random strangers from a group chat, and not an unverified gig-market screenshot.
Real-device demo
Testers complete a qualification task so the team can inspect recording quality, instruction following, and device reality before paid work unlocks.
One human, one account
Before paid marketplace or AI-data work unlocks, basic checks confirm one real person per account and reduce duplicate or fraud risk. No emulators, no VPNs, no synthetic personas.
Approval before payout
A task is paid only after review confirms the submission is usable, on-brief, and safe to deliver to the buyer.
Public metric board
What is public today, and what must be confirmed per buyer.
Reviewers asked for active tester counts, completion rates, and replacement rates. We agree those belong here once real pilot volume is large enough. Until then, the safer public proof is a clear status board and buyer-confirmed cohort evidence before payment.
| Metric | Public status | Buyer evidence |
|---|---|---|
| Active qualified testers | Not publicly claimed yetConfirmed cohort roster is shared for accepted fixed-pack work before payment. | Confirmed cohort roster is shared for accepted fixed-pack work before payment. |
| Active-in-last-30-days count | Not publicly claimed yetFor paid pilots, availability is checked against the target profile before invoice/payment link. | For paid pilots, availability is checked against the target profile before invoice/payment link. |
| State / geo coverage | Covered as matching criteria, not inflated as a public mapBuyer briefs can request state/city targeting; accepted scope states which locations can be routed. | Buyer briefs can request state/city targeting; accepted scope states which locations can be routed. |
| Device / OS / network mix | Captured in tester profiles and report evidenceDelivered reports include anonymised device/context fields where applicable. | Delivered reports include anonymised device/context fields where applicable. |
| Language coverage | English, Pidgin, Yoruba, Igbo, Hausa lanes publishedLanguage-specific work is scoped before payment; AI-data work requires separate consent/licence terms. | Language-specific work is scoped before payment; AI-data work requires separate consent/licence terms. |
| Completion / replacement rates | Not publicly claimed until real pilot sample is enoughFixed-pack tester-replacement terms and timing are written before payment. | Fixed-pack tester-replacement terms and timing are written before payment. |
Nigeria-first geography
The public product is designed around Nigerian testers, not a generic global panel with Nigeria as a filter.
- State and city targeting
- Buyer-confirmed cohort fit
- No fake map coverage
Device and network reality
The matching path captures Android/iOS devices and network context because Nigerian product friction often appears on real phones, not emulators.
- Tecno / Infinix / Samsung / iPhone reality
- Mobile-network context
- Evidence included in reports
Language and culture
Language matching supports product research and AI-data work where Nigerian English, Pidgin, Yoruba, Igbo, or Hausa context matters.
- Product-session narration
- AI-data pilots
- Consent before data reuse
Next proof milestone
Publish real pilot stats only when they are permission-safe.
A higher bar is not “more confident copy.” It is real public evidence: active tester count, active-in-30-days count, completion rate, replacement rate, payout totals, and permissioned case studies. This page is the place those metrics will live once they are real and safe to publish.
Buyer-safe ruleIf a metric is not backed by real data or permission, we label it instead of selling it. That is slower, but it survives diligence.