--- title: In-House Telehealth vs MSO Platform: Cost and Speed (2026) description: In-house telehealth operations vs an MSO platform: cost centers, timelines, CPOM/HIPAA/DEA risk, a decision matrix and the hybrid API path. slug: build-vs-buy-telehealth-operations date: 2026-10-06 updated: 2026-10-06 author: MyOrbitHealth Partner Growth Team category: Growth --- # In-House Telehealth Operations vs an MSO Platform: Cost and Speed For most brands launching or scaling a cash-pay telehealth program in 2026, an MSO platform is cheaper and faster than building operations in-house, and it stays cheaper until volume is very high or the clinical model is genuinely unique. Building in-house means forming an MSO and a physician-owned professional entity, recruiting and credentialing clinicians state by state, licensing or building a HIPAA-compliant EHR with e-prescribing, negotiating pharmacy and lab contracts, running a compliance program, and earning LegitScript certification before a single ad runs. Our [telemedicine startup cost breakdown](/blog/cost-to-start-telehealth-business) puts that path at $250,000 to $900,000 or more and 6 to 12+ months to first patient. An MSO platform typically costs a four-to-low-five-figure setup plus a monthly fee and per-consult costs, and brands go live in weeks. In-house wins in three situations: very high and predictable volume, insurance billing, or a clinical model no platform can run. Everyone else should buy the regulated layer, keep the brand, and reconsider once the numbers justify owning more. This is general information, not legal advice. ## Key takeaways - Building telehealth operations in-house requires at least ten separate cost centers, from entity formation and physician ownership to credentialing, EHR, EPCS, pharmacy, labs, compliance, LegitScript and support, and most of them are fixed costs that start before the first patient. - The in-house path typically costs $250,000 to $900,000 or more and takes 6 to 12+ months, while a white-label or MSO platform typically costs a four-to-low-five-figure setup plus monthly and per-consult fees and launches in weeks. - The risk comparison matters as much as the cost comparison: CPOM, HIPAA, and DEA obligations do not disappear on a platform, but a platform that already operates the MSO and friendly-PC structure, a BAA, and EPCS absorbs most of the day-to-day exposure. - Building in-house wins at very high and predictable volume, for payer-billed practices, and for clinical models that no platform can support; for everyone else, the per-consult fee is cheaper than owning an idle clinical operation. - A hybrid path exists: existing practices and software companies can keep their EHR, storefront or app and add the regulated layer through an API, which avoids both a full build and a full migration. ## Who this is for - Founders and operators deciding whether to hire clinicians and form entities or launch on a telehealth infrastructure partner. - Finance and operations leads at a DTC health brand modeling year-one cost and time to first patient under each path. - Existing clinics and product teams with a stack already in place who want to add virtual care without replacing what works. ## What does "in-house" telehealth actually mean? The phrase hides a lot of work. An in-house telehealth operation is not a Zoom link and a doctor. It is a regulated medical practice plus the technology, pharmacy and compliance operations that surround it, all owned and operated by your company and its affiliated professional entity. At minimum, the in-house list is: a corporate structure that satisfies the corporate practice of medicine doctrine (CPOM), meaning an MSO you own, a professional corporation owned by a licensed physician, and a fair-market-value management services agreement between them, as covered in our [MSO model and compliance guide](/blog/telehealth-compliance-mso-model-guide); clinical staffing, including a medical director, prescribers (MD, DO, NP, PA) licensed in every state you serve, and collaborating physicians where state law requires them for NPs and PAs; one license per clinician per state; primary-source credentialing and recurring exclusion screening; an EHR and telehealth platform with a BAA from every vendor that touches PHI; Surescripts-connected e-prescribing, with EPCS and two-factor identity proofing if testosterone is ever on the roadmap; pharmacy contracts licensed to ship into each state, with cold chain where needed; lab accounts, provider-signed orders and result ingestion; a HIPAA and state-rule compliance program with counsel on retainer; LegitScript certification, which Google and Meta require before telehealth and pharmacy ads run; and HIPAA-trained patient support with a clinical escalation path. An MSO platform (sometimes called white-label telehealth infrastructure) runs all of that under its own structure and lets your brand sit on top. You keep marketing, pricing, the storefront and the customer relationship. That division of labor is the entire argument, so the rest of this post prices and times each item under both paths. ## What are the cost centers of building telehealth operations in-house? Every line below is a real invoice if you build. The ranges are directional and consistent with our [startup cost breakdown](/blog/cost-to-start-telehealth-business); for ranges applied to your own states, vertical and volume, use the [telehealth startup cost calculator](/tools/startup-cost-calculator). Your numbers will differ with footprint and negotiating leverage. | Cost center | In-house: what you pay for | Directional magnitude | On an MSO platform | |---|---|---|---| | Entity formation and CPOM structure | MSO plus physician-owned PC, management services agreement, fair-market-value opinion, per-state entity work | Low to high five figures in year one, plus annual maintenance per entity | Operated by the platform; you still retain your own counsel | | Physician owner and medical director | Monthly retainer for the PC owner and clinical leadership, paid whether or not patients arrive | Recurring monthly cost that starts at zero patients | Included | | Prescribing clinicians | Hourly or per-visit pay, benefits for W-2 staff, idle time between visits | Scales with staffing, not with visits | Per-consult fee; you pay for completed visits | | Collaborating physicians for NPs and PAs | Required in states without full practice authority; usually a monthly fee per NP or PA | Scales with headcount | Included | | State licensure | Application and renewal fees per clinician per state, plus the admin time to track them | Grows with every state and clinician | Covered by the network's existing licenses | | Credentialing and exclusion screening | Primary-source verification, malpractice checks, monthly OIG and SAM screening | Vendor fees or an internal FTE | Included; ask for the credentialing policy in writing | | EHR and telehealth software | Licensed EHR with telehealth, portal, intake, video, audit trail, or a custom build | Monthly license in the low-to-mid four figures, or a six-figure custom build | Included as the platform | | E-prescribing and EPCS | Surescripts-connected e-Rx module, EPCS identity proofing and two-factor tokens per prescriber | Module fees plus prescriber onboarding time | Included | | Pharmacy contracts and integration | Legal review, minimums, API or fax integration, cold-chain SOPs | Low to mid five figures in setup, then per-fill cost | Included; medication cost passes through | | Labs | Lab accounts, kit inventory, result ingestion, provider review workflow | Setup plus per-test cost | Included as a workflow; labs quoted per program | | Compliance program | HIPAA policies and risk analysis, state modality mapping, ad review, breach plan, counsel on retainer | Recurring; counsel billed hourly | Platform maintains its program; you keep a thinner one for your own entity | | LegitScript certification | Application and annual fees tiered by company size, plus the weeks spent assembling evidence | Low thousands per year plus calendar time | Managed application; the certification still attaches to your brand | | Patient support | HIPAA-trained agents, tooling, clinical escalation path | Recurring staffing | Varies by platform; confirm who handles clinical escalations | Two patterns stand out. First, most in-house lines are fixed. The physician owner, the collaborating physicians, the EHR license and the compliance counsel are paid at zero patients and at a thousand patients. Second, the biggest lines, software and clinical staffing, are exactly what a platform amortizes across many brands, which is why the per-consult model works at startup volume. ## How do the two paths compare on total cost? Use the ranges from our [startup cost breakdown](/blog/cost-to-start-telehealth-business) as the anchor: | | Build in-house | Launch on an MSO platform | |---|---|---| | Realistic cost to first patient | $250,000 to $900,000 or more | $10,000 to $75,000 | | What that buys | Your own entities, software, clinical team, pharmacy and lab contracts, and compliance program | A branded clinic on shared infrastructure, your own marketing and storefront assets, your own counsel review | | Largest fixed costs | Software, physician owner, clinicians, counsel | Monthly platform fee | | Largest variable costs | Marketing, medication cost of goods | Marketing, per-consult fees, medication cost of goods | | Costs that are identical | Branding, website, launch marketing, your own insurance | Same | The honest comparison is not "a platform is one-tenth the cost." It is "a platform converts a stack of fixed costs into a monthly fee and a per-consult fee, so cost tracks revenue instead of running ahead of it." That is why a brand doing 200 consults a month and a brand doing 2,000 can both be on the same platform with sensible economics, and why [flat fees beat revenue share at scale](/blog/white-label-telehealth-platform-cost). Three terms decide whether a platform fee is actually cheap: medication markup (a percentage on every fill is a revenue share in disguise), revenue share (a fixed percentage forever, while a flat fee shrinks as you grow), and merchant of record (whoever holds the merchant account commercially owns the customer). MyOrbitHealth publishes its fee model rather than a price list: a flat platform fee scoped at onboarding to verticals, states and volume, 0% medication markup, no revenue share, the brand as merchant of record with export at any time, no exit fee, and month-to-month after onboarding. Details are on the [pricing page](/pricing). ## How do the two paths compare on speed? Speed is where in-house loses hardest, because the long items are sequential and outside your control. You cannot credential a clinician until the license is issued; you cannot run ads until LegitScript approves; you cannot ship testosterone until the EPCS token is provisioned and a pharmacy licensed in the patient's state is contracted. | Milestone | In-house | MSO platform | |---|---|---| | Entities formed and MSA signed | Weeks to a few months, depending on counsel and the number of states | Already in place | | Clinicians licensed in launch states | Months per clinician per state; compacts help for physicians in participating states but not every state | Existing 50-state network | | Credentialing complete | Weeks per clinician after licensure | Already complete and re-screened monthly | | EHR, intake and e-prescribing live | Months for a licensed system configured properly; longer for a custom build | Branded clinic configured in days | | Pharmacy contracts signed and integrated | Weeks to months per pharmacy | Already contracted | | LegitScript approved | Weeks to months, paced by evidence gathering and LegitScript's review | Managed application; typically days once filed, though LegitScript decides and approval is never guaranteed | | First paid patient | 6 to 12+ months | Days to weeks; paid ads follow LegitScript | Competitors describe similar timelines on the buy side. As of October 2026, per their sites, Wheel targets go-live under 90 days for enterprise engagements and Cuvo Health describes launches in under 30 days as typical. MyOrbitHealth brands go live in days, and 50+ digital clinics run on the platform. Our [telehealth launch timeline](/blog/telehealth-launch-timeline) walks the week-by-week sequence. The speed gap has a cost of its own: six months of building is six months of zero revenue and zero learning about which offer, price and channel convert. ## How do the two paths compare on risk? Cost and speed get the attention. Risk is what decides whether the business survives year two. Three regimes matter most. **Corporate practice of medicine.** If your MSO exerts control over clinical decisions, pays the PC owner above fair market value, or splits fees in a way a state board reads as the lay company practicing medicine, the structure fails. In-house, you own that risk directly and you re-analyze it every time you add a state or change the fee. On a platform, the platform operates the structure and the licensed providers practice through its affiliated professional entity, so your exposure is narrower. It is not zero: you still want counsel to review the agreement and confirm the structure fits your states. State activity in this area continued through 2025 and 2026, so this is a live topic, not settled law. **HIPAA.** Building in-house means running a full compliance program: risk analysis, policies, training, vendor BAAs, breach response. A platform does not remove your obligations, but one that signs a BAA in every contract, holds SOC 2 Type II and runs a HITRUST-aligned architecture carries the technical and operational controls, and you keep a smaller program for your own entity. Our [HIPAA guide for founders](/blog/hipaa-for-founders) explains what stays yours. **DEA and controlled substances.** The moment your roadmap includes testosterone, you inherit the Ryan Haight Act's framework, DEA registrations, EPCS with identity proofing, state PDMP checks, and whatever the DEA's permanent telemedicine rule says when it lands. As of October 2026 the DEA's fourth temporary extension of telemedicine flexibilities runs through December 31, 2026, with the permanent framework still pending; see our [telehealth prescribing rules guide](/blog/telehealth-prescribing-rules-2026). In-house, this is a sub-program to build and monitor. On a platform with EPCS-ready prescribing and DEA-registered partner pharmacies, it is a configuration you turn on per vertical and per state. Pharmacy list changes and advertising rules (LegitScript, Google and Meta policy, FTC substantiation) round out the picture; the first is tracked by a certified pharmacy network, the second stays a brand-level risk either way. ## When does building in-house win? It does, sometimes. Be honest about whether you are one of these. **Very high, predictable volume.** At some point, a per-consult fee multiplied by a large and stable monthly volume exceeds the cost of owning a clinical team. Where that point sits depends on your visit mix and the platform's pricing, so model it with real numbers. Our [provider network vs hiring comparison](/blog/telehealth-staffing-provider-network-vs-hiring) walks the staffing side of that math. **Payer billing.** If your model depends on insurance reimbursement, you need payer contracting, plan credentialing, revenue cycle management and billing-compliant documentation. Most cash-pay MSO platforms are not built for that, and the enterprise vendors that are, such as OpenLoop, target health plans and health systems rather than DTC founders. **A unique clinical model.** Longitudinal chronic-care programs with custom protocols, device integrations, in-person components or research arms may need clinical staff you employ and direct through a properly structured PC. If the clinical model is the product, owning it can be the moat. The same applies if you intend to sell infrastructure to other brands. If none of these describes you, the per-consult fee is cheaper than an idle clinical operation and the speed difference compounds in your favor. ## Decision matrix: which path fits your brand? Score your situation on each row. The column with the most checks is usually the right path, and a mixed result points at the hybrid option below. | Factor | Build in-house | MSO platform | Hybrid (API) | |---|---|---|---| | Capital available for infrastructure before revenue | $500,000+ committed | Five figures | Engineering time plus platform fees | | Runway before you need revenue | 12+ months | Weeks to a quarter | A development sprint | | Monthly volume | High and predictable | Any, including zero at launch | Any | | Revenue model | Payer billing or mixed | Cash-pay subscriptions and visits | Cash-pay inside an existing product | | Clinical model | Unique, protocol-heavy, device or research components | Standard DTC verticals: GLP-1, TRT, HRT, peptides, sexual health, hair, skin, primary care | Standard verticals embedded in your flow | | Existing stack | None or fully custom | None; you want the storefront, portal and app included | EHR, storefront or app already live and worth keeping | | Controlled substances on the roadmap | You will build EPCS and DEA workflows | Turned on per vertical with the platform's EPCS rail | Same, through the API | | Exit and portability | You own everything | Confirm you own patients, data and the merchant account, with no exit fee | Confirm the same, plus data export through the API | ## Is there a hybrid path between building and buying? Yes, for two groups: existing medical practices that already run an EHR, and software companies with an app or storefront that already has users. The hybrid pattern keeps your stack and adds the regulated layer by API. Your product handles the front door, the account and the checkout; the platform supplies the licensed clinicians, the MSO and friendly-PC structure, intake, EPCS-ready e-prescribing, pharmacy and labs, and returns status through signed webhooks. MyOrbitHealth's developer product is built for this. The product REST API at `https://api.myorbithealth.com/v1` uses bearer-token auth with test and live environment-scoped keys, path versioning, documented endpoints for patients, appointments, prescriptions and webhook registration, and webhook events such as `appointment.completed` and `prescription.dispensed`. Rate limits are 600 requests per minute per key with burst to 1,200, and a sandbox is provisioned within a day after a short partner review. There is a React SDK for teams that want drop-in components. The [telehealth API page](/telehealth-api) and the [API docs](/api-docs) cover the contract. For practices that want to keep their EHR intact while adding virtual care under their own brand, the [clinics solution page](/solutions/clinics) describes the setup. ## Which MSO platform should you buy from? If you have decided to buy, compare vendors on published terms and ownership clauses rather than demos. As of October 2026, per their sites: Cuvo Health publishes Launch at $9,800 setup plus $997 a month and Grow at $15,000 setup plus $2,500 a month, with $25 per completed consult, 0% medication markup and no revenue share, with its API on Grow and above and its SOC 2 Type II report on Enterprise only; Telegra publishes Plus at $3,000 a month plus $5,000 onboarding and Pro at $6,000 a month plus $10,000 onboarding, with consult fees billed separately; Fuse Health publishes $699 and $3,000 monthly tiers plus a 2% merchant fee on sales; Wheel and OpenLoop price deal by deal. MyOrbitHealth publishes its fee model rather than a price list. The differences that matter at scale are who is merchant of record, whether there is a medication markup or revenue share, whether SOC 2 Type II and the API are on your plan, and whether you can leave with your data. Our compare pages cover each vendor in detail: [Cuvo](/compare/myorbit-vs-cuvo), [Telegra](/compare/myorbit-vs-telegra), [Fuse Health](/compare/myorbit-vs-fuse-health), [Wheel](/compare/myorbit-vs-wheel) and [OpenLoop](/compare/myorbit-vs-openloop). A structured scoring method is in our guide on [how to choose a white-label telehealth partner](/blog/how-to-choose-a-white-label-telehealth-partner), and if you are scaling rather than launching, read the companion piece on the [enterprise stack for a consumer health brand](/blog/scaling-consumer-health-brand-stack). ## Frequently asked questions ### Is it cheaper to build telehealth operations in-house or to use an MSO platform? At launch and early-scale volume, an MSO platform is almost always cheaper. Building in-house typically costs $250,000 to $900,000 or more before the first patient, most of it fixed, while a platform converts that into a setup fee, a monthly fee and per-consult costs that track revenue. In-house can become cheaper at very high, predictable volume, which is a problem worth having. ### How long does it take to build telehealth operations in-house? Typically 6 to 12 months or more. The pacing items are sequential and external: state licenses, credentialing, pharmacy contracts and LegitScript review. A platform brand can go live in days to weeks because those items are already done, with paid advertising following LegitScript approval. ### Do I still need a lawyer if I launch on an MSO platform? Yes. The platform operates the MSO and professional-entity structure, but your own counsel should review the agreement, confirm the structure fits your states and advise on your advertising, billing and privacy obligations as a brand. The scope of that engagement is far smaller than building the structure yourself. This is general information, not legal advice. ### When does building in-house make sense? When volume is very high and predictable, when the business bills insurance and needs payer contracting and revenue cycle management, when the clinical model is unique enough that no platform can run it, or when you are building infrastructure to sell to other brands. Outside those cases, a per-consult fee is cheaper than owning idle clinical capacity. ### Can I keep my existing EHR or app and still use a platform? Yes. The hybrid path adds the regulated layer by API beside the stack you already run. MyOrbitHealth's REST API, signed webhooks and React SDK let a practice keep its EHR or a software company keep its app while licensed providers, prescribing, pharmacy and labs run through the platform. ### Does a platform remove my HIPAA and DEA obligations? No, it narrows them. A platform that signs a BAA, holds SOC 2 Type II and runs EPCS-ready prescribing with DEA-registered partner pharmacies carries the technical and clinical controls, while your brand keeps obligations around its own marketing data, vendors and claims. Confirm the division of responsibilities in writing before launch. ## Sources - [21 CFR Part 1311, Requirements for Electronic Orders and Prescriptions (EPCS), eCFR](https://www.ecfr.gov/current/title-21/chapter-II/part-1311) - [DEA Diversion Control Division, Telemedicine](https://www.deadiversion.usdoj.gov/telemedicine/index.html) - [HHS Office for Civil Rights, HIPAA for Professionals](https://www.hhs.gov/hipaa/for-professionals/index.html) - [AICPA, SOC 2 Reports](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2) - [LegitScript, Healthcare Merchant Certification](https://www.legitscript.com/) - [Google Ads Healthcare and Medicines Policy](https://support.google.com/adspolicy/answer/176031) - [Interstate Medical Licensure Compact](https://www.imlcc.org/) - [FTC Health Products Compliance Guidance](https://www.ftc.gov/business-guidance/resources/health-products-compliance-guidance) ## Model your own build-vs-buy numbers MyOrbitHealth runs the regulated layer so you do not have to build it: 2,400+ board-certified providers across 38+ specialties in all 50 states, OrbitOS, Orbit Intake, OrbitRx with EPCS-ready prescribing into a LegitScript-certified pharmacy network, Orbit Labs, a branded storefront and app, and a REST API for teams with a stack of their own. Flat platform fee, 0% medication markup, no revenue share, no exit fee. You control the brand, we power the medicine. Run your directional numbers in the [startup cost calculator](/tools/startup-cost-calculator), then [book a demo](https://myorbithealth.com/book) to get a scoped quote and see the [platform](/platform) in your vertical. ```html ```