From Zero to Production: Our 8-Week Telehealth Platform Story
A founder came to us with a validated idea and no code. Eight weeks later, 2,000 users were booking appointments. Here's exactly what we built and how.
The brief was simple: "I've validated the idea, I have 12 GPs ready to onboard, and I need a platform that lets patients book video consultations. I have 10 weeks before my funding round."
We had 8 weeks to build it, 2 weeks buffer for testing. Here's exactly what happened.
Week 1–2: Discovery and architecture
We ran a two-day workshop with the founder to map the core user journeys: patient booking, GP availability management, and the consultation itself.
Tech decisions made early:
We spent day 3 writing the data model. Getting this right saved us two weeks of migration pain later.
Week 3–5: Core product
By end of week 5 we had: patient registration and onboarding, GP profile pages, a working booking flow, and video consultations end-to-end. Not beautiful — functional.
We tested with two GPs and five patients internally. Found 23 issues. Fixed 19 of them.
Week 6–7: Polish and GP tooling
The GP dashboard was the most requested feature during internal testing. We built a clean schedule view, availability settings, and a patient history summary that shows before each consultation.
We also rebuilt the booking flow UI — the functional version was confusing. The rebuilt version tested at 94% task completion vs 71% in the original.
Week 8: Production
We deployed to GCP, set up monitoring with Datadog, configured alerts for failed bookings and dropped calls, and handed the founder a runbook.
The outcome
Go-live on a Thursday. 340 bookings in the first week. 2,000 registered users by end of month one. The founder closed their funding round.
What made it work: a sharp scope, a founder who made fast decisions, and a team that didn't disappear after hours.
Ready to build something?
Whether you're at idea stage or ready to scale, we'd love to hear about your project.
Start a conversation