Why an annual SOSTAC plan does not fit a launch
The standard SOSTAC plan covers a year and assumes a steady business: the situation describes a market the company already sells into, the objectives are reviewed monthly, and slippage in one tactic can be absorbed by another. A launch removes that slack. There is one public moment, many teams outside marketing must be ready at the same time, and the first weeks of evidence decide whether the product gets further investment. The plan has to manage a dependency chain as much as a market, and the sections most teams treat as administration, who does what and how progress is checked, are where launches actually fail. The product launches hub sets out launches as a repeatable process; the decisions below translate that process into SOSTAC's sections.
Decisions that change for a launch
| SOSTAC section | In a generic plan | In a launch plan | Decision it forces |
|---|---|---|---|
| Situation | Market, customers, competitors, past results | The same, plus a readiness audit across product, support, sales and stock | Who signs each readiness line and what counts as ready |
| Objectives | Annual outcomes with a date | Launch-window targets and separate post-launch adoption targets | Which window each target is measured over |
| Strategy | Segments, positioning, channel weight | A launch tier, a positioning statement and the sequence of audiences | How big the launch is and who hears first |
| Tactics | Channel detail for the year | Three phases, pre-launch, launch and sustain, each with its own mix | Which channels carry each phase and when spend shifts |
| Action | Owners and dates | A dated run-of-show and a single go or no-go owner | Who can stop the launch and on what evidence |
| Control | Monthly KPI review | Daily checks in the launch window with written triggers | What result causes which change, decided in advance |
Extend the situation with a readiness audit
In a launch plan the situation analysis answers two questions: what does the market look like, and is the company able to deliver what it is about to promise? The second half is a short audit with one line per function. Product confirms the release is stable; support confirms trained staff and published help articles; sales confirms the team can demo and price the product; operations confirms stock or capacity for the expected demand. Each line gets a named signatory and a written definition of ready. Choose this form over a narrative risk section whenever more than two teams are involved, because a narrative can be nodded through while a signature cannot. The launch planning and tiers guide lists the items a bill of materials usually covers, and the audit should reference it rather than restate it.
Split objectives across two windows
A single objective such as revenue by year end hides the shape of a launch. Write two sets. Launch-window objectives cover the first weeks and measure attention and first demand: coverage, sign-ups, pre-orders, Share of VoiceYour share of market visibility. in the category conversation. Adoption objectives cover the following months and measure whether buyers use and keep the product. The trade-off is focus: two sets double the reporting, but one set either rewards a loud launch nobody adopts or judges the launch on a curve that has not had time to form. Use both whenever the product needs setting up or habitual use; a simple consumable may need only the first.
Choose a tier and a sequence in the strategy
Strategy in a launch plan states the launch tier, which fixes the scale of everything after it, and the order in which audiences hear the news: existing customers, press and analysts, partners, then the wider market. A clear positioning statement belongs here, written once so that every phase uses the same claim. Pick a lower tier than the team would like when readiness lines are weak; a smaller launch done well can be followed by a bigger moment, while a large launch that disappoints cannot easily be repeated.
Phase the tactics, each with its own channel mix
Tactics split into pre-launch, launch and sustain. Pre-launch builds interest among people who can amplify the news, so it leans on earned and owned channels: briefings handled through media relations and pitching, a waiting list, and partner preparation. Launch is the moment of maximum ReachUnique people who saw an ad., where paid media and announcements run together, planned with the media planning framework. Sustain converts interest into use, so it moves to lifecycle messages such as a welcome series for new buyers, retargeting and customer stories. Decide in advance the date on which budget shifts from launch to sustain; teams left to judge it on the day tend to keep spending on reach after the novelty has gone.
Write an Action section with a run-of-show and a go or no-go owner
The Action section becomes a dated run-of-show: every task from embargo lift to the first customer email, with an owner, a time and a dependency. Above it sits one person with authority to delay the launch, and a short list of conditions under which they will. The trade-off is speed against safety: naming a single owner can feel bureaucratic, yet a committee rarely postpones anything. The product launch playbook sets out readiness gates and the go or no-go meeting in operational detail.
Tighten Control to daily checks with predefined triggers
During the launch window, control runs daily against a handful of signals, each with a threshold and a pre-agreed response: if checkout errors pass a level, pause paid traffic; if support queues exceed a limit, slow the email sends. Writing the triggers before launch matters because launch days produce more data than anyone can interpret calmly. After the window, control relaxes to the weekly and monthly rhythm of the ongoing plan.
Decision points in a worked SOSTAC for a launch
An invented smart-thermostat maker, Larchmere Controls, plans its first app-connected thermostat
Larchmere Controls sells programmable thermostats through installers and plans to launch its first app-connected model, the Larchmere Link, in the UK on 3 March, priced at £149.
| Section | What the plan says |
|---|---|
| Situation | Installer channel healthy, direct-to-consumer untested. Readiness audit: firmware signed off by product on 10 February; support trained, but only 12 of 20 help articles written; sales demo kits for 40 installer partners; stock of 6,000 units against forecast first-quarter demand of 4,500 |
| Objectives (launch window, first four weeks) | 1,800 units sold, 25 pieces of trade and consumer coverage, 9,000 app registrations |
| Objectives (adoption, months two to six) | 70% of buyers with a heating schedule set in the app within 14 days; returns below 4% |
| Strategy | Tier one launch; installers told first, then press, then consumers; position on lower bills without rewiring |
| Tactics | Pre-launch (six weeks, £18,000): installer webinars, press briefings under embargo, a waiting list. Launch (two weeks, £42,000): paid social and video, retailer listings, launch email to 22,000 owners of older models. Sustain (ten weeks, £20,000): onboarding emails, installer case studies, retargeting of waiting-list sign-ups |
| Action | Head of product marketing owns go or no-go; gate meeting on 24 February; run-of-show of 64 tasks |
| Control | Daily for 14 days: app pairing failures, support contacts per 100 units, paid cost per sale. Trigger: pairing failures above 5% pauses paid media |
The readiness audit did the most work. At the gate meeting the help articles were still incomplete, so the go or no-go owner moved the consumer phase back a week while letting installers start on time, which the run-of-show allowed because each phase had its own dates. On day three pairing failures reached the trigger level after a router compatibility issue, paid media paused for two days, and the launch-window sales objective was missed slightly while the adoption objective held. Without the two objective sets the board would have read the launch as a failure; without the trigger the paid budget would have sent more buyers into a broken setup flow.
Measuring the launch: KPIs and cadence
A launch plan needs a KPIA metric tied directly to an objective. for each objective set plus operational signals that sit outside the objectives but can sink them. Launch-window measures are attention and first demand: coverage won, category share of conversation, sign-ups, pre-orders and first sales against the tier's expectation. Adoption measures follow the product into use: activation, usage frequency, returns and support contacts per unit. Operational signals cover stock, error rates and queue length. Read operational signals daily during the window, launch-window measures weekly, and adoption measures monthly until the trend settles. The guide to measuring launch success covers KPIs by tier and the post-launch review, and the marketing budget calculator helps check that the phase budgets add up before the plan is signed.
Where a launch SOSTAC misleads
The structure can give a weak launch an air of control. A complete readiness audit says nothing about whether the market wants the product; it confirms only that the company can ship it. Phase budgets set before launch assume a response curve nobody has seen yet, so they need a review point rather than a fixed split. And because launch-window results arrive quickly, they tend to dominate the post-launch review even though adoption is the better guide to whether the product will last. Setting the post-launch reviewThe meeting that closes a launch once its measures have had time to move: goals against results, what worked, what did not, and process changes for the next. late enough for the adoption targets to be read keeps both windows in view.
Common mistakes
- Treating readiness as a product question. Support, sales and stock fail launches as often as software does, and each needs a signature.
- One set of objectives. A single target either flatters a noisy launch or condemns one whose adoption has not yet shown.
- A fixed date in the objectives. Dates belong in Action, where the gate can move them.
- No owner for the go or no-go call. Without one, the launch goes ahead by default.
- Triggers written on launch day. Decide the responses before the data arrives.
