Skip to main content

BusinessCodeCross Team

Who Should Own App Store Connect and Play Console in an Austin App Build (2026)

Your legal entity should hold Apple and Google publisher seats — not a freelancer laptop and not “the agency for now.” A 2026 ownership gate for Austin app builds.

Business

6 min

Owner
Your entity

Account Holder + Play owner

Studio role
Admin invite

Not a transfer later

Deadlines
Before TestFlight

D-U-N-S, Sep 30, agreements

In an Austin app build, App Store Connect and Google Play Console should sit under your company’s legal entity, with named admins and a second human who can ship. Agency or freelancer custody is a temporary risk, not a default. CodeCross LLC sequences seat proof before store submission. Book a call when seats are still personal.

Start from home if you are new to CodeCross LLC, or the Austin app development company page if you are buying a partner. If your binary began in an AI builder, pair this seat map with vibe coding store-ready checklists.

The brief and estimate can look fine while the real hostage sits in Accounts: a personal Apple ID, a contractor’s Play Console, or an agency “holding” the publisher seat until launch. That pattern breaks at staff turnover, acquisition diligence, or the week you need an emergency release.

The rule

Your entity owns the publisher seats. Partners get roles. Partners do not become the account.

Exceptions need a written transfer date in the SOW — not a handshake.

What “own” means in practice

  • Apple: Organization enrollment (when you qualify), or Individual with a documented upgrade path. Admins named. Certificates and provisioning reachable from CI or a company vault — not one laptop.
  • Google Play: Play Console under the company developer account. Play App Signing acknowledged. Upload keys recoverable by more than one person.
  • Banking / tax / DUNS: The legal details match the brand users will see.

Roles partners should have

  • App Manager / Developer (Apple) and appropriate Play roles for builds and crashes.
  • Not Account Holder unless the SOW explicitly transfers later.

Failure modes we see in Austin builds

  1. Founder personal Apple ID used “just for TestFlight.”
  2. Agency creates the Play account with their entity so “review is faster.”
  3. Signing keys live only on a contractor MacBook.
  4. Nobody can reset 2FA when the holder is traveling.

Any one of these is enough to pause a store date.

How this ties to kickoff and estimates

Seat ownership belongs in kickoff week (kickoff after SOW) and should appear as assumptions in the estimate (how to read an Austin estimate). If the SOW is silent, ask before you sign.

Vibe-coded apps

If you shipped a preview from Rork, FlutterFlow, Cursor, or similar, publisher seats are still yours. The builder does not replace Apple or Google enrollment. See Cursor prototype → App Store / Play for the binary path.

Next steps

Inventory who can log in today. Move Account Holder / owner roles to your entity. Book a call when transfer is stuck.

What only the Account Holder can do

  1. Developer / App Manager invite

    Binaries, profiles, internal TestFlight — scoped to the job

  2. Admin invite (all apps)

    Secondary contact. Cannot become Account Holder by invite.

  3. Account Holder transfer and identity

    A legal process to another employee with binding authority

  4. Legal agreements and membership renewal

    Paid Apps, tax, banking — the seller name on the store

Admin can run the build. Account Holder is the entity. Do not confuse the two.

Three Apple seats, one honest default

  1. 01 · Account Holder

    Your officer

    Enrollment, agreements, renewal, banking. One per membership.

  2. 02 · Admin

    Studio default

    All apps, users, certificates. Cannot take the membership.

  3. 03 · Developer

    Scoped build

    Binaries and TestFlight. Limit app access if the bench is wide.

The invite is labor. The Account Holder seat is the company.

What the Play owner holds vs. what an invited admin can do

Play account owner (you)

  1. Legal entity + D-U-N-S

    Organization identity, payments profile, transfer rights

  2. Package-name registration

    The Sep 30, 2026 leftover clock sits here

  3. Play App Signing + Data safety

    Upload-key reset and the form every listing owes

so the listing ↓

Invited admin / release manager

  1. Internal / closed / production tracks

    Enough to ship a binary on your listing

  2. Release and crash consoles

    Labor. Not the seller name.

  3. No ownership transfer

    They cannot take the org with them

Invite the shop. Do not let them create the organization.

Ownership shape → when it is honest

Founder entity holds, studio invited

  • When it is honest

    Almost every Austin v1

  • Studio seat

    Admin / Developer

  • Leave test

    Revoke the invite

Studio holds, promises a transfer

  • When it is honest

    Almost never

  • Studio seat

    Account Holder / owner

  • Leave test

    D-U-N-S + legal process

Hybrid: split consoles

  • When it is honest

    Rare, written, dated

  • Studio seat

    One store only

  • Leave test

    You still lack a store

Shared personal login

  • When it is honest

    Never

  • Studio seat

    The founder's Apple Account

  • Leave test

    No audit, no revoke

Score the shape against a leave test, not a kickoff convenience. Transfer is not a later ticket.

Illustrative weeks to leave after a bad ownership shape

