Onboarding: your first two weeks

Onboarding is mostly about access and context, and we run it from a checklist so nothing stalls. You will get a single onboarding document listing every account, credential, and decision we need from you — typically completable in one afternoon.

• Kickoff call: introductions, communication channels, decision-makers, and the definition of done for milestone one.
• Access setup: repositories, cloud accounts, and environments — created in your name, with our engineers added under SSO.
• Architecture walkthrough of any existing systems, including the undocumented parts (there are always undocumented parts).

By the second week the team is shipping: CI/CD pipelines stood up, environments reproducible, and the first feature work underway. The first sprint demo happens at the end of week two — it is usually small, and that is the point. You see the delivery rhythm immediately, not after a month of "setup."

This is the actual checklist from our onboarding template — what we typically need, all created in your name with our engineers added under SSO:

• Cloud account (AWS/Azure/GCP) — owner: you; our role: scoped admin via SSO.
• Source control organization (GitHub/GitLab) — owner: you; our engineers as members.
• DNS & domain registrar — owner: you; we get delegated zone access, never registrar credentials.
• CI/CD, monitoring, and error-tracking accounts — provisioned fresh or access granted.
• Third-party services in scope (payment provider, email, analytics) — sandbox credentials first.
• A shared channel (Slack/Teams) and a named decision-maker for day-to-day questions.