Tester Management
Keep a single, current roster of everyone testing your app.
Google Play Closed Testing Made Simple
Run the campaign from one place: build the tester roster, see who actually opted in and stayed active, and watch the testing window close. The test still runs in your Play Console. You just stop tracking it in a spreadsheet.
- No Play Console access needed
- Personal and organisation accounts
- Roster, window and feedback in one record
Closed testing is not hard. Keeping it accurate is.
Every failed campaign we hear about fails on bookkeeping rather than testing: the roster drifts, participation is assumed, and the window is tracked somewhere nobody looks.
Invites counted as testers
Twelve invitations accepted in conversation is not twelve testers opted in. Collapsing the two numbers is how a campaign looks healthy on day nine and is not.
The roster drifts
A spreadsheet is accurate the day it is made. Without a reason to update it during the window, it quietly stops describing reality.
Nobody notices a dropout
Testers do not announce that they stopped opening the build. The gap surfaces at the end, when replacing anyone costs you the window.
Days elapsed is a guess
The one number that decides whether you can apply is the one that gets recomputed from memory the week you fill the form in.
Four stages, in order
Setup is an afternoon. What the four stages buy you is a testing window you can describe precisely, three weeks later, without reconstructing anything.
Create the campaign
Name the app, record the build under test and fix the testing window you are committing to. The dates exist before the testers do.
Build the roster
Import the addresses you already have, or start a new list. Each tester is recorded against the Google account they will opt in with.
Run the window
Opt-in and activity are tracked separately and continuously, so anyone going quiet is visible while replacing them is still an option.
Close out and keep the record
Findings stay attached to the build they came from. The campaign summary records the window, participation and feedback as they actually were.
What the workspace does
Eight capabilities. Six are in the product today and two are still being built, which is why those two say so.
Campaign Tracking
Every campaign has a start date, a target and a current state.
Testing Progress Dashboard
See how far through the testing window you are.
Participation Monitoring
Distinguish invited, opted in, active and inactive testers.
Testing Feedback
Collect findings in a structured, per-campaign record.
Campaign History
A durable record of every test you have run.
Notifications and UpdatesUpcoming
Reminders before a tester goes quiet.
Testing ReportsUpcoming
Exportable campaign summaries.
What a campaign actually records
Five things, each of which answers a question somebody has to answer later. Everything else on this page is a consequence of keeping these accurate.
- Testing window
- Exact start and end date
- Opt-in state
- Per tester, with the date
- Activity
- When the build was last opened
- Findings
- Against a build and a device
- Interruptions
- Recorded, not smoothed over
Because the record is written during the window rather than after it, the dates in it are the dates the campaign actually ran.
Plans, by how many campaigns you run
Plans differ by concurrent campaigns, whether tester pools carry across releases, and how much hands-on support you want. Rates are agreed per engagement and confirmed in writing first.
Starter
For a single app heading into its first closed test.
Rate on request
Scope and rate are confirmed before your campaign starts.
- One active testing campaign
- Tester roster management
- Campaign tracking and progress dashboard
- Participation monitoring
- Structured testing feedback
- Campaign history
- Campaigns
- One at a time
- Tester roster
- Scoped at kickoff
- Testing window
- Single release cycle
- Support
- Email support
Growth
RecommendedFor teams shipping regular releases and running tests back to back.
Rate on request
Scope and rate are confirmed before your campaign starts.
- Multiple concurrent campaigns
- Everything in Starter
- Reusable tester pools across releases
- Per-campaign feedback records
- Priority email support
- Onboarding walkthrough for your team
- Campaigns
- Multiple concurrent
- Tester roster
- Reusable across releases
- Testing window
- Continuous release cycles
- Support
- Priority email support
Scale
For studios with several apps in flight and auditing requirements.
Rate on request
Scope and rate are confirmed before your campaign starts.
- Everything in Growth
- Multiple apps under one account
- Campaign reporting exports
- Shared team access
- Named point of contact
- Review of your testing evidence before submission
- Campaigns
- Multiple apps, multiple campaigns
- Tester roster
- Shared pools per app
- Testing window
- Rolling, per app
- Support
- Named point of contact
Concrete differences, not claims
Each of these describes how the product behaves rather than what we would like it to be.
We do not claim to influence Google
Production access is granted by Google after review. Our job is to make the testing you ran legible, and to say plainly that the outcome is not ours to promise.
Your Play Console stays yours
We never ask for access to your account. You keep the track, the release and the application, which also means you are never locked in to us in order to ship.
Three states, never one number
Invited, opted in and active are tracked separately for the whole window. A flattering single figure becomes a liability the moment you have to justify it.
Built for the second release
Testers stay on the track and rosters carry forward, so the next campaign costs less coordination than the first one did.
Not sure the approach fits?
Both of these pages say what is included and what is not, including the parts that are still being built.
Questions developers ask first
Short answers on how the service works, what testers have to do, and what happens at the end of a window.
Ready to Start Your Closed Test?
Tell us about your app and target timeline. We will confirm scope, tester requirements and the testing window before anything starts.
We confirm the app, the testing window and the tester scope in writing before any campaign work begins.