Analyze

/sunboard.analyze is the front door for improving onboarding that already exists. It grounds every "why aren't users activating?" question in real data, agrees on a plan with you, then drives the fix itself — editing the spec, re-wiring, re-targeting, and shipping a new version through the underlying skills. It's the improve-existing counterpart to Onboarding.

When to use it

• An experience is live and you want to know where users drop off.
• After shipping a fix, to confirm the funnel actually moved.
• You want to prioritize by money — which onboarding path is worth the most, and whether activation is converting to revenue.

What happens

1. Finds the experience (or reads sunboard state to pick one).
2. Fetches analytics — sunboard analytics experience <key> --json, defaulting to a 30-day window.
3. Reads the diagnostics first — noViews (nothing wired or bound), missingGoal (no activation event), largestDropoff (the primary funnel signal), noTourStarts (launcher problem).
4. Pulls enrichment when PostHog is connected — reruns with --enrich to see what dropped users did instead: rage clicks and exceptions point at wiring, detours to other pages point at the spec, acquisition skew points at targeting, and session replay links go straight into the plan. See the PostHog integration.
5. Cross-references the spec to form a hypothesis — wrong route/selector, an event firing from the wrong path, a step demanding too much before value, tour copy, or the wrong audience.
6. Slices when needed — by version, segment, environment, or origin. When the question is about money, it also pulls sunboard analytics revenue to rank fixes by conversion and revenue, not just funnel shape.
7. Shows you a plan and waits for approval — naming the fault, the numbers, the proposed change (cheapest plausible fix first — a copy tweak before a resegmentation), and which skill it'll use to make it.
8. Drives the fix — once you approve, it runs Spec, Tour, Implement, or Segment, then deploys a new version to the sandbox to test and promotes it to production (the old production version stays for rollback).
9. Closes the loop — tells you which metrics to watch, then compares versions on the next run to confirm the funnel moved.

Related