The plan, day by day
The order of work for the first two weeks, who does each part, and what "done" looks like each day. Print it, or copy it into the project's task board.
How it works
Apple, Google Play and payment accounts are started on day 0 and arrive during week 2. Nothing else waits for them.
The plan
| When | Do | Who | Page | Done when |
|---|---|---|---|---|
| Day 0 | Fill OWNERSHIP.md with the client | Project lead | 1. Ownership and access | Client signed it off |
| Day 0 | Collect legal entity details; start D-U-N-S, Apple, Google Play, merchant KYC | Project lead, client signatory | 2. Long lead-time accounts | All applications submitted |
| Day 1 | Create the GitHub organisation, teams, empty repos | Tech lead | 3. GitHub organisation | Repos exist with branch rules |
| Day 1 | Create the AWS management account, turn on Organizations | Tech lead | 4. AWS organisation | Root has MFA, budget alarm set |
| Day 2 | Member accounts, Identity Center, guardrails | Tech lead | 4. AWS organisation | Team signs in with SSO |
| Day 3 | Hosted zones, delegation, certificates | Tech lead | 5. Domain, DNS and certificates | dig answers for each environment |
| Day 4 | First service from the template, first deploy to dev | Tech lead | 6. First repo and pipeline | /health returns 200 on dev |
| Day 5 | Sentry, email, monitoring and alerts | Tech lead | 7. Services | Test error and test email arrive |
| Week 2 | Push notifications, crash reporting, analytics, AI keys | Tech lead | 7. Services | Each service checked on dev |
| End of week 2 | Walk the checklist with the project lead | Both | Kickoff checklist | Every box ticked |
Rules
Rule
Do not start feature work before day 4 is done. The first feature should be deployed by the pipeline, not copied by hand.
Rule
Each day ends with a two-line update to the project lead: what is done, what is blocked. Blocked items in week 1 are almost always waiting on the client; chase them early.