Previously on The Build: Asha turned ClinicFlow from an idea into a spec a stranger could build correctly — including a page that listed everything she was deliberately not building. (Episode 2 is here.) Then she handed it over, and the hardest eight weeks of being a non-technical founder began.
Here's the fear, stated plainly: for the next two months, someone is building the most important thing in your life, and you can't read a single line of what they produce. How do you tell if it's going well?
Asha couldn't audit the code. But she could absolutely tell whether the project was healthy — and so can you, with the right handful of habits. None of them require being technical. All of them require refusing to be passive.
Demand demos, not status reports
A status report is words: "Made good progress on the scheduling module this week." Words are easy to fake, even unintentionally. A demo is the thing actually working in front of you, that you click yourself. Asha's one rule, set on day one: every Friday, I see it work, and I drive.
This single habit catches more problems than any contract clause. A developer who's genuinely on track is happy to show you. A developer who keeps offering reasons why a demo isn't possible this week is telling you something — usually that there's less working than the status updates implied.
The danger sign isn't a missed deadline. It's a talky demo.
This is the counterintuitive part. A slipped date is normal and honestly told. The real warning is the demo that's all narration — "so here's where the calendar will go, and imagine this button does X." Drifting projects don't announce themselves with a red flag. They announce themselves with a tour of things that don't quite click yet. When you find yourself watching a slideshow instead of using software, slow down and ask hard, specific questions.
Catch scope drift in both directions
Scope drift cost more of Asha's nerves than anything else. It runs two ways. Sometimes the developer gold-plates — building an elaborate version of something your spec marked simple. Sometimes you do it — "while we're in there, could we also…". Both eat the timeline. The fix is the spec from Episode 2: when a request appears, you ask out loud, "Is this on the page, or is this new?" New isn't forbidden. It just has to be a decision, with a cost, not a drift.
Own everything from day one — especially the keys
This is where I see non-technical founders get genuinely hurt, and it has nothing to do with code quality. Every account must be in your name. The code repository, the hosting, the database, the domain, the third-party services. You grant the developer access; you never receive access to their accounts. If the relationship ends — amicably or not — you walk away owning your business. Founders who skip this discover, at the worst possible moment, that they've been renting their own company. This is the same dynamic that decides whether your first developer hire becomes an asset or a hostage situation.
The twist: control isn't about catching them. It's about being someone worth doing great work for.
Halfway through, Asha's build slipped a week. Her instinct was to clamp down. Instead, the Friday demo showed her exactly why — a third-party insurance integration was fighting back — and because she could see the real problem, she made a real decision: cut that integration from v1, ship without it. The slip became a scoping win.
That's the secret. The habits above aren't surveillance. They're how you stay close enough to make good calls fast — and good developers love a founder who can make a fast, informed decision. The same eight-week rhythm I describe in my exact build process only works because the founder is present in it, not hovering over it. Whether you went with a solo developer, an agency, or some mix of the two, the muscle is identical: show me it working, weekly.
What to take from this
- See it work every week, and drive yourself. Demos beat status reports; clicking beats watching.
- Fear the talky demo more than the slipped date. Drift hides inside narration.
- Make every "while we're at it" an explicit decision. New scope is fine; drift is not.
- Put every account in your name on day one. Own the keys, or you're renting your company.
Eight weeks later, Asha had something real: ClinicFlow worked, it was hers, and it had never taken a single payment from a single customer. Which is its own kind of terrifying — because now she had to put it in front of the world and ask people to pay.
Next in The Build: Launch Day to Your First 10 Paying Customers — the unglamorous grind nobody warns you about.
If you've handed off a build and that quiet dread about whether it's going well is creeping in, you don't have to guess. I sit in on demos for founders and translate — green, yellow, or red — in plain English. Send me where your project's at.
