The GLP-1 Telehealth Stack: What You Actually Need to Launch

GLP-1 is the fastest-growing vertical in telehealth. Semaglutide and tirzepatide programs are launching every week, backed by everything from venture-funded startups to established med spas pivoting into weight management. The demand is real, the margins are attractive, and the patient interest is enormous.

But here's what most teams get wrong: they think launching a GLP-1 program means finding a provider, building a website, and plugging in a payment form. That gets you a landing page, not a business. The difference between programs that scale and programs that stall out at 200 patients is almost always the stack, the infrastructure underneath.

We've helped dozens of telehealth operators build and launch GLP-1 programs. This is the guide we wish existed when we started: a layer-by-layer breakdown of the technology stack you actually need, the decisions that matter at each layer, and the mistakes that cost teams months.

The Seven Layers of a GLP-1 Stack

Every GLP-1 telehealth program, regardless of size, needs to solve seven problems. Some teams use one platform to cover multiple layers, others assemble best-in-class tools. Either way, you need coverage across all seven:

1. Marketing site: how patients find you and decide to start
2. Checkout and intake: how patients pay and submit their health information
3. Provider network: who writes the prescriptions and manages clinical care
4. Pharmacy and eRx: how prescriptions get filled and shipped
5. Patient portal: how patients track orders, message support, and manage refills
6. CRM and data routing: how patient data flows between systems
7. Analytics: how you measure what's working and what's leaking

Let's walk through each one.

1. Marketing Site

What Does a GLP-1 Marketing Site Do?

Your marketing site is the front door. It's where paid traffic lands, where organic search converts, and where patients decide whether your program feels legitimate. In GLP-1, trust is everything. Patients are putting a needle in their body based on what they read on your site.

What Makes a GLP-1 Marketing Site Convert?

Page speed, mobile experience, and conversion rate. A site that scores below 80 on Lighthouse is leaving money on the table, especially on mobile, where most GLP-1 traffic converts. You also need strong SEO fundamentals. Paid acquisition costs in this vertical are climbing fast, and organic traffic is the only channel that gets cheaper over time.

Common GLP-1 Marketing Site Mistakes

Using a bloated page builder or a generic template that loads 2MB of JavaScript before the patient sees a single word. Over-designing the site instead of optimizing the funnel. Ignoring structured data and local SEO, which are massive for "GLP-1 near me" queries even for telehealth programs.

This is one layer where custom work pays for itself. A conversion-focused site built for performance (90+ Lighthouse scores, fast LCP, clean markup) will outperform a template every time. That's exactly what Thimble Sites is built to deliver.

2. Checkout and Intake

What Does GLP-1 Checkout and Intake Do?

This is where the patient goes from interested to enrolled. They select a program, enter payment, and complete their medical intake questionnaire. The checkout and intake experience is the single highest-leverage piece of your stack. Small improvements here compound across every patient.

What Makes GLP-1 Checkout and Intake Work?

Flexibility in offer structure is critical. GLP-1 programs are rarely simple one-time purchases. You need subscriptions with different billing cycles, tiered dosing plans, membership models, add-ons like lab work or nutrition coaching, and upsells for supplies or ancillary products. Your checkout needs to handle all of this without duct tape.

On the payment side, Stripe is the default for most teams, and for good reason: the developer experience is excellent and the ecosystem is deep. Braintree and Authorize.Net are solid alternatives, especially if you're working with a payment processor that requires them or you need specific gateway features.

For intake forms, you have strong options: Formsort is purpose-built for healthcare intake with conditional logic and HIPAA compliance. Typeform and Jotform work well for simpler flows. Cognito Forms is underrated for teams that need complex form logic without a big budget.

This is where Thimble Cart lives. It handles custom checkout flows with subscriptions, one-time purchases, memberships, tiered plans, add-ons, and upsells, all integrated with your intake forms, provider network, and payment processor. It's designed to work with any provider network and any pharmacy, which means you're not locked into a single fulfillment path.

3. Provider Network

What Does a GLP-1 Provider Network Do?

The provider network is who actually evaluates patients and writes prescriptions. Unless you're a medical group with your own clinicians, you're contracting with a provider network that supplies licensed prescribers in the states where your patients live.

How to Choose a GLP-1 Provider Network

State coverage, turnaround time, clinical quality, and integration capabilities. The major players each have different strengths. OpenLoop and Wheel offer broad state coverage and are well-suited for high-volume programs. Wizlo and CareValidate are strong options if you need flexible provider matching or specific credentialing workflows. MD Integrations works well for teams that want more control over the clinical relationship. SteadyMD is popular for dedicated provider models where you want the same clinician seeing your patients consistently.

Common Provider Network Mistakes

