Telehealth

The MSO and Friendly-PC Model, Explained for Non-Physician Telehealth Founders

You do not need to be a physician to build a telehealth company. The MSO and friendly-PC model is the well-established structure that lets non-clinician founders build, fund, and scale virtual-care brands while licensed clinicians own the medicine. This is the plain-language explainer: what each entity does, how the pieces fit, why the structure exists, and how to set it up so it supports growth instead of slowing it.

You do not need to be a physician to build a telehealth company

One of the first questions every non-clinician founder asks, usually quietly, is whether they are even allowed to build a healthcare company. The answer is yes, and the structure that makes it work has been operating at scale across American healthcare for decades.

It is called the MSO and friendly-PC model, and nearly every DTC telehealth brand you can name runs on some version of it. The founder's company handles the business. A clinician-owned professional entity handles the medicine. A services agreement connects them. Each side does what it is best at, and the arrangement respects the rules most states have about who can own and direct medical practice.

Founders hear about this structure in fragments, a lawyer mentions CPOM, a forum thread mentions friendly PCs, a diligence checklist mentions MSAs, and the fragments sound intimidating. Assembled properly, the picture is straightforward, and getting it right early is one of the highest-leverage moves a founder can make: it is the foundation investors, partners, and platforms all look for.

This is the plain-language explainer. It is educational, not legal advice; the structure is well-trodden, and healthcare counsel will tailor it to your states and program.

For the vocabulary this builds on, see The DTC Telehealth Glossary: 75 Terms Every Founder and Operator Should Know in 2026.


The three pieces, in plain language

The PC: where medicine lives

The professional corporation (or professional association, depending on the state) is the clinical entity. It is owned by a licensed clinician, employs or contracts the providers, holds the clinical relationships with patients, and makes every medical decision: who qualifies, what gets prescribed, when to refuse, how care proceeds.

The "friendly" in friendly-PC simply means the physician owner works collaboratively with the business entity, aligned on building something good together, while retaining full and genuine authority over the medicine.

The MSO: where the business lives

The management services organization is the founder's company. It owns the brand, builds the product, runs marketing, provides the technology, manages non-clinical operations, handles billing mechanics, and employs the non-clinical team. This is the entity founders own and investors invest in.

The MSA: the connection

The management services agreement is the contract between them. The MSO provides defined business services to the PC; the PC pays for those services at fair market value; and the agreement draws the line that matters: business decisions on one side, clinical decisions on the other, with clinical authority explicitly untouchable.

DecisionWho makes it
Brand, marketing, product, technologyMSO
Pricing structure and business modelMSO
Which patients qualify for treatmentPC
What gets prescribed and when to refusePC
Clinical protocols and standards of carePC, often with advisory input
Provider hiring standards and supervisionPC
Non-clinical staffing and operationsMSO

Why the structure exists

Most states maintain some form of the corporate practice of medicine doctrine: the principle that medical decisions must be made by licensed clinicians accountable to patients, not directed by corporate owners accountable to shareholders. It is a patient-protection principle, and it is a good one. Nobody wants prescribing decisions optimized by a growth dashboard.

The MSO and friendly-PC model is how the healthcare industry honors that principle while still letting entrepreneurs build. Hospitals, dental groups, dermatology chains, and telehealth brands all use versions of it. The structure is not a loophole; it is the designed answer, and regulators, investors, and courts have decades of familiarity with it.

The practical takeaway for founders is a mindset, not just a filing: the structure works when the clinical independence is real. Founders who genuinely want strong clinical leadership, real refusal authority, protocols owned by clinicians, a medical director with standing, build companies that are both compliant and better at care. The structure and the quality bar point the same direction.

For the clinical-leadership layer that makes this real, see Building a Clinical Advisory Board That Strengthens Your Telehealth Brand and Clinical Protocols for DTC Telehealth: What to Standardize Before Your First Patient.


How the pieces work day to day

Money

Patients pay for care; clinical revenue belongs to the PC. The PC pays the MSO for the services it actually receives, technology, marketing, administration, at fair market value documented in the MSA. The MSO earns real fees for real services. Clean books on both sides, with the service fees defensible on their merits, are what make the structure durable through diligence and growth.

Providers

Providers are engaged by the PC. Their clinical supervision, quality review, and medical accountability run through the PC's clinical leadership, typically a medical director with genuine authority. The MSO can build great tools for providers and set service-level expectations for the business relationship; it does not direct diagnosis, prescribing, or refusals. For the staffing model choices, see Provider Network vs. Your Own Clinicians: How DTC Telehealth Brands Should Choose.

Multi-state growth

State rules vary: which entity forms are allowed, who may own them, and how strictly the doctrine applies. Growing brands typically operate one or more PCs covering their states, with providers licensed appropriately in each. The expansion playbook is knowable and sequenced: see State Expansion for Telehealth: The Ops Checklist Before You Launch a New State and Licensing Momentum: Using Compacts to Sequence Your 50-State Rollout.

Data

