Launch Tier Framework

<!--
COMMUNITY SKILL — included under its original MIT license.
Source: https://github.com/adam-lagerhausen/b2b-marketing-skills by Adam Lagerhausen (MIT).
License text: ../LICENSE-b2b-marketing-skills.txt
Curated into Growth Marketing OS by Mahmoud Omar (mahmoudomar.com) — this file
is NOT original work by the repo author; see /skills/community/README.md.
-->

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