Choosing a provider network based solely on per-consult cost without evaluating turnaround time or integration depth. A network that's $5 cheaper per consult but takes 48 hours instead of 12 will cost you more in patient drop-off and support tickets than you'll ever save on the consult fee.

Also: not confirming state coverage before you start running ads. Nothing burns money faster than acquiring patients in states your providers can't serve.

4. Pharmacy and eRx

How Does GLP-1 Pharmacy Fulfillment Work?

Once a provider writes a prescription, it needs to get to a pharmacy, get filled, and get shipped to the patient. This layer covers electronic prescribing (eRx), pharmacy fulfillment, and shipping logistics.

What Makes GLP-1 Pharmacy Fulfillment Reliable?

Reliability and speed. Patients who just paid $300+ for a GLP-1 program expect their medication to arrive quickly. Truepill is a popular choice for digital-first pharmacy fulfillment with strong API integrations. Alto Pharmacy offers a more consumer-facing experience with real-time delivery tracking. For eRx routing specifically, DoseSpot and DrFirst are the two dominant platforms, and most provider networks already integrate with one or both.

Common Pharmacy Fulfillment Mistakes

Not having a fallback pharmacy. Supply chain issues with compounded semaglutide are real and ongoing. Teams that rely on a single pharmacy source will eventually face a situation where they have paying patients and no medication to ship. Build relationships with at least two pharmacy partners from day one.

5. Patient Portal

What Does a GLP-1 Patient Portal Do?

The patient portal is the ongoing experience after enrollment. It's where patients check their order status, message your support team, request refills, complete follow-up questionnaires, and manage their account. For subscription-based GLP-1 programs, the portal is where retention happens.

What Makes a Good Telehealth Patient Portal?

Clarity and self-service. The number-one driver of support tickets in GLP-1 programs is "where is my medication?" A good portal answers that question before the patient has to ask. It should show clear status tracking, from intake submitted, to provider review, to prescription sent, to pharmacy fulfillment, to shipped, to delivered.

Beyond status tracking, the portal needs to handle messaging, refill requests, and follow-up health assessments. Integration with your EHR is important here. Healthie is excellent for telehealth-native workflows and has a modern API. Elation Health and athenahealth are stronger choices if your clinical team prefers a traditional EHR interface. Canvas Medical is worth evaluating if you want a developer-friendly, API-first EHR that gives you maximum control over the patient experience.

This is where Thimble Portal fits in. It provides the patient-facing experience layer (accounts, status tracking, messaging, refills, and follow-ups) designed to sit on top of whatever EHR or CRM you're already using. It's not trying to replace your clinical system; it's giving your patients a better front end to it.

Common Patient Portal Mistakes

Treating the portal as an afterthought and sending patients to a generic EHR patient portal that wasn't designed for a DTC telehealth experience. Your checkout was branded and polished, and your portal should be too. The gap between a premium checkout experience and a clunky patient portal is where churn lives.

6. CRM and Data Routing

What Does CRM and Data Routing Do in Telehealth?

The CRM layer is the connective tissue of your stack. It's where patient data lives, where automations trigger, and where your operations team manages the day-to-day. It's also where most stacks fall apart.

What Makes Telehealth Data Routing Work?

Data flow between systems. When a patient completes checkout, their information needs to flow to your CRM, trigger a provider assignment, notify the clinical team, and eventually route the prescription to the pharmacy. When the pharmacy ships, that status needs to flow back to the patient portal. Every gap in this chain creates a manual task for your team or a confusing experience for your patient.

For the CRM itself, Tellescope is purpose-built for telehealth and handles patient communication, task management, and care coordination well. HubSpot and Salesforce are the enterprise options, powerful but heavier to configure. GoHighLevel is popular with smaller operators who want an all-in-one marketing and CRM platform, though it requires more customization for healthcare workflows.

For connecting everything together, automation platforms are essential. Zapier is the easiest to set up and has the broadest integration library. Make (formerly Integromat) offers more complex logic at a lower price point. n8n is the self-hosted option for teams that want full control. Keragon is worth a look if you need healthcare-specific automations with built-in HIPAA compliance.

Common Data Routing Mistakes

Building automations that are fragile and break silently. A Zapier workflow that fails at 2 AM means a patient doesn't get routed to a provider, which means a 24-hour delay they weren't expecting. Monitor your automations like you'd monitor a production server, with alerts, retries, and fallback logic.

7. Analytics and Lab Integration

What Do Analytics and Labs Cover in a GLP-1 Program?

Analytics covers both business metrics (conversion rates, churn, LTV) and clinical data (lab results, dosing outcomes, patient-reported progress). For GLP-1 programs that require lab work, which is increasingly common as programs mature, you also need lab integrations.

