neolife vs TEHR: Fulfillment Rail vs Turnkey Clinical Stack

It depends on whether you want a clinical stack handed to you or want to own one. TEHR is a turnkey telehealth platform: per its public materials it supplies the MSO-PC structure, licensed prescribers in all 50 states, partner pharmacies, and a large medication catalog. neolife is the fulfillment rail underneath, overlaying the pharmacy you already use while you stay the system of record.

Neither is universally right. The honest version of this comparison is not "platform bad, rail good"; it is a question about which parts of a regulated business you are willing to rent, and for how long.

What does TEHR actually do?

TEHR is an all-in-one launch platform for direct-to-consumer health brands. According to TEHR's public materials, it acts as the management services organization in an MSO-PC arrangement, pairs the operator with an independent physician-owned professional corporation, supplies licensed prescribers across all 50 states, connects FDA-registered partner pharmacies, and markets launching a brand in "as few as 14 days."

The breadth is the product. TEHR's site describes more than two thousand medication protocols across categories including peptides, TRT, HRT, ED, dermatology, longevity, and diagnostics, plus access to a network it puts at over 5,000 lab locations alongside at-home kits. It names its buyers plainly: creators and celebrities with an audience, clinic owners who want to go national, and entrepreneurs without a medical license who want a regulated health brand anyway. Fulfillment is offered in several shapes, from end-to-end handling to Rx-only or lab-only partnerships to cash-pay pickup at a local pharmacy.

That is a real amount of assembly work absorbed. Standing up a compliant multi-state clinical operation from scratch means entity formation in each state, primary-source license verification, malpractice coverage, a pharmacy contract, an EHR, payment processing that survives underwriting, and a catalog someone has actually reviewed clinically. A platform that hands all of it over in a fortnight is not selling nothing.

The structural point is what comes bundled with the convenience. When the professional corporation, the prescriber network, the pharmacy contracts, and the patient record all arrive from one vendor, they arrive as one object. You did not assemble them, which means you cannot easily disassemble them. That is not a hidden trick; it is the shape of the model, and it is the thing to read carefully before you sign. We cover the general version in the structural problems with telehealth-in-a-box platforms.

What is the MSO-PC structure, and why does it matter here?

An MSO-PC structure separates the business from the practice of medicine. A physician-owned professional corporation employs the clinicians and holds clinical authority; a management services organization provides technology, marketing, and operations under a management services agreement. It exists because most states apply some form of the corporate practice of medicine doctrine, which bars lay-owned entities from owning a medical practice.

This is a legitimate legal architecture, not a workaround. Federal regulators have engaged with it directly: in June 2025 the HHS Office of Inspector General issued Advisory Opinion 25-03, a favorable opinion on a proposed arrangement in which a management support organization and an affiliated professional corporation would contract with telehealth providers to lease employees and supply administrative services (https://oig.hhs.gov/compliance/advisory-opinions/25-03/). OIG concluded the arrangement would not generate prohibited remuneration under the federal Anti-Kickback Statute, on the requestors' certification that it met the personal services and management contracts safe harbor.

Two cautions matter when a vendor cites that opinion at you. Advisory opinions are fact-specific and may be relied upon only by the parties that requested them, so it is not a blanket blessing of every MSO-PC arrangement in the market. And the anti-kickback analysis is separate from the corporate-practice analysis, which is state law: an arrangement can be clean federally and still raise CPOM questions in California or Texas.

The commercial question is different from the legal one, and it is the one this post is about. The structure is fine. The question is who supplied it. If the PC was formed by your counsel with a physician you chose, the structure is yours and it survives a change of vendor. If the PC, the physician, the MSA template, and the EHR all came from the platform, then your legal structure and your software vendor are the same counterparty. Our longer treatment of this is in the MSO-PC structure and the lock-in trap inside it.

What does neolife do differently?

neolife is the fulfillment rail for telehealth: AI-native intake, compliance, and cross-pharmacy order routing that sits on top of the compounding pharmacy a clinic already uses. It does not supply your PC, your physician, or your storefront. It owns the order path and nothing else, which is precisely why the operator stays the system of record.

A licensed provider approves every order that moves through the rail. That is not a compliance ornament. Compounding under section 503A presumes a licensed pharmacist compounding for an identified patient with a valid prescription, per FDA's compounding guidance (https://www.fda.gov/drugs/human-drug-compounding/compounding-and-fda-questions-and-answers), and neolife's intake and routing are designed around that presumption rather than bolted onto it afterward.

The overlay posture is the whole design. neolife annexes the thin intake and routing layer and leaves the pharmacy's fill backbone untouched, which is what makes adding a second pharmacy a routing change rather than a migration. Your storefront stays yours, whether that is Shopify or something you built. Your patient database stays in infrastructure you control. Your pharmacy contract stays in your name, because neolife never became a party to it.

The honest limitation: neolife will not hand you a prescriber network or a professional corporation. If those are your gap, the rail alone does not close it.

Which one is right for you?

Start from what you already hold, not from the feature list. Four questions usually settle it; the first two settle most.

1. Do you hold, or can you form, your own PC and physician relationship? If yes, a platform-supplied clinical stack is solving a problem you do not have. If no, and you do not want to build one, an all-in-one closes a genuinely hard gap.
2. Do you have a pharmacy account in your own name? If yes, you want something that overlays it. If no, a bundle gets you filling orders sooner.
3. How likely are you to switch pharmacies or add a modality in the next two years? The more likely, the more the bundled model costs you later.
4. Is being the system of record strategic to you? If your patient base is the asset you are building, the layer that holds it should be one you own.

Here is the head-to-head on the criteria operators actually weigh.

Decision criterion	TEHR (all-in-one platform)	neolife (fulfillment rail)
What you are actually buying	A launched brand: PC, prescribers, catalog, pharmacy, EHR	An order rail over the stack you already own
Who holds the patient record	The platform's EHR	You, the operator, as system of record
Who holds the prescriber relationship	The platform's affiliated PC and network	Your own PC and clinicians
Pharmacy flexibility	Routed to partner pharmacies within the platform	Your account; add pharmacies without a rip-and-replace
Storefront ownership	Platform-provided brand storefront	Your own (Shopify or otherwise)
Switching cost	High: unwinding the clinical structure and the software together	Low: a routing change, not a migration
Pricing shape	Catalog-tiered plus per-transaction fees, per public materials	Flat FMV SaaS plus per-order buy-down; pharmacies free

On pricing, credit where it is due: TEHR's published approach uses flat, catalog-based tiers plus per-transaction fees rather than a percentage of revenue, which is a more defensible shape than the take-rate models common in this category. neolife charges a flat fair-market-value SaaS fee plus a per-order buy-down, and pharmacies pay nothing to be on the rail. We avoid percentage-of-value structures deliberately, to stay clear of federal fee-splitting concerns and to keep the incentive on filling orders correctly rather than maximizing a cut.

What happens when you want to switch pharmacies or add a modality?

This is where the two models separate hardest. On a rail, adding a pharmacy or a new category is a routing and configuration change: the storefront, the patient database, and the order history do not move. In a bundled arrangement, the same request is a change to the platform's supply chain, and it moves at the platform's pace.

The mechanism is not malice, it is dependency. If the partner pharmacies, the prescriber rates, and the protocol catalog all sit on the vendor's side of the line, then every expansion is a request rather than a decision. A compounder with better sterile capacity in your region, renegotiated per-Rx economics as volume triples, a modality the catalog does not carry yet: each one puts you back in the queue behind every other brand on the platform, and your negotiating position is bounded by how hard it would be to leave.

That difficulty compounds with time, because every month adds patients, refill history, and payment relationships to the vendor's side of the ledger. It is the dynamic we describe in the switching costs baked into platform lock-in. Run the exit in your head before you sign: if you left in eighteen months, which assets walk out with you? If prescribers and pharmacy contracts are not on that list, price it in.

Who holds the patient record and the prescriber relationship?

On neolife, you do. In a platform-supplied MSO-PC arrangement, the professional corporation holds the clinical relationship and the platform's EHR typically holds the record, which means your practical control runs through their export tooling and their contract terms rather than through your own systems.

Data is the sharpest edge of this. Under HIPAA's right of access, patients can generally obtain their records within 30 days (45 CFR 164.524, https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html). That is a patient right, not an operator right. Your contractual ownership of the patient database, your ability to export it in a usable structure rather than a PDF dump, and your standing as the operator of record are separate questions that no statute answers for you. They are answered in the agreement, which is why we push operators to settle who is the system of record for patient data before signing rather than after.

The prescriber side deserves the same scrutiny. If the physician who owns your PC was introduced by the platform and the MSA came from the platform's template, the relationship is real but it is not portable. Ask in writing: on termination, does the PC continue, does the physician continue with us, and who holds the records at the PC level. The questions to ask before signing a fulfillment platform is built for that conversation.

Is TEHR ever the better call?

Often, actually. If you have an audience and no clinical infrastructure, no physician relationship, no pharmacy account, and no intention of acquiring any of them, an all-in-one that hands you a working, compliantly structured clinic is the right answer and a rail is not. Speed from a genuine cold start is a real advantage, and the MSO-PC scaffolding is not something a first-time operator should improvise.

There is a second case where the bundle wins on the merits: when you do not want to hold provider relationships at all. Owning a PC, managing physician succession, and carrying clinical governance is work some operators neither want nor should be doing. For that buyer, renting the clinical layer is not a compromise, it is correct.

The framing we would push is sequence, not verdict. Launch on a bundle to prove demand, then own the layers that turn out to matter. The failure mode is drifting into year three with the patient database, the prescribers, and the pharmacy contracts all sitting on someone else's balance sheet and discovering the cost only during a renegotiation. If you are already there, getting off platform dependency is a solvable project, just a more expensive one than starting clean.

The short version

TEHR gives you a whole regulated health brand, structure included, quickly, in exchange for running inside its clinical infrastructure. neolife gives you an order rail that overlays your own storefront, your own PC, and your own pharmacy, and keeps you the system of record, in exchange for bringing those pieces yourself. If you are starting from zero and do not want to hold provider relationships, the platform is the defensible choice. If your patient base and pharmacy relationships are the asset you are building, the rail is the one that leaves them yours.

neolife is the rail those platforms hide. It overlays the pharmacy you already use, keeps a licensed provider on every order, and makes switching a routing decision instead of a legal unwind. If you want a read on your specific setup, talk to us and we will map it honestly, including where a platform is the reasonable move.

This article is for informational purposes only and is not legal, medical, or regulatory advice; consult qualified counsel and licensed clinicians for your specific situation.