What is Sunboard

Sunboard turns your coding agent into a customer success hire: it builds your onboarding, Sunboard watches your funnel, and your agent ships the fixes.

Sunboard turns your coding agent into a customer success hire. Your agent plans an activation flow with you and wires it into your product: surveys, checklists, and tours in your real UI, not hand-built in a separate visual editor that drifts from your product. From then on, Sunboard watches your funnel and sends you insights, and your agent ships the fixes.

You don't need to be a growth expert. Your agent studies your product, then interviews you about your users and the job they're hiring it for: the aha moment, the must-have setup, the segments worth targeting. It turns your answers into an activation plan and builds it. Sunboard hosts and versions every change, so the server is the source of truth and your agent drives it, not a dashboard you maintain by hand.

What you can build

Checklists

A guided list of the steps that lead a new user to their first real win.

Product tours

Short, focused walkthroughs that point at the real buttons and routes in your app. They start from a checklist item or straight from the UI, so they also work as standalone in-app help.

Signup surveys

A couple of questions at signup that route each new user into the right onboarding path.

Every step anchors to real UI through data-sunboard-id selectors, and completes when a real product event fires via useSunboard().track(). Because your agent already knows your codebase, the anchors land on the right elements.

How it fits together

The sunboard CLI

Local commands your agent runs to author, deploy, and promote. Every command supports --json for AI-friendly output.

@sunboard/react

The SDK that renders the checklist, tours, and hotspots in your app. Installed by sunboard init.

Sunboard (hosted)

Where your sandbox and production environments live: promote tested versions, target audience segments, and read activation analytics.

Your AI agent

The reasoning layer — Claude Code, Codex, or opencode — driving the whole workflow through first-party skills.

The workflow

You drive everything from your AI agent through two skills — Onboarding to set it up and Analyze to improve it. Under the hood they run a loop you can repeat as your product grows:

Plan & author — Onboarding interviews you about the aha moment and your cohorts, then drafts the experience(s) — plus a survey when new users need routing.
Implement — wire the data-sunboard-id selectors and track() calls into your real product.
Deploy — activate the version in the sandbox, where it's live for testing against your pk_test_ key.
Test — run your local app and walk the real loop (survey → segment → experience) with real persistence and routing.
Promote — ship the tested version to production with sunboard promote. Old versions stay available, so rollback is one promote away.
Analyze — read the real funnel, find where users drop off, and ship a concrete fix. Then measure again. Connect your PostHog and the agent also sees what dropped users did instead — detours, rage clicks, session replays.

Production changes are always deliberate

Deploy activates a version in the sandbox, never production. Production changes only through a separate sunboard promote step you approve. A public runtime key can read its environment's onboarding and report events, but never publish or alter what your users see.

How it's different

Tools like Pendo, Appcues, or Userpilot build onboarding in a separate visual dashboard that drifts from your product, and they stop once it ships. With Sunboard, your agent wires onboarding into the real codebase, so it targets your actual UI and activation events, and Sunboard keeps watching the funnel after launch. It's a natural fit for teams shipping with AI coding agents, including AI-built and vibe-coded SaaS apps.