Two years ago, launching a UK telehealth brand meant hiring a superintendent pharmacist, finding a GPhC-registered premises, negotiating with prescribers and waiting nine to eighteen months before you saw a single patient. By 2026, most new UK telehealth brands skip almost all of that. They sign a white-label agreement with a platform vendor, plug in their brand assets, and ship a working clinic in three to six weeks. The path is fundamentally different — and so is the trade-off matrix.

This piece is for founders looking at white-label platforms right now. We'll cover what white-label actually means at the layer level, the three pricing models you'll be quoted, how regulatory risk gets allocated (the question most founders skip), and a twelve-question checklist for evaluating any platform on its merits.

Disclosure: PExpo, the platform behind this site, is one of the UK white-label vendors in this market. The framework below is the one we apply to ourselves — and we recommend that founders evaluating us hold us to the same questions.

Why white-label became the dominant launch path in UK telehealth 2024–2026

Three things shifted between 2022 and 2026.

The first was regulatory clarity. The GPhC, MHRA, CQC and ICO all published updated guidance for online and remote healthcare during this period. That made it possible — for the first time — for a platform vendor to package compliance posture as a product. Before, every brand had to interpret the rules themselves. Now there is enough precedent that vendors can hand a brand a starting point that is defensibly correct.

The second was supply. Enough specialist categories — weight management, HRT, ADHD, mental health — hit critical patient demand that the unit economics of a focused brand made sense. Founders no longer had to argue with investors about whether the category existed.

The third was operational. A handful of UK platform vendors built genuine multi-tenant infrastructure capable of running multiple brands on the same compliance posture, prescriber network and dispensing operation. Before that, "white-label" usually meant "we will customise our existing portal with your colours" — which is not the same product.

Today, a founder evaluating white-label is looking at a different product class entirely.

What 'white-label' really means — clinical, dispensing, intake, portal layers

The word is overloaded. Different vendors use it to mean very different things. Here's a layer-by-layer breakdown of what is actually being offered.

Clinical layer. A network of GMC, NMC and GPhC-registered prescribers operating under a published clinical governance framework. Some vendors run their own prescriber network; others act as a marketplace introducing brands to independent prescriber groups. The difference matters at scale, when prescriber capacity becomes the binding constraint.

Dispensing layer. The pharmacy itself — picking, packing, dispatch. The GPhC requires a named superintendent pharmacist for any registered pharmacy, and that pharmacist holds personal regulatory accountability. Different platforms structure this differently: some operate their own pharmacy, some partner with licensed third parties, and some let the brand use its own pharmacy on the back end. Each option has different implications for control, margin and liability.

Intake layer. The clinical questionnaire engine. Most platforms now ship with a drag-and-drop builder with conditional logic, red-flag routing and consent capture. Depth varies — some are pure logic engines, others include built-in clinical pathways aligned to NICE guidance.

Portal layer. The branded patient-facing surface — sign-up, dashboards, repeat ordering, payments. Quality here is the most visible to your customers and the easiest to evaluate in a demo.

Adjacent services. Marketing and lifecycle integrations, analytics, payments, support tooling. These are sometimes bundled, sometimes priced separately. (Our integrations page is one example of the scope a brand might expect.)

When a vendor says "white-label," ask which of these five layers they actually deliver, and what the contract looks like for each. The cheapest "white-label" platforms typically only deliver the portal — you still bring your own prescribers, pharmacy and intake. The most complete deliver all five — our brand model page is one example of an all-five offer — with the operational and regulatory implications that follow.

Three pricing models you'll see

White-label commercials in UK telehealth in 2026 cluster into three patterns.

  1. Flat fee. A monthly subscription, typically £2,000 to £20,000 per month depending on volume tier and feature scope. Predictable cash flow for both sides. Best for brands with predictable demand or a strong commercial team who want margin upside as they scale. Watch for: per-order fees layered on top, and "enterprise" usage limits not priced into the headline number.
  2. Margin share. The platform takes a percentage of medication revenue, typically 15-35%. Aligned incentives — the platform only makes money when the brand makes money. Best for brands with capital constraints or uncertain early-stage demand. Watch for: margin share calculated on gross vs net (after refunds, returns, chargebacks), and floor minimums that kick in regardless of volume.
  3. Hybrid. A small monthly platform fee plus a per-order or per-prescription dispensing fee. Often the most honest structure because it separates fixed platform costs from variable dispensing costs. Best for brands who want predictability without paying flat-fee rates at low volumes. Watch for: forecasting complexity, especially when product mix shifts (cheaper SKUs make dispensing fees feel disproportionate). See our pricing page for an example of a hybrid structure in practice.

In practice, the right answer depends on your volume curve, capital position, and how much margin upside you are willing to share for de-risked launch.

Key takeaway

