How to Run Kickoff Week After an Austin App Development SOW (2026)

The SOW is signed. Then someone pastes a studio login into Slack so "we can just upload," or the first-value sentence from the estimate is missing from the board. That is how an Austin build burns week one without a binary you can revoke. Kickoff week is the 5–10 working days after signature that prove the SOW is still true: entity-held App Store Connect and Google Play Console, a US Central overlap window with a named seat, TestFlight and Play internal tracks that claim your identifiers, and a first-value moment still attached before the build clock starts.

This is the kickoff-week operator playbook that comes after the eight-section brief, the Austin partner shortlist, the estimate read, and who owns App Store Connect and Play Console. Those pages already wrote the job, scored the bench, priced the PDF, and named the seller. This page is narrower: what must finish in the first 5–10 working days after SOW signature before coding velocity is honest.

This is not another brief, shortlist, estimate read, or store-roles piece, and it is not Flutter versus native. The question is the calendar: Day-0 gates closed, a priced overlap window, the first internal binary on your tracks, and the first-value moment still on the board when the compilers start.

What must already be true on Day 0 before kickoff is a real calendar?

The legal entity is already Account Holder and Play owner, Admin invites are the only studio seat, the bundle ID and package name are reserved by the client, and the SOW still names the first-value moment. If any of those four are still a ticket, you do not have kickoff week. You have a bench waiting on enrollment. CodeCross's Austin app development company work treats that wait as a gate, not as sprint zero with a nicer name.

The ownership article already named the seats. Kickoff only checks they are done. Apple's accounts-and-roles overview: Account Holder is the membership; Admin is the invite. Play Console is the same shape — the first registered owner holds the listing, the package, and Play App Signing. Invite the shop as Admin. Do not share the founder login. Do not create the app in the studio console "just for this week."

Bundle ID and package name are claims, not labels. Play's testing help is blunt: once you upload an artifact, the package name is fixed. If that first AAB lands in a vendor console, the name is theirs. Reserve the package in your Play owner account and the matching bundle ID in your Apple team before anyone opens Xcode. Play App Signing stays on that owner — Google holds the app-signing key; you hold the upload key.

The first-value moment is the other Day-0 gate. The brief wrote it; the estimate attached a number. Kickoff copies that sentence onto the board — the job a stranger can finish in the first release — plus the out-of-scope list. If the board now says "we'll discover in sprint one," the SOW already slipped. Velocity on a rewritten job is a change order with a burndown chart.

Why is the US Central overlap window a priced, named calendar?

Because App Review and Play will ask a question at 2 p.m. Central, and someone with a console seat has to answer the same afternoon. "We're local" is not a clock. A named person, a bookable window, and a backup who can accept an agreement or reply to TestFlight App Review is a clock. The estimate read already said overlap has to be a priced line. Kickoff week is when that line becomes a hold on a real calendar.

Write the window the way you write a compiler: people, hours, time zone. Who answers when Review asks for a demo account or a Data safety edit. Who can clear Missing Compliance at 1:40 p.m. Who can revoke an Admin invite if a laptop walks. If the only officer who can accept an Apple agreement "will look tonight," you have a voicemail, not overlap.

CodeCross is an Austin-registered product studio — CodeCross LLC — with engineering on hours that overlap US Central. That sentence is load-bearing on kickoff, not a footer. A store binary that cannot answer Review the same afternoon idles a staffed week. Kickoff puts a name on Tuesday 14:00–17:00 Central and a backup for Thursday. If they will not put the hold on a calendar, the SOW's "local delivery" line was marketing.

What is the difference between a TestFlight internal build and the first external build?

Internal testers are App Store Connect users on your team; the first external build of a version is what TestFlight App Review actually reviews. Apple's TestFlight overview: upload a build, invite internal testers (up to 100 Connect users with content access) and external testers (up to 10,000). When you add the first build of your app to a group, that build goes to App Review against the App Review Guidelines. A review is required for the first build; later builds may not need a full review. Testing starts once the build is approved.

