Blog
FoundersiOSProductArchitecture

Never Publish Your App Under Your Agency's Apple Developer Account

Vishal Paliwal

Vishal Paliwal

Founder & CEO · November 13, 2026 · 8 min read

Your app should never ship under your agency's Apple Developer account. Not for the first release, not "just until launch," not because it saves you a week of setup. The account is where your app, your reviews, your revenue and your users' downloads live, and whoever holds it holds your product.

The practical answer to "who should own the Apple Developer account for my app?" is you. Enroll your company as an organization, make yourself the Account Holder, and give the agency a limited team role. The rest of this post is why founders skip that step, why the reasons do not survive contact with a real launch, and how to set it up in an afternoon.

What the account actually controls

Founders treat the developer account as admin plumbing. It is closer to a deed. According to Apple's enrollment documentation, the legal entity that enrolls is listed as the seller of every app it distributes. For an individual, that is a personal legal name. For an organization, it is the company.

Apple's team roles page adds the part that matters for control. The Account Holder renews the annual membership, accepts legal agreements on behalf of the organization, and approves banking changes. To sell paid apps or offer In-App Purchases, the Account Holder signs the Paid Applications Agreement. If you want money to reach your bank account, that is you or it is nobody.

The strongest argument for letting the agency do it

The case for the agency's account is real, so here it is at full strength. Setup is faster. You skip the paperwork. The agency has done it before, knows the quirks, and "we will transfer it to you after launch." Many founders also have no company registered yet, and an agency account feels like a bridge.

I understand the pull. A good agency on its own account is convenient for the agency. It is rarely convenient for you. You are taking on a migration project at the exact moment you can least afford one, with a live app, live subscribers and a launch you have already announced.

Why a transfer later is harder than it sounds

Apple does let you move an app between accounts, and it is a supported path. It also has conditions. Per Apple's app transfer criteria, both accounts must be out of a pending state and have accepted the latest agreements. The app needs at least one released version. It cannot be on pre-order. It cannot be sitting in any of the states between submission and release, including Waiting for Review, In Review and Pending Developer Release.

That last list is the trap. A transfer can only start when nothing is in flight, and a young app is nearly always in flight: a bug-fix build in review, a release waiting for your go-ahead, a pricing change queued. You end up freezing your roadmap to satisfy a precondition.

There is one more rule worth a note. In-App Purchase product IDs on the transferring app cannot match product IDs on any app in the recipient's account. If you reuse naming conventions across products, you may find the conflict on transfer day.

What goes wrong when the agency holds the keys

None of this requires a bad agency. It requires an ordinary business event. The agency gets acquired, changes its legal name, lets a membership lapse, or simply goes quiet. The Account Holder is the person Apple expects to renew the annual membership. If it lapses, the renewal is theirs, not yours, and your app's availability is tied to someone else's calendar reminder.

There is also the quieter problem of reputation. The seller name on your App Store page is your agency's company, not yours. Customers can read it, and a listing that names another company as the seller sends the wrong signal about who stands behind the product.

We cover the wider version of this in how to de-risk hiring a boutique app agency, where the rule is the same for code, infrastructure and API keys: your accounts, their access. The developer account belongs on that list, at the top.

The setup we recommend instead

You own the account. The agency works inside it as a team member with only the access it needs. This is how we run engagements at Eightinity Technologies, and it is also the shape that makes an eventual handover a non-event. KIN and IngrediCheck both belong to FungeeLLC . We built them. That sentence should be true of every app we touch.

A short checklist, in the order we would do it:

  1. Register the legal entity first. Apple does not accept DBAs, fictitious businesses, trade names or branches for organization enrollment. If your company is not formed, form it before you enroll.
  2. Get a D-U-N-S Number. Apple requires one to identify organizations, and says they are free in most jurisdictions. Check whether your company already has one before requesting a new one.
  3. Enroll as an organization. The membership is 99 USD per year, a rounding error next to any build budget. You, or a named founder, become the Account Holder.
  4. Invite the agency with narrow roles. App Manager or Developer is enough for uploading builds, running TestFlight and submitting for review. Keep the Account Holder seat and the banking details with you.
  5. Put the Account Holder on two calendars. Set a reminder for membership renewal and one for agreement updates. When Apple updates an agreement, your Account Holder is the person who must accept it.
  6. Write it into the contract. One line: all store accounts are owned by the client, and the agency has revocable team access.

The honest cost: a few days of friction up front

This path has a cost. Organization enrollment involves verification, and if you do not yet have a D-U-N-S Number, you will wait for one. Apple says that if you enroll as a non-founder, it may ask for a reference who can confirm you have the legal authority to bind the company. A founder doing this on launch week will find it annoying.

So start early. Run the enrollment while the agency is still in design or discovery, not when you are one week from submission. The cost is a few hours of your time spread across a few weeks, versus a migration under launch pressure.

What if you are a solo founder with no company?

Apple handles this plainly: sole proprietors and single-person businesses enroll as individuals, and their personal legal name is listed as the seller. That is still your account, which beats the agency's. If you incorporate later, Apple says to contact it about converting an individual account to an organization account.

If you already shipped under an agency account, do not panic. Plan the move rather than rushing it. Keep releases moving while you plan it: our App Review playbook covers getting a build through, and the TestFlight playbook covers beta distribution. Aim to have nothing in flight when the transfer starts.

FAQ

Who should own the Apple Developer account for my app?

You should. Enroll your company as an organization in the Apple Developer Program and make yourself Account Holder, then give the agency a limited role such as App Manager or Developer. Apple lists the account's legal entity as the seller on the App Store, so the account is part of your ownership.

Can I move my app to a different Apple Developer account later?

Yes, but with conditions. Apple's app transfer requires the app to have at least one released version, no pending review states, and no matching in-app purchase IDs in the recipient account. Both accounts must have accepted current agreements. It is doable, but it adds delay and risk you can avoid by starting in your own account.

Does my agency need to be the Account Holder to publish my app?

No. Agencies publish apps every day as team members. An invited App Manager or Developer can upload builds, manage TestFlight and submit for review, while you remain Account Holder, accept legal agreements and approve banking changes. Eightinity Technologies works this way: your account, their access, revocable whenever you decide.

Should my startup enroll in the Apple Developer Program as an individual or an organization?

Enroll as an organization if you have a registered company. Apple then lists your legal entity as the seller instead of your personal name, and it requires a D-U-N-S Number to confirm the entity. Sole proprietors enroll as individuals. Converting later means contacting Apple, so choose the right type before the first release.

Not sure whose name is on your current store account? Bring it to a free 30-min call and we will map the cleanest way to get it into your hands →

Share

Eightinity Technologies

Building something like this?

We'd love to hear about your product. 30 minutes, no pitch — just a direct conversation with the team that ships it.

Book a free strategy call→

Keep reading