GLP-1

The 60-90 Day Plan After a 30-Day GLP-1 Soft Launch: Scaling What Works

The 30-day soft launch is the starting line, not the finish line. The next 60 to 90 days are where a real program emerges: scaling the funnel that worked, building provider capacity before the backlog forms, retiring the manual workarounds, and shipping the items you deliberately deferred. This is the founder playbook for the second sprint.

Day 30 was not the finish line

A 30-day soft launch gets the founder to a real, operational program with the first patients served. That is genuinely worth celebrating. It is also, on day 31, only the beginning.

The next 60 days are the more interesting work. The first cohort has shown the team what the program actually is. The data is real. The patient interviews have started returning patterns. The providers know where the chart-note template is awkward. The support tickets are starting to cluster.

Most importantly, the team now knows what is worth scaling, what needs fixing, and what was deliberately set aside in the first 30 days. The second sprint is where those answers turn into a program that can comfortably serve hundreds of patients per month and is ready for the next state, the next program, and the next layer of the team.

This post is the playbook for days 31 to 90: what to focus on, in what order, and how to keep the momentum the first 30 days created.

For the foundational 30-day work this builds on, see The 30-Day GLP-1 Telehealth Launch Plan: From Incorporation to First Patient Served and Launching a GLP-1 Telehealth Business in 2026: The Best Setup Founders Have Had Yet.


Day 30 retrospective: extract everything the first cohort taught you

Before the second sprint starts, run a real retrospective. Not a metrics update. A structured review that sets the next 60 days on the right foundation.

A practical day-30 retrospective covers seven areas.

AreaWhat to look at
AcquisitionChannels, creatives, and audiences that brought the best-fit patients
FunnelStep-level conversion, drop-off concentration, completion rate
Provider reviewApproval rate, refusal rate and reasons, time per chart note
FulfillmentOrder-to-ship latency, patient delivery confirmation, supply reliability
SupportTop ticket categories, time-to-resolution, themes from cancellations
Retention so farFirst-month behavior, portal engagement, second visit booking
Team and operationsWhere the team felt stretched, what manual steps held it together

The retrospective is not about scoring. It is about what to do next. For each area, the question is the same: what worked, what needs to change, what to ship in the next 60 days.

For the broader first-100-patient learning approach this dovetails with, see Your First 100 Telehealth Patients: What to Learn Before You Scale.


Days 31 to 45: Scale what worked, fix what broke

The first half of the second sprint is about leaning into the patterns the first 30 days surfaced.

Scale the acquisition that brought the right patient

The first 30 days usually surface one or two acquisition channels and creatives that bring the right-fit patient at sustainable economics. The next 30 days are about doubling down on those, with discipline.

Practical steps:

  • Increase budget on the channels and creatives the data supports
  • Build a library of variations on the winning creative concept
  • Set up structured creative testing with one variable at a time
  • Expand the audience that worked into adjacent audiences
  • Hold spend steady on anything that has not proven itself yet

Resist the urge to scale everything at once. The brands that survive a paid spend increase are the ones that scale what is working and pause what is not.

For the underlying advertising patterns, see Marketing Your GLP-1 Program in 2026 and GLP-1 Telehealth Advertising in 2026: The Creative Patterns and Channels Winning Right Now.

Tighten the funnel where it leaked

The first 30 days revealed exactly where the funnel leaks. Now is the time to fix it.

The fixes that usually return the most in the first half of the second sprint:

  • Reorder or rewrite the intake questions that confused the first cohort
  • Add reassurance content where drop-off concentrated (price clarity, eligibility messaging, what-to-expect language)
  • Tighten the pre-checkout messaging to set the right expectation about provider review and timing
  • Add or improve the resume-link flow for abandoned intake
  • Refresh trust signals on the landing page where the data showed friction

A small set of intake and landing-page fixes here often lifts overall conversion by meaningful margins.

For the broader funnel measurement layer, see Find the Leaks: How to Instrument a GLP-1 Sales Funnel and Fix the Step That's Actually Costing You.

Tighten provider review and chart-note workflow

