The short version: a product launch is a sequence with five beats spread across roughly two weeks: the tease (curiosity, no link), the early-access window (the list's structural reward), launch day (the announcement done once, well), the proof follow-up (first reviews and social evidence, three to five days later), and the flow handoff (the new SKU wired into welcome, cross-sell, and browse logic so the launch keeps selling after the campaign ends). Launches are also the calendar's best non-price promotional energy, per the promo cadence rules: novelty creates urgency that no discount has to subsidize. This post is the five beats in full, the two variants (the preorder build and the constrained drop), two worked launches, and the failure modes that turn a launch into a spike-and-silence.
Beat 1: the tease, 5 to 7 days out
One email, curiosity-shaped: the silhouette, the problem it solves, the date, and the early-access invitation (get it first Thursday). No product page link because there is nothing to buy, and the absence is the point: the tease's job is priming and the early-access opt-in, which doubles as an intent segment for launch day. The tease's mechanics matter more than its cleverness: the opt-in should be a single click that writes a profile property (interested-in-launch-X), because that property is launch day's best audience and the honest measure of whether the tease worked. For drop-culture brands this beat carries the whole scarcity frame (quantity honesty included); for education-led categories (supplements per the calendar) the tease is the mechanism story with the product as its payoff; for considered categories the tease stretches earlier and doubles as the craft story, per the wait-content logic applied pre-sale.
Beat 2: early access, 12 to 24 hours before public
The list buys before anyone else, framed as the standing privilege of being on the list: this is the access offer from the offer framework doing its structural work, teaching that the email list is where advantages live (the lesson that compounds into every future signup). Send to the engaged segment plus the tease's hand-raisers; SMS earns a slot here for the hand-raisers specifically, per the time-sensitive-moment rule. For genuinely constrained inventory, early access is also the fairness mechanism: the people who asked get first claim, the same queue ethics as the waitlist build, and saying the queue logic out loud (hand-raisers first, then the list, then public) converts scarcity from frustration into privilege. The window length is a real decision: 12 to 24 hours keeps urgency honest; a 72-hour early access is just a soft launch that trains nobody.
Beat 3: launch day
The announcement, sent once to the full engaged list (suppressing early-access purchasers, who instead get their order confirmed like the insiders they are): the product, the why-it-exists story, the strongest single differentiator, the price stated plainly, one CTA. The copy structure that consistently works: the problem in one sentence, the product as its answer in two, the one spec or ingredient or design choice that proves you did it differently, the price without apology, the button. Resist the double-send-day temptation; the fast-follow reminder lands with beat four's proof instead, because a same-day re-send to non-openers is the promo-pressure pattern the frequency guardrails exist to stop, and post-MPP the non-opener segment is polluted anyway per the open-inflation problem.
Beat 4: the proof follow-up, day 3 to 5
The second full-list touch, and the one most launch calendars skip: the first reviews, the UGC from early-access buyers, the press or creator mentions, the selling-fast truth where true. This is the send that converts the considered majority who never buy on day one, and it is why the post-purchase review engine gets pointed at launch buyers immediately: a same-week review ask to early-access customers (who are your warmest fans by self-selection) reliably produces the proof this beat needs. If reviews genuinely have not landed yet, the beat still runs on what exists: the founder's why-we-built-it, the development story, the first customer photos, restock timing if the first run moved. The one version that fails is the bare reminder: still available is not a reason to open an email.
Beat 5: the flow handoff
The launch ends when the flows absorb the SKU: the welcome flow's product paths updated where the new item serves a goal, the cross-sell maps extended with its genuine pairings, browse abandonment inheriting it automatically, the back-in-stock flow armed for the first sellout, and for consumables the replenishment clock configured with the new SKU's days-of-supply math before the first orders even deliver. The handoff has a checklist shape on purpose (five systems, one pass, thirty minutes) and it is the difference between the two revenue curves: a launch without the handoff spikes and dies; with it, the campaign two weeks become the flow-powered forever.
Variant one: the preorder launch
When the product is real but not shippable, the sequence stretches: the tease becomes a short series (the problem, the build, the date), early access becomes the preorder window itself (the list reserves before public preorder opens), and a new beat appears between order and delivery: the production update cadence, borrowed directly from the considered-purchase wait arc, because a preorder customer is a wait-arc customer regardless of category. The proof beat splits in two: social proof at preorder (demand evidence: units reserved, the waitlist count) and product proof at delivery (the first real reviews), and the second one matters more: preorder programs die on the gap between ordering excitement and delivery silence.
Variant two: the constrained drop
When inventory is genuinely scarce, the sequence compresses and the fairness mechanics take over: the tease carries the quantity truth, early access becomes the drop itself for the priority tier, and the public announcement may be a sold-out announcement with the waitlist as its CTA, which sounds like failure and is actually the flywheel: back-in-stock notifications convert at 7.9% on email and 8.5% on SMS, so a drop that sells out into a well-run waitlist converts its own scarcity into the next drop's guaranteed first hour. The discipline: quantity honesty always (fake scarcity is instantly legible to drop audiences), batch notifications sized to stock, and the restock tease the day before per the waitlist build's warm-up pattern.
Worked launch one: a supplement SKU
New magnesium complex, evergreen brand, two-per-week baseline cadence. Day minus 6: tease (the sleep-architecture mechanism story, no link, one-tap interested button). Day minus 1, 6pm: early access to hand-raisers plus engaged 90-day segment, subscription option beside one-time from the first minute. Day 0, 9am: launch to full engaged list, goal-segmented (the sleep-goal cohort gets the deep version; everyone else the standard). Day 4: proof beat (first 12 reviews, two customer quotes, the founder's dosing note), plus the review ask already running to early-access buyers. Day 7 to 10: handoff pass: welcome flow's sleep path updated, stacking map adds the magnesium-plus-sleep-formula pairing, replenishment clock set at 24 days on the 30-day bottle. Calendar accounting: the launch consumed that fortnight's product slots; value and community slots ran normally, per the four-job ratio.
Worked launch two: an apparel drop
Limited jacket run, drop-culture brand, no discounts ever. Day minus 5: tease with silhouette and the honest number (300 made), one-tap notify-me. Day minus 1: SMS plus email to notify-list only: your window opens at 10am tomorrow, one hour before public. Day 0, 10am: notify-list window; 11am: public announcement; 2pm: sold-out announcement to non-purchasers with the waitlist CTA, which converts frustration into the next cycle's demand. Day 3: proof beat as a lookbook: the drop on real customers, the waitlist reminder, the next-drop teaser date. Handoff: back-in-stock armed for returns-driven restocks, the size-out patterns feeding the next run's size curve, and the fit-check data from the post-purchase build closing the loop to production.
Segment and calendar mechanics
- The launch takes over the monthly theme, per the calendar SOP: the month's value slots feed it (the ingredient story before, the how-to-use after) rather than competing with it.
- Vertical properties sharpen every beat: the goal, concern, species, and room properties turn the launch into its relevant version per segment, and a niche product launches to its niche plus a soft-tease to everyone else.
- Existing-customer framing beats stranger framing: owners of the adjacent product get the pairing angle (your X now has its Y), the highest-converting launch audience in most accounts.
- Frequency accounting: launch beats count against the weekly cadence; the rotation's product slots become the launch beats rather than stacking on top, and the launch fortnight still respects the guardrails.
The failure modes
- The announcement-only launch: one email on launch day, no tease, no proof beat. It captures the day-one buyers who would have found it anyway and leaves the considered majority unconverted.
- The discounted launch: teaching the list that new things go on sale immediately, the single worst pricing lesson available, and a waste of the one moment when novelty makes urgency free.
- The skipped handoff: the spike-and-silence curve, diagnosed weeks later as the product failing when the plumbing simply never absorbed it.
- The stacked calendar: launch beats added on top of the normal cadence instead of replacing product slots, tripping the frequency guardrails in the exact week engagement matters most.
- The extended early access: a window that quietly never closes, converting the access offer into a soft discount on urgency itself.
What to measure
- Revenue by beat, expecting early access plus launch day to carry the spike and the proof follow-up to add a meaningful second wave; a dead beat four means the proof pipeline was not ready
- Early-access share of launch-week revenue, the structural-reward metric that justifies the beat and prices the list's privilege honestly
- Hand-raiser conversion (tease opt-ins who purchased), the priming test, and hand-raiser count itself as the pre-launch demand forecast
- Week-eight run rate versus launch week, the handoff test: a healthy launch settles into flow-sustained sales rather than a spike and silence
- List growth during launch windows: launches with public buzz should show signup bumps, and the notify-me capture is the drop variant's list-growth engine
Frequently asked questions
How many emails should a product launch include?
Five beats over roughly two weeks: tease, early access, launch day, proof follow-up, and the flow handoff, with the beats occupying the calendar's product slots rather than stacking on the normal cadence.
Should the list get early access?
Yes, structurally: it converts the warmest audience first, creates fair queues for constrained inventory, and teaches that the list is where advantages live, the access lesson that compounds into signups. Keep the window to 12 to 24 hours so the privilege stays sharp.
Do launches need a discount?
No: novelty is the urgency. A launch discount teaches the worst possible lesson (new things go on sale immediately) and burns the non-price promotional energy launches exist to provide.
What makes launch revenue last past the spike?
The flow handoff: the SKU wired into welcome paths, cross-sell maps, browse abandonment, the back-in-stock arm, and the replenishment clock for consumables. Campaigns spike; flows sustain.
How does a preorder launch differ?
The sequence stretches: early access becomes the reservation window, and a production-update cadence fills the gap between order and delivery, because preorder programs die on delivery-wait silence, not on demand.
When does the second launch email go out?
Day three to five, carrying proof (first reviews, UGC, honest stock truth) rather than a bare reminder. It converts the considered majority who never buy on announcement day.
Sources
- Klaviyo. Email marketing benchmarks.
- Klaviyo. Back-in-stock notification data.
- Omnisend. Email marketing frequency guidance.
- Mailflow Authority. Apple Mail Privacy Protection and measurement.