Somewhere in the middle of a growth-mode sprint -- competitor landing pages, an About page, a Careers page -- I shipped the thing you're reading right now. A public /blog and /changelog, live on the site, with the build-in-public posts that until today only existed in my notes. The recursion isn't lost on me: I'm writing a blog post about shipping the blog that contains the blog posts.
But there's something worth saying about why this matters beyond the meta joke.
Why a blog on a booking platform
Book A Sloth is a tool. Tools don't have stories -- they have features and pricing pages. Except: nobody trusts a tool built by a ghost. Especially in India, where the default assumption about a new SaaS product is that it'll disappear in six months and take your data with it. A blog that shows the building happening, week by week, decision by decision, is proof of life. It's the founder saying "I'm still here, I'm still working, and I'm not going anywhere."
That's worth more than a feature announcement. Features can be faked on a landing page. Thirty posts of honest, messy, sometimes-tired building can't.
The competitor pages
The other growth work this week: landing pages for people searching for alternatives. "Topmate vs Book A Sloth." "Calendly vs Book A Sloth." Not attack pages -- comparison pages. Honest about what they do well, clear about where we're different, and written for the person who's already frustrated with the other thing and looking for something that fits better.
Sujata's fingerprint is all over the copy. She kept asking: "What's the pain they're googling?" Not "what features do we have that they don't" -- that's a spreadsheet, not a story. "What's the specific frustration that made them type 'Topmate alternative' at midnight?" Find that frustration. Speak to it directly. That's the page.
The rest of the sprint
An About page that tells the truth instead of performing professionalism. A Careers page that exists even though it's just me, because it signals intent -- this thing is going somewhere, and there will be room for people. Branded error pages, because even a 404 is a moment your product is talking to a real person. And an app-layer IP-blocking system, because growth also means the wrong kind of traffic showing up, and you need a way to say no without breaking everything else.
Growth mode is different from building mode. Building mode asks "does it work?" Growth mode asks "can someone find it, understand it, and trust it enough to try it?" Different questions. Different muscles. Same product, finally seen from the outside.