Provider feedback from the first 30 days is the input. The patterns that often emerge:

  • A chart-note template that needs new fields or fewer fields
  • An intake question that did not give the provider what they needed
  • A refusal pathway that providers want to use more easily
  • A follow-up workflow that needs better automation

Each of these is a small, high-leverage fix that compounds over the next 60 days. For the broader protocol and chart-note layer, see Clinical Protocols for DTC Telehealth: What to Standardize Before Your First Patient and How to Use Healthie Charting Notes in a Telehealth Workflow Without Creating Double Work.

Move the top support topics upstream

Cluster the first 30 days of support tickets. The top three categories often represent 60 to 70 percent of contact volume. Each of those categories belongs in:

  • The landing-page FAQ
  • The post-checkout email
  • The patient portal
  • The provider chart note where relevant

Moving the top support topics upstream cuts support load, lifts patient satisfaction, and frees the team for the work that requires a human.


Days 31 to 60: Provider capacity planning before the backlog

The single most common scaling failure in months two and three is a provider capacity backlog. The funnel is working, the team is excited, the prescription queue starts to grow, and suddenly patients are waiting two days, then four, then a week for provider review.

The fix is to plan capacity ahead of demand.

Forecast provider load

A simple forecast keeps the team ahead. The key inputs:

  • Current intake completion rate per day
  • Current approval rate
  • Average chart-note time per provider
  • Provider hours available per week
  • Refill cadence for the active patient base

A simple model translates inbound intake to weekly chart-note workload. When the workload approaches the available provider hours, the team has a problem coming.

Add providers before the backlog forms

The brands that scale provider capacity smoothly add a provider when capacity is at 70 to 80 percent, not when the backlog is forming. Onboarding takes weeks. The wait is not over once the contract is signed.

Useful steps:

  • Maintain a small bench of credentialed providers ready to onboard
  • Build provider onboarding into a documented process with templates and training
  • Run a peer-review or co-signature pattern for the first chart notes from new providers
  • Track provider productivity by chart-note time, refusal rate, and patient satisfaction

For the broader capacity layer, see Provider Capacity Planning for Telehealth: How to Grow Without Creating Review Backlogs and Provider Network vs. Your Own Clinicians: How DTC Telehealth Brands Should Choose.

Train providers on the program, not just on the workflow

The technical onboarding (EHR access, chart-note template, ePrescribing) is the easy part. The program-specific training is what makes a new provider valuable quickly. That includes:

  • The program's clinical philosophy and patient population
  • The intake questions and what they are looking for
  • The refusal pathway and how to use it confidently
  • The retention and follow-up cadence
  • Common patient concerns and how the team prefers to address them

A documented provider playbook earns its keep here.


Days 45 to 75: Retention infrastructure goes live

The first 30 days served the first cohort with manual workflows and founder attention. That works when the program has 20 patients. It does not work at 200.

The second half of the second sprint is when the retention infrastructure has to go live so the program can serve hundreds of patients without dropping any.

The retention milestones that earn their place

A practical milestone-based retention program covers:

  • Day 0: welcome and what-to-expect message
  • Day 3: side-effect support and education
  • Day 7 to 10: first-week check-in
  • Day 14 to 21: titration window content and provider message
  • Day 30: month-one milestone content
  • Day 45: cross-program education for relevant patients
  • Day 60 to 90: the well-known month-two churn window deserves its own treatment

Each milestone is a chance to reduce churn before it happens, not after. For the underlying content, see GLP-1 Retention Emails: What to Send in Month 2 to Prevent Drop-Off and Month 2 Churn in GLP-1 Programs: Why Patients Drop and How to Recover Them.

Lifecycle messaging across channels

The retention program runs across email, SMS, the patient portal, and the provider check-in. Each channel does what it is best at:

  • Email: education, milestones, longer-form support
  • SMS: short reminders, appointment-style messages, urgent prompts
  • Portal: surface lab results, refill status, next steps in plain language
  • Provider message: the human, clinical layer that no automation replaces

For the broader subscription and lifecycle design, see Subscription Design for Telehealth Programs: What Improves Retention and What Creates Churn.

Refill operations and pharmacy status visibility

