Launching Stack Dyno should feel like turning on a feature flag, not a rewrite. Use this simple cadence for your first customer cohort.

Week 0: branding and access

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

• Upload logos and tweak theme tokens to match your palette.
• Decide on auth: SSO via your IdP or temporary magic links for the pilot.
• Create a private landing page route for your pilot customers.
• Add 3-5 real screenshots that reflect your verticals (telco, SaaS, retail).

Week 1: data plumbing

Before diving in, frame what success looks like before rattling off steps.

• Turn on the billing export to BigQuery and confirm fresh partitions.
• Drop in your service account key and test the spending view with a sandbox project.
• Map label keys used for ownership, environments, and product lines.
• Import one month of historical spend for baselines.

# Quick sanity check for billing export freshness
bq query --use_legacy_sql=false \
"SELECT MAX(_PARTITIONTIME) as latest FROM \`billing.export.table\`"

Week 2: dashboards and narratives

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

• Customize outcome labels in the Sankey and savings cards to match your playbooks.
• Draft three stories you can demo live: "CUD coverage trend", "GKE namespace cleanup", "Storage lifecycle wins".
• Wire Slack and email destinations so alerts do not vanish into the ether.

Week 3: customer rollout

Before diving in, frame what success looks like before rattling off steps.

• Invite 3-5 power users from each customer (finance + platform).
• Run a 30-minute "first look" session with their own data.
• Capture questions and push them into your next sprint. Small UX wins create huge trust early on.

Definition of done

• Billing export is live and monitored.
• At least two alerts and one scheduled report are enabled.
• Demo deck contains before/after screenshots from your environment.

When you follow this checklist, the "launch" becomes a sequence of small, reversible steps instead of a big-bang cutover. That is how we keep momentum while shipping real FinOps results.

---