How to Talk to Clients About Google Play's Closed Testing Requirement

The build is done. The client is expecting a live link. And now there's a two-week Google-mandated waiting period standing between "finished" and "launched" — one the client almost certainly didn't know existed when the project was scoped. How you explain this shapes whether it reads as your team being thorough, or your team being slow.

Say it early, not when it becomes a problem

The single biggest driver of client frustration here isn't the two weeks — it's finding out about the two weeks for the first time after the build is already finished. Mentioning the requirement during kickoff or scoping, even briefly, turns it into an expected step instead of a surprise excuse. A single sentence in the project timeline document does most of the work: "Google requires a mandatory 14-day closed testing period before any new app can go live in production — we build this into the schedule."

Frame it as Google's policy, because it is

This isn't a step your agency invented or could skip if it tried harder. Being specific and factual defuses most pushback: it's a requirement Google applies to every new personal developer account created after November 13, 2023, it applies to every app regardless of who built it, and there's no way to expedite it beyond running the test correctly the first time. Clients generally respond better to "here's Google's actual rule" than to a vaguer "there's some extra testing we have to do."

Give them something to look at during the wait

Two weeks of silence feels much longer than two weeks with visible progress. A simple update — "8 of 12 testers active, day 6 of 14" — turns a black box into a status bar. If you're running the test yourself, this is worth building into whatever project-status update you're already sending. If you're using a testing service, ask whether they provide a progress dashboard or report you can forward or paraphrase to the client directly.

Don't promise a launch date until the test has actually started

A specific date promised before testers are opted in is a date at risk from day one — recruitment delays, a country/region misconfiguration, or a slow release review can all push the actual start of the 14-day clock. Committing to a date only once the closed test is confirmed running gives you a number you can actually hit.

Have an answer ready for "can we just skip it?"

This comes up more than agencies expect, usually from a client who found a forum post about buying old developer accounts or fake testers. Worth having a short, direct answer prepared: the shortcuts that exist carry real risk of the app or account being suspended entirely, which costs far more time than the two weeks it was meant to save — see what actually works, and what doesn't.

FAQ

How do I explain Google's closed testing requirement to a client who's never heard of it?

Frame it as a mandatory Google Play policy, not an agency decision — it applies to every new personal developer account and every app on it, with no way to skip it legitimately.

Should closed testing be mentioned during project scoping?

Yes — mentioning it before the build starts, rather than after it's finished, is the single biggest factor in whether clients see it as expected diligence or an unexplained delay.