The first 30 days had few refills. Days 60 to 90 are when refill volume starts to matter, and the patterns the team builds now scale for the rest of the year.

The infrastructure that earns its place:

  • Automated refill reminder and approval workflow
  • Pharmacy status visibility in the portal and to support
  • Clear handling of out-of-stock, delayed, or returned shipments
  • A defined patient communication pattern for any refill exception

For the operational layer, see GLP-1 Refill Operations: A Workflow to Prevent Missed Cycles and Support Spikes and Pharmacy Status Visibility in Telehealth: How to Reduce 'Where Is My Prescription?' Support Tickets.


Days 60 to 90: Add the second state without breaking the first

Most teams launch in one or two states. Around days 60 to 90, the right second state opens up real growth.

Pick the next state on purpose

The right second state is not the next biggest market. It is the next state where licensure, regulatory environment, pharmacy partner coverage, and clinical leadership all line up.

Useful inputs to the decision:

  • Provider licensure and compact participation
  • Telehealth establishment rules for the program category
  • Controlled-substance considerations if relevant
  • Pharmacy partner shipping capabilities
  • Estimated demand based on first-state data
  • Marketing channels that work in the target state

For the broader expansion playbook, see State Expansion for Telehealth: The Ops Checklist Before You Launch a New State.

Run a controlled expansion, not a full rollout

The right pattern is a controlled expansion: open the next state, drive modest volume, validate the workflow end to end, fix anything that broke, and then scale spend.

A small, controlled expansion in days 60 to 90 sets up larger and faster expansion later. A big-bang expansion that breaks fulfillment or provider capacity sets it back.

Add programs only if the foundation is ready

Some brands consider adding a second program (an additional indication, a specialty lane, an adjacent category) in this window. The honest test is whether the first program is running smoothly enough that the team has the bandwidth.

If the first program still has open issues, fix those first. The same team adding a second program before the first one is solid often causes both to underperform.

For the broader program expansion decision, see Telehealth Specialty Expansion: How to Decide the Next Program After GLP-1, Hair Loss, or Sexual Health.


Ship the deliberately deferred items

Days 60 to 90 are when the items deliberately set aside in the first 30 days get scheduled. The team has the data now to know which ones earn their place.

A short list of common day-60 candidates:

  • Patient mobile app or improved mobile portal experience
  • Advanced segmentation in the CRM and lifecycle messaging
  • Pharmacy redundancy or a second pharmacy partner
  • Lab vendor integration if labs are part of the program
  • An affiliate or creator program with structured compliance review
  • A GEO program for AI answer engines
  • An expanded support model (tier-2, dedicated clinical support)
  • A patient education content library

The list is long; the budget is short. Pick the two or three items that the first 30 days proved the program needs most.

For the related ad-channel and GEO layer, see Generative Engine Optimization for Telehealth: How to Show Up in ChatGPT, Claude, and Perplexity Answers and Affiliate and Creator Programs for DTC Telehealth: How to Grow Without FTC, Fake Review, or Medical-Claims Risk.


Build the team for sustained scale

The 30-day launch ran on a small team, often with the founder playing multiple roles. The second sprint is where the team starts to specialize.

The patterns that usually pay off in days 31 to 90:

RoleWhat they cover
Clinical leadProtocols, refusal patterns, provider quality, clinical leadership
Operations leadPharmacy, lab, supply, fulfillment, refill operations
Marketing or growthAcquisition, creative, content, GEO, partnerships
Engineering or productIntegrations, observability, intake, portal, mobile
Support and careFirst-line patient support, clinical escalation, ticket clustering
Provider teamScheduled hours, defined patterns, peer review

In a small team, several of these roles are still played by one person. The discipline is to know which role is being played at any moment, and to be honest about where the team is stretched.

Hiring decisions in this window often pay back quickly. A dedicated patient support hire reduces founder time by tens of hours. A dedicated operations hire frees the clinical team to focus on patients. A dedicated growth hire moves the funnel faster.

For the broader operating cadence, see The Weekly Telehealth Ops Dashboard: 12 Metrics Leadership Should Actually Review.


The day-90 strategic gate

Day 90 is the moment to step back and decide. The program now has three months of real data, two waves of cohort learnings, and a team that has lived through both the launch and the second sprint.

