Direct-to-Patient Telehealth and Pharmacy MVP for a Specialty Pharma
Let's Connect
Overview
What we built
A specialty pharma had to launch its first direct-to-patient telehealth and pharmacy channel in a fraction of the time its own teams believed possible. We delivered a compliant MVP in sixteen weeks, live across all 14 target states.
In plain terms: the company made specialty medicines but had never sold or delivered anything directly to patients. It wanted patients to be able to see a clinician by video and have prescriptions delivered to their door across 14 states, yet it had no consumer-facing engineering capability in house. Internal estimates put a full platform at eighteen months, while the executive team wanted to launch within two quarters. On top of that, every state applied its own telehealth and pharmacy rules, and those rules had to hold from the first day of trading.
We built the smallest platform that could launch legally and grow afterwards. In sixteen weeks patients could check their eligibility, book and attend a video consultation with an independent clinician, and have their prescription passed to a licensed fulfilment pharmacy for home delivery, all running on HIPAA-aligned infrastructure. The channel went live in all 14 target states within 16 weeks, 74% of eligible patients completed intake through to a booked consultation in a single session, and the median time from completed intake to a shipped first prescription held under 72 hours across the launch quarter.
The Problem
First direct-to-patient channel launch
The company knew specialty medicines, but its entire commercial model ran through intermediaries. Launching telehealth consultations and home-delivery pharmacy across 14 states meant becoming a consumer business overnight: patient sign-up, clinical scheduling, prescriptions and doorstep delivery, none of which the organisation had ever built. There was no consumer-facing engineering capability in house, so every option started from zero.
The timelines did not agree with each other. Internal estimates put a full platform at eighteen months, while the executive team wanted a launch within two quarters. Waiting was commercially unacceptable, but nobody inside the business could show a credible path to the shorter date, and the gap between ambition and estimate widened in every planning session.
Regulation raised the stakes further. Each of the 14 states carried its own telehealth and pharmacy rules, covering how consultations could run and how prescriptions could be fulfilled, and those rules had to hold from day one. A platform that launched fast but failed a single state's requirements would have been worse than no launch at all.
No consumer capability
The pharma had never built patient-facing software and had no consumer-facing engineering capability in house, so the new channel could not be staffed from within.
Eighteen-month estimate
Internal estimates put a full platform at eighteen months, far beyond the two-quarter launch window the executive team had set for the channel.
Rules in every state
Each of the 14 states applied its own telehealth and pharmacy rules, and every one of them had to be satisfied from the first day.
Everything at once
Intake, eligibility, consultations, prescriptions and delivery all had to work together at launch; there was no partial version of the channel worth shipping.
What it was costing them
The cost of the status quo was the channel itself. Every month spent on an eighteen-month build was a month patients could not reach the company directly, a month competitors could use, and a month of executive patience spent. Worse, a compliance failure in any one of the 14 states at launch would have put the whole direct-to-patient strategy at risk, not just the platform.
The Solution
Sixteen-week compliant MVP
We scoped the MVP around a hard question: what is the smallest platform that can legally serve a patient in every one of the 14 states? Anything that did not serve that answer moved out of scope. Native apps and loyalty features were deliberately deferred to post-launch releases, which kept the sixteen-week plan honest from the first sprint.
The build centred on a state-aware rules engine. Patient intake and eligibility flows read their behaviour from configuration for each state, so regulatory differences lived in data rather than in code. Scheduling and video consultations ran through an independent clinician network's API, and e-prescriptions handed off to a licensed fulfilment pharmacy partner, letting us integrate proven, compliant services instead of building them from scratch.
Everything ran on HIPAA-aligned infrastructure from the first commit, and order tracking gave patients visibility from consultation through to the parcel at their door. Because state rules lived in configuration, regulatory changes after launch did not need engineering time: 11 state-rule updates shipped in the first quarter through the configuration-driven rules engine, without a single code release.
Key decisions
Rules as configuration, not code
Every state's telehealth and pharmacy requirements were expressed as configuration driving the intake and eligibility flow, so regulatory change became an update rather than a release.
Partner for clinical capacity
Scheduling and video consultations ran through an independent clinician network's API rather than an in-house clinical operation, removing the hardest licensing burden from the build.
Hand fulfilment to a licensed partner
E-prescriptions passed to a licensed fulfilment pharmacy partner, so the MVP could promise home delivery without the pharma standing up its own dispensing operation.
Defer apps and loyalty
Native apps and loyalty features were consciously pushed to post-launch releases, protecting the sixteen-week window for the flows a legal launch actually required.
Compliant infrastructure from day one
The platform ran on HIPAA-aligned infrastructure from the start, so patient data handling never needed a retrofit as the channel grew.
Measurable Impact
What changed after launch
The MVP went live in all 14 target states within 16 weeks, against an 18-month internal build estimate. The launch funnel worked from the start: 74% of eligible patients completed intake through to a booked consultation in a single session, and the median time from completed intake to a shipped first prescription held under 72 hours across the launch quarter.
The rules-engine bet paid for itself in the first quarter, when 11 state-rule updates shipped through configuration alone, without a code release. The pharma now runs a working direct-to-patient channel on a platform designed to grow, and the deferred native apps and loyalty features have a live, revenue-earning foundation to land on.
Launch timeline
A full platform estimated at eighteen months
MVP live in all 14 states within 16 weeks
Patient journey
No direct channel, every sale through intermediaries
Intake to booked consultation in a single session for 74%
Prescription delivery
No home-delivery capability of any kind
Median under 72 hours from intake to shipped prescription
Regulatory change
Every rule change implied an engineering release
11 state updates shipped via configuration, no code release
Headline results
MVP live in all 14 target states within 16 weeks, against an 18-month internal build estimate
74% of eligible patients completed intake through to a booked consultation in a single session
Median time from completed intake to shipped first prescription held under 72 hours across the launch quarter
11 state-rule updates shipped in the first quarter through the configuration-driven rules engine, without a code release
Tech & Tools Used
What powered the build
Every tool below earned its place in this engagement. Here is the part each one played.
Next.js
Delivered the patient-facing intake, eligibility, booking and order-tracking experience, giving the pharma's first consumer channel a fast, accessible web front end from launch day.
NestJS (Node.js)
Ran the backend services behind intake, scheduling and fulfilment hand-offs, including the configuration-driven rules engine that applied each state's telehealth and pharmacy requirements.
PostgreSQL
Held patient journeys, orders and the per-state rule configuration in one relational store, keeping eligibility decisions and order history consistent and auditable.
Redis
Cached state-rule lookups and managed session state through the intake flow, keeping the eligibility experience responsive during the single-session journey patients were asked to complete.
AWS ECS + RDS
Provided the HIPAA-aligned infrastructure the platform launched on, running the containerised services and managed database inside a compliance-ready environment from the first commit.
Stripe
Handled patient payments for consultations and prescriptions, so the pharma's first consumer transactions ran on proven payment infrastructure rather than an in-house build.
Twilio SMS
Sent appointment reminders and order-status updates by text, keeping patients informed at every step from booked consultation through to the prescription arriving at home.
DoseSpot e-prescribing API
Carried the e-prescription hand-off from the consulting clinician to the licensed fulfilment pharmacy partner, the regulated link between the telehealth visit and home delivery.
Datadog
Monitored the launch across every state's traffic, alerting the team to failures in the intake, consultation or fulfilment flows before patients felt them.
Ready to Build your Pharma & Life Sciences Business with MVP Development
Ask Byte
Ask Byte
Typically replies instantly
just Now
Hi! I'm OrganByte's assistant. How can I help you today?
AI-generated content may be incorrect