What Metrics Matter Most for GLP-1 Programs?

On the lab side, Health Gorilla is the leading aggregator for electronic lab ordering and results retrieval, connecting to both Labcorp and Quest Diagnostics. If your program requires baseline metabolic panels or A1C testing before prescribing, you need a clean integration here. Some provider networks handle lab ordering natively; others expect you to manage it.

On the business analytics side, the metrics that matter most for GLP-1 programs are: checkout conversion rate, time from payment to medication delivered, refill rate by month, and support ticket volume per active patient. If you can't measure these four things reliably, you're flying blind.

How the Layers Connect

Understanding each layer individually is the easy part. The hard part, and the part most teams underestimate, is how the layers connect to each other.

Here's the core data flow in a GLP-1 program: a patient lands on your marketing site, clicks through to checkout, selects a plan, enters payment, and completes their medical intake. That intake data needs to route to your CRM, which triggers a provider assignment. The provider reviews the intake, conducts a consultation (async or sync), and writes a prescription. That prescription routes through eRx to your pharmacy partner. The pharmacy fills and ships the medication. The shipping status updates flow back through your CRM to the patient portal, where the patient can track delivery.

Every arrow in that chain is a potential failure point. And when something breaks, the patient doesn't see a technical error. They see silence. No update, no medication, no response. That's when they dispute the charge.

This is exactly why we built Thimble Cart, Thimble Sites, and Thimble Portal as modular products that integrate with best-in-class tools at every layer. You shouldn't have to use our pharmacy or our providers; you should be able to use whatever works best for your program and have the data flow cleanly regardless.

Build vs. Buy: A Layer-by-Layer Decision

Not every layer deserves the same approach. Here's how we think about the build-vs-buy decision for each one:

• Marketing site: Build custom. This is your brand. A performance-optimized, conversion-focused site will outperform any template, and the investment pays back in lower acquisition costs for the life of the program.
• Checkout and intake: Buy or partner, but demand customization. Your checkout flow needs to feel like your brand, handle your specific offer structure, and integrate with your specific provider and pharmacy partners. Off-the-shelf rarely cuts it here.
• Provider network: Buy. Building your own provider network is a regulatory and operational burden that most teams shouldn't take on until they're well past product-market fit. Use an established network.
• Pharmacy and eRx: Buy. No question. The compliance and logistics complexity makes this a pure partnership decision.
• Patient portal: Build custom or use a purpose-built tool. This is a retention surface and it needs to feel like your brand. Generic EHR patient portals create a jarring experience gap.
• CRM and data routing: Buy the CRM, invest in the routing. The CRM platform matters less than the quality of your automations and integrations. Pick a CRM your ops team likes, then invest heavily in building reliable data flows.
• Analytics and labs: Buy. Use Health Gorilla or direct lab integrations for clinical data. For business analytics, instrument your stack with events and build dashboards in whatever your team already uses.

The Modular Advantage

The GLP-1 market is moving fast. Pharmacy partnerships change. New provider networks emerge. Regulations shift. The programs that thrive are the ones that can adapt without rebuilding from scratch.

A modular stack, where each layer is handled by a best-in-class tool connected through clean integrations, gives you that flexibility. If your pharmacy partner has supply issues, you can switch to another without touching your checkout or patient portal. If a new provider network offers better coverage in your key states, you can onboard them without rewriting your intake flow.

The goal isn't to find one platform that does everything. It's to pick the best tool for each layer and make sure they talk to each other reliably.

That's the philosophy behind everything we build at Thimble Hub. Thimble Cart handles checkout and intake with the flexibility to support any offer structure and any downstream partner. Thimble Sites delivers marketing sites that convert. Thimble Portal gives patients a polished experience without requiring you to rip out your existing clinical systems.

Each piece works independently. Together, they give you a stack that's built for the reality of running a GLP-1 program. Not the pitch deck version, but the version where pharmacy supply chains hiccup, provider networks update their APIs, and patients expect Amazon-level tracking on a $350 monthly subscription.

Where to Start

If you're launching a GLP-1 program today, start with the three layers that touch the patient directly: your marketing site, your checkout and intake flow, and your patient portal. Get those right first. They determine your conversion rate, your first-impression quality, and your retention, the three metrics that decide whether your program scales or stalls.

Then build out your provider network relationship, pharmacy integration, and CRM routing. These are the operational layers that determine how reliably you can fulfill what you sold. They're less visible to the patient but they're what keep the machine running.

The stack you choose today doesn't have to be the stack you run forever. But the architecture decisions you make (modular vs. monolithic, custom vs. template, integrated vs. siloed) are much harder to change later. Get the architecture right, and the individual tools can evolve as your program grows.