Who it's for
- Product-led SaaS teams
- Growth and activation engineers
- Onboarding PMs running activation experiments
- Founders debugging trial-to-paid conversion
The problem
- ·Activation metrics tell you *that* users drop off, not *why*.
- ·Long post-onboarding surveys kill what little momentum is left.
- ·You rebuild onboarding every quarter without knowing which change mattered.
How it works
- 1
Trigger the send 24–72 hours after signup, or at a milestone (first project, first integration, first 'aha' event).
- 2
User rates the onboarding experience 1–5 in one tap.
- 3
High scores route to a getting-started guide or a 'next step' upgrade prompt.
- 4
Low scores open: 'Where did you get stuck?' — answers feed product tickets directly.
- 5
Cohort view shows how onboarding ratings move as you ship changes.
Example question
“How was getting started with us?”
Threshold: 4/5 — ratings at or above this number route to the review page; below this number trigger a private follow-up.
Questions
When should I trigger the onboarding survey?
The best window is 24–72 hours after signup, or immediately after the user completes the key activation action. Too early and they haven't felt the product yet; too late and churned users are gone.
How is this different from NPS?
NPS measures overall loyalty after months of use. Onboarding feedback measures a specific 10-minute experience while it's fresh. Both are useful; neither replaces the other.
Can I feed low scores straight into my product-ticket backlog?
Yes — use our webhook or API to push every sub-threshold response into Linear, Jira, or whatever you use. Most teams tag them 'activation' and review weekly.
Matching template
Customer satisfaction (CSAT) template
A one-tap CSAT score you can send after any support ticket or purchase.