Skip to content
Skip to content

Guide

How to Choose a White-Label Telehealth Platform: 25 Questions

Choosing a white-label telehealth platform comes down to 25 questions across six areas: which model you are actually buying (software, services, network, or an operated stack), the all-in per-patient economics, clinical coverage, pharmacy supply, compliance posture, and the contract terms that decide who owns your patients and your margin. Vendors differ far more in what they leave out than in what they demo. This checklist is the set we would use on the buying side, and it applies to EmbedCare as hard as to anyone else; take it into every sales call and ask for the answers in writing.

10 min readUpdated September 7, 2026

First: know which of the four models you are buying

Every vendor in this category sells one of four things: software you operate (storefront builders and platform tools), services you plug in (clinician staffing, admin, support), a clinical network behind an API (visits and Rx routing for your build), or an operated stack (the whole clinic run behind your brand). Demos blur these lines; contracts do not. The single most common buying mistake is comparing a software price against an operated-stack price as if they bought the same thing.

The model question decides everything downstream: with software you are the operator and the integrator; with services and APIs you are the assembler of the remaining layers; with an operated stack you are trading some control for one contract and one throat to choke. None of these is wrong. Buying one while believing you bought another is.

  • 1. Which of the four models is this, in the vendor's own words: software, services, clinical API, or operated stack?
  • 2. Exactly which layers are included, and which of the nine stack layers (legal, clinical, storefront, pharmacy, payments, labs, compliance, marketing, support) remain mine?
  • 3. Who operates day two: when a patient message, a refill exception, or a support ticket arrives, whose staff handles it?
  • 4. What does launch actually require from my team, in hours and in skills?
  • 5. Which parts of the demo were the vendor's product, and which were integrations I will contract for separately?

The one-question shortcut, if you only get one: 'Walk me through everyone who touches a dollar between the patient's card and my payout, and who keeps the medication margin.' The answer maps the whole model, and the hesitation maps the rest.

Economics: the five questions that find the real price

List prices in this category are the start of the math, not the math. The number that matters is the all-in cost per active patient per month at your realistic volume, including the costs that are quoted per deal rather than published: visit fees, medication cost per fill, payment processing, and any per-service line items. Vendors who want your business will build that number with you; vendors who keep it vague are telling you where the margin hides.

  • 6. What is my all-in cost per active patient per month at 100, 500, and 2,000 patients, with every fee included?
  • 7. How is medication priced: included in flat rates, passed through at cost, or marked up per fill, and by how much?
  • 8. Which costs are published and fixed in the agreement, and which are 'custom' (meaning re-negotiable, usually upward)?
  • 9. What are the minimums, setup fees, and the price of leaving: termination notice, data export, wind-down support?
  • 10. Do the rates change with volume in writing, or by renegotiation when I have leverage or they do?

Clinical coverage: four questions, all verifiable

Clinical claims are the easiest to verify and the least verified. 'Nationwide coverage' can mean a deep 50-state network or two NPs and an aspiration; 'our providers' can mean an employed group, a contracted network, or a reseller relationship with a network you could contract directly. Ask precisely, and expect precise answers.

  • 11. Which states are actually covered today for MY product lines, and how is coverage staffed where NP practice rules require physician collaboration?
  • 12. Who employs or contracts the clinicians, and is clinical independence structurally protected (no quotas, no per-approval pay)?
  • 13. What are current visit turnaround times, by state and by hour, and what happens at 3am and on holidays?
  • 14. How are protocols governed: who writes them, which clinician reviews them, and how do state-by-state differences get enforced in the product?

Pharmacy and supply: four questions that decide your P&L

In recurring-Rx categories, supply is the business. The difference between a platform that owns pharmacy supply, one that routes to partner pharmacies at negotiated rates, and one that leaves fulfillment entirely to you is the difference between three different companies with the same landing page. For compounded products, the legal-basis question is not optional diligence; it is the survival question of the category.

  • 15. Who dispenses: owned pharmacy, partner network, or my problem? And who holds the non-resident licenses for every state I sell into?
  • 16. For any compounded product: on what specific, current legal basis is it compounded, in writing, and who re-verifies that quarterly?
  • 17. What does a fill cost me, all-in with shipping and cold chain where needed, and who keeps the spread between that and my retail?
  • 18. What happens when a product's regulatory status moves: whose job is reformulation, patient communication, and the revenue bridge?

