The 30-Day Runway: What Has to Happen Before a Launch Event

The first question almost every clinic owner asks is some version of "how soon can we do this?" The honest answer disappoints people, and it is the single most useful thing we tell them: the event date is the last thing you pick, not the first.

A launch event is the visible part. What fills it is a four-week runway of infrastructure work that happens before a single patient hears from you. Two of those four weeks are consumed by processes that no amount of money or urgency can accelerate, because they are controlled by mobile carriers and messaging platforms rather than by your clinic. Compress the runway and you do not get a faster event. You get an event with an empty consult schedule and a patient list you have damaged for the next twelve months.

Here is what actually has to happen, in order, and what breaks when it does not.

The Two Long Poles Start on Day One

Everything else on the runway is schedulable. These two are not, so they start immediately and run in the background while the rest of the build happens around them.

Carrier registration. Business text messaging in the United States on standard ten-digit phone numbers runs through a registration system. Brands and campaigns are verified before they are allowed to send, and as The Campaign Registry describes it, clinics do not register themselves. They register through their messaging service provider, who submits the business details and the campaign use case on their behalf. In our own launches, that review has typically taken seven to fourteen days. A denial and resubmission pushes it past three weeks. Nothing sends before it clears, so it goes in on day one or two, every time.

Message volume warming. This is the one nobody sees coming. Messaging platforms cap brand-new sending accounts at a low daily volume and raise the cap in stages. Each increase requires the account to actually use its current allowance, then sit through a pause while the increase processes. In the platform we build on, that pause is twenty-four hours per level, and there is no manual override at any support tier. An account created the week of the launch is an account that can send roughly a hundred messages on launch day.

The good news is that these two run in parallel. Warming traffic is internal test messaging, not commercial outreach, so it does not wait on the carrier registration to finish. Running them simultaneously instead of sequentially is the difference between a three-week runway and a six-week one.

The Four-Week Map

Written as a countdown from launch day, which is itself two to four weeks before the event:

T-4 weeks. Intake and onboarding. The sending account gets created, phone numbers get purchased, the campaign registration goes in, and the practice website goes live if it is not already. That last item is not decoration. A live, legitimate business website is part of what gets reviewed during carrier registration, and a thin or missing site is a common cause of denial.

T-3 weeks. Warming begins in earnest and the account climbs its first level. In parallel, the clinic-specific configuration gets built: pricing, package structures, calendar with real event dates and deposit amounts, payment links, consult scripts, and the reminder sequences. This is also when we settle the event week structure, which we will come back to.

T-2 weeks. Warming continues climbing. The patient list arrives and gets cleaned, which is a bigger job than most owners expect. Records without a phone number come out. Records without a first name come out, because the messages open with one. Invalid number formats, previously opted-out contacts, patients who are already booked, and patients who already own a package all come out, each with a documented reason kept for the record. A dirty list inflates error rates and opt-out rates in ways that follow you for the rest of the campaign.

T-1 week. Final warming level. Full quality assurance: the complete happy path tested live on a registered number, plus the failure paths, plus verification that every payment product and pipeline reference actually resolves. This is the one step on the runway that cannot be parallelized. It blocks launch, and it is where broken payment links and stale automation references get caught. Finding them here costs an afternoon. Finding them during a live campaign costs bookings.

Launch day. Contacts get created without the tags that trigger outreach, then get enrolled in controlled batches with deliberate spacing between them. A small test batch goes first and gets verified end to end before anything else moves. Sudden volume spikes from new numbers are exactly what carrier filtering is built to catch.

What Compression Actually Costs

The failure mode is not "the event happens a bit worse." It is a cascade, and we have watched it run.

On an under-warmed account, the daily cap is hit within seconds of the sending window opening. Most of day one's messages fail. So far that is just a delay. The problem is what happens next: the platform attaches its required opt-out language on the first send attempt per contact, not the first successful delivery. Every contact whose first attempt died at the cap has already burned that slot. When they later receive a message that does go through, it arrives without the opt-out line. Recipients who cannot see a soft way out reach for the hard opt-out keyword instead, and that is the exact metric platforms and carriers score you on.

On one under-warmed launch we ran in spring 2026, the analytics showed more failed sends than total sends, a ratio that is impossible on a clean account and is pure cap-hit noise. Combined opt-outs on that campaign landed around seven percent, split between roughly 1.7 percent hard opt-outs and the rest soft declines. Our working targets are under two percent hard and under four percent combined. Sustained hard opt-outs above two percent got the account temporarily restricted from bulk and automated messaging entirely, mid-campaign, with the event nine days out.

None of that was a copy problem. The messages were fine. The runway was short. That is the whole lesson, and it is why we will not schedule an event date before the runway is committed. Outcomes vary by list size, market, and database quality, but the direction of this failure is consistent.

Then There Is the Event Week Itself

Three structural decisions get made during the runway, not during the event.

Training and selling are different days. Blending them serves neither. The training day is open, unhurried, and full-access for the clinic team. The sales days are locked down, because on those days we are closing patients, not teaching staff.

Weekdays beat Saturday. For most clinic patient bases we have worked with, Saturday converts worse. We concentrate consults Wednesday through Friday and use Saturday as a training day or a low-volume overflow day. This one varies by market, so it gets decided against the actual database.

Owner observation is capped. Clinic owners want to sit in on every close, and it is a reasonable instinct. It is also a sales risk. We reserve a small fixed number of observation slots across the entire weekend and keep the rest closed-door, because a well-meaning interruption from the owner during a close has cost confirmed buyers. That cap gets explained during the runway, in writing, so event week is not the first time anyone hears it.

What to Tell a Clinic Owner

Three weeks minimum from account setup to outreach launch, four to be safe. Event two to four weeks after launch. Five to eight weeks from commitment to patients in chairs. Anyone promising a launch next week is either skipping the carrier registration, skipping the warming, or has not run one of these before.

The runway is not overhead. It is the thing that decides whether the calendar fills. If you want the downstream mechanics, we have written about how the consult calendar actually gets filled, what happens on event day itself, and why the email half of the outreach lands in Promotions when the same signals get ignored.