Not every launch deserves the same launch
A company that ships often cannot give every release the same treatment. If it tries, the effort spreads too thin to make any launch stand out, the audience learns that announcements are routine, and the teams involved burn out on a cycle that never stops. If it does nothing systematic, important releases slip out unnoticed and sales hears about them from customers.
Tiering is the answer most product marketing teams arrive at. Each release is placed in a tier according to its expected impact, and each tier comes with a standard scope: which audiences hear about it, which channels carry it, which teams have to prepare, and how much lead time it needs. The Product Marketing Alliance describes tiering as one of the simplest ways to make launches repeatable, and the logic is straightforward. The decision about effort is made once, against criteria, rather than reargued for every release.
Tiering also protects attention, which is the scarcest launch resource. Customers, prospects, the press and the company's own sales team can absorb only a few significant announcements in a year. Reserving the largest launches for the releases that genuinely change what the product is, who it serves or how it competes means that when a major launch happens, people notice. The product launches hub places tiering in the wider process; this guide covers how to do it and what follows from it. Hardware brands face the sharpest version of the attention problem, because most interest in a device arrives around its announcement; the consumer electronics marketing guide covers how reviewers, retailers and launch timing fit that window.
Launch tiers
Most companies use three tiers, sometimes with a fourth for releases that need no external announcement at all. The names vary; what matters is that the triggers are written down and the scope of each tier is agreed.
| Tier | Trigger | Typical scope | Lead time |
|---|---|---|---|
| Major launch | A new product, a new segment or market, a significant pricing change, or a capability that changes the competitive picture | Full plan; positioning and messaging update; website, email, paid and social; press or analysts; sales training; customer events | Long; planning starts when the release is scheduled |
| Feature launch | A meaningful improvement that a large share of customers will use or that sales will mention | Short plan; email to relevant customers; in-product message; website update; sales briefing | Moderate; a few weeks |
| Minor release | An improvement or fix that helps existing users but changes little for buyers | Changelog, help documentation, in-product note where useful; support briefing | Short; days |
| Silent release | Infrastructure, beta or experiment not ready for an announcement | Internal note only | Minimal |
The triggers deserve the most care. Good criteria are observable before launch: the share of customers the release affects, whether it opens a new revenue stream, whether it answers a common reason for lost deals, whether it needs customers to change how they work, and whether it is strategic for the company's positioning. A simple scoring sheet against those criteria makes the decision quick and explainable. Bad criteria are anything that depends on enthusiasm, such as how hard the team worked or how proud the product manager is. Placing the release in the Ansoff matrix of growth directions is a quick check on the new-product and new-market triggers, because a release that takes a new offer to buyers the business does not yet serve carries the most unknowns and usually belongs in the major tier.
Two rules keep tiering honest. First, a tier is about the market's interest, not the engineering effort: a release that took months may be a minor launch if buyers will barely notice it, and a small change may be a feature launch if it removes a common objection. Second, releases can be bundled. Several minor improvements around one theme can be launched together as a feature launch, which gives the market a story rather than a list.
The launch plan: goals, audiences, message, channels
The plan is a short document, often a single page, that answers four questions in order. Its form should follow the company's existing campaign brief, so that channel teams recognise it, with a few launch-specific additions. For a major launch, the go-to-market plan template adds the first segment, the offer and the gates between phases.
Goals come first, because everything else is chosen to serve them. A launch goal names the change the launch is meant to cause: awareness of a capability among a target audience, adoption of a feature among existing customers, pipeline from a new segment, or a shift in win rates against a competitor. Each goal needs a KPIA metric tied directly to an objective. and a target agreed before launch, which is what makes the launch measurement guide possible. A plan with goals like "raise awareness" and no measure attached cannot be judged afterwards.
Audiences come next. Most launches have more than one: existing customers who could use the release, prospects in the target segment, internal teams, and sometimes partners, press or analysts. Each audience has a different starting point and needs a different message. Existing customers already understand the product and need to know what changed and how to use it. Prospects need to know why the change matters to them.
Message is drawn from the messaging hierarchy rather than written fresh. The launch message connects the release to one of the existing value pillars, explains the problem it solves for each audience, and names the proof. A launch that needs a pillar the hierarchy does not have is a signal that positioning may need a review. If the release is to carry a name of its own rather than a plain description, settle that early with the tutorial on naming a product or brand, because screening, buyer tests and legal clearance advice all take place before launch materials can be made.
Channels follow audiences and tier. The RACE framework is a useful check that the plan covers the whole journey: reaching the audience, getting them to act, converting them and engaging them afterwards. AIDA does a similar job for the message sequence within a channel, from attention through interest and desire to action. Both stop a plan from ending at the announcement, which is where many launch plans run out of ideas. The ReachUnique people who saw an ad. of each channel matters less than whether it reaches the right audience at the right point in the FunnelModel of the customer journey stages.. For the channel choice itself, the launch objective hub ranks every channel by how well it concentrates attention into the window, and the guide to PR for a product launch shows how press effort should scale with the tier.
Roles and ownership
A launch involves most of the company, and unclear ownership is the most common reason assets are late or missing. The plan should name one owner for each workstream, and one person, usually the product marketer, who owns the launch as a whole.
| Role | Owns | Typical contribution |
|---|---|---|
| Launch owner (product marketing) | The plan, the timeline, the message and the go or no-go review | Runs the launch meetings, chases dependencies, writes the core message and the internal briefing |
| Product management | The release itself and its readiness | Confirms scope, availability and date; supplies demos and technical detail |
| Channel marketing | Each channel's execution | Builds and runs email, paid, social, website and events within the plan |
| Content and design | Launch assets | Produces pages, visuals, videos and documentation to the bill of materials |
| Sales and sales leadership | Readiness of the sales team and outreach to prospects | Attends training, agrees target accounts, reports early feedback |
| Customer success and support | Readiness for existing customers | Prepares help content, briefs agents, contacts key accounts |
| Communications | Press, analysts and partners where used | Drafts announcements, manages briefings and embargoes |
| Executive sponsor | Final decisions on major launches | Approves the tier, resolves conflicts, joins external moments where needed |
A responsibility matrix in the plan, showing who is responsible, who approves and who needs to be informed for each workstream, prevents the familiar problem of three people each assuming someone else is writing the email. For minor releases the table collapses to a couple of names; for major launches it may need a weekly meeting to keep it current. Building a RACI matrix around launch decisions, such as the date and the go or no-go call, gives each of those decisions a single accountable owner.
The bill of materials
The bill of materials is the list of every asset the launch needs, each with an owner, a due date and a status. It turns the plan into work and makes gaps visible early.
For a major launch, the list typically covers the external assets (a launch page or updated product page, announcement email, blog post, social posts, paid adverts, video or demo, press release where used, help documentation and in-product messages), the sales assets (an updated deck, a one-page summary, a talk track, updated battlecards and a training session), and the internal assets (a briefing note, a set of frequently asked questions for staff, and a support guide). A feature launch carries a shorter list, and a minor release may need only documentation and a changelog entry. Where the product is an app, the guide to designing in-app messages shows how to put an in-product announcement in front of the users who would use the feature without burying the session. The tutorial on writing release notes and a changelog covers that changelog entry itself, leading with the change for the user and stating who has it and from when.
Three practices make the bill of materials useful. Keep it in one shared place, with status visible to every contributor. Order it by dependency, because the message has to be final before copy can be written and the copy before design can finish. And review it at each launch meeting, with anything late escalated rather than quietly dropped. Assets that will be measured, such as emails and adverts, should carry tracking from the start so that click-through (CTRShare of impressions that result in a click.) and conversion can be read by audience and channel after launch.
Timeline: pre-launch, launch, post-launch
A launch timeline works backwards from launch day, with every milestone set relative to it so that the plan survives a moved date. It is worth placing major launches on the company's campaign calendar as soon as they are tiered, so that they do not collide with other campaigns competing for the same audience. When the launch is a new app, the guide to launching a new app adds the store review to the timeline and holds paid spend until tracking is confirmed in the live build.
Pre-launch begins with the tier decision and the plan, moves through messaging and asset production, and ends with readiness. Sales and support briefings happen shortly before launch, close enough that the detail is fresh and far enough ahead that questions can be answered. Early-access customers, beta usersSelected customers use a working product or feature before general release, so the business learns whether it works for them and what the launch needs. or analysts may be briefed under embargo. When a release needs customers to try it before launch, the tutorial on running a beta or early-access programme sets exit criteria in advance and hands its evidence back to this plan. A go or no-go review a few days before launch checks that the release is ready, the assets are complete and the teams are briefed. Before anything goes live, the campaign launch QA checklist catches broken links, missing tracking and inconsistent copy.
Launch day follows a running order: what goes live, in what sequence, and who checks it. Internal teams and existing customers usually hear first, the wider market afterwards. By email, that order becomes a staged sequence, and the tutorial on running a sale or launch by email sets out who hears first, who is reminded and how to read what the emails added. Someone should monitor the response during the day, from social mentions and support queues to the first sales conversations, and have authority to fix problems quickly. Where the release reaches customers in stages rather than on one day, the guide to launching a feature that rolls out gradually maps who has it when and decides which stage the announcement waits for.
Post-launch is where most plans stop too early. The weeks after launch are when adoption campaigns run, sales follows up with target accounts, and the team collects the questions and objections the launch surfaced. A post-launch review, covered in the measurement guide, closes the launch formally and feeds lessons into the template for the next one. 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. reads results against the goals this plan sets, which is why they are written down before launch.
A procurement platform plans a major launch
Tallowmere, a procurement software company with 180 staff, scheduled a supplier-risk module for release in twelve weeks. Scored against the tier criteria, it opened a new buyer persona and answered the most common reason for lost deals, so it was tiered as a major launch. The plan set three goals: 400 existing customers enabling the module in the first quarter, 60 qualified opportunities from risk teams, and a higher win rate against the competitor cited in 30% of losses. The bill of materials listed 34 assets across 7 owners. At the go or no-go review, the help documentation was a week behind, so the external announcement moved by five days while customer-facing teams were briefed on the original date.
If the launch plan is written in SOSTAC sections, the guide to applying SOSTAC to a product launch shows where readiness sign-offs, phased tactics and the go or no-go owner sit.
When the tier is set and the window agreed, the marketing budget calculator for a product launch turns a borrowed acquisition cost and a raised testing reserve into a budget range.
If the product is meant to spread through invitations or sharing, growth loops for a product launch sets the loop's cycle time against the launch window and plans it for the post-launch phase.
To see how a launch's objective by stage and its audience by adopter group fit together, the comparison of the product life cycle and diffusion of innovations sets the two models side by side.
Common mistakes
- Tiering by effort, not impact. How long the release took to build says nothing about how much the market will care.
- No written criteria. Without them, every launch becomes a negotiation and the tiers drift upwards.
- Goals without measures. A plan that cannot be judged afterwards will be judged a success by whoever ran it.
- Writing a new message for each launch. Launch messages should connect to the existing messaging hierarchy, not compete with it.
- Shared ownership. An asset with two owners has none; name one person for each workstream.
- A bill of materials nobody reviews. The list is only useful if late items are escalated at every meeting.
- Plans tied to calendar dates. Set milestones relative to launch day so the plan survives a slip.
- Briefing sales on launch day. Customer-facing teams should hear first, with time to ask questions.
- Stopping at the announcement. The adoption and follow-up work after launch is where most of the value is realised.
