A Launch Is an Operation, Not a Date
The calendar lies about launches. It shows a single circled date — the floor set, the site go-live, the first shipment to accounts — and hides the truth that the date is simply the moment an eight-week operation becomes visible. Everything the market will see on that day (the photography, the copy, the stocked shelves, the seeded reviews, the trained staff) was either built in the preceding weeks or it was not, and no heroics on the day itself substitute for the absent pieces.
The operational view also fixes the failure analysis. When a launch underperforms, the post-mortem that blames the product is usually wrong: the same bag, launched by a competitor with disciplined execution, sells through. The more useful post-mortem audits the operation — which checklist item was skipped, which was done late, which was done but unverified. Launches fail in the preparation ledger, not on the stage. This guide is that ledger, and its discipline compounds: the program that runs it fully once has a template for every launch after.
One boundary before the checklist: this guide covers the market-facing execution — the eight weeks from goods-ready to first-review. The upstream disciplines that feed it (the forecast and order quantities, the capacity booking that secured the production window, the buying calendar that chose the season) are covered in their own guides and are assumed here. The launch begins when the product is real; its job is to make the product real to the market.
The Launch Backward Chain
The launch backward chain anchors on the go-live date and works back through fixed-duration links: retail set or site live (day zero) minus staff training and merchandising (one week) minus inventory received, inspected, and allocated (two weeks) minus marketing assets final and loaded (three weeks) minus samples seeded and photography shot (five weeks) minus launch plan approved with quantities firmed (eight weeks). Each link has an owner and a definition of done; the chain is only as strong as its weakest verified link.
The chain below is the checklist's master table. Two disciplines make it real: every link carries a named owner (a launch with shared ownership has no ownership), and every link carries a written definition of done — not 'assets basically ready' but 'the forty SKUs have final copy, final photography, and final pricing loaded in the staging environment, verified by a second person.'
| Weeks Before Go-Live | The Link | Definition of Done |
|---|---|---|
| 8 | Launch plan approved | Quantities firmed by SKU and channel, pricing signed, the calendar on one page |
| 5 | Samples seeded, photography shot | Seed units shipped with the tracking list; the shot list executed and selects retouched |
| 3 | Assets final and loaded | Copy, photography, pricing, and specs loaded in every channel's staging area |
| 2 | Inventory received and allocated | Goods through receiving inspection, allocated to channels, pick-ready |
| 1 | Training and merchandising | Staff sheets distributed, retail displays staged, the site in final review |
| 0 | Go-live | The rehearsed day: orders flow, stock holds, the war-room chat is quiet |
The Asset Package
The asset package is everything the market will touch that is not the bag itself, and it is the link most often started late because it feels like marketing rather than operations. The complete package for a golf bag launch: the photography set (studio white-background for every SKU and colorway, the three-quarter hero, the detail crops of the features the copy will claim, and the lifestyle set that carries the brand's tone), the copy set (the hundred-word short description, the four-hundred-word long description, the feature bullets in descending order of what golfers actually ask about, and the specification table — weight, dimensions, divider layout, pocket count, materials), the pricing sheet (retail, MAP where applicable, opening-offer terms, and the channel-specific variants), and the sell-in kit for accounts (the one-page talking-points sheet and display guidance from the onboarding discipline).
The asset package's scheduling rule: photography cannot wait for bulk goods, because bulk goods arrive at week two of the chain. The seed units — the production-line samples pulled at final inspection — are the photography subjects, which is why the shot list is written at week eight and the studio is booked at week five. A launch whose photography starts when the container docks is a launch whose assets load at week one, and the chain shows what that costs: the training and merchandising week becomes the assets week, and something reaches the market unfinished.
The verification habit that separates the smooth launches: the asset audit at week three, where one person who did not build the package opens every channel's staging area and checks every SKU against the master list. The audit catches the missing colorway image, the spec table that still shows the prototype's pocket count, the price that was updated in the sheet but not in the system. Caught at week three, these cost an afternoon; caught by a customer on day one, they cost trust and a support ticket.
Inventory Positioning for Day One
Day-one inventory is a geometry problem: the right units in the right places before the date, with enough depth to survive the opening week's concentrated demand. The positioning math starts from the launch forecast — the forecasting discipline produces the number; this section positions it. The rules: the launch allocation is sized to the first thirty days, not the season (the replenishment cycle handles the season; the launch stock handles the spike), the allocation respects the channel's geometry (e-commerce depth in the warehouse, retail breadth across doors — the same units do different work in different places), and the safety stock sits where it can actually rescue a stockout (a reserve pallet in the home warehouse, not split into unusable slivers across channels).
The positioning timeline binds the chain's week-two link: goods clear receiving inspection, move to allocated, pick-ready positions, and the channel shipments to retail doors leave with enough transit buffer to arrive before the training week, not during it. The launch whose stock arrives at retail on go-live day is merchandised by whoever is free, from a pallet, under time pressure — and the photography shows it for the rest of the season.
The honest constraint that shapes every positioning decision: launch demand is the least predictable demand in the product's life. The positioning answer is not more stock — it is optionality: the reserve pallet, the replenishment trigger pre-agreed with the factory (the second PO quantity already discussed, ready to release), and the allocation software discipline that lets mid-week rebalancing happen from data rather than from panic.
Channel Allocation at Launch
Channel allocation decides who gets to sell the launch, on what terms, in what order — and it is decided at week eight, not negotiated at week one. The allocation framework: the direct channel (the brand's own site) carries the full range and the deepest storytelling, the retail accounts carry the edited range their floor space earns (the account onboarding kit tailored to the launch), and any marketplace presence is deliberate, priced to the channel map, and stocked thin enough that it never becomes the price leader the other channels must answer to.
The exclusivity question arrives at every launch: an account wants the launch, or a colorway, exclusively. The answer follows the channel conflict discipline — exclusivity is a currency spent deliberately, priced in volume commitments and merchandising support, never given as a favor. The launch-time variant that usually works: a time-boxed exclusive (thirty to sixty days on a specific colorway) that gives the account its story and returns the SKU to the full channel map before the season's peak.
The allocation table that belongs in the week-eight plan: for each channel, the SKUs it carries, the depth it receives, the pricing it honors, the assets it displays, and the date it goes live. When the table is written and agreed, launch week has no allocation surprises; when it lives in someone's head, launch week is a series of small betrayals that accounts remember into the next season.
The Sample Seeding Plan
Seeded samples are the launch's advance guard: the units placed, before go-live, with the people whose opinions and content will shape the first thirty days. The seeding list for a golf bag launch has five tiers, in descending order of certainty: the retail buyers and floor staff who must know the product physically before they can sell it (the demo units from the onboarding program, arriving with the talking-points sheet), the teaching professionals and club fitters whose bag endorsement is the category's most credible, the reviewers and content creators whose timelines need four to six weeks of actual use before publication, the team or ambassador players if the program has them, and a small reserve of units held back for the opportunities the list did not predict.
The seeding economics: seeded units are marketing spend, and the spend is tracked like any other — a list, a cost, an expected return, and a review. The seeding plan at week five records each unit's recipient, purpose, and the follow-up date. The follow-up is the discipline most seeding programs skip: the unit shipped is not the asset; the review published, the floor staff trained, the buyer's reorder — those are the assets, and they only happen if someone owns the follow-up.
The seeding trap to refuse: the unlimited list. Every additional seed unit feels cheap (a bag at cost) and is expensive (a bag not sold, plus the follow-up bandwidth it demands). The launch that seeds twenty units with twenty follow-ups outperforms the launch that seeds sixty units with none.
Pricing and the Opening Offer
Launch pricing sets the reference point the market will remember all season, which is why the pricing decision belongs to week eight and not to launch-week enthusiasm. The pricing architecture: the list price (set against the value story and the competitive price bands, because the market will position the bag against the band whether the brand does or not), the MAP floor where the program enforces one, and the opening offer — if any — designed as a bounded event with a stated end date, never as an unbounded discount that becomes the price.
The opening-offer options, in ascending order of margin cost: the bundle (the bag with a headcover set or accessory at a combined price — value added rather than price cut, and the bundle economics show why the attach is worth more than the discount), the gift-with-purchase (a bounded-cost item that photographs well and disappears on schedule), the early-buyer incentive (a limited-quantity offer that rewards speed and self-terminates), and the straight discount (the bluntest instrument, reserved for the launches that genuinely need it and bounded hard).
The discipline that protects the season: the opening offer's end date is in the week-eight plan, on the calendar, owned by someone who will enforce it. The offer that quietly extends becomes the reference price, the MAP floor erodes to meet it, and the autumn margin is spent in April.
Launch Week Execution
Launch week is a rehearsed week, and the rehearsal is the week-one link: every system tested with real transactions before the audience arrives. The rehearsal checklist: the site processes a test order end-to-end through payment and fulfillment, the retail doors have their displays staged and their staff sheet in hand, the customer-service team has the FAQ document (the twenty questions the first week will actually ask — sizing, weight, divider configuration, shipping times, returns), and the war-room channel exists (one chat where the launch team reports, in real time, anything unexpected).
The launch-week rhythm that works: a daily fifteen-minute stand-up on the dashboard — orders against forecast, stock position by channel, the support-ticket themes, and any press or social pickup worth amplifying. The stand-up exists to catch the small failures while they are small: the SKU image showing the wrong colorway (fixed in an hour on day one, screenshotted forever by day three), the shipping-promise text that contradicts the checkout logic, the retail door that never received its allocation and was too polite to ask.
What the launch team does not do during launch week: improvise strategy. Price changes, allocation changes, and offer extensions made mid-week, under adrenaline, are the decisions the post-launch review regrets. The week's job is execution and observation; the decisions belong to the first-thirty-days review, where the data has had time to mean something.
The First Thirty Days of Data
The first thirty days produce the launch's verdict, and the data discipline is deciding at week eight which numbers will deliver it. The launch dashboard, agreed before go-live: sell-through against the launch allocation (the headline number — the percentage of the thirty-day allocation actually sold, read weekly), the channel mix (is the shape of demand matching the allocation geometry, or is one channel starving while another sits), the SKU mix within the launch (which colorways and configurations are leading — the signal for the replenishment PO's mix), the return rate and its reasons (the early warning for a product or copy problem — returns citing 'smaller than expected' mean the photography lies; returns citing a component mean the component lies), and the support-ticket themes (the unfiltered voice of the confused customer, which is the market's most honest feedback).
The reading discipline: weekly, against pre-written thresholds. The thresholds, set at week eight when nobody is emotionally invested: the sell-through number that triggers the replenishment PO (the second production window, if the capacity booking reserved one, released now with the mix adjusted to the data), the number that triggers the mid-course marketing push, and the number that triggers the honest underperformance conversation — all three written down before the first order arrives.
The Post-Launch Review
The post-launch review, held at day thirty to forty-five, is the checklist's compounding mechanism: the hour that converts one launch's experience into every future launch's template. The agenda is four questions, answered with the dashboard and the calendar: what sold versus plan (by SKU and channel, with the honest why), what executed versus plan (which chain links held their dates and definitions of done, which slipped, and what the slip cost), what the market said (returns reasons, ticket themes, review content, the accounts' read), and what changes in the template (three improvements, assigned and dated — the same three-improvement rule as every drill and review in this library).
The review's hardest habit: separating the product verdict from the execution verdict. A launch that missed its number because the chain broke at week three is a different problem from a launch that executed perfectly and still missed — the first calls for a process fix, the second for a product or positioning conversation, and confusing them produces the wrong fix. The review that ends with clear separation has done its job; the template updates, the next launch inherits the improvements, and the checklist grows teeth.
When the Launch Underperforms
Underperformance is a launch outcome, not a launch verdict, and the response menu is written before it is needed. The diagnostic first: is the miss an awareness miss (traffic and door counts below plan — the marketing and seeding failed to deliver the audience), a conversion miss (traffic arrived, purchases did not — the price, the offer, or the product-page truthfulness is the suspect), or a product miss (purchases happened, returns and reviews say the product disappointed — the hardest and most honest category).
The response ladder, matched to the diagnosis: awareness misses get the mid-course marketing push (the assets exist; the spend moves), conversion misses get the bounded offer (the bounded instruments from the pricing section, deployed deliberately with the same end-date discipline), and product misses get the honest program response (the feedback to the factory and the spec, the copy corrected where it overpromised, and the pricing decision made against the full-season margin math rather than against pride). What none of the three gets: the unbounded panic discount, which converts a thirty-day problem into a season-long price-position wound.
The compounding view: every program launches products that underperform; the mature programs are not the ones that never miss but the ones whose misses are diagnosed honestly, responded to deliberately, and converted into template improvements. The checklist holds no grudges — it holds the lessons.
A Launch Executed, Worked
A worked launch from a mid-size program's spring line, told against the chain. Week eight: the plan approved — three new stand-bag SKUs in five colorways, 2,400 units of launch allocation split 60/25/15 across direct, retail, and marketplace, pricing signed, the replenishment trigger set at sixty-five percent sell-through by day twenty-one. Week five: seed units shipped — twelve to retail accounts' floor staff, four to reviewers with six-week lead times, two to the teaching-pro ambassadors; the studio shot the full range from the same seed units in two days. Week three: assets loaded; the audit caught two colorway images swapped and a spec table showing the prototype's nine-inch top instead of the production ten-inch — fixed in an afternoon. Week two: goods cleared receiving inspection, allocated, pick-ready; retail shipments left with a week of transit buffer. Week one: training sheets out, displays staged, the test order processed cleanly. Go-live: quiet. The dashboard at day seven showed sell-through at twenty-two percent, on plan; day fourteen, forty-eight percent, with the navy colorway running double its forecast share; day twenty-one, sixty-eight percent — the trigger fired, the replenishment PO released with the navy mix raised from twenty to thirty-five percent. Day thirty: seventy-nine percent sell-through, return rate 1.1 percent against a two percent budget, zero pricing moves made. The review produced three template improvements: seed units ship at week six not five (the reviewers wanted more lead time), the spec-table audit gains a second checker, and the reserve pallet is formalized at fifteen percent of launch allocation. Total drama: none. Total cost of the discipline: eight weeks of owned calendar. The next launch inherits all of it.
Frequently Asked Questions
How far ahead should launch planning start?
The market-facing checklist needs eight weeks from goods-ready to go-live; the plan itself (quantities, pricing, channel allocation) belongs to week eight of that chain. Upstream of it, the production capacity and the purchase order were settled months earlier — the launch checklist assumes the product is real and makes it real to the market.
What belongs in the launch asset package?
Four sets: photography (white-background for every SKU and colorway, hero shots, detail crops, lifestyle set), copy (short and long descriptions, feature bullets in the order golfers ask about them, the specification table), the pricing sheet (retail, MAP, opening-offer terms), and the sell-in kit for accounts (talking points and display guidance). All of it verified by the week-three asset audit.
How much inventory should a launch hold?
Size the launch allocation to the first thirty days, not the season — the replenishment cycle handles the season. Position it to match channel geometry (warehouse depth for e-commerce, breadth across retail doors), hold a reserve pallet of roughly ten to fifteen percent in the home warehouse, and pre-agree the replenishment trigger with the factory so a strong launch can be chased.
Should we offer an exclusive to a retail account at launch?
Exclusivity is a currency, spent deliberately: price it in volume commitments and merchandising support, never give it as a favor. The launch-time variant that usually works is a time-boxed exclusive — thirty to sixty days on a specific colorway — which gives the account its story and returns the SKU to the full channel map before peak season.
How many samples should we seed, and to whom?
A working number is fifteen to twenty-five units across five tiers: retail floor staff (demo units with talking points), teaching professionals and fitters, reviewers with four-to-six-week lead times, ambassadors, and a small reserve for unpredicted opportunities. Every unit gets a named recipient, a purpose, and a follow-up date — the follow-up, not the shipment, is the asset.
Is an opening discount a good idea?
Only as a bounded event with a stated end date on the calendar. Prefer value-added structures — the bundle, the gift-with-purchase, the limited-quantity early-buyer incentive — over straight discounts. An offer that quietly extends becomes the reference price, erodes the MAP floor, and spends the autumn margin in spring.
What should we measure in the first thirty days?
Five numbers agreed before go-live: sell-through against the launch allocation read weekly, channel mix against the allocation geometry, SKU and colorway mix (the replenishment PO's guide), return rate with reasons (the early warning for product or copy problems), and support-ticket themes. Each number gets a pre-written action threshold so launch-week adrenaline makes no pricing decisions.
When should the replenishment PO be released?
At the trigger written at week eight — a common working threshold is sixty to seventy percent sell-through of the thirty-day allocation by day twenty-one, with the mix adjusted to the actual colorway data. The capacity booking that reserved the second production window is what makes the trigger actionable; without the window, the trigger is a wish.
What if the launch misses its numbers?
Diagnose before responding: an awareness miss (no traffic) gets the mid-course marketing push, a conversion miss (traffic without purchases) gets a bounded offer, a product miss (purchases followed by returns and poor reviews) gets the honest program response — feedback to the spec, corrected copy, and pricing decided against full-season margin math. None of the three gets the unbounded panic discount.
What does the post-launch review cover?
Four questions at day thirty to forty-five: what sold versus plan and why, which chain links held their dates and definitions of done, what the market said (returns reasons, ticket themes, reviews), and three improvements to the launch template — assigned and dated. The review's hardest habit is separating the product verdict from the execution verdict, because they call for different fixes.
Who should own the launch?
One owner for the operation, with each chain link carrying its own named owner and written definition of done. A launch with shared ownership has no ownership; the week-eight plan names everyone before the clock starts.
Does this checklist apply to a small first-time launch?
Yes, scaled down but not thinned: the chain links are the same, the definitions of done are the same, and the review is the same — only the quantities and the seeding list shrink. A first launch run on the full checklist becomes the template for every launch after it, which is the cheapest operations education a program can buy.