4
7 Comments

The payment path works — activation doesn't. Redesigning our onboarding around one event.

I'm redesigning ShotBook's onboarding around one activation event: finding a useful reference and saving it to a Board.

The payment path works; the real problem is helping a new user reach the collaborative value before they leave. The new flow starts from the project, runs the first search for the user, and guides them toward saving and sharing.

on June 25, 2026
  1. 1

    I like the single-event focus here.

    The tricky part is that payment proves intent, but activation proves the workflow worked.

    A user can pay, finish onboarding, and still never reach the first useful outcome. So measuring “saved to Board” instead of “completed onboarding” feels like the right move.

    Curious whether you’ll track just first save, or something like first useful board with 3 saved references?

  2. 1

    The ‘run the first search for them’ move is underrated. Most onboarding assumes users know what to do next removing that first decision completely changes activation rates. Curious how you’re handling the drop-off between saving and actually sharing?

  3. 1

    The single-event focus is the right instinct. The thing I'd watch is that the drop usually happens one step before the event you're optimizing, not at the save itself. If you auto-run that first search and the results come back mediocre, people judge the whole tool on that one result set and leave before they save anything, so the quality of that seeded first search probably matters more than the save UI you're building around it.

    The other thing is that one save is a solo action but the value you described is collaborative. I'd check whether the cohort that saves three-plus references in their first session retains better than the one-save cohort, because if it does, your real activation target might be the third save rather than the first. That makes onboarding about keeping them going after the first save, which is a different design problem than just landing it.

    Either way I'd instrument time-to-first-save and the search-to-save drop separately, so you can see which half is leaking.

  4. 1

    Running the first search for the user is a smart move since the empty state is where most people bail. I had the same thing with a niche tool where nobody got the value until they saw one real result, so I started doing the first action for them. How are you measuring whether someone actually hit the activation moment versus just clicking through the flow?

  5. 1

    Picking ONE activation event is the right call. Most founders try to design an onboarding that covers everything and end up covering nothing.

    One question: how did you identify that 'finding a useful reference and saving it to a Board' is THE event? Did support tickets tell you, or data?

    Just curious what signal made it click.

  6. 1

    Focusing on that single activation event is such a smart move, Alexander. If users don't hit that core value or 'Aha! moment' quickly, they just bounce.
    Running the first search automatically to guide them towards saving/sharing sounds like a solid way to reduce friction. Love this approach, good luck with the redesign.

  7. 1

    I like that you're optimizing around one activation event instead of trying to improve the whole onboarding at once.

    It also changes the success metric. The goal isn't "finish onboarding"—it's reaching the first moment where the product starts feeling useful.

    I'd be interested to see how much that shifts retention.

Trending on Indie Hackers
I built a tool directory that doesn't pretend every founder has the same needs User Avatar 61 comments Drop your landing page URL. I'll use Ferguson to tell you why visitors might be leaving User Avatar 46 comments AI helped me ship faster. Then I forgot what my product actually does. User Avatar 36 comments I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 29 comments Most early-stage SaaS companies miss churn signals — here’s how to catch them early User Avatar 27 comments How I Run a 1.7M Product Search Engine at 66ms on a $0 Hosting Budget User Avatar 18 comments