The answer, in weeks
A single-state DTC telehealth brand launched on a white-label platform typically takes 8 to 13 weeks from incorporation to first patient, and paid ads start once LegitScript certifies the site, which on the standard track is four to eight weeks after you file. Built from scratch, the same launch takes 5 to 9 months. Those ranges match the budget math in our line-item cost post, which puts a platform launch at 60 to 90 days and a self-assembled one at 5 to 9 months.
What surprises most founders is where the weeks go. On a platform, the software is ready long before you are. The slow items are the professional corporation, the physician's license in your launch state, the pharmacy relationship, the payment processor's approval and the LegitScript file. Those take the same calendar time whichever path you choose. A custom build does not speed any of them up; it adds a second, longer track that the paperwork ends up waiting on.
Everything below is an estimate drawn from published timelines and the launches we see, for one state and one program. Ten states mostly adds licensure time per state, which runs in parallel if you start every state in the first week.
The week-by-week table
| Week | Paperwork track (same on both paths) | Platform path | Custom build path |
|---|---|---|---|
| 1 | Form the MSO, get an EIN, hire healthcare counsel, sign a physician owner or medical director, start the PC filing | Sign the platform, start brand kit and domain | Write the spec, hire or contract engineers |
| 2 | Draft the MSO-PC management agreement; start pharmacy onboarding | Storefront and intake configured for one program | Design starts: storefront, intake, portal |
| 3-4 | PC filing in progress; malpractice quote; refund and cancellation policy drafted | Pricing, subscriptions, pharmacy routing set; storefront copy final | Pick an EHR, e-prescribing vendor, billing stack and support desk; integration scoping |
| 5-6 | Pharmacy live; processor application filed once PC, medical director, pharmacy and checkout can all be named | Test orders end to end; clinician accounts set up | Storefront and intake in development |
| 7-8 | PC registered (1 to 2 months is typical); insurance bound; LegitScript filed if the site is final | Waiting on paperwork | Billing and pharmacy integrations in development |
| 9-13 | Processor approved; LegitScript under review (4 to 8 weeks standard, or review starts within two business days for an extra $2,500) | First patients from organic, referral and email; ads once certified | Still building |
| Months 4-6 | Scaling the ad test | Portal, refills, retries, QA; LegitScript can only be filed once the real site exists | |
| Months 5-9 | First patients; ads after certification |
Two notes on the table. The PC filing time is the one number in it that varies most by state, and the LegitScript timeline is the one founders misjudge most: one r/telehealth founder reported eleven weeks doing it alone (September 13, 2026), largely because of round trips on an incomplete application.
The four tracks that actually set your launch date
Think of the launch as four paperwork tracks plus one software track. On a platform the software track is short, so the longest paperwork track is your launch date.
Entities and the physician. A non-physician founder cannot own a medical practice in most corporate-practice-of-medicine states, so the standard structure is a management company you own plus a professional corporation owned by a physician, connected by a management agreement (the MSO and friendly-PC model explains the mechanics). You need the physician before you can file the PC. That makes recruiting the medical director a week-one task, and the single most common reason a launch slips by a month. If that physician is not already licensed in your launch state, add licensure time; the Interstate Medical Licensure Compact covers 44 states plus DC and Guam and issues licenses in weeks rather than months, per our 50-state sequencing post.
Pharmacy. Onboarding takes roughly weeks 2 to 6 and is mostly calendar time (contracts, state coverage checks, test prescriptions). It can start before the PC exists because the conversation is commercial at first, but the pharmacy will need the prescriber details before anything ships.
Payment processing. Stripe lists telemedicine, online pharmacies and card-not-present prescription products as restricted businesses that need approval. Underwriters ask for the PC, the medical director, the pharmacy, the refund policy and the checkout flow, which is why this application cannot go in until week 5 or 6. Processors do not publish review times; we budget two to four weeks, and plan for a rolling reserve. The underwriting side is in passing payment processor review.
LegitScript. It reviews licensure, your pharmacy and clinical partners, and the website itself, including state disclosures, privacy policy and claims. So it can only be filed when three other things are true: the PC is registered, the pharmacy is certified or accredited, and the storefront copy is final. It costs $975 to apply and $2,150 a year once certified, per website.
What runs in parallel, and what has to wait
Founders lose most of their time by running in sequence things that could overlap. The dependencies are simpler than they look.
Can start on day one, all at once: the MSO, counsel, medical director search, platform contract, brand work, pharmacy conversations.
Has to wait for the physician: the PC filing, and anything that needs a prescriber named (pharmacy activation, processor application).
Has to wait for the PC, the pharmacy and a final website: LegitScript.
Has to wait for the processor: taking money. You cannot charge a patient without an approved merchant account, so the processor is a hard gate on first revenue.
Does not have to wait for LegitScript: seeing patients. Certification gates advertising on Google, Microsoft, Meta and TikTok. It does not gate care. A brand with an email list, a clinic's existing patients or a creator audience can treat its first patients while the application is under review, and we think every founder should try to, because those first cohorts are where the intake and support problems show up cheaply.
On a platform, that last point is the biggest timeline lever you have. The storefront is live in the first weeks, so organic patients can start the day the processor approves, and the ad budget starts when the certificate arrives.
Where a custom build lands on the critical path
A custom stack means building a storefront, an intake engine with conditional logic, an EHR or charting layer with e-prescribing, provider routing by state, subscription billing that charges only after clinical approval and retries failed cards, a pharmacy integration with status updates, and a patient portal for refills and messages. Each piece has a vendor or an engineer, and the integration between them is where the months go. Our cost post prices that pile at $60,000 to $250,000 before the first patient.
The timing problem is worse than the cost problem. LegitScript reviews the live website. If the website is still being built in month four, the certification clock has not started, so the custom path delays ads by the build time plus the review time. And a custom build rarely finishes on schedule: the last 20% (failed payments, refunds, pharmacy exceptions, patients who change state) is exactly the part a first spec misses.
There are good reasons to build anyway. A team with an unusual clinical workflow, payer billing, or an existing engineering org may decide the control is worth two quarters. We laid out that decision in the build vs buy analysis. For a founder-led cash-pay brand, we would not build first and launch second.
Where Turbopills fits
Turbopills removes the software track. The storefront on your domain, conditional intake, state-aware routing to licensed providers, billing that starts only after a provider approves, pharmacy routing with live status, and the branded patient portal ship as one configured system, so the build column in the table above collapses into a few weeks of configuration that run alongside the paperwork. That is what "weeks, not months" means on our homepage, and it is also its limit: we cannot make your PC register faster, recruit your medical director, file your LegitScript application or approve your merchant account. Those stay yours, and on our platform they become the critical path.
We are in private beta, onboarding is hands-on and capacity is limited. Ask us in a demo to walk your program through the table above and tell you which weeks are ours and which are yours.
FAQ
How long does it take to start a telehealth business? For one state on a white-label platform, about 8 to 13 weeks from incorporation to first patient, with ads starting after LegitScript certification. Building the software yourself stretches that to 5 to 9 months. Each extra state mostly adds entity and licensure time, which can run in parallel.
What takes the longest when launching a telehealth company? Usually the professional corporation and the physician who owns it, followed by LegitScript if you file late or incompletely. On a custom build, the software is the longest step and pushes LegitScript back with it.
Can I see patients before LegitScript certification? Yes. LegitScript certification is required to advertise prescription telehealth on Google, Microsoft, Meta and TikTok, not to treat patients. You still need the PC, a licensed prescriber, a pharmacy and an approved processor.
How long does it take to build a telehealth platform from scratch? Typically four to nine months before the first patient, for a storefront, intake, e-prescribing, billing, pharmacy integration and portal that work together, plus ongoing maintenance after launch. The budget side is in our line-item cost post.