Back to GrowthDex
Growth idea action plan

Superhuman onboarding notes as product backlog

Turn each live onboarding into a structured product-research session with feature requests, bugs, friction points, and follow-up promises captured immediately.

uncommon tactic
Best-fit channelCustomer Research · Activation · Product
Stage + contextcustomer research · onboarding · product feedback · retention
BudgetLowbudget tier
Suggested operator signalShare of target users completing the product's first-value action

Why this can grow a startup

Analytics can show where a user stops, but it rarely shows the sentence they say right before losing trust. In Superhuman’s early days, onboardings ran up to 90 minutes: discovery first, then guided setup while the team captured every request, bug, and friction point. It was common to leave with ten pages of notes plus several bugs and feature requests. That turns onboarding from labor into a learning engine. It also lets the team close loops later, which makes early customers feel heard instead of processed.

Source-backed example

Superhuman used early onboarding sessions to collect workflow notes, product requests, bugs, and unnoticed friction, often producing ten pages of notes from a single customer conversation.

Source-reported evidence

Source: First Round Review: Superhuman Onboarding Playbook · Browse First Round Review: Superhuman Onboarding Playbook tactics

Early sessions commonly generated 10 pages of notes, 5-10 feature requests, and 5-10 bugs to fix before the next onboarding.

Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

Customer ResearchActivationProductcustomer researchonboardingproduct feedbackretention
GrowthDex operator note

When to use it

Use this when Customer Research, Activation, Product is relevant to customer research, onboarding, product feedback and you can run a bounded test with a low budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to Customer Research and Activation, using evidence from First Round Review: Superhuman Onboarding Playbook as context—not as a promised result.
  3. Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian

SOURCE HUB

More tactics from First Round Review: Superhuman Onboarding Playbook

Explore related GrowthDex examples and evidence connected to First Round Review: Superhuman Onboarding Playbook.

Open First Round Review: Superhuman Onboarding Playbook source hub