Top of funnel
Launches that produce a decision, not a report.
A launch has no history to compare against, which every other program on this site assumes. The first ninety days are spent establishing that baseline, with three decision gates — weeks four, eight, and twelve — deciding what continues, what changes, and what stops.
Every other program on this site can point to a history: last quarter's cost per booked outcome, last year's seasonal pattern, an established baseline to beat or defend. A launch has none of that. There is no comparable number for a location that has never taken a booking or a service line that has never had a customer, which means the first ninety days cannot be spent trying to beat a number that does not exist yet — they have to be spent establishing one.
That changes the order operations happen in. Instrumentation — call tracking, form tracking, CRM fields for the new location or line — goes in before the first dollar of spend, with enough lead time that the first report already has something real behind it. And the plan is structured around three specific checkpoints, so "how is the launch going" has a scheduled, criteria-based answer on a fixed calendar.
How the work differs
- Instrumentation-first setup
- Tracking, tagging, and CRM fields for the new location or line installed and verified before any spend goes live.
- Baseline-quarter framing
- The first ninety days treated explicitly as the period that establishes a baseline, judged against criteria agreed before launch.
- Decision gates
- Checkpoints at weeks four, eight, and twelve, each with criteria agreed before launch for continuing, changing, or stopping a specific channel or the launch itself.
- Multi-channel sequencing
- Channels launched in a deliberate, staggered sequence, so an early result can be traced to a specific channel.
- New-location versus new-line criteria
- Separate baseline assumptions and gate criteria set for a new physical location versus a new service line, since one has comparable geography and the other does not.
Weeks one through twelve
Weeks one through three: instrumentation goes live and gets verified against test transactions before real spend starts, and channels begin launching in their planned, staggered sequence. Week four: the first gate, checking that tracking is capturing what it should and that no channel is obviously broken — this is a data-quality checkpoint more than a performance one, since volume this early rarely supports a confident performance read.
Weeks five through seven: spend continues across the sequenced channels, and enough volume starts accumulating for a first real look at channel-level cost per booked outcome. Week eight: the second gate, where underperforming channels get restructured or cut and budget moves toward what the data actually supports, using the same criteria agreed before launch.
Weeks nine through eleven: the surviving channel mix runs at its adjusted allocation, building the sample the week-twelve gate needs. Week twelve: the launch as a whole is judged against its original criteria — continue into standard ongoing management, extend the baseline period if volume fell short of what the criteria required, or stop and redirect the budget if the criteria were not met.
How it is measured
There is no prior period to compare this quarter against, so the first ninety days measure against the criteria set before launch — the substitute for a history this program does not have yet. Once baseline volume exists, the same booking-intent-scored conversion standard used across every other channel applies, matched through the attribution layer from the first tracked click or call onward.
What this channel cannot claim credit for: performance in month four and beyond, which belongs to whichever ongoing program — paid search, paid social, SEO — the launch graduates into once its own ninety days are complete. This page's job ends at week twelve, by design.
Who this is for
Built for operators opening a new location or introducing a new service line who need the first quarter to produce a real, criteria-based decision by week twelve, part of the top-of-funnel lineup — self-storage operators opening a new facility are a common case, since a facility with no booking history needs its baseline established before anyone can say whether its marketing is actually working. The channels sequenced into a launch are typically paid search first, with creative concepted and tested through creative ads strategy as the launch matures past its first gate. Client results show a finished ninety-day launch framework and the decisions made at each gate.
The week-four gate gives a first real signal, but it is deliberately a narrow one — enough to confirm instrumentation is capturing what it should and to catch an obviously broken channel early. The week-eight gate is where a genuine read on channel-level performance becomes possible, and week twelve is where the launch as a whole gets judged against the criteria set before it started. Expecting a confident answer before week four is asking the data to say something it does not have enough volume to support yet.
The criteria for that judgment are agreed before launch, specifically so the question does not get argued after the fact based on whichever number looks worst. A launch that misses its week-twelve criteria gets one of three responses decided in advance: extend the baseline period if volume was the constraint, restructure specific underperforming channels while keeping others, or stop and redirect the budget entirely. Which response applies is written into the plan before spend starts, not improvised afterward.
Enough to reach a meaningful sample on at least two channels by the week-eight gate, which varies by market and category. Below that level, the ninety-day structure still applies, but the honest expectation is a longer baseline period rather than a compressed one, since the gates are tied to data volume rather than to the calendar.
Yes, in what the baseline is being compared against. A new location competes in a market with known demand and known competitors, so early signal can be sanity-checked against comparable existing locations. A new service line has no internal comparable at all, so the week-four and week-eight gates lean more heavily on qualitative signal — call quality, inquiry relevance — since the volume needed for a purely quantitative read takes longer to accumulate for something genuinely new.
Someone with authority to approve a mid-launch channel change without a full committee review, since a week-eight decision made three weeks later than planned wastes exactly the time the gate structure exists to protect. Whoever handles inbound calls or leads for the new location or line also needs to be looped in before launch, since instrumentation on their end has to be verified working before spend starts, not discovered broken at the week-four gate.
Plan a launch with the decision gates built in from day one.
A ninety-day launch framework for one new location or service line, with instrumentation, sequencing, and decision criteria set before the first dollar spends.