Skip to content
SaaS

We Already Sold This Thing. So Why Am I Rebuilding It From Zero?

A working PHP product, real paying customers — and I'm rebuilding it from scratch anyway. Day 1 of building Book A Sloth in public, and the honest reason for the reset.

SD
Shubham Datarkar
· 3 min read
Updated

Let me start with the part that makes no sense.

I already have a product that works. It's built in PHP and SQL, it's running right now, and it has paying customers — real people who use it every week and tell me they love it. By every reasonable measure, I should be pouring my energy into selling more of it.

Instead, I'm sitting in front of an empty code repository, about to rebuild the entire thing from scratch on a completely different stack. No customers on it. No revenue. Nothing but a blinking cursor and a decision I can't fully justify to anyone, including myself.

So before I write a single line, I want to be honest about why.

What Book A Sloth actually is

The product is Book A Sloth — a booking page for creators and professionals. A coach, a tutor, a physiotherapist, anyone who sells their time. They get a page, clients pick a slot, pay, done. The whole promise is: be live and taking paid bookings in under two minutes.

The PHP version delivers that promise. But it delivers it with a catch nobody sees from the outside: every new customer means me. Someone wants in, and I'm SSH-ing into a server at midnight, running an install, fixing the one thing that always breaks. The software works. The delivery of the software is held together by my own two hands and my own sleep schedule.

That's not a business. That's a job I accidentally gave myself.

The question that wouldn't leave

A few weeks ago a customer asked me a simple question: "Can my friend just sign up for this somewhere?" And the honest answer was no. There's nowhere to sign up. There's only "message me and I'll set it up for you."

That question sat in my chest for days. Because the entire point of Book A Sloth — be live in two minutes — was a lie for everyone except the handful of people I'd personally onboarded.

The decision

So here's the decision: I'm rebuilding it as a proper web app. Anyone can sign up. No install, no server, no midnight me. New stack — and I'll get into why next post, because that choice deserves its own argument.

The scary part isn't the code. I can write code. The scary part is the feeling that I'm walking away from something that works to chase something that doesn't exist yet. Every instinct I have screams that you don't tear down a working thing.

Why I'm not throwing the old one away

But I keep coming back to this: the PHP version isn't being thrown away. It's the proof. It taught me what to build by letting me build it wrong first.

Real customers, real money, real feedback — that's not a failed prototype, that's the most expensive market research I'll ever get, and I already paid for it.

Today is Day 1. Empty repo. Working product I'm about to abandon on purpose. A two-minute promise I intend to finally make true.

Let's go.

Follow the rebuild

New entries as I go — wins, breakages, and the stack decisions behind Book A Sloth. One email when each drops.

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.