Inviting external testers adds the version rule kickoff forgets: create an internal group before an external group; one build of each version in review at a time; the first submitted build needs a full review, later builds of the same version might not. TestFlight Internal Only uploads from Xcode can only join internal groups. If Friday's "first TestFlight" is a customer link, you budgeted a review you did not put on the calendar.

Test information is required before that external invite: beta description, feedback email, and the TestFlight App Review fields. Account Holder, Admin, and App Manager can file it. Write the demo account, what-to-test notes, and feedback mailbox on Day 0. Do not invent them at 4 p.m. on the day you wanted a public link.

Export compliance is a separate hold: Missing Compliance. Apple's beta export-compliance help says to answer the questions or attach approved documentation. Account Holder, Admin, and App Manager can clear it. If the app only uses exempt encryption, declare that in the Info.plist so later uploads do not re-ask. Leaving the questionnaire unanswered is not "Apple being slow." It is an unanswered form on your TestFlight tab.

How do Play internal and closed tracks behave in the same week?

Play's internal track is the fast, 100-tester lane; a closed track is a wider, slower test — and the first artifact still locks the package name. Play Console testing help is the source. Internal testing goes to up to 100 testers by email, can start before the listing is fully configured, and Google says a new bundle is typically available in minutes. First-time uploads can show a temporary name for up to 48 hours. Closed testing is the next ring: email lists or Google Groups, and a longer wait before the link is useful.

Three Play facts belong on the board while everyone watches iOS. The package name cannot change after the first artifact — reserve it on the client owner account first. Internal tests might skip standard Play policy review, and internal-only apps are exempt from the public Data safety section; that exemption is not a reason to skip the form if a closed or production track is in the same SOW. Testers on internal are not eligible for closed or open until they opt out. If Friday's stakeholder link is closed-track and those people already joined internal, the link looks broken.

The July 15, 2026 Play policy announcement is not a new kickoff ritual. It reminds you leftover unregistered Play packages still sit on the owner account — Google says about 99% of Play apps were registered automatically; the leftovers are the dangerous ones. If a prior vendor or old listing exists, check Play Console Home in week one. The verification inventory is the how-to. Kickoff only asks: is the name on your owner account before the first AAB?

What has to finish before the first internal binary is allowed?

Enrollment, invites, reserved identifiers, a named overlap seat, export-compliance ownership, and the first-value sentence — then, only then, the upload. The first internal binary is how a bundle ID, a package name, and a signing identity get claimed. If those claims land in the wrong console, kickoff week has already failed even if the stand-up looked busy.

Write the checklist as a table a PM can read without Slack. One row per console: entity, Account Holder / owner, invite list, bundle ID or package name, who holds the distribution certificate or upload key, Play App Signing, who files export compliance and Data safety, the 14:00–17:00 Central seat, and the date the first internal binary is allowed. If two rows disagree on the entity, stop. Year-one TCO still assumes you hold the console.

Where do kickoff days go when a Day-0 gate is still missing?

They go into accounts, D-U-N-S, an unnamed overlap seat, and TestFlight App Review — not into the first-value moment the SOW paid for. An honest week spends five to ten working days on invites, reserved identifiers, the first internal binary, and a demo that still matches the brief. A missing gate spends the same calendar on vendor clocks. The chart is an operator estimate, not a published survey. Use it to reject "we'll sort it in kickoff," not to pad a contingency.

What first-value moment has to stay on the kickoff board?

The same sentence the SOW priced — the job a stranger can finish in the first release — written where the team can see it before anyone talks compilers. Kickoff is when that sentence survives or gets replaced by a nicer backlog. If the board now says "foundation sprint," you are funding architecture theater. The brief already defined the job. Kickoff copies it. It does not workshop a new one.

Attach three artifacts to that sentence. The out-of-scope list from the estimate, still dated. The store path — internal TestFlight and Play internal first; first external only when Review is on the calendar. The leave test from store-account ownership — revoke the Admin invite and you still have the listing. If any of those three moved, stop the build clock and rewrite the sheet.

Whose legal entity must already be enrolled when kickoff Monday starts?

