Launch
Build vs. Buy: Should You Use a Telehealth-in-a-Box Platform or Own Your Stack?
Use an all-in-one telehealth platform or build your own Shopify + pharmacy stack? This decision framework shows exactly what you give up — and what it costs.
Quick answer
All-in-one telehealth platforms get you live faster, but you rent your patient data, your pharmacy contracts, and your prescriber relationships. Building your own Shopify front-end with a pharmacy fulfillment overlay takes 4–8 weeks longer to launch but leaves you owning the system of record — the asset that compounds over time.
Key takeaways
- All-in-one platforms are fast but extractive — you rent patient data, pharmacy access, and prescriber relationships rather than own them.
- Owning your stack requires a Shopify front-end, a prescriber/medical group relationship, a pharmacy services agreement, and a fulfillment layer connecting them.
- Provider approval is not optional — every order must flow through a licensed prescriber; that is the operating model, not a compliance checkbox.
- Category breadth beats category depth: operators running TRT, HRT, hair, skin, and peptides across multiple pharmacies are structurally more resilient.
- A purpose-built fulfillment overlay cuts 6–8 weeks off the build timeline (estimated) and eliminates engineering risk without giving up stack ownership.
The short answer: All-in-one telehealth platforms get you live faster, but you rent your patient data, your pharmacy contracts, and your prescriber relationships. Building your own Shopify front-end with a pharmacy fulfillment overlay takes 4–8 weeks longer to launch but leaves you owning the system of record — the asset that compounds over time.
Most operators ask the wrong question. They ask "which platform has the best features?" when they should ask "what am I agreeing to give up?"
This post lays out exactly what's on the table — so you can make the call with your eyes open.
What "telehealth-in-a-box" actually means
Platforms like Bask Health, OpenLoop, SteadyMD, Wheel, MD Integrations, and DrCare247 bundle everything into a single product: a prescriber network, a pharmacy relationship (often a single preferred partner), and a patient-facing storefront or checkout flow.
That's a real value proposition. You can go live in days. You don't need to credential a prescriber, negotiate a pharmacy contract, or build a checkout. For founders who want to validate demand before investing in infrastructure, that speed is worth something.
The honest version of the pitch is: you're buying a fast on-ramp with a toll on exit.
What you give up when you buy
This is the part of the sales conversation that gets soft-pedalled.
Your patient data
On most all-in-one platforms, the patient record lives in the platform's database. You can see it. You usually can't export it cleanly, and you can't take it with you if you leave. HIPAA compliance is the platform's headline feature — and also the reason they can argue the data is "in their custody."
What this means in practice: if you ever want to switch pharmacy partners, launch a new protocol, or sell the business, your patient list is not a portable asset. It's locked behind a vendor relationship.
Your pharmacy contracts
Most platforms have one or two preferred pharmacy partners — often compounding pharmacies where they've negotiated a volume arrangement. That arrangement exists between the platform and the pharmacy, not between you and the pharmacy.
If your platform's pharmacy relationship breaks down — a formulary change, a compliance event, a price renegotiation — you're exposed. You have no direct relationship to fall back on.
This matters especially for operators across multiple categories: TRT/men's health, HRT/menopause, hair protocols, ED, tretinoin and skin, low-dose naltrexone, peptides, and oral weight-management. Compounding pharmacy availability varies by compound, by state, and by quarter. Operators who own their pharmacy relationships can route around disruption. Operators who rent them cannot.
Your prescriber relationships
Some platforms supply the prescribers. That's efficient until it isn't. You have no insight into prescriber capacity, prescriber quality, or what happens when the platform decides to reprice or restructure its medical group.
If your brand's identity depends on provider quality — and it should, because provider approval is the one thing that makes this whole model work — you want control over who signs your orders.
Your payment relationship and billing stack
On all-in-one platforms, payment processing often runs through the platform. That means platform visibility into your revenue, platform-set processing fees, and potential delays in capital access. When you own your Shopify store, you own the Stripe or payment processor relationship directly.
Your freedom to move
The compounding landscape shifted fast in 2025 and is still moving. Operators locked into platforms that concentrated on a single compound category learned this the hard way. Owning your stack means you can pivot protocols without waiting for a platform roadmap update or a formulary approval process you don't control.
What you actually need to own your stack
This is the part the "build your own" camp undersells. Let's be direct about what it requires.
A Shopify storefront
Shopify handles the patient-facing purchase flow, subscriptions, and payment processing. It does not hold protected health information (PHI) — that constraint is non-negotiable and it's the right call. Your PHI lives in your clinical system, not your storefront.
Shopify setup for a telehealth operator is a 1–2 week project for someone who's done it before. If you're building intake forms, expect another week for custom implementation or a Typeform/JotForm bridge.
A licensed prescriber or medical group
You need a prescriber on your order flow. There is no model where something ships without a licensed provider approving it — and that's not a legal technicality, it's the only model that's safe for patients and defensible for operators. See our guide on building provider approval into your fulfillment flow.
Options: a telehealth medical group under a management services agreement (MSA), a staff prescriber, or a hybrid. This takes 2–6 weeks to credential and contract depending on state.
A pharmacy relationship
You need at least one compounding pharmacy — ideally two for redundancy — with a signed pharmacy services agreement. Most operators in men's health, women's health, and skin start with one pharmacy and add a second once they're at volume.
Cold outreach to pharmacies is slow. The fastest path is an introduction through a clinic or a fulfillment infrastructure partner who already has relationships established.
A fulfillment layer that connects the three
This is the piece that most operators underestimate. Shopify doesn't natively talk to compounding pharmacies. You need something that:
- Receives the order from Shopify
- Holds it pending prescriber approval
- Routes it to the right pharmacy based on compound, state, and availability
- Pushes status updates back to the patient
- Keeps the patient record in your system, not a third party's
You can build this from scratch. A senior engineer, 3–4 months, $80–120K (estimated). Or you can use an overlay — a purpose-built layer that sits between Shopify and your pharmacy and handles the routing, the HL7/API translation, and the compliance workflow. That's exactly what neolife is built to do.
The real comparison: what each path costs you
| All-in-one platform | Shopify + overlay | |
|---|---|---|
| Time to first patient | Days to 2 weeks | 6–10 weeks (estimated) |
| Who owns patient data | Platform | You |
| Pharmacy relationship | Platform's | Yours |
| Prescriber control | Platform's network | Your MSA or staff |
| Formulary flexibility | Platform's roadmap | Your pharmacy agreements |
| Payment relationship | Platform | Your Stripe/processor |
| Platform fee (ongoing) | % of revenue or per-order, often opaque | Infrastructure cost, no rev-share |
| Exit / acquisition value | Patient list is not portable | Patient list is yours |
No model is right for every operator. The all-in-one platforms are a legitimate choice for a founder who wants to validate demand with minimal capital — provided they go in knowing what they're trading.
If you're building a brand with real acquisition value, repeat patients, and a long-term clinical protocol, the question isn't whether to own your stack. It's when.
A framework for deciding
Three questions worth answering honestly before you commit:
1. What is the asset I'm building?
If the answer is "a patient list and a clinical relationship," you need to own the data. An asset you can't port or sell isn't a business asset.
2. How dependent am I on a single compound or category?
The more concentrated your protocol, the more you need flexibility in pharmacy routing. Operators running diverse protocols across TRT, HRT, skin, and hair have proven more resilient than single-category operators. See our piece on building a multi-category fulfillment strategy.
3. What's my 12-month runway and my go-to-market sequence?
If you have 90 days to validate and no engineering resources, an all-in-one platform is probably correct for month one. Build the exit plan into the contract. Know what you're getting into.
If you have a pharmacy relationship, a prescriber, and a Shopify store — or the ability to get them — the overlay path puts you in a fundamentally better position by month six.
What the incumbents get right (and where they fall short)
In the interest of being useful: the established platforms built real infrastructure. Wheel's prescriber network is large. OpenLoop's compliance framework is solid. Bask's onboarding is fast. None of them are bad products.
The issue isn't the product quality. It's the model. When your pharmacy, your prescriber network, your patient data, and your payment processing all run through one vendor, that vendor has significant leverage over your business. Price increases, formulary changes, and terms renegotiations all happen on their timeline.
The operators who built durable businesses in DTC Rx — the ones who've scaled past $5M ARR without a single-platform dependency — are uniformly the ones who own their fulfillment rail. Read how operators are escaping platform lock-in.
Key takeaways
- All-in-one platforms are fast but extractive. You rent patient data, pharmacy access, and prescriber relationships. The asset doesn't compound; the platform's leverage does.
- Owning your stack requires three things: a Shopify front-end, a prescriber/medical group relationship, and a pharmacy services agreement. The fourth piece — the fulfillment layer — is where most operators need help.
- Provider approval is not optional. Every order must flow through a licensed prescriber. That's not a compliance checkbox; it's the operating model.
- Category breadth beats category depth. Operators running TRT, HRT, hair, skin, and peptides across multiple pharmacies are structurally more resilient than single-category operators.
- The platform question is really a leverage question. Who has leverage over your pricing, your formulary, and your patient list in year two?
- An overlay changes the math. If the hard part is the Shopify-to-pharmacy connection, purpose-built infrastructure cuts 6–8 weeks off the build timeline (estimated) and eliminates the engineering risk.
FAQ
How long does it realistically take to launch a telehealth brand on Shopify with a fulfillment overlay?
Most operators go from signed pharmacy agreement to first patient order in 4–8 weeks using a purpose-built fulfillment overlay. The longest lead time is usually prescriber credentialing and state licensing, not the technology. An all-in-one platform can shave this to 1–2 weeks, but the timeline difference narrows significantly once you account for onboarding and compliance review on the platform side.
Can I use Shopify for telehealth if I can't store PHI there?
Yes. Shopify handles the commerce layer — purchase flow, subscriptions, payment processing — and does not hold PHI. Protected health information stays in your clinical system (or your pharmacy management system). This is standard architecture for DTC Rx operators and is not a barrier to using Shopify as your patient-facing storefront.
What happens to my patient data if I switch fulfillment platforms later?
If you own your stack — Shopify front-end, your own pharmacy agreements, your own prescriber relationship — your patient and order data stays with you. If your patient records live in a third-party all-in-one platform, exportability depends entirely on the platform's terms and data policies. Review this clause before you sign anything.
Do I need a prescriber on staff, or can I use a medical group?
Either works. Most early-stage DTC Rx operators use a telehealth medical group under a management services agreement (MSA) rather than hiring a staff prescriber. The MSA model gives you licensed provider coverage without the overhead of employment. As you scale, some operators bring prescribers in-house for specific protocols. Your counsel and pharmacy will have views on the right structure for your state and category mix.
Is compounded medication FDA-approved?
No. Compounded medications are not FDA-approved. They are prepared by licensed compounding pharmacies under applicable federal and state pharmacy law, and they require a valid prescription from a licensed provider for each patient. Every order in a compliant telehealth model is reviewed and approved by a licensed provider before it ships — that review is not a formality, it's the foundation of the model.
If you're at the point where you have a Shopify store (or are ready to set one up), a pharmacy you want to work with, and a prescriber relationship — and you need the fulfillment layer that connects them — that's what neolife is built for. Orders out in under 60 seconds, provider approval on every one, and your clinic stays the system of record.
Talk to us about your stack.
Frequently asked questions
How long does it realistically take to launch a telehealth brand on Shopify with a fulfillment overlay?
Most operators go from signed pharmacy agreement to first patient order in 4–8 weeks using a purpose-built fulfillment overlay. The longest lead time is usually prescriber credentialing and state licensing, not the technology.
Can I use Shopify for telehealth if I can't store PHI there?
Yes. Shopify handles the commerce layer — purchase flow, subscriptions, payment processing — and does not hold PHI. Protected health information stays in your clinical or pharmacy management system. This is standard architecture for DTC Rx operators.
What happens to my patient data if I switch fulfillment platforms later?
If you own your stack, your patient and order data stays with you. If your patient records live in a third-party all-in-one platform, exportability depends entirely on that platform's terms and data policies — review this clause before signing.
Do I need a prescriber on staff, or can I use a medical group?
Either works. Most early-stage DTC Rx operators use a telehealth medical group under a management services agreement (MSA). The MSA model provides licensed provider coverage without employment overhead.
Is compounded medication FDA-approved?
No. Compounded medications are not FDA-approved. They are prepared by licensed compounding pharmacies under applicable federal and state pharmacy law and require a valid prescription from a licensed provider for each patient.
This article is operator education, not medical, legal, or tax advice. Telehealth and pharmacy regulation vary by state and product and change frequently. Verify the specifics for your business with qualified counsel and your pharmacy partner.