Otter Growth
    Advisory
    Resources

    The wellness onboarding teardown.

    28 wellness onboarding flows, every screen documented.

    Enter your email to get the teardown.

    You'll be subscribed. You'll get occasional growth notes in your inbox.

    What you get

    The Figma file

    All 28 flows screen by screen, the 9 rules, and a recommended flow for each of the five segments.

    The prompts

    What we ran the teardown with. Point them at your own vertical.

    The dataset

    The screen-by-screen data the findings were read from.

    What the flows do

    Wellness onboarding is doing one thing before it asks for anything: making a vague feeling specific.

    1. 1.What is actually bothering you right now?
    2. 2.What would better look like for you?
    3. 3.Where does this fit into your day?

    People arrive here with a real but blurry motivation, much blurrier than in health and fitness, so the flow's job is to turn it into something concrete enough to act on and then hand back a number or a plan that proves it was heard. The apps that ask for an account before doing that are asking someone to commit to a feeling they have not articulated yet.

    Defer signup until you have shown something real

    Wellness users arrive with a more immediate and uncertain motivation, so the first interaction has to establish value before it asks for commitment. Balance and Happier both hold registration until a plan is ready. RISE goes further and shows a real Sleep Debt figure before it ever asks for an email.

    Back personalization with a computed result

    A number built from the user's own input reads as proof. A generic completion screen does not. Breathwrk runs a timed lung-capacity test and hands back a specific score before asking for anything else.

    Put the reason on the screen that asks

    It is the difference between a form and a conversation, and it changes how the same question lands. RISE pairs its motion permission with a plain reason and a link explaining why it needs it, both on the same screen.

    Make reassurance specific enough to verify

    A concrete, checkable claim is the only kind a user could catch you breaking, which is what makes it worth believing. RISE says it does not share the data with anyone. Bloom says it will never show ads inside the app.

    More questions is not more personalization

    Depth without a visible payoff just reads as a longer form. Ahead builds a personalized map of recommended journeys straight from the concerns and goals a user just entered.

    Earn a permission before you ask for it

    Where a permission sits in the sequence matters as much as the permission itself. Endel asks for app-tracking access at screen 9 of 27, which sounds late until you notice the app still has not shown a single personalized result.

    Name the mechanism, do not just reassure around it

    Disclosing that a question was algorithm-generated, paired with a skip in the same sentence, is a stronger trust device than boilerplate privacy language. BetterHelp does exactly that.

    Never dress a repeated ask as separate choices

    It works until the user notices, and then it costs more trust than the extra yes was worth. Me+ closes its onboarding with three near-identical commitment screens in reworded language.

    Attach a real number to a claim

    A cited stat makes an ask feel safer, not just more persuasive, because it shows other people said yes and got something for it. Endel states a 7x increase in focus, backed by a cited study, before its account or notification ask.

    I've already done some of this work. I do it for my consulting business, I have all the teardowns, and I've done the work that other people don't have to do.

    Want this run on your app?

    The teardown is the category. An onboarding audit reads your flow, screen by screen.

    See the onboarding audit
    Otter Growth AdvisoryProduct growth for consumer apps and products