Previously on The Build: Asha won her first ten paying clinics the hard way — by hand, one conversation at a time — and discovered the unscalable grind was actually her roadmap. (Episode 4 is here.) This is the finale: the first 90 days after launch, when the problems that only appear once people truly depend on you come due.
It was a Saturday morning. A fully-booked clinic was running its front desk on ClinicFlow when the app went down — right in the middle of their busiest hour. Asha's phone lit up. Her stomach dropped. This, she thought, was the disaster.
It wasn't. The outage was scary and it was fixed by lunch. The real threat to her business was quieter, slower, and she almost missed it entirely.
First: the stuff you deferred comes back to collect
Remember all the things Asha deliberately marked "out of scope" to ship in eight weeks? They don't disappear. They wait. In the first 90 days, the deferred decisions show up as real problems:
- The things that break under real use. Code that worked fine for one test clinic behaves differently when ten clinics hit it on a Monday morning. The Saturday outage was a database query that was lazy at one-clinic scale and fatal at ten.
- The debt you couldn't afford before — and can now. Post-launch, with revenue coming in, you finally have the room to pay down the corners you cut. This is the good kind of "what breaks" — you fix the foundation while it's cheap, instead of waiting for the $50K version of the same problem.
- The reliability bar quietly rose. Before launch, a bug was an inconvenience. Now it's someone's ruined Saturday. The same technical decisions you made casually pre-launch are now load-bearing.
The twist: the bottleneck wasn't the code. It was the founder.
Here's what nearly killed Asha's momentum, and it had nothing to do with servers. Every new clinic was onboarded by Asha. Every support question went to Asha. Every small fix request routed through Asha. The thing that won her the first ten customers — doing everything herself — became the thing that capped her at ten.
She wasn't running a business. She was the business, and she was full. The outage was loud, so it got fixed fast. The bottleneck was silent, so it almost didn't. In the first 90 days, the most dangerous problems are the ones that don't page you.
When to hire, and what to hire first
The fix isn't "hire a team." It's to find the one task eating the most of you and remove it. For Asha, it wasn't a second developer — it was a part-time support person who could handle onboarding from a checklist she wrote (the checklist she'd earned by doing it ten times by hand). That freed her to do the two things only she could: sell, and decide.
The rule for early hiring: don't hire to grow, hire to un-stick. Find your bottleneck, name it honestly, and remove that — not the thing that sounds most impressive to hire for.
Stay close to the right numbers — not all of them
Ninety days in, you can finally see real usage, and it's tempting to drown in dashboards. Resist. A handful of numbers tell you whether you're healthy: are customers still showing up, are they paying, are they leaving, and is the thing reliable. I've broken those down into the six numbers worth watching — and pointedly, the analytics dashboard Asha was once sure was the heart of ClinicFlow still doesn't exist. She never needed it.
What to take from this — and from the whole series
- Deferred decisions come due. The corners you cut to ship are now your first fixes — and post-revenue, you can finally afford them.
- The loud problem isn't the real one. Outages page you; bottlenecks don't. Hunt the silent threat.
- Hire to un-stick, not to impress. Remove your single biggest bottleneck first.
- Watch a few numbers, not all of them. Health is a handful of metrics, not a wall of charts.
Five episodes ago, Asha was a physiotherapist with an idea and the urge to start building immediately. She ended up with a real, paying, working product — not because she moved fast, but because at every stage she did the unglamorous thing first: validated before building, specced before handing off, watched before trusting, sold by hand before automating, and fixed the foundation before chasing growth. That's the whole series. That's the whole job.
That's a wrap on The Build. If you read it in order — Episodes 1, 2, 3, 4 — you now know the journey better than most people who've taken it.
Wherever you are on this path — idea, build, launch, or the messy first 90 days — you don't have to navigate it alone or by guesswork. Tell me where you're stuck, and I'll give you an honest, senior read on what to do next.
