Plans differ by how many campaigns run at once, whether tester pools carry across releases, and how hands-on the support is. Every engagement is confirmed in writing before work starts.
Each plan is scoped per engagement. No fixed rate is published, because the tester count and window length differ between apps.
For a single app heading into its first closed test.
Scope and rate are confirmed before your campaign starts.
For teams shipping regular releases and running tests back to back.
Scope and rate are confirmed before your campaign starts.
For studios with several apps in flight and auditing requirements.
Scope and rate are confirmed before your campaign starts.
Capabilities rather than invented numbers, so nothing here is a figure we cannot stand behind.
| Capability | Starter | Growth | Scale |
|---|---|---|---|
| Tester roster management | |||
| Campaign tracking | |||
| Participation monitoring | |||
| Testing feedback records | |||
| Concurrent campaigns | One | Multiple | Multiple apps |
| Reusable tester pools | |||
| Onboarding walkthrough | |||
| Campaign reporting exports | |||
| Shared team access | |||
| Named point of contact |
The short version. The full terms are on the Refund Policy page.
How engagements are scoped, billed and supported.
Tell us about the app, your account type and the window you are working towards. We come back with what the engagement covers and what it costs.
Policy content reviewed 2026-09-27.