A practical day-90 strategic gate covers:

What is working at scale

The acquisition channels, creative concepts, intake patterns, provider workflows, and retention milestones that have proven themselves. These are the foundation for the next stage.

What still needs fixing

The gaps the team has documented and not yet shipped. The realistic timeline for each.

Where the next state, program, or channel goes

The second state, second program, or new channel that the data supports. With a realistic timeline.

The team for the next phase

The hires and role expansions the program needs to support the next quarter and the next year.

The financial picture

A clear view of unit economics, including channel-level CAC, real LTV signal, gross margin, and contribution margin. Honest enough to underwrite real growth investment.

For the related economics framing, see How to Evaluate ROI on a Telehealth Platform Without Getting Lost in Vanity Metrics and Subscriber Growth vs. Patient Quality: The DTC Telehealth Metrics That Actually Matter in 2026.

The artifact

A short strategic document, perhaps 10 to 15 pages, that captures the answers. This becomes the reference for the next quarter and the input to the next strategic review at month six.


What the program looks like at day 90

A program that uses days 31 to 90 well has, by day 90:

  • 200 to 500 patients served end to end across the active program
  • Acquisition channels and creatives that scale at sustainable economics
  • A tightened funnel with documented step-level conversion
  • A provider model with capacity ahead of demand and onboarding pattern in place
  • An operational retention infrastructure across email, SMS, and portal
  • A live refill operations workflow with pharmacy status visibility
  • A second state launched and validated
  • The two or three deferred items that mattered most shipped
  • A team with specialized roles and a clear hiring plan
  • A documented day-90 strategic review with named decisions
  • An honest financial picture grounded in real data

This is not a complete program. No program is. It is a confident, learning, scaling program that earned the right to grow into the next phase.


Implementation checklist

Use this through days 31 to 90.

Day-30 retrospective

  • Retrospective scheduled and prepared
  • Seven areas reviewed with named conclusions
  • Next-60-day priorities documented

Scale and fix (days 31 to 45)

  • Winning acquisition channels and creatives scaled deliberately
  • Funnel fixes shipped where the data pointed
  • Provider chart-note and review tightened
  • Top support topics moved upstream

Provider capacity (days 31 to 60)

  • Provider load forecast in place
  • Bench of credentialed providers ready to onboard
  • Provider onboarding playbook documented
  • Peer review or co-signature pattern for new providers

Retention infrastructure (days 45 to 75)

  • Milestone-based retention program live
  • Lifecycle messaging running across email, SMS, portal, provider
  • Refill operations workflow live
  • Pharmacy status visibility in the portal

Second state and program decisions (days 60 to 90)

  • Second state selected and validated
  • Controlled expansion executed
  • Second program decision (yes or not yet) made with reasoning

Deferred items shipped

  • Top two or three deferred items shipped

Team

  • Specialized roles defined
  • Hiring plan documented

Day-90 strategic gate

  • Strategic review prepared and run
  • Decisions documented
  • 10-page strategic snapshot saved

Final takeaways

The 60 to 90 days after a 30-day soft launch are where a real telehealth business emerges. The first 30 days proved the program could exist. The next 60 prove it can grow.

What to remember:

  • Day 30 is the start of the second sprint, not the end of the first
  • A real retrospective extracts the first 30 days' lessons before the next 60 begin
  • Scale the acquisition and creative that brought the right-fit patient; pause what did not work
  • Fix the funnel where the data showed friction
  • Plan provider capacity ahead of demand; add providers at 70 to 80 percent load
  • Ship the retention infrastructure that turns a small program into a hundreds-of-patients program
  • Add the second state on purpose, with a controlled expansion before a full scale
  • Add a second program only if the first is running smoothly
  • Build the team for sustained scale by specializing roles
  • Run a real day-90 strategic gate with documented decisions and a snapshot artifact

A program that uses these 60 days well moves from "we launched something" to "we run something." That shift is the foundation for everything that comes next: serious growth, more states, more programs, the team that supports them, and the patient relationships that compound for years.

The first 30 days were the proof. The next 60 are the foundation.

More from GLP-1