$ npm start▋
A new signup gets watched, not just welcomed
The expensive failure mode in onboarding isn't a bad welcome email, it's a good-fit account going stalled silently because nobody was watching hour 73. This agent is the thing watching: working demo, real pipeline, output below copied verbatim from an actual run.
The problem this automates
Every new signup needs the same three things to happen fast: a welcome message that isn't generic, a nudge toward the one action that predicts they'll stick around, and a human getting looped in before a promising account goes quiet, not after they've already churned. Most teams do this by hand until it doesn't scale, then bolt together a drip-email tool that can't tell a rollout-evaluating enterprise account from a solo founder who's lost.
How it works
One pipeline, per signup, the moment the signup event fires.
Classify the persona
From the signup form's structured "what are you here for" field, rule-based, instant, free. No LLM call needed for something a dropdown already told you.
Score activation risk
From hours-since-signup and whether a first activation event has fired. Three states: on-track, at-risk (24h+, no activation), stalled (72h+, no activation), plain, readable code, not a black box a CS lead has to trust blindly.
Draft a personalized welcome email
With Claude, grounded in what the user actually typed in their signup form (their stated goal), their plan tier, and their company, not a mail-merge template.
Build a plan-aware onboarding checklist
Rule-based, tailored to what they said they're trying to do.
Draft a Slack alert if at-risk or stalled
With Claude, but it only ever drafts. The agent never contacts an at-risk customer on its own; a human always makes the save call. That boundary is hard-coded, not a prompt instruction that could be ignored.
A real run: 4 signups
“Northstar Analytics” is fictional, invented for this demo, same disclosure the rest of this site uses for illustrative work. The digest below is copied verbatim from a committed sample run.
# Onboarding digest: Northstar Analytics 4 new signups processed · 1 on-track · 3 need attention ## Brightloom · Priya Nandakumar (Starter) - Persona: Usage analytics practitioner - Risk: on-track - Welcome email subject: "Welcome to Northstar Analytics, Priya" - Checklist: Connect your first data source → Define what counts as an "active" user for your product → Set up your first weekly-active-users chart ## HavenPay · Marcus Feld (Growth) - Persona: Growth / Funnel analyst - Risk: at-risk - CS alert (#cs-activation-alerts): HavenPay (Growth) is 30h in with no activation event yet. Worth a lightweight nudge, they came in wanting help with "funnel analysis". ## Nordfleet Logistics · Ingrid Solberg (Scale) - Persona: Enterprise IT / Rollout owner - Risk: stalled - CS alert (#cs-activation-alerts): Nordfleet Logistics (Scale) has gone 91h with zero activation, flagging before this reads as churn. Suggest a personal outreach call re: "enterprise rollout / SSO", not another automated email. ## SoloShelf · Tomasz Wierzbicki (Starter) - Persona: Unguided evaluator (needs a nudge) - Risk: at-risk - CS alert (#cs-activation-alerts): SoloShelf (Starter) is 26h in with no activation event yet. Worth a lightweight nudge, they came in wanting help with "unclear / needs guidance".
This one doesn't carry an adversarial test suite the way the enquiry-to-CRM build does, it's a working example, not a hardened one yet. The source lives in X-GenAI's working repo, which also holds unreleased pricing and outreach material, so it isn't public. Happy to walk through the actual code on a call.
Adapting this for a real client
In a real engagement, the signup step subscribes to your product's actual signup webhook, the Slack alert posts to a real channel (or your CRM), and the risk thresholds get tuned against your product's real activation data instead of the illustrative defaults here. The pipeline shape doesn't change, that's the point of building it this way.
Have a signup flow worth watching?
15 minutes, no pitch deck. Bring your actual activation problem.