Skip to content
Build in Public

The onboarding flow that decides everything

Every other screen matters to people who are already customers. Onboarding matters to people who aren't sure they want to be.

SD
Shubham Datarkar
· 3 min read
Updated

Every other screen in Book A Sloth matters to people who are already customers. Onboarding matters to people who aren't sure they want to be. That makes it the most important screen in the entire product, and the one with the least room for error. It's the front door. If the door sticks, nobody ever sees the beautiful rooms I spent a month building behind it.

And remember: onboarding is the whole reason this rebuild exists. The PHP version's fatal flaw was that there was no self-serve front door -- I had to personally let every customer in. The entire point of the new Book A Sloth is that a stranger can walk in, set themselves up, and be live and taking paid bookings without me touching anything. If I get onboarding wrong, I haven't built a new product. I've just rebuilt the old problem in nicer clothes.

So today I built the guided flow that takes a total stranger from "what is this" to "my page is live." It's a series of steps, and the order of those steps is the whole game: claim your username, verify who you are, set a password, build out your profile, create your very first service, pick a plan. Each step doing one job, each one moving them a little closer to a live page.

Two design decisions I want to explain, because they're where the psychology lives.

First: claiming the username comes early. Almost first. Before you've invested any real effort, you pick your name -- the one that becomes bookasloth.com/yourname -- and it's yours. Why so early? Because the moment you claim your name, you own something. It's not "a website I'm evaluating" anymore, it's "my page that I've started." That flip from browsing to owning is what carries someone through the rest of the steps. People finish setting up things that already feel like theirs. Ownership is the fuel; you hand it to them up front.

Second, and I feel strongly about this one: I force the creation of a first service during onboarding. You don't get to finish setup with an empty page. Before you're done, you've made at least one real thing someone could actually book. Because the fastest way to lose a brand-new host is to dump them onto a blank, lifeless profile and say "okay, good luck!" An empty page feels like failure, like a chore not yet started. A page with one service on it feels alive -- it feels like a business that exists. I'd rather add one more step now than lose someone to the emptiness later.

That's the constant, brutal tension running through the whole flow, and there's no clean answer to it: every extra step loses people, but every skipped step loses them later. Add too many steps and they drop off mid-setup, exhausted. Add too few and they reach the end with a half-built page that doesn't work, get confused, and leave anyway. There's no setting where you win both. You just feel for the balance, step by step, cutting anything that isn't pulling its weight and keeping the few things that genuinely have to happen before someone can succeed.

One thing I actually moved while building it: plan selection. I'd originally put it earlier, and it felt wrong -- asking someone to think about money before they've even seen their page come to life. So I pushed it to the end. Let them build the thing, feel the ownership, see their live page -- and then talk about plans, when they're invested and can actually see what they're choosing between. Ask for commitment after you've delivered value, not before.

At the end of the day I did the test that matters: I ran a fake brand-new host through the entire flow, cold, start to finish, pretending I'd never seen this product before. Username to live page. And it worked -- a stranger could go from nothing to a real, bookable page, entirely on their own. No me. No hand-holding.

That's the moment the PHP problem officially died. The front door opens by itself now.

And tomorrow -- the same day, actually -- someone I've never met walks through it, and I get the smallest, best win of the whole month.

Explore more from Shubham — discover curated reads at BookASloth, or check out Rajmudra Media for media & marketing solutions.

Explore more from Shubham — discover curated reads at Book AS loth, or check out Rajmudra Media for media & marketing solutions.

by Shubham DatarkarBuild in Public

Reactions

How was this article?

Newsletter

Never miss the next one

Get the latest playbooks, build logs, and the occasional unpublished idea straight to your inbox. One signal a week — no noise.