Pricing model is not the actual question. The actual question is what regulatory and operational risk gets allocated to each side — and the cleanest pricing structure in the world cannot paper over a bad risk-allocation clause. Read the contract layer-by-layer.

Risk allocation: who carries the GPhC, MHRA and CQC obligations on each layer

This is the question most founders skip — and it is where the actual money is in the contract.

Every layer has regulatory obligations attached. The contract decides who carries which.

GPhC. The platform's pharmacy holds the GPhC registration. The superintendent pharmacist named on that registration carries personal accountability. The brand typically has no direct GPhC obligation — until the brand operates its own pharmacy, at which point everything changes. Make sure the contract is explicit about what happens when GPhC raises a finding: who responds, who pays for remediation, who can be held responsible.

MHRA. MHRA distance-selling regulations apply to every UK-facing online medicine sale, and the responsibility splits depending on who is doing the selling. Where the platform's pharmacy is the seller of record, MHRA obligations sit with the platform. Where the brand is marketing prescription-only medicines (which is itself restricted under MHRA rules), the brand carries advertising-compliance responsibility. The boundary between the two is where most brand-level breaches occur.

CQC. This depends on the brand's service architecture. If the brand provides clinical services in its own name — assessments, follow-ups, treatment decisions made by its named clinicians — the brand needs its own CQC registration. If the brand purely partners with an externally-CQC'd clinical group (often the platform's clinical partner), the brand may sit outside CQC scope. Read the contract carefully here. Misunderstanding this point is one of the most expensive mistakes in UK telehealth setup. Prescriber discretion applies on any individual clinical decision.

UK GDPR. Patient data flows between brand and platform. A DPA between brand (Controller) and platform (Processor) is a legal requirement under UK GDPR. The DPA should specify subprocessors, retention periods, transfer mechanisms and breach notification timelines. A vendor who cannot produce a DPA on request is not ready for serious commercial conversations.

The contract decides who carries the regulator letter when it arrives. Founders treat that letter as hypothetical right up until it lands on the desk.

We have seen brands sign generic "white-label" agreements that say nothing useful about regulator response, ASA complaint handling or remediation cost allocation. When the test happens — and it will, eventually — both sides discover what they actually agreed to.

Vendor selection checklist — twelve questions to ask before signing

Walk through every one of these in writing.

  1. Which of the five layers (clinical, dispensing, intake, portal, adjacent services) does the platform actually deliver, and which require the brand to bring its own?
  2. Who is the named superintendent pharmacist for the dispensing pharmacy, and how do we contact them?
  3. What is the platform's GPhC inspection history, and what was the most recent rating?
  4. Can we see the standard DPA template now, before signing?
  5. What is the realistic launch timeline given our category and brand readiness — and what is the typical 3–6 week claim contingent on?
  6. How are prescriber capacity limits handled if we grow faster than expected?
  7. What is the offboarding process — patient data, in-flight orders, prescriber records — if we end the contract?
  8. Who responds to MHRA, GPhC or ICO enquiries, and who bears the cost of remediation?
  9. What is the SLA on same-day dispatch, what is the historical actual performance, and what is the remedy if it is missed?
  10. What does the integrations layer look like — REST API, webhooks, Customer.io, Segment, Stripe — and what data flows are supported out of the box?
  11. What is the commercial structure (flat fee, margin share, hybrid) and what is the floor minimum?
  12. What does "white-label" mean in the patient flow — does the platform's brand or any other vendor name ever appear to the patient?

A vendor who can answer all twelve in writing within a week is operating at the maturity required to host your brand. A vendor who cannot is asking you to take regulatory risk on faith.

When the trade-offs flip and you should think about building your own pharmacy instead

White-label is not permanent. The economics shift at scale.

At low volumes (under 5,000 monthly orders), the cost of running your own pharmacy — superintendent salary, premises, licensing, software, locum cover, insurance — typically exceeds the margin share you would pay to a white-label platform. White-label wins on pure economics.

Somewhere between 5,000 and 15,000 monthly orders, the curves cross. The fixed cost of running your own pharmacy becomes smaller per-order than the platform fees. Brands with strong unit economics in narrow categories cross this point faster than diversified brands.

Above 15,000 monthly orders, in-house typically wins on pure cost — but the strategic question becomes whether building pharmacy operations is the right use of founder attention. Most brands at that scale find that operating their own pharmacy adds management overhead they would rather spend on growth.

A reasonable rule of thumb: stay white-label until you have unit-economics certainty and operational bandwidth to absorb the regulatory weight of running your own pharmacy. That is usually past meaningful revenue scale for category-focused brands, and rarely sensible for diversified brands operating in five or more verticals.

What to do next

If you are at the start of this evaluation:

The UK telehealth landscape in 2026 makes white-label a credible default for new brands. The work is in choosing well, not in defending the choice.