I draw ERDs during stakeholder calls.
I code enough to challenge estimates.
I ship fast enough to catch overengineering.
I don't just build what stakeholders ask forâI ask what they actually need.
Patient outcomes over feature counts. Working software over perfect specs. The best product decisions aren't about what to buildâthey're about what not to build.
In 12 months at Hedfirst/Teligant, I co-led product strategy for a multi-tenant telehealth platform from concept to productionâwith real patients, live prescriptions, and operational pharmacy fulfillment.
Launched August 4, 2025 with 25 beta patients generating $12,475 in first-month revenue ⢠499 medications across 39 disease states ⢠48-state prescription fulfillment ⢠Zero routing errors across 200+ monthly prescriptions
Multi-tenant SaaS architecture with patient portals, doctor workflows, admin dashboards, and pharmacy integrations. Led product strategy, coordinated 4 engineers + CTO, and prioritized features that enabled 48-state fulfillment.
First brand implementation on Teligant platform. Launched August 4th, 2025 with beta patients, validating $499/year membership model. Integrated Choose Health lab testing and DoseSpot e-prescribing based on user research insights.
Three years in telehealth building compliant platforms for prescription-based healthcare services. Started as a full-stack engineer, evolved into technical product management by solving real implementation problems and learning what actually ships.
Started as Solutions Engineer helping enterprise healthcare clients deploy CompoundLive's white-label telehealth platform. Through discovery sessions with 6+ C-suite teams, I identified that our 5-month deployment cycles were killing sales velocityânot because features were missing, but because implementation was too bespoke. Built reusable integration frameworks and streamlined compliance workflows that cut deployment to 5 weeks. Result: 4 successful client implementations, 30% satisfaction increase, 25% boost in deal closures. This taught me that the fastest way to ship isn't more featuresâit's better processes.
Started as IC2 Software Engineer building prescription and subscription features in Ruby on Rails. When retention metrics dropped, I didn't just implement the feature request on the ticket. Analyzed user data, talked to support, and discovered the real problem: inflexible subscription management was forcing patients to cancel when they wanted to pause. Proposed a solution, wrote detailed specs, and built it. Result: 35% retention increase. This was my 'product manager moment'ârealizing my highest impact wasn't writing code faster, it was asking better questions first.
Trained 170+ developers across 9 cohorts in full-stack development. Designed curriculum based on industry feedback, iterated based on student outcomes, and achieved 85% placement rate within 6 months. Teaching taught me to break down complex technical conceptsâa skill I now use daily to bridge gaps between clinical stakeholders, engineers, and business leaders. Nothing tests your technical depth like explaining recursion to 30 people staring at you, or debugging someone else's code in real-time. Those skills directly translate to writing specs developers can implement and explaining technical tradeoffs to non-technical executives.
Looking for a technical product manager who can translate complex healthcare requirements into working software? Someone who writes specifications developers can actually implement?
I'm seeking senior product roles in healthcare technology where I can leverage my domain expertise and technical depth. Ideal fit: Series A-C health tech startups, B2B healthcare SaaS, telehealth platforms.