Launch tier framework skill

Launch Tier Framework

When to use

Use this skill when you need to decide how big a launch should be, what GTM motions it deserves, and how multiple product moments should fit into a broader launch season.

Use it for:

• Classifying roadmap items into launch tiers
• Deciding whether a feature needs its own launch moment or should be bundled into a bigger narrative
• Building a launch plan that does not depend on one Big Bang launch day
• Aligning Product, PMM, Campaigns, PR/AR, Sales, CS, Support, and executive stakeholders
• Defending launch investment decisions with a consistent framework
• Turning a release train or roadmap into a season-of-launch plan tied to company goals

Do not use it as a generic campaign calendar. The point is to make launch scope, narrative, channels, and cross-functional investment match the strategic importance of each product moment.

Required inputs

Ask for or infer these inputs. If an input is missing, state the assumption and mark confidence as low.

• Company or product context
• Roadmap item, feature, release, integration, package, or product name
• Target customer segment and persona
• Customer problem or job to be done
• Business goal the launch should support: awareness, usage/adoption, revenue, retention, expansion, category perception, customer confidence, or competitive response
• Strategic importance to the company or product line
• Customer impact: new buyer value, user workflow change, adoption potential, retention impact, or risk reduction
• Revenue or pipeline potential, if known
• Competitive or market relevance
• Proof points, customer evidence, demos, screenshots, beta results, or stories
• Timing constraints, launch window, dependencies, and roadmap confidence
• Available GTM resources across Product, PMM, Campaigns, PR/AR, Sales, CS, Support, Web, Content, and Exec
• Related roadmap items that could be bundled into a bigger story

Core principles

• A launch is not one day. Launch day can create top-of-funnel attention, but follow-on tactics move people through consideration, acquisition, adoption, expansion, and retention.
• Build a Season of Launch tied to broader company goals, not a single Big Bang moment that exhausts all effort at announcement.
• The tier is a resource-allocation decision, not a vanity label.
• The same core launch content should be repurposed across sales enablement, videos, case studies, demos, customer comms, campaign assets, analyst briefings, and the sales toolkit.
• A good framework makes tradeoffs explicit and defensible. It helps teams say why one launch gets PR, exec support, and a full campaign while another gets targeted enablement and lifecycle comms.
• Smaller features can be bundled into a bigger narrative when they support the same customer problem, audience, or strategic theme.
• Divergent features should not be forced into one story. They may need smaller separate moments if they serve different personas, segments, buying triggers, or business goals.
• Launch intensity should follow customer value, business impact, market relevance, and proof. Not internal excitement.

Tiering workflow

1. Start with company and GTM goals

Name the broader business goal before assigning launch scope.

Common launch goals:

• Awareness: make the market notice a company direction, category point of view, or major product shift
• Consideration: give buyers a reason to evaluate or re-evaluate the product
• Acquisition: create pipeline, trial starts, demo requests, partner demand, or new logo interest
• Adoption: get existing customers or users to activate and build a habit
• Expansion: give accounts a reason to upgrade, attach, or broaden usage
• Retention: reinforce customer confidence, reduce churn risk, or show product momentum
• Competitive response: reframe a comparison, close a capability gap, or blunt a competitor narrative

If the launch goal is unclear, do not default to a bigger launch. Clarify what the business needs the launch to do.

2. Inventory roadmap moments

For each roadmap item, capture:

• What is launching
• Who it matters to
• What customer problem it solves
• How visible or novel the change is
• Whether it changes the buyer story, user workflow, or customer value proposition
• Whether it supports an existing company narrative
• Whether proof exists or still needs to be created
• What teams would need to support it
• Whether timing is fixed, flexible, or risky

3. Score launch impact

Assess each item across six dimensions:

1. Customer impact

   • Does this materially improve a job customers care about?
   • Does it change a workflow, unlock a new outcome, or reduce meaningful risk?

2. Business impact

   • Does it support pipeline, revenue, expansion, retention, adoption, or strategic account goals?

3. Market impact

   • Is it newsworthy, competitively relevant, category-shaping, or useful for analyst/influencer conversations?

4. Narrative impact

   • Does it advance a bigger company story or product direction?
   • Can it anchor a campaign, keynote, sales story, or executive narrative?

5. Audience breadth and specificity

   • Does it matter to a broad priority segment, a narrow high-value segment, or only a subset of users?

6. Proof readiness

   • Can the company show it credibly with demo, customer story, beta data, screenshots, ROI, or analyst/customer validation?

