Customer Onboarding Checklist
A PM-focused onboarding checklist covering the full user journey from signup to first value — activation milestones, friction points, in-app prompts, and a 30-day health check. Free to copy, download, and use. No signup required.
# Customer Onboarding Checklist **Product:** [Product or feature name] **PM Owner:** [Name] **Date:** [Date] **Target Segment:** [e.g. "Individual PMs", "SMB ops teams", "Enterprise IT admins"] --- ## What Good Onboarding Looks Like > The goal is not tutorial completion — it's **time to first value**. A user who reaches their first meaningful outcome in session 1 is 5× more likely to return in week 2. Define your "first value" moment before checking anything else: **First Value Event:** [e.g. "User generates their first PRD with at least 3 insights", "User sends their first report", "Team member invites a colleague"] **Target Time to First Value:** [e.g. "< 10 minutes from signup", "< 1 session"] --- ## Phase 1: Signup & Account Setup - [ ] Signup flow is < 3 steps - [ ] Password requirements are clearly stated (not discovered on error) - [ ] Email verification sends within 30 seconds - [ ] Verification email lands in inbox, not spam (test with Gmail, Outlook, Apple Mail) - [ ] Verification link works on mobile browser - [ ] After verification, user lands on the right page (not a 404 or raw dashboard) - [ ] If SSO / OAuth — flow completes in one window, no redirect loops - [ ] Error states are human-readable (not "Error 422: Unprocessable Entity") - [ ] Progress indicator present if setup is multi-step - [ ] User can recover from a wrong email address **Friction audit:** > [Note any drop-off observed in funnel analytics — where do users abandon?] --- ## Phase 2: First Session — Activation - [ ] Empty state is helpful, not blank (shows what to do next, not a blank canvas) - [ ] First action is obvious from the UI (one primary CTA above the fold) - [ ] First action is achievable in < 2 minutes with zero prior knowledge - [ ] Sample data or a guided demo project is available (reduces blank-page paralysis) - [ ] Tooltips / coach marks explain core vocabulary on first encounter - [ ] Tooltips can be dismissed and don't re-appear on every visit - [ ] Progress toward "first value" is visible to the user - [ ] User is shown a success state after completing the first action (celebration moment) - [ ] No dead ends — every error or empty state has a next step **First Value Gate:** - [ ] User reaches the First Value Event above within the target time - [ ] Event is tracked in analytics (not just assumed) --- ## Phase 3: Email Onboarding Sequence - [ ] Welcome email sends immediately after signup (not after verification) - [ ] Welcome email content matches the product — no generic SaaS template language - [ ] Day 2 email: nudge users who haven't reached First Value Event - [ ] Day 5 email: feature highlight for users who have reached First Value - [ ] Day 10 email: social proof or use-case story - [ ] Unsubscribe works and is GDPR/CAN-SPAM compliant - [ ] Emails render correctly on mobile (test in Litmus or equivalent) - [ ] From name is recognizable (not "[email protected]") - [ ] Reply-to is a real inbox that gets read **Email sequence map:** | Day | Trigger | Subject | Goal | |---|---|---|---| | 0 | Signup | [e.g. "Welcome to PMRead — here's where to start"] | First login | | 2 | No First Value | [e.g. "Haven't gotten started? Here's 3 minutes"] | Activation | | 5 | First Value reached | [e.g. "You've got your first PRD — here's what's next"] | Second session | | 10 | Active user | [e.g. "How [Customer] uses PMRead for sprint planning"] | Habit formation | --- ## Phase 4: In-App Onboarding Elements - [ ] Onboarding checklist (sidebar or dashboard widget) with completion % - [ ] Checklist items are actionable, not informational ("Upload your first file" not "Learn about uploads") - [ ] Checklist auto-hides after completion (does not persist as clutter) - [ ] Feature discovery tooltips fire contextually (on relevant page/state, not on every page) - [ ] Help docs linked from within the app (not only in a footer link) - [ ] In-app chat or support widget accessible during onboarding - [ ] Video walkthrough available (2–3 min max, linked from empty state or checklist) --- ## Phase 5: 30-Day Health Check Review these signals at day 30 for each new cohort: | Signal | Target | Actual | Status | |---|---|---|---| | Day 1 retention (returned after signup day) | > 40% | | | | Day 7 retention | > 25% | | | | Day 30 retention | > 15% | | | | % reached First Value Event | > 60% | | | | % completed onboarding checklist | > 40% | | | | Support tickets in first 7 days (topic) | < 5% of cohort | | | | NPS / CSAT at day 14 | > 30 NPS | | | **Top friction points identified this cohort:** 1. [e.g. "30% of users abandon at step 2 of project setup"] 2. [e.g. "Most common day-1 support question: 'how do I invite teammates'"] **Actions for next cohort:** - [ ] [Improvement 1] - [ ] [Improvement 2] --- ## Onboarding Anti-Patterns (Avoid These) - **Forced product tour on login** — users skip it. Contextual tips beat linear tours. - **Requiring credit card at signup** — drops activation by 20–40% in most B2B SaaS. - **Generic empty state** — "No projects yet" is not a CTA. "Create your first project in 2 minutes →" is. - **Verification email > 2 minutes** — users move on. Check your sending infra. - **Onboarding that teaches features, not outcomes** — show the user what they can do, not how the system works.
How to use this Onboarding Checklist template
Define your First Value Event before reviewing the checklist
Everything in this checklist is in service of getting the user to one moment: the first time they get genuine value from the product. If you can't articulate that moment, the checklist will optimize for feature exposure rather than user success. Write it at the top before proceeding.
Run through Phase 1–4 as a new user
Open an incognito window, sign up with a fresh email, and go through the entire flow while checking items off. Do this with someone who has never used the product (a friend, a new hire, a designer). You will find friction you have been blind to.
Instrument every phase before optimizing
You need funnel data for each phase to know where to invest. Guessing that the email sequence is the problem when 40% of users abandon at signup is wasted effort. Set up event tracking for each phase gate before running the 30-day health check.
Review Phase 5 by cohort, not by overall averages
Day 30 retention averaged across all time loses the signal in noise. Compare the August cohort to the September cohort after you made an onboarding change — that's how you know if it worked. Cohort analysis is the only honest measure of onboarding improvement.
Treat onboarding as a product surface, not a one-time project
Onboarding decays as the product changes. A tooltip written for v1 that refers to a button that no longer exists creates confusion. Assign someone to own onboarding health as an ongoing metric — not a quarterly audit.
Want a Onboarding Checklist grounded in your actual customer data?
PMRead ingests your customer interviews, feedback, and Slack threads — and generates PRDs backed by real evidence, not guesses.
Frequently asked questions
What's the most common onboarding mistake PMs make?
Optimizing for tutorial completion instead of first value. A user who watches all 5 onboarding videos and never sends a real message has not been successfully onboarded. Track the First Value Event as your north star, not 'checklist completed %'.
Should onboarding be the same for all user types?
No. A solo PM and an enterprise team have different goals, different first actions, and different success criteria. If you have meaningfully different segments, consider branching the onboarding flow: 'Are you using this for yourself or with a team?' routes to different checklists and email sequences.
How long should the onboarding email sequence run?
For most SaaS products: 14 days is sufficient. After 14 days, users are either active (shift to feature education) or churned (shift to win-back, not more onboarding). Extending onboarding emails past 30 days for inactive users rarely works and trains users to ignore your domain.
When should you use an in-app tour vs. contextual tooltips?
In-app tours (modal overlays on login) work only when the product is very simple and the first action is genuinely unclear. For any product with more than 3 features, users skip tours. Contextual tooltips that fire when a user first encounters a feature are 3–5× more effective than tours because they appear when the user is motivated.
What's a good day-30 retention target for a new SaaS product?
Benchmarks vary by category: B2B SaaS tools average 20–35% D30. Consumer apps average 10–20%. The more important metric is the delta between cohorts — if D30 improves from 18% to 24% after an onboarding redesign, that's a strong signal regardless of absolute benchmark.
Other free templates