Onboarding is the moment you prove value or stall momentum. Here is the lean runbook we use with new customers.

Day 1: prepare access

Before diving in, anchor the list to the outcome customers should feel on the other side.

• Create a shared Slack channel and a single owner on each side.
• Share the billing export instructions and the service account key template.
• Collect label keys used for teams, environments, and products.

Labels to map:
- team: finops, platform, data
- env: prod, staging, dev
- product: payments, analytics, internal-tools

Day 2: wire data and validate

Before diving in, tie the actions to a clear outcome instead of a generic task list.

• Drop the billing export into Stack Dyno and confirm the last 30 days load without gaps.
• Turn on two alerts: one for anomalies and one for CUD coverage regression.
• Invite 3-4 early adopters from finance and engineering.

Day 3: deliver the first win

Before diving in, remind teams how Stack Dyno supports this stage so the bullets feel connected.

• Pick one play: storage lifecycle coverage, GKE namespace cleanup, or commitment planning.
• Demo the before/after state with a screenshot they can share internally.
• Capture blockers and add them to the backlog.

Day 4-5: enablement and handoff

Before diving in, remind teams how Stack Dyno supports this stage so the bullets feel connected.

• Schedule weekly reports and a monthly exec summary.
• Send short Looms or docs that show how to self-serve common questions.
• Celebrate the first savings win in the shared channel.

Keep the runbook tight and predictable. By the end of week one, customers should know that Stack Dyno is running FinOps for them, not asking them to build it themselves.

---