What it really costs to launch a telehealth product

The cost centers nobody puts in the pitch deck

A prescription telehealth product is a medical practice wearing a product's clothes. Before the first patient, someone has to pay for each of these:

• Medical leadership. A medical director who owns protocols, an escalation path, and quality review. Fractional at first, but never optional.
• Legal structure. Corporate-practice-of-medicine compliance usually means forming professional entities and management agreements (the MSO/PC model) — specialized healthcare counsel, state by state.
• Clinician network. Recruiting, credentialing, licensing support, and scheduling coverage for every state you serve — plus the ongoing cost of keeping licenses current.
• The vendor stack. An EMR, e-prescribing (EPCS-certified if you touch controlled substances), a pharmacy partner, a lab partner, benefits/eligibility tooling if you take insurance, and identity verification. Five to seven contracts is typical.
• Integration engineering. The unglamorous majority of the build: making those five to seven vendors behave like one system, with retries, reconciliation, and audit logging at every seam.
• Compliance operations. Board registrations, telehealth rule monitoring across states, HIPAA program, BAAs, and audit-trail discipline. This is a payroll line, not a project.

The timeline is a cost too

Assembled in-house, this is commonly an eight-to-twelve-month path and a low-six-figures budget before revenue — the $200K+ figure you will hear is mostly people and contracts, not software. The subtler cost is the calendar: a year of a competitive category's best growth window spent building plumbing your customers will never see.

What "buy" actually buys

Clinical infrastructure collapses the middle four cost centers — clinician network, vendor stack, integration, and compliance operations — into one contract and one API. You still own the parts that differentiate you: brand, product experience, funnel, pricing, and the patient relationship. The economics shift from fixed (payroll and retainers before your first patient) to variable (platform and per-visit fees that scale with volume).

When building yourself is right anyway

Honesty requires the other column. Owning the full stack can make sense when clinical operations isyour differentiation (you are building a medical group, not a brand), when your category needs protocols no platform supports, or when you are already at a volume where infrastructure margin exceeds the cost of an in-house team — a calculation worth actually running, not assuming.

The comparison that matters

Do not compare "platform fee versus free." Compare platform fee versus the fully loaded cost of the six centers above, divided by your realistic patient volume in year one. At small and mid volume the answer is rarely close — which is why the build-vs-buy decision is usually really a decision about how fast you want to find out whether your product works.

Frequently asked questions