Clinical records belong to the clinical side and live under healthcare privacy safeguards. Business data, marketing analytics, product usage, financial operations, lives with the MSO. A well-built arrangement documents this boundary, and a well-built platform enforces it structurally. See Data Ownership in DTC Telehealth: What to Ask Before You Choose a Platform.


How platform architecture supports the structure

This is the part founders consistently underestimate: your software either makes the two-entity model easy to live, or it quietly fights it every day.

What structure-aware platform architecture looks like:

  • Role and entity separation built in. Clinical workflows, charts, and prescribing live in clinician-controlled spaces; business dashboards see operational and de-identified views, not levers over care
  • Refusal authority as a first-class workflow. Providers decline with documentation and referral paths, and nobody's conversion dashboard pressures the decision
  • Audit trails on everything. Who accessed what, who decided what, when, the record that lets the PC demonstrate genuine clinical control
  • Clean financial rails. Clinical revenue and service fees separable and reportable per entity, so the books match the agreement
  • Licensure-aware routing. Patients reach providers licensed in their state automatically, keeping the clinical entity's obligations honored at scale

A platform built this way turns the structure from a legal document into an operating reality, which is exactly what diligence wants to see and what patients quietly benefit from. For the evaluation framework, see How to Pick a White-Label Telehealth Platform in 2026: The Operator's Vendor Evaluation Framework.


Setting it up: the founder's sequence

StepWhat happens
1. Engage healthcare counselThe structure is standard; the tailoring to your states and program is where counsel earns it
2. Find the physician partnerA clinician who genuinely wants to lead the medicine, not lend a signature. Recruit for engagement
3. Form the entitiesMSO and PC(s) appropriate to launch states
4. Execute the MSADefined services, fair-market-value fees, explicit clinical-authority protections
5. Stand up clinical governanceMedical director authority, protocols, quality review, refusal pathways
6. Configure the platform to matchRoles, boundaries, audit trails, and financial rails aligned with the documents
7. Operate like the documents are trueThe structure is a living practice, not a filing

The timeline fits comfortably inside a modern launch plan; entity formation and agreements typically run in parallel with platform configuration and program build. See The 30-Day GLP-1 Telehealth Launch Plan: From Incorporation to First Patient Served.

The single most important choice in the sequence is the physician partner. The strongest brands treat that person as a true co-builder: compensated fairly, engaged in the roadmap, and visibly leading the clinical program. That relationship, more than any document, is what makes the model work.


FAQs

Can a non-physician own a telehealth company? Yes. The founder owns the MSO, the business entity that holds the brand, technology, and operations. Licensed clinicians own the professional entity that delivers care. The two are connected by a management services agreement. This is the standard structure across DTC telehealth.

What is a friendly PC? A professional corporation owned by a licensed clinician who works collaboratively with the business entity while retaining full authority over medical decisions. "Friendly" describes the alignment, not any dilution of clinical control.

What is an MSO in healthcare? A management services organization: the business entity that provides technology, marketing, administration, and operations to a medical practice for a fee. In DTC telehealth, the MSO is the company the founder owns and investors fund.

What does the MSA cover? The services the MSO provides, the fair-market-value fees the PC pays, and the explicit boundary: business decisions with the MSO, clinical decisions with the PC, clinical authority untouchable.

Why do states require this structure? Most states hold that medical decisions must be made by licensed clinicians accountable to patients rather than directed by corporate owners. The MSO and friendly-PC model is the long-established way to honor that principle while letting entrepreneurs build.

Does the structure slow down a launch? No. Entity formation and agreements run in parallel with platform setup and program build, and fit inside a 30-day launch arc. Getting it right early is dramatically cheaper than restructuring later.

What makes the model strong in practice? A genuinely engaged physician partner, real clinical governance, fair-market service fees, clean books per entity, and a platform whose roles, audit trails, and data boundaries make the documents true in daily operation.


Implementation checklist

Structure

  • Healthcare counsel engaged for launch states
  • Physician partner recruited as a true clinical leader
  • MSO and PC entities formed
  • MSA executed: defined services, fair-market fees, clinical authority protected

Governance

  • Medical director authority documented and real
  • Clinical protocols owned by the clinical side
  • Refusal pathway live and respected
  • Quality review cadence established

Platform alignment

  • Roles and entity boundaries configured
  • Audit trails on clinical access and decisions
  • Financial rails separable per entity
  • Licensure-aware provider routing enabled

Final takeaways

The MSO and friendly-PC model is the established answer to the question every non-clinician founder asks first.

What to remember:

  • Founders own the business through the MSO; clinicians own the medicine through the PC; the MSA connects them with clinical authority explicitly protected
  • The structure exists to protect patients, and it works best for founders who genuinely want strong clinical leadership
  • Money, providers, growth, and data each have a clean lane through the arrangement
  • Platform architecture either operationalizes the structure or quietly fights it; choose software that makes the documents true
  • The physician partner is the most important hire-adjacent decision in the company's life
  • Set up properly at launch, the structure is a growth asset: it is what investors, partners, and enterprise customers expect to find

Build the business you are great at, empower clinicians to lead the medicine they are great at, and put real architecture under both. That is the whole model, and it has carried every serious brand in the category.

More from Telehealth