Growth

The January Surge: A September Build List for Telehealth's Biggest Month

January is the biggest demand month in DTC telehealth, and the programs that win it are built in September, not December. Provider capacity, support staffing, pharmacy commitments, ad staging, and load tests all have lead times measured in months. This is the build list, laid out on a September-to-December timeline, with the two failure points that break first: intake review queues and lead response time.

January is won in September

Every operator in weight loss, fitness-adjacent care, and wellness telehealth knows the shape of the year: demand builds through Q4, then the New Year hits and January runs at multiples of an ordinary month. Resolution intent, new insurance years, and post-holiday momentum all land in the same two weeks.

The mistake is treating that as a marketing event. January is an operations event that marketing points a firehose at. The constraint that decides your January is almost never ad budget, it is whether your providers, support team, and pharmacy partners can absorb what the budget buys. And every one of those constraints has a lead time: provider onboarding takes weeks, pharmacy commitments are negotiated in the fall, creative testing needs November data. Start the build in September and January is a harvest. Start in December and January is triage.

It also stacks on top of a Q4 that is already busy: open enrollment season runs September through November with its own demand wave, which we planned in Open Enrollment Season: The Q4 Demand Plan. The January build has to run alongside that, which is exactly why it needs its own timeline.


The build timeline

MonthCapacity and clinicalSupport and opsMarketingSystems
SeptemberModel January volume at 3-5x baseline; open provider recruiting; map state coverage gapsBaseline your support metrics; start hiring or contracting seasonal coverageAudit last January's data; brief creative pipelineRun the first load test; list every queue and its owner
OctoberProvider offers signed; licensing and credentialing in motionDraft the macro library; document escalation pathsProduce creative volume; launch tests to gather dataFix what the load test exposed; instrument queue dashboards
NovemberOnboard and train new providers on protocols; dry-run the review queueTrain seasonal support staff; test macros on live ticketsRead test results; lock winning creative and audiencesSecond load test at full simulated volume; game-day drill
DecemberConfirm on-call and holiday-week schedules; final capacity checkFreeze process changes; publish the surge runbookStage budgets; ramp from December 26 as retail CPMs fallChange freeze; monitor dashboards live; final pharmacy sync

Print it, assign an owner per cell, and review it in a thirty-minute weekly standing meeting from now to New Year's. The rest of this post walks the rows.


Provider capacity: the 3-5x model

Start with arithmetic, not vibes. Take your current daily intake completions, multiply by the surge factor you are planning for, 3x is conservative for an established program, 5x if you intend to push acquisition hard, and divide by your realistic per-provider daily review capacity. The gap between providers-needed and providers-you-have is your September recruiting requisition, and the full method, including state-mix math and backlog dynamics, is in Provider Capacity Planning for Telehealth.

Three January-specific wrinkles:

  • State mix shifts with ad spend. If January budgets open new geographies, your capacity has to be licensed where the new volume lands. Model capacity per state, not in aggregate.
  • The surge is front-loaded. The first two weeks of January carry a disproportionate share of the month. Staff for the peak fortnight, not the monthly average, and use flexible per-review contracts to absorb the spike without carrying the cost structure into March.
  • Credentialing is the long pole. Recruiting a provider takes a conversation; licensing, credentialing, and protocol training take weeks. A provider signed in late September is a January asset. One signed in December is a February asset.

Support staffing and the macro library

Support volume scales with patient volume, but January support is also different in kind: more first-timers, more "where is my order," more pre-purchase questions from deliberating buyers. Two September moves:

Staff to a modeled ticket forecast. Tickets per hundred new patients is a number you already have; apply it to the January intake model and hire or contract against it in October so seasonal staff are trained by December, not learning live in week one.

Write the macro library now. Every question January will ask has already been asked by last January: shipping timelines, eligibility basics, pricing and refunds, lab and pharmacy status, dose and refill logistics. Draft the macros in October, have clinical review the ones that brush against medical territory, and wire them into your ticketing views so a seasonal agent resolves the routine 80 percent in one touch and escalates the rest cleanly.

One warning from experience: do not let surge staffing degrade safety triage. Escalation paths for symptom reports hold at any volume, and seasonal staff need that training most of all.


Pharmacy commitments: have the conversation in October

Your January is also your pharmacy partner's January, and every other program they serve is planning the same surge. The operators who get priority in the second week of January are the ones who shared forecasts in October.

