Should Client Apps Publish Under Their Own Developer Account, or Yours? An Agency's Guide
Most agencies answer this question once, by accident, on their first Android project — and then repeat whatever they did the first time without revisiting it. It's worth actually deciding, because the two options carry meaningfully different consequences.
Publishing under the client's own account
What it means: the client (or you, on their behalf, with access) creates their own Play Console developer account, and every app, review, and piece of testing history lives there permanently — independent of your agency relationship.
Pros: the client owns their asset outright, which matters if the relationship ends, if they switch agencies later, or if they want to bring development in-house. There's no ambiguity about who controls the listing, responds to reviews, or can push updates.
Cons: a brand-new client account created after November 13, 2023 means the 12-tester, 14-day requirement applies fresh — every time, for every new client, with no shortcut from your agency's prior experience or existing organization status.
Publishing under your agency's account
What it means: the app lives on your agency's Play Console account, typically as one of several apps you manage, sometimes with the client given collaborator-level access.
Pros: if your agency account is a verified organization account, apps published there can skip the closed testing requirement entirely, per our breakdown of the personal vs. organization distinction. It also means you're not re-learning a new client's Play Console quirks each time.
Cons: the client doesn't own the listing. If the relationship ends, transferring an app and its accumulated reviews/install history to a new account is possible but disruptive, and some clients — reasonably — are uncomfortable with their production app living on a vendor's infrastructure long-term.
A middle path: client-owned organization accounts
The option that gets the best of both usually isn't either extreme — it's helping the client set up and verify their own organization account (not personal) up front. This takes the 4-8 weeks of D-U-N-S verification covered in our organization account post, but once done, the client owns the account outright and is exempt from the closed testing requirement for every future app. For a client planning more than one app, this pays for the upfront delay quickly.
What we'd actually recommend by scenario
- One-off project, client wants full ownership: client's own personal account, run closed testing properly, budget the 14 days into the timeline.
- Ongoing retainer client, multiple apps planned: worth the upfront cost of helping them verify a client-owned organization account — it removes the testing requirement for every subsequent app.
- Fast-turnaround MVP or prototype, ownership not yet decided: agency account short-term is reasonable, with an explicit, written plan for transferring to the client later if the project continues.
Whichever account structure you land on, if a personal-account closed test is on the timeline, the part worth outsourcing is the 14-day engagement itself — real devices, real usage, done the same way for every client app.
Talk to us about Agency pricing →FAQ
Does publishing under an agency's organization account skip closed testing for client apps?
Yes, if the agency's account is a verified organization account and the client's app is genuinely published under it — but the client won't own the listing directly.
Can a client app be transferred between developer accounts later?
Yes, Google Play supports app transfers between accounts, but it's a manual process that can disrupt install history and reviews — worth avoiding by deciding account ownership correctly upfront.