weeks

Studio Account Holder on Apple

4–10 wks

They cannot transfer Account Holder to a vendor client.

02357Studio-observed recovery after a split (not a bid)Your entity,invite revokeddaysHybrid,one store missing2–5 wksStudio-heldPlay listing3–8 wksStudio AccountHolder on Apple4–10 wks

Illustrative operator ranges. Use them to reject a shape, not to pad a contingency line.

The week is the unpriced discovery you do after the Slack channel dies. Not a published survey.

Illustrative lead time before the first honest upload

weeks

Studio-held consoles, then "transfer"

5–12 wks

Apple will not transfer Account Holder to a vendor client.

02579Calendar weeks from "we signed" to a console that can shipEntity already enrolled, studio inviteddays–1 wkNew org, D-U-N-S already on file1–3 wksNew D-U-N-S, then org enrollment3–6 wksStudio-held consoles, then "transfer"5–12 wks

Illustrative. Start identity before you staff a sprint, not after.

Illustrative studio bands. D-U-N-S is a vendor clock. Transfer is a legal process. Neither is a Slack task.

Kickoff checklist before the first internal binary

  1. 01 →

    Legal entity named on the SOW

    Not a DBA. Not the studio.

  2. 02 →

    Account Holder + Play owner are officers

    Identity done. D-U-N-S on file or in flight.

  3. 03 →

    Agreements accepted in your consoles

    Paid Apps, tax, banking, Play payments profile

  4. 04 →

    Studio invited as Admin / Developer

    No shared passwords. Dated revoke path.

  5. 05 →

    Bundle ID + package name reserved by you

    Play App Signing on your owner account

  6. 06

    Then — only then — first TestFlight / internal

    The binary claims a name you already hold

If 01–03 are missing, you do not have a kickoff. You have a bench waiting on a legal entity.

The ownership loop a kickoff has to finish

  1. 01

    Enroll the operating entity

    Apple + Play, your D-U-N-S

  2. 02

    Accept the agreements

    Account Holder / owner only

  3. 03

    Invite the studio

    Admin, not Account Holder

  4. 04 · loops

    Upload, or stop

    No binary until the name is yours

If the loop returns "still their login," you do not open an internal track. You stop.

Illustrative recovery mix after "we'll handle the stores"

weeks

Both consoles in their login

10 weeks

You are rebuilding the seller name · Legal / identity / D-U-N-S 3 · Transfer or re-enrollment 4 · Keys, package, listing rebuild 3

036811Illustrative weeks in a bad-exit quarter (not a quote)Your entity, invite revokedThe leave path you bought on day one0.7Studio-held Play, Apple yoursOne store is still a hostage5.5Both consoles in their loginYou are rebuilding the seller name10
  • Legal / identity / D-U-N-S
  • Transfer or re-enrollment
  • Keys, package, listing rebuild

Illustrative operator ranges. Not a published survey and not a bid.

Legal and identity time is the cost of a studio-held membership. Pricing ownership on day one pulls that wait off the calendar.

Six questions that finish the ownership gate

  1. 01 →

    Whose legal entity is Account Holder / Play owner?

    Yours, named, before signature

  2. 02 →

    Will they work as Admin — not Account Holder?

    Invite, dated revoke, no shared login

  3. 03 →

    Where do bundle ID and package name live?

    Reserved in your consoles

  4. 04 →

    Who holds certificates and the upload key?

    Your CI + Play App Signing on your owner

  5. 05 →

    Is D-U-N-S already on file?

    Or the 28-day clock starts now

  6. 06

    What happens when the SOW ends?

    Revoke. Not transfer. Not rebuild.

If a shop cannot answer 01–03 in writing, you do not need a chemistry call.

FAQ

Should our Austin agency hold the Apple Account Holder seat?

No, not as the default. Your legal entity should hold it. Give the agency App Manager or Developer roles. If a temporary hold is unavoidable, put a transfer date in the SOW. Book a call.

We used a personal Apple ID for TestFlight — how bad is that?

Fixable, but do it before public review and before you depend on that binary for revenue. Move to an Organization account when you qualify, or document the Individual path and who inherits 2FA.

Does CodeCross LLC take publisher ownership for clients?

Only when the SOW says so in writing — and even then the preference is your entity as owner with CodeCross on roles. See Austin app development company.

What about Play App Signing and upload keys?

Company Play Console owns the app. Play App Signing stays enabled as Google requires. Upload keys must be recoverable by more than one person — not a single contractor machine.

How does this interact with a vibe-coded MVP?

Builder previews do not create store ownership. Enroll and seat-map first, then harden for review. Start from vibe coding.

Book a call

Thirty minutes with a senior teammate — honest next steps.

Ready to price an Austin build?

Bring the problem, the users, and a budget ceiling. We’ll tell you whether an app is the right next spend — and what the first year actually costs.

Book a call

Prefer writing? Send project details on the contact page.