From signed contract to first prescription: a realistic telehealth launch timeline
Launch timelines in this industry range from 'days' to 'a quarter,' and both numbers are honest — they just measure different things. Here is what is on the critical path and what only looks like it is.
Lithos Staff
Photograph via UnsplashOn existing infrastructure, the clinical back office (clinicians, pharmacies, compliance) is ready on day one; what gates your launch is your side — protocol sign-off, the front-end, payments, and the marketing review you need for ads. A realistic path: week 1 kickoff and protocol selection, weeks 1–3 front-end integration and content, week 3 end-to-end test patients, week 3–4 soft launch with real patients, then LegitScript and paid acquisition in the following weeks. Nine-day launches happen when the brand uses a hosted portal and skips paid ads; ninety-day launches happen when the medical group is being built from scratch.
Two different clocks
When a vendor says “live in nine days,” they usually mean a hosted portal with their template, their checkout, and organic traffic. When a founder says “it took us a quarter,” they usually mean they stood up a medical group, recruited clinicians, negotiated with pharmacies, and then built the product. The interesting number is in between: a brand with its own front-end, on infrastructure that already runs the clinical side, targeting real patients and then paid acquisition.
Week by week
| Week | Clinical side (infrastructure) | Your side (brand) | Gate |
|---|---|---|---|
| 1 | Kickoff; protocol selection for launch products; sandbox credentials; pharmacy bench confirmed for launch states | Confirm products, states, pricing; assign owners for front-end, payments, content | Protocols signed off |
| 1–2 | Intake configured per product and state; consent and identity flows ready | Integrate patient creation, intake, and encounter submission; design the patient status screens | Intake renders in your product |
| 2–3 | Webhook events wired; clinician queue tested with synthetic patients | Checkout and subscription billing; order-status and messaging UI; support playbook | End-to-end test patient succeeds |
| 3 | Production credentials; real pharmacies; on-call escalation path agreed | Website and policies written to ad-platform standard; LegitScript application submitted | Go/no-go |
| 3–4 | First real encounters reviewed; turnaround monitored daily | Soft launch to waitlist, email, and partners; watch conversion and support tickets | First prescription shipped |
| 5–12 | Add states and products as demand shows; refill cycle running | LegitScript decision; ad accounts approved; paid acquisition begins | Certified; ads live |
What is actually on the critical path
- Protocol decisions. Which products, at which starting doses, with which labs, in which states. Every change after week one costs a week. Decide, launch, iterate with data.
- Your front-end and checkout. Intake, payment, status, messaging. This is the bulk of launch engineering and it is entirely under your control.
- Marketing content to standard. Written for LegitScript and ad-platform review from the start. Rewriting a website after a rejection is the most common cause of a launch slipping a month; see LegitScript certification.
- Payments. Processors treat telehealth and compounded medications as higher-risk categories; underwriting can take longer than you expect. Start early.
What only looks like it is on the critical path
- Clinician recruiting and licensing. Months if you do it yourself; day one on a network that already covers the states. See collaborating physicians for why.
- Pharmacy contracts. Same: a bench with verified licensure exists or it does not. See pharmacy licensing.
- Compliance documentation. BAAs, consent forms, state modality rules — already encoded in mature infrastructure.
- Building every vertical at once. Launch one product line well; add the second when the first has a refill cohort.
Sequencing the launch
The pattern that works: a two-week integration sprint, one week of test patients, a soft launch to owned channels while LegitScript is in review, then paid acquisition once certified. Programs that wait for certification before touching a single patient lose a month of learning; programs that run ads before certification lose the ad account.
Frequently asked questions
How long does it take to launch a telehealth business?
On infrastructure that already operates the medical group and pharmacy network, three to four weeks to first real patients is typical, with a custom front-end. A hosted portal can be faster; building your own clinical operations from scratch takes months.
What is usually the bottleneck?
Rarely the clinical side. Most often it is the brand’s front-end and checkout, protocol decisions that keep changing, and — for paid acquisition — LegitScript certification and ad-platform approval, which run on their own clock.
Can we launch before LegitScript certification?
Yes, through organic, email, partner, and affiliate channels. Paid ads on Google and Meta for prescription telehealth wait for certification. Many programs soft-launch to a waitlist while the application is in review.
What do we need to have decided before kickoff?
Which products and states you are launching with, your pricing and subscription structure, whether visits are async-first, and who on your team owns the front-end, payments, and marketing content. Everything else can be decided during integration.
From first call to first patient, in weeks.
A 15-minute intro call, sandbox credentials the same day, go-live in 3–4 weeks — new launches and existing patient bases alike.