Co-founder · Head of Product & Tech · HealthPilot.ai
I built HealthPilot's team from zero to fifteen, rebuilt the product until it clicked with doctors, and took it into two large hospitals. Along the way I headed both product and engineering.
By the numbers
[ 01 ]
0→0
People hired
Built the HealthPilot team from nobody to fifteen across engineering, product and operations.
[ 02 ]
0
Hospitals closed
Signed two large hospitals on the platform after finding product-market fit.
[ 03 ]
PMF
Product-market fit
Built, shipped, scrapped and rebuilt until clinics kept coming back.
[ 04 ]
P+T
Product & Tech
Headed product strategy and engineering: roadmap, architecture and delivery.
Chapter 01
An idea and an empty repo
HealthPilot started with a simple observation: patients drop out of care between visits, and clinics have no way to see it coming. No team, no product, no customers, just the problem.
~ $
team: 1 · users: 0 · revenue: 0
Day zero
Chapter 02
0 → 15 people
I hired and led the team from the first engineer to fifteen people across engineering, product and operations. I set up the hiring bar, the rituals and the engineering culture along the way.
00 / 15
Headcount
Chapter 03
Build · ship · learn · rebuild
We built the product, put it in front of real doctors and patients, and threw away what didn't work. Then we did it again, several times, with each version shaped by what we heard in the clinic.
Iteration loop
Chapter 04
The signal
Eventually it clicked: an AI-native patient engagement platform that clinics actually used every day to keep patients on track and cut dropouts.
Retention, illustrative
Chapter 05
2 large hospitals
With product-market fit in hand, we took HealthPilot to enterprise and closed two large hospitals on the system.
Hospitals live
The role
I owned the whole path from a doctor's problem to shipped code: deciding what to build, designing how it works, and hiring the people to build it.
Currently listening to your favorite vibes.