Use the assessment to recommend a tier. Do not force false precision with fake scores if the inputs are qualitative.

4. Decide bundle vs separate moment

Bundle roadmap items when they:

• Serve the same audience or buying committee
• Solve adjacent parts of the same customer problem
• Support one strategic narrative
• Can share the same hero message, proof, demo, and campaign motion
• Create a stronger story together than alone
• Help turn several small updates into visible product momentum

Separate roadmap items when they:

• Serve different personas, segments, or buying triggers
• Require different proof, demos, or sales motions
• Pull the narrative in different directions
• Need different timing due to readiness or market windows
• Would make the main story feel bloated or incoherent
• Deserve targeted adoption or enablement rather than a broad announcement

5. Assign tier and GTM motion

Choose the smallest tier that can accomplish the business goal. Bigger is not better if the story, proof, audience, or resource case is weak.

For each item or bundle, define:

• Recommended tier
• Rationale
• Primary business goal
• Target audience
• Core message
• Required assets
• Cross-functional owners
• Launch-day motion
• Follow-on season-of-launch motion
• Risks and dependencies

6. Build the season of launch

Plan a sequence before and after launch day.

A useful season-of-launch arc:

• Pre-launch: narrative, beta/customer validation, sales readiness, analyst/customer previews, campaign build, internal alignment
• Launch day/window: announcement, web update, blog, press/AR if warranted, sales/customer comms, demo, social, executive amplification
• Follow-on weeks: webinars, customer stories, demo videos, sales plays, enablement refresh, nurture, lifecycle comms, community/customer education, partner activation
• Adoption and proof loop: usage reporting, customer wins, case study pipeline, objection feedback, sales learnings, product feedback, retention/expansion signals

Launch day creates awareness. The follow-on plan creates consideration, acquisition, adoption, expansion, and retention.

7. Make decisions defensible

Summarize why each item got its tier and what would have to change to move it up or down.

Examples:

• Move up if beta customer proof lands, a competitor announces similar functionality, or the release becomes the anchor for a company narrative.
• Move down if roadmap confidence is low, proof is weak, the audience is narrow, or the item is better handled through enablement and customer lifecycle channels.

Tier definitions

Use these definitions as defaults. Adjust names or thresholds to match the company's operating model, but keep the logic consistent.

Tier 1: Company-level launch

Use when the launch is strategically important enough to anchor a company narrative or major business goal.

Signals:

• Major new product, platform, market entry, pricing/package shift, or category-defining capability
• Clear tie to awareness, pipeline, revenue, market perception, or executive-level company strategy
• Meaningful customer and business impact
• Broad enough audience or strategic segment to justify large cross-functional effort
• Strong proof path: demo, customer evidence, beta data, analyst/customer validation, or executive narrative
• Can support a full season of launch, not just an announcement

Typical motions:

• Executive narrative and internal alignment
• Hero messaging and launch bill of materials
• Website/product page update
• Announcement blog or newsroom moment
• PR/AR/influencer motion where warranted
• Analyst/customer briefings
• Launch video or demo video
• Sales narrative, talk track, deck slides, objection handling, and enablement session
• Customer comms and CS playbook
• Campaign, webinar, nurture, paid/organic social, and follow-on content
• Customer story or proof development
• Post-launch measurement and feedback loop

Tier 2: Campaign-level launch

Use when the launch matters to a priority segment or pipeline/adoption goal but does not need a company-level moment.

Signals:

• Meaningful feature set, integration, package, workflow, or use-case launch
• Clear audience and business goal
• Useful for campaign, sales play, adoption push, or expansion motion
• May support a broader narrative but is not the whole company story
• Some proof exists or can be created quickly
• Needs cross-functional support, but not full executive/PR machinery

Typical motions:

• Messaging brief and tier rationale
• Blog, landing page section, changelog, or product page update
• Targeted campaign or nurture
• Sales/CS enablement and account targeting guidance
• Demo snippets, screenshots, or walkthrough video
• Customer email or in-app/customer lifecycle comms
• Webinar, field enablement, or use-case content where useful
• Measurement tied to pipeline, adoption, expansion, or engagement

Tier 3: Targeted launch

Use when the launch is important to a specific customer segment, persona, lifecycle stage, or sales motion but does not warrant a broad campaign.

Signals:

• Valuable feature or integration for a defined subset of customers or prospects
• Helps adoption, retention, competitive response, or account conversations
• Limited market news value
• Narrow audience or tactical use case
• Best handled through targeted enablement, lifecycle, customer, or partner channels

