Going from zero to one is a different discipline from scaling one to ten, and the habits that make senior operators great at big companies actively hurt them here. Zero-to-one rewards embarrassingly small scopes, launches that feel premature, and a willingness to learn in public. I know because I've done it twice with my own companies — and spent years unlearning big-company instincts in between.
The receipts
- Medzin — co-founded a healthcare discovery platform in Delhi, took it from idea to 18,000+ users and Rs. 60L ARR, and raised $150,000 in seed capital on the traction.
- WisOwl AI — currently building an agentic hiring platform; shipped the semantic matching engine myself (FAISS, Supabase pgvector) and grew to 5,000+ signups and 15+ recruiter partnerships with zero paid marketing.
My operating principle, learned the expensive way: speed is a feature. The best product strategy is a fast feedback loop — shipping early and iterating on real user behavior beats months of planning in a silo, every single time.
How a launch engagement runs
Weeks 1–2: cut the scope. We define the single behavior v1 must produce and delete everything else. Most launch plans I see shrink by 60% in this step, and every deletion moves the date closer.
Weeks 3–6: build and instrument. I run the build as your product lead — specs, trade-offs, weekly user exposure even before launch — and wire the instrumentation so day one produces learning, not just a press release.
Weeks 7–10: launch and iterate. Distribution plan matched to where your users already are, then tight loops: watch behavior, talk to users, ship, repeat. The goal by week ten is not polish — it's evidence.
If you have a validated idea and a team that can build, I'll get you to a real launch in a quarter. If the idea isn't validated yet, say so — that's a shorter, cheaper engagement that should happen first.