launch-tier-framework

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.