FAQ
Straight answers about scope, pricing, and evidence.
Read the service details before you brief a test or apply as a tester.
Who is the service for?
Kenya-based founders, startups, and small businesses buying testing for a mobile app, website, or desktop application.
What does a tester submit?
Each finding includes a title, severity, category, reproduction steps, expected result, actual result, device, operating system, browser where relevant, environment notes, and visual evidence.
Can I choose how many testers I need?
Yes. Tiers control depth, not tester quantity. Final capacity is checked against approved, available testers who match the selected environment.
How is the total calculated?
The tester rate for the selected tier is multiplied by your tester quantity. One tier platform fee is then added to the order.
How do retests work?
A paid retest is linked to the original project and report. You select the fixes to verify and returning testers to invite. New testing scope needs a new initial order.
Can a project require an NDA?
Yes. An assigned tester must sign the project-specific NDA before access is revealed when that requirement is enabled.
What files can I provide?
Use secure distribution links such as app-store testing links, Firebase App Distribution links, website URLs, or private desktop download links. Direct executable uploads are excluded at launch.
When can I dispute a report?
You have seven days after report publication to accept it, ask for clarification, or open a dispute.
What happens if fewer testers are recruited?
You may accept a smaller group with a transparent refund for the unfilled slots or cancel under the refund policy.
Does the service guarantee every issue will be found?
No. Findings apply to the agreed scope, assigned testers, environments, and testing dates.