The October agenda with each pharmacy partner: your monthly volume forecast with the January multiple made explicit, their capacity confirmation in writing, expected fill-time under surge load rather than the ordinary SLA, inventory posture on your core SKUs, and holiday-week schedules on both sides, because January 2 order volume lands on a fulfillment operation just returning from the holidays. If you run multi-pharmacy routing, agree on the failover thresholds now. And remember the surge echoes: January's new starts become February's first refills, so the commitment conversation covers Q1, not one month, with the refill mechanics from GLP-1 Refill Operations carrying the load.


Ad staging and the week-by-week calendar

December ad money is expensive and distracted: holiday retail owns the auctions and attention until the day after Christmas. The staging that works: spend October and November on creative testing while CPMs are ordinary, lock winners by mid-December, hold December spend modest, then ramp hard from December 26 when retail pressure exits the auction and resolution intent enters. Creative patterns that fit the category are cataloged in GLP-1 Telehealth Advertising in 2026; January-specific angles skew fresh-start and plan-oriented, and the compliance rules do not take holidays off.

The campaign calendar, week by week:

  • December 26-31: launch the New Year campaign, capture early movers, and open any early-commit or waitlist offer. Search volume starts climbing before the ball drops.
  • January 1-7: peak demand. Maximum budgets on proven creative, all capacity online, leadership watching queue dashboards daily. This week is about absorbing, not experimenting.
  • January 8-14: the second wave: deliberators who researched in week one come back to buy. Retargeting and email follow-up carry more weight than cold reach.
  • January 15-21: motivation wobbles. Shift messaging from "start" to "stick": program-support proof, real expectations, easy re-entry for abandoned intakes.
  • January 22-31: convert the long deliberators and pivot attention inward: the January cohort's onboarding experience is now your February retention number.

What breaks first, and how to load-test it

Two failure points claim most January casualties, and neither is the ad account.

The intake review queue. Volume in, fixed review capacity, and the queue compounds: a day of backlog becomes three by Friday. Patients who paid and then waited four days for review are your worst January reviews and your first February refunds. The dashboard metric is queue depth and age, watched daily, with a pre-agreed trigger for overflow capacity.

Lead response time. Speed-to-contact decides conversion on every lead that does not self-serve straight through checkout, and response time is exactly what collapses under volume. The evidence and targets are in Lead Response Time in Telehealth; the January question is whether your follow-up automation and staffing hold those targets at 4x lead volume.

Load-test both before December:

  1. Synthetic volume through staging: generate intake submissions at your modeled January peak and watch what queues, what times out, and which automations throttle.
  2. A game-day drill: one November day, run the surge on paper with the real team: here is Monday January 5's volume, walk every queue, name every owner, find the step where someone says "I'd just handle that manually." That step is your breakage.
  3. Fix, freeze, monitor: remediate in November, then freeze process and system changes in mid-December. January runs on the machine you have; the improvements you think of on January 3 go in the February list.

Programs on Turbopills get a head start here, the intake, routing, and queue infrastructure is built for spike loads, but the staffing model, the pharmacy commitments, and the drills are yours to run. Run them in September and October, and January stops being the month you survive and becomes the month you bank.


FAQ

Why is January the biggest month for telehealth programs? New Year resolution intent, new insurance plan years, and post-holiday health motivation all concentrate demand into early January, especially in weight loss and wellness categories. Established programs commonly plan for intake volume at 3-5x an ordinary month, with the peak front-loaded into the first two weeks.

When should a telehealth program start preparing for January demand? September. Provider recruiting, licensing, and credentialing take two to three months; pharmacy capacity commitments are negotiated in October; creative testing needs October and November data; and load testing has to happen in November so fixes land before a December change freeze.

What breaks first during a telehealth demand surge? The intake review queue and lead response time. Review backlogs compound daily once intake volume exceeds provider capacity, and follow-up speed collapses exactly when lead volume spikes, so both need explicit load tests, live dashboards, and pre-agreed overflow triggers before the surge arrives.

How do you load-test a telehealth funnel before January? Three layers: synthetic intake volume pushed through a staging environment at modeled peak load, a game-day drill where the real team walks a simulated surge day queue by queue, and a November remediation window followed by a December change freeze. The goal is to find the step someone would "just handle manually" before that step is handling four thousand patients.

More from Growth