Compliance and certification: four questions before you advertise

If paid acquisition is anywhere in your plan, the certification chain (LegitScript, then ad-platform approvals) runs on its own multi-month clock, and your platform either accelerates it or becomes the reason you fail it. The corporate-practice structure underneath is the other non-negotiable: it is unglamorous until the day it is the only thing that matters.

  • 19. What legal structure does the platform operate or require (MSO/PC or equivalent), and has it survived scrutiny in strict corporate-practice states?
  • 20. Will my storefront, as the platform builds it, meet LegitScript's published standards on day one, and who does the certification work?
  • 21. How is patient data handled: BAAs in place, tracking pixels configured for health-data rules, and consent captured to TCPA standards?
  • 22. Has the vendor, or programs on it, had regulatory actions, certifications revoked, or public incidents I should hear about from them first?

Contract and data: the three questions about leaving

You learn the most about a platform by negotiating your exit before your launch. Patient relationships, records custody, and your storefront's portability decide whether you own a business or rent a revenue stream, and every vendor's answer is knowable in advance because it is written in their agreement. Read it for the leaving terms first.

Ask every finalist for two reference customers at your scale, and ask the references the same 25 questions; where the vendor's answers and the references' answers diverge is exactly where your problems will live.

  • 23. Who owns the patient relationship and the records, and what exactly do I receive (format, timeline, cost) if we part ways?
  • 24. Is my brand, storefront content, and audience data mine in the agreement's words, not the sales deck's?
  • 25. What are the exclusivity, non-compete, and territory terms, and would they survive my lawyer reading them out loud?

How EmbedCare answers these

We built EmbedCare to be the easy answer to this list: an operated stack (model four) with owned pharmacy supply, flat product rates fixed in a signed partner agreement (medication included on GLP-1 programs), a 50-state clinical network with independence protected structurally, storefronts built to certification standards, and your brand, audience, and patient relationships yours in writing. The self-serve Launch tier starts at $495/mo, and a demo walks the whole checklist with your numbers in it.

Frequently asked

How do I choose a white-label telehealth platform?
Work six areas in order: identify which of the four models you are buying (software, services, clinical API, or operated stack), build the all-in per-patient economics including quoted-per-deal costs, verify clinical coverage state by state, pin down pharmacy supply and medication margin, confirm certification readiness, and read the contract's exit terms first. The 25 questions in this guide cover each area and belong in writing.
What is the most important question to ask a telehealth platform?
Who keeps the medication margin. In recurring-Rx categories the fill economics decide the P&L, and the answer instantly reveals the model: owned supply with flat rates, partner routing with markups, or fulfillment left to you. The vendors' answers differ far more than their landing pages do.
What are red flags when choosing a telehealth platform?
Vague answers on all-in per-patient cost, 'nationwide' clinical claims that can't be broken down by state, compounded products without a written current legal basis, certification treated as your problem after launch, and agreements where patient records or your storefront don't clearly leave with you. Any one is a reason to slow down; two is a pattern.
Should I pick a telehealth software platform or a full-service operator?
Pick by what your team should be doing at 9am: operating a clinic (then buy software or APIs and hire for the rest) or growing an audience and brand (then buy the operated stack and keep your team on demand). The wrong answer is buying software economics while expecting operator outcomes, which is the most common mismatch in the category.
How long should telehealth platform diligence take?
Two to four weeks of real work: sales calls with the 25 questions, agreement review with the exit terms first, two reference calls per finalist at your scale, and a written per-patient economics model per vendor. Compressing it below that mostly defers the same hours into the switching project a year later.

Want pricing for your program, and the Rx menu that goes with this?

The partner overview in one email; a human follows up with pricing scoped to your program.

The fastest way to understand it is to see it running.