This is the question that comes up on the second client, never the first. You have one app live, the process worked, and now you are looking at doing it nine more times — and paying Apple $99 nine more times, out of your margin, feels absurd. Surely you can publish them all from the account you already have?
You cannot, and the reason is not billing. It is a written App Review guideline, and it is the single rule that decides the shape of this entire business.
The rule
Guideline 4.2.6 of Apple's App Review Guidelines exists specifically for services like this one. It reads:
“Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences.”
Read the second sentence again, because it is unusually direct for Apple. It does not say the apps must be different enough. It names the practice — a service submitting on behalf of its clients — and says do not do it.
So the answer to the question is yes: each client needs their own Apple Developer Program membership, enrolled in their own name, and their app is submitted from there. The client is the provider of the content, so the client has to be the submitter.
What that does not mean
It does not mean the client does the work. This is where most people get the rule backwards and either give up on the model or hand a non-technical café owner a copy of Xcode.
The account belongs to the client. The labour does not. Apple has a documented mechanism for exactly this, and using it is both normal and expected:
- The client enrols and becomes the Account Holder. Their legal name or company name is what appears as the seller on the App Store listing.
- They invite you into their App Store Connect account as an App Manager, which is the role that can upload builds, edit the listing and submit for review. Adding a user requires the Account Holder, Admin or App Manager role, so the client does this part themselves, once.
- Access to Certificates, Identifiers & Profiles is a separate checkbox on that invitation, not part of the role. You need it ticked to handle signing, and it is the thing people forget, which then costs an email and another three days.
- You do not need your own paid membership to be in their account. An individual enrolment can add up to 50 such users, and Apple is explicit that they get App Store Connect access only — they are not part of the team and receive no other membership benefits.
One practical detail worth putting in your onboarding email: the invitation expires after three days. It can be resent, but a client who opens it on Monday and gets to it the following weekend has to be chased, and you will do this often enough to want the sentence prewritten.
The third option, which Apple offers itself
The same guideline ends with an alternative most people never read as far as:
“Another acceptable option for template providers is to create a single binary to host all client content in an aggregated or ‘picker’ model, for example as a restaurant finder app with separate customized entries or pages for each client restaurant, or as an event app with separate entries for each client event.”
One app, under your account, containing all your clients. No per-client $99, no invitations, no chasing. It is a legitimate route and Apple names it.
It also destroys the product you are selling, in most cases. The thing a small business is actually buying is their icon on their customer's home screen, with their name under it. In a picker app they are an entry in somebody else's directory, they cannot send a push that belongs to them, and they are one tap deeper than the competitor who paid for a real app.
Where it does work: a franchise with one brand and many locations, an organiser running many events a year, a trade association with member businesses. The common factor is that the clients already share an identity with each other. If they do not, you are selling a directory and should price it like one.
Google Play is a different problem, not a smaller one
Google has no equivalent of 4.2.6, and the fee is a one-time US$25 rather than $99 a year. On paper, the Android side is trivial. In practice it has become the harder half, for a reason that has nothing to do with templates.
A developer account created as a personal account after 13 November 2023 must, before it can publish to production, run a closed test with at least 12 testers opted in continuously for 14 days. Google's own help page states that requirement and scopes it to personal accounts created after that date. It says nothing either way about organization accounts, so treat the widely repeated claim that companies are exempt as something to verify for the specific client in front of you, not as a given.
What this means operationally is that an Android launch for a brand-new client is two weeks longer than you think, and the two weeks are not yours to compress. You cannot start the clock until the client's account exists, and internal testing does not count toward it — only closed testing does. Personal accounts must also verify access to an Android device through the Play Console app.
Put the fourteen days in the quote. A client who is told about them up front treats them as a process; a client who discovers them in week three thinks you missed a date.
What it costs, per client
| Item | Who pays | Amount |
|---|---|---|
| Apple Developer Program | Client, own account | $99 per year, recurring |
| Google Play Developer | Client, own account | $25, one time |
| Your access to both | Nobody | Free — invited user, no membership needed |
| Your own developer account | You | $99 a year, for your own test builds and demos |
The number that matters is the first one, and it is recurring. It is the client's cost, not yours, which is a conversation worth having early — a $99 annual charge appearing on a café owner's card eleven months after launch, unexplained, is how a renewal gets cancelled and an app quietly disappears.
The detail that catches people in Europe
If the client's app is distributed in the EU and they are a trader — which covers anyone earning money through the app, including via paid downloads or in-app purchases — Apple requires verified trader status, and the contact details that come with it are published on the App Store listing: an address, a phone number and an email.
Apple set 17 February 2025 as the date from which apps without verified trader status would be removed from EU storefronts. For a company client this is paperwork. For a sole trader operating out of their home it is a home address on a public page, and some of them will refuse once they understand it. Better that they understand it from you, in week one, than from a removal notice.
What to tell the client
The whole thing compresses into four sentences, and having them ready is the difference between a short call and a confused one:
- The app has to be published under your name, not ours — that is Apple's rule, not our preference.
- It costs you $99 a year to Apple and $25 once to Google, paid directly, and we do not mark it up.
- You sign up, you click one button to give us access, and we do everything after that.
- It means the app is yours. If you ever leave us, it stays on the store under your account.
That last line is worth saying out loud even though it costs you leverage, because the objection behind the question is almost never the $99. It is the suspicion that they are about to be locked into something. Telling them plainly that the asset is theirs tends to close the topic faster than any discount.
And one argument for the rule
It is easy to read 4.2.6 as Apple making your life harder. It is also the rule that stops the obvious disaster in this business: thirty client apps published under one account, sharing one fate. Accounts get terminated, cards expire, the person who set it up leaves. Under 4.2.6 a problem with one client's account is a problem with one client.
Mostly, though, it is the rule that makes the model honest. You are selling a business its own app, and after the invitation is accepted, that is literally what it owns.
Where this fits
The other rule that decides whether the app ships at all is Guideline 4.2 on minimum functionality, which is about the app itself rather than who submits it. What the whole first year costs, store fees included, is in what it actually costs to start. And what to charge once you have worked out that the $99 is not your problem is in what to charge a small business for their app.