Client onboarding

What the first 30 days look like

This is the exact process every new client goes through. No ambiguity, no hand-wavy “we will get started” — a week-by-week breakdown of what happens from signature to first improvements in production.

1
Week 1

Access and discovery

  • We send you a short onboarding questionnaire — 10 questions, 15 minutes
  • You grant read access to your cloud account, CI/CD, and repositories
  • We do a full infrastructure audit — same process as the free audit, but with full access and more time
  • Kick-off call: we walk through what we found, agree on priorities for the first sprint
deliverable:Audit report and prioritised backlog
2
Week 2

First sprint

  • We start on the highest-priority items from the backlog
  • All changes are made in a feature branch, reviewed by you before merge
  • We document every change in a shared runbook as we go
  • Daily async updates in Slack — no need to ask for status
deliverable:First set of improvements live in staging
3
Week 3

Into production

  • Staging validation and promotion to production
  • Monitoring and alerting set up or reviewed for the new changes
  • We run a post-deployment review to confirm nothing regressed
  • Second sprint planning based on what is next in the backlog
deliverable:First improvements live in production
4
Week 4

Rhythm established

  • Sprint 2 delivered
  • Weekly async check-in report sent every Friday
  • Runbook updated with everything we have built so far
  • 30-day review call: what was done, what is next, any adjustments to scope
deliverable:30-day report and updated roadmap

What we need from you

  • Read access to your cloud account (AWS IAM role, GCP service account, or Azure service principal)
  • Access to your CI/CD system and main repositories
  • A Slack channel where your engineering team can reach us
  • One technical point of contact who can answer questions and review pull requests
  • 15 minutes for the kick-off call and 30 minutes for the monthly review

What you can expect from us

  • All changes documented before they go to production — no surprises
  • Every pull request has a description explaining what changed and why
  • A shared runbook that your team can read and operate without us
  • Honest weekly updates — including when something did not go as planned
  • Response to Slack questions within 4 business hours

Ready to start?

Every engagement begins with the free audit. It sets the baseline for everything in week one.

Book the free audit