Typical motions:

• Short messaging brief
• Changelog/release notes or help center update
• Sales/CS talk track and FAQs
• Target account or customer list
• In-app message, lifecycle email, community post, or partner/customer enablement
• Demo guidance or screenshot
• Adoption metrics and qualitative feedback

Tier 4: Release-note or enablement-only update

Use when the item should be communicated clearly but does not need a launch moment.

Signals:

• Small enhancement, quality improvement, UI change, admin control, bug fix, or incremental capability
• Low buyer impact but useful to existing users
• No broader narrative or campaign need
• Better suited to docs, release notes, support readiness, or CS notification

Typical motions:

• Release note, docs/help center update, or support article
• Internal note for Sales, CS, and Support if customers may ask
• Optional in-product education
• No separate campaign, PR, or launch event

Output format

Produce the launch tier framework in this structure:

1. Executive summary

   • One-paragraph recommendation on the launch strategy and season-of-launch shape

2. Roadmap classification table

   • Item or bundle
   • Target audience
   • Customer problem
   • Business goal
   • Recommended tier
   • Rationale
   • Confidence level

3. Bundle vs separate recommendations

   • What should be bundled
   • What should remain separate
   • Why

4. Tier rationale by item

   • Customer impact
   • Business impact
   • Market impact
   • Narrative impact
   • Audience breadth/specificity
   • Proof readiness
   • Decision: why this tier is appropriate

5. Season-of-launch plan

   • Pre-launch
   • Launch day/window
   • Follow-on weeks
   • Adoption/proof loop

6. Core launch content system

   • Hero message
   • Sales enablement
   • Demo/video
   • Case study/proof plan
   • Campaign/content plan
   • Customer/CS assets
   • Sales toolkit

7. Cross-functional alignment map

   • Product
   • PMM
   • Campaigns/Demand Gen
   • PR/AR/Comms
   • Sales
   • CS/Support
   • Web/Content/Creative
   • Exec sponsor, if needed

8. Measurement plan

   • Awareness metrics
   • Consideration/acquisition metrics
   • Usage/adoption metrics
   • Revenue/expansion metrics
   • Retention/customer confidence metrics
   • Qualitative feedback loop

9. Risks, dependencies, and open questions

   • Roadmap risks
   • Proof gaps
   • Narrative risks
   • Resource constraints
   • Decisions needed

10. Move-up / move-down criteria

• What would justify a higher tier
• What would justify a lower tier

Quality bar

A strong output:

• Connects launch scope to company goals, not internal excitement
• Makes the tier decision easy to defend to Product, Campaigns, PR/AR, Sales, CS, and execs
• Separates launch-day awareness from follow-on consideration, acquisition, adoption, expansion, and retention work
• Reuses core content across enablement, videos, case studies, demos, sales toolkit, customer comms, and campaigns
• Bundles small features into a stronger narrative when they share audience, problem, and proof
• Keeps divergent features separate when bundling would muddy the story
• Names owners, assets, proof gaps, dependencies, and measurement
• Recommends the smallest launch motion that can achieve the goal
• Uses plain PMM language and practical GTM motions

Pressure tests

Before finalizing, check:

• Goal test: Is the launch tied to awareness, adoption, revenue, retention, expansion, competitive response, or another clear company goal?
• Tier test: Would another team understand why this item got this tier?
• Big Bang test: Does the plan avoid putting all value on launch day?
• Bundle test: Are bundled items connected by audience, problem, narrative, and proof?
• Divergence test: Are unrelated items kept out of the main story?
• Proof test: Can the company credibly show the value, not just announce it?
• Sales test: Does Sales get a usable story, talk track, demo path, and objection guidance?
• Customer test: Do existing customers know what to do next and why it matters?
• Measurement test: Are metrics tied to the actual launch goal?

Anti-patterns

Avoid:

• Treating every release as a Big Bang launch
• Using launch tiers as status symbols instead of resource decisions
• Giving PR to launches with no real market news, proof, or company narrative
• Hiding weak strategy behind a long asset checklist
• Bundling unrelated features just because the dates are close
• Splitting every small feature into its own moment and fragmenting the story
• Optimizing only for announcement-day impressions
• Forgetting the follow-on work that moves buyers through consideration and acquisition
• Forgetting adoption, customer education, CS readiness, and retention
• Creating launch content that Sales cannot use in real conversations
• Assigning a high tier because Product is excited but customers will not care
• Measuring every launch with the same metrics regardless of the goal