Skip to content
Build in Public

The homepage I should have built first

Nine sections, a pricing table, testimonials, and the question I'd been avoiding: what does this thing even look like to a stranger?

SD
Shubham Datarkar
· 3 min read
Updated

For a month I built the inside of the house -- the booking engine, the payments, the dashboard, the whole operational spine. Today I finally built the front of the house. The part a stranger actually sees first. And the moment I started, I understood why I'd been avoiding it.

Building the homepage forces you to answer the hardest question in one sentence: what is this, and why should I care? Every other screen gets to assume the person is already interested. The homepage can't assume anything. A stranger lands, gives you maybe five seconds of attention, and decides whether you're worth their time. Five seconds to earn the next thirty. That's it.

So I built it properly. Nine sections, each doing one job. The hero that states what Book A Sloth is in one line. Social proof from real people (Yukta, Mukesh -- their words, not mine). The feature breakdown that shows what a host actually gets. A pricing table that's honest about the tiers. A FAQ that answers the skeptical questions instead of hiding from them. And a footer that makes the whole thing feel like a real company, not a side project.

Sujata's rule

Sujata read the first draft and said something that rewrote half of it: "You're selling features. Nobody buys features. Sell the removal of pain." She was right. My first draft was a list of things the product does. The rewrite was about what a host's life looks like after the product removes their specific frustrations. "Automated reminders" became "no more no-shows." "Online payments" became "get paid before they arrive." Same product. Completely different story. The story that matters is never what you built -- it's what disappears from someone's day because you built it.

The admin side, too

While I was in homepage mode, I also overhauled the admin shell -- the internal interface I use to manage everything. Not customer-facing, but I live in it daily, and a tool you resent using is a tool you avoid using. Clean navigation, proper layout, the kind of small investment that pays back in every future hour spent managing the platform.

The product now has a proper front door and a proper story. A stranger can land, understand, and decide -- in the time it takes to read a sentence. That's what a homepage is for. Everything else I built this month was the answer. Today I finally wrote the question.

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.