The operating company that will be the seller — already Account Holder on Apple and owner on Play — not the studio, and not a personal Apple Account you plan to share for a week. Enrolling an organization and Play's organization account are Day-0 work, not kickoff chores. If counsel has not picked the entity, or D-U-N-S is still a ticket, the honest next spend is a wait. It is not a store binary sprint with a login to "sort later."

Can we share a studio login so kickoff week moves faster?

No. Invite the shop as Admin. A shared password is not a kickoff acceleration — it is a listing you cannot revoke. Apple's roles overview: Admin runs the build; Account Holder is the company. Play's owner seat is the same line. A pasted login has already picked the studio console. If you cannot revoke the seat on Friday, you handed over the seller name — the ownership article is that leave test.

When does TestFlight App Review actually start?

On the first build you add to a group — and, for external testers, on the first build of a version you submit for review — not on the internal install your team already has. TestFlight overview sends that first grouped build to App Review. External-tester help: the first submitted build needs a full review; later builds of the same version might not. Schedule customer links on the review clock and the engineering smoke on the internal clock.

What does Missing Compliance actually block?

It blocks a usable TestFlight build until someone with Account Holder, Admin, or App Manager clears export compliance — it is not an App Review rejection. Apple's beta export-compliance page is the fix: open the build and provide the information, or attach approved documentation. If the app only uses exempt encryption, declare it in the Info.plist. Kickoff names who clicks that path at 2 p.m. Central.

How long can a missing D-U-N-S idle a staffed kickoff?

Long enough to replace the week with a vendor clock — Google cites up to 28 days for a new D-U-N-S number, and Apple will not enroll an organization without it. Enrollment is a Day-0 gate, not a Thursday task. If the number has not been requested, do not staff a store binary squad to watch a Dun & Bradstreet ticket. Kickoff week refuses to pretend that wait is a sprint.

Who answers when App Review asks at 2 p.m. Central?

A named Admin or officer on a bookable US Central hold — not "the team," and not a Slack channel that goes quiet after lunch. TestFlight App Review emails Admins when a beta build is approved or rejected. Play will ask for a Data safety edit on the same clock. If you cannot put the hold on a calendar in kickoff week, the shortlist already told you what you bought: a marketing line, not local delivery.

What does CodeCross open on an Austin kickoff call?

The Day-0 gates, the overlap hold, the first internal tracks, and whether the next five to ten days are a kickoff or a stop. CodeCross is an Austin-registered product studio — CodeCross LLC — with engineering on hours that overlap US Central. We work as invited Admin. We do not become Account Holder. We do not create your Play organization. The kickoff conversation is how we tell a readable SOW from a week that will burn on someone else's login.

What we will actually open in that conversation:

• The first-value sentence on the brief and the estimate — copied onto the board, or a rewrite before anyone talks compilers.
• Account Holder for Connect and Play owner: your entity, already enrolled. The ownership gate is closed, not a kickoff story.
• The Admin / Developer invites we need, and the date you can revoke them.
• Bundle ID, package name, and Play App Signing on your owner account.
• The US Central hold: who answers at 2 p.m. when Review or Missing Compliance asks.
• Internal TestFlight and Play internal first; first external only with TestFlight App Review on the calendar.
• Dated proof you can click on the proof dashboard.
• A written no, if we are the wrong shape: no walk-in lab, no staff-aug bench, no studio-held membership.

We will tell you whether the next spend is a closed kickoff, a store binary, or a stop. Directional ranges already live on the estimate page. The brief keeps those numbers attached to a job. The shortlist keeps them attached to a bench you can reach. This article is how you keep week one from becoming a stand-up about tickets that should have been closed before signature.

The kickoff conversation is a booking — not a homepage form that invents your seller name. Bring the entity, the two consoles, the invite list, the overlap hold, and the first-value sentence. Do not send the studio password. Do not schedule a customer TestFlight on an internal clock.

An honest Austin kickoff week is shorter than the Slack thread you already have. Close the Day-0 gates. Name 2 p.m. Central. Reserve the identifiers. Ship the first internal binary only after those are true. Then start the build clock — or stop before the wrong listing has a TestFlight and no leave path.