Adding Lab-Driven TRT and HRT Programs to a Scaling Telehealth Brand, Without Locking Into One Vendor
The client had a fast, heavily customized platform and a growing patient base. Adding hormone therapy meant labs, and the client refused to be trapped in any single vendor. We built the missing layer on top of what the client already owned.
- Industry
- Direct-to-patient telehealth (men's health and hormone optimization)
- Stage
- Well-funded, scaling fast
- Region
- United States (multi-state)
- Engagement
- Custom integration build on the existing platform, then ongoing retainer
- Services used
- Custom middleware, provider-network integration, lab-ordering integration, e-prescribing, auto-refill engine, patient portal
- Outcomes
- New TRT/HRT program added, labs wired end to end, full data and vendor ownership, foundation to scale toward eight figures
The Client
The client runs a direct-to-patient telehealth brand in men's health and hormone optimization. Technical by background, the client could build much of this in-house, but does not have the time, so hires for leverage. The platform is a heavily customized WordPress and WooCommerce backend, hand-coded rather than assembled from off-the-shelf blocks, and it is fast.
The current flow already works. A patient comes to the platform, meets a physician for a synchronous intake through a provider network, the prescription is fulfilled by the pharmacy, tracking goes to the patient, and the system runs a 30-day renewal cycle on its own. The client is well funded and moving quickly toward an eight-figure target, and wanted a development partner to work with, not a vendor to hand the work to.
The Challenge
The client wanted to add TRT and HRT programs, and that is a different kind of workflow. Hormone therapy needs labs. A patient has to get bloodwork, the results have to come back into the system, a provider has to review them, and only then does the protocol move forward. The existing setup had no way to order labs, no way to pull results back in, and no scheduling step for the provider to act on them.
A bolt-on, not a rebuild
The client wanted the new workflow fast, not a replatform that stalled the business they were funded to scale.
Own the data and the code
The client wanted to own the data, the customers, and the code, so a provider or a lab could be switched later without losing anything.
No vendor lock-in
The client did not want to be locked into one vendor's plugin. Vendors change pricing and regulations change faster. The FDA can force site changes on any given morning, and the platform has to keep moving.
The risk was real. Bolt onto the wrong closed platform and the client would trade one bottleneck for another, hand customer data to a vendor, and slow the very scaling the business was funded to hit.
The Solution
We built the missing workflow as an integration layer the client owns, on top of the platform they already had. We did not tie them to any one vendor's plugin, because that is the trap they were trying to avoid.
- 1
We built a custom middleware layer that sits between the client's storefront and the clinical services. It connects to a licensed provider network through their API for the intake and the follow-up review.
- 2
It connects to Rupa Health to order labs and to pull results back into the client's system, and routes the prescription through DoseSpot over Surescripts to the pharmacy.
- 3
We extended the client's existing 30-day renewal engine to the hormone-therapy protocol, so the lab-review-prescribe-fulfill-renew cycle runs on its own.
- 4
Because the logic lives in the client's middleware and not in a vendor's plugin, every piece is swappable. If a provider network changes terms, or a better lab option appears, we re-point the integration and the business keeps running.
- 5
We kept the client's fast, custom frontend in place. We did not replatform it. We layered the new capability on top and left what already worked alone.
- 6
Everything runs on HIPAA-eligible infrastructure with the full BAA chain across the provider network, the lab network, the e-prescribing service, and the pharmacy. The data and the code stay in the client's accounts.
- 7
We ran it as a partnership on a retainer: the same team that built the integration keeps improving it, with twice-weekly 15-minute check-ins and clear scopes and milestones.
Architecture
The new workflow is one owned layer with clean connections out. A patient starts on the existing storefront and completes intake. The middleware sends the visit to the provider network, orders labs through Rupa Health, and waits for results. When results come back, the provider reviews and approves the protocol. The prescription routes through DoseSpot over Surescripts to the pharmacy, tracking flows back, and the renewal engine takes over on a 30-day cycle.
What We Delivered
Hormone-therapy workflow
- Lab ordering built into the patient flow, with results routed back into the system
- Provider review and scheduling wired to the lab results
- A TRT/HRT protocol that runs from intake to fulfillment without manual steps
Owned integration layer
- A custom middleware connecting the storefront to the provider network, the lab network, and e-prescribing
- Every vendor swappable, so a pricing change or a better option does not break the business
- The existing fast frontend kept in place, not replatformed
Renewal and retention
- The 30-day auto-refill engine extended to the new hormone-therapy protocol
- A patient portal view of visit, lab, prescription, and shipment status
Ownership and compliance
- HIPAA-eligible infrastructure with the full BAA chain
- All data, customers, and code owned by the client
- Support for the client's ongoing FDA-compliance workflow
A lab-driven TRT/HRT program added to the existing platform as one owned layer, with no vendor lock-in, launched in ~8 weeks.
What I needed was straightforward. I wanted to add TRT and HRT without ripping out what already works. They built the lab piece, the provider connection, and the renewal logic as one layer on top of my platform, and they built it so I own it. The point is I am not locked into one vendor. I can swap a provider or a lab and the business does not break. That is what let us move fast. Outstanding work, and the right team to keep on.Founder, direct-to-patient hormone-therapy brand
Business Impact
The client added a whole new revenue line without slowing the platform that was already working. The hormone-therapy program runs on its own, from lab order to renewal, so growth does not add manual load.
Because the integration layer belongs to the client and every vendor is swappable, the client is not exposed to one provider's pricing or one plugin's roadmap. The client owns the data and the customers, so nothing ties the business down as it scales. And with the same team on a retainer, the platform keeps moving at the speed the business needs, including the daily compliance work this market demands.
Technologies Used
Why Scalater
Healthcare platforms take more than code. This one needed a workflow that respects how labs, providers, and prescriptions actually move, built so the client keeps control.
We worked as a partner, not a vendor. We added the hormone-therapy program as a layer the client owns, kept their fast frontend intact, and made every integration swappable so no vendor can trap the business. The data and the customers stay the client's. The result is a new revenue line on a foundation built to scale.
Ready to add a new program without rebuilding your platform?
Book a 30-minute architecture call and we'll map your provider, lab, and e-prescribing integrations end to end.