Document Type: Framework
Status: Canon
Authority: HeadOffice
Applies To: Product Brain, Strategy Brain, Operations Brain, Sales Brain, Ads Brain, Content Brain, Data Brain
Parent: Product Brain Canon
Version: v1.0
Last Reviewed: 2026-05-06
Purpose
The Product Brain Launch Classification Framework defines how MWMS classifies product, feature, customer, market, soft, and general availability launches before planning execution.
This framework ensures MWMS does not treat all launches the same.
Correct launch classification prevents:
- overbuilding small launches
- underbuilding important launches
- unclear ownership
- weak planning
- wasted resources
- poor launch measurement
Core Principle
The type of launch determines the level of effort.
A launch must be classified before:
- goals are set
- timelines are planned
- teams are assigned
- campaigns are built
- sales enablement begins
- reporting is created
Launch Classification Questions
Every launch must answer five questions.
1. What Are We Launching?
Classify as:
- Product Launch
- Feature Launch
- Package Launch
- Company / Brand Launch
- Initiative Launch
2. Who Needs To Know?
Classify as:
- Customer Launch
- Market Launch
- Internal Launch
3. How Available Is It?
Classify as:
- Soft Launch
- Beta Launch
- Early Access Launch
- General Availability Launch
4. How Important Is It?
Classify as:
- Tier One
- Tier Two
- Tier Three
5. What Outcome Is Required?
Classify by primary goal:
- revenue
- adoption
- awareness
- upgrade
- retention
- feedback
- product market fit validation
Product Launch
A Product Launch introduces a standalone offering that can be purchased, used, downloaded, subscribed to, or adopted independently.
Common Goals
- net new revenue
- new market entry
- new customer acquisition
- portfolio expansion
- strategic positioning
MWMS Rule
A product launch usually requires:
- Strategy Brain involvement
- Product Brain ownership
- Sales Brain enablement
- Ads Brain or Content Brain support
- Data Brain measurement
Feature Launch
A Feature Launch introduces a new capability inside, attached to, or improving an existing product or offer.
Common Goals
- increase usage
- improve retention
- drive upgrades
- improve experience
- reduce friction
- match competitor parity
MWMS Rule
A feature launch must not automatically become a full market launch.
Feature importance determines launch tier.
Package Launch
A Package Launch introduces or changes pricing tiers, bundles, add-ons, subscriptions, or access levels.
Common Goals
- increase revenue per customer
- improve upgrade path
- shift package mix
- clarify value
- monetize feature value
MWMS Rule
Package launches must involve:
- Product Brain
- Finance Brain
- Strategy Brain
- Data Brain
No package launch may proceed without pricing and value alignment.
Customer Launch
A Customer Launch targets existing users, customers, members, subscribers, or internal audiences already connected to MWMS.
Common Activities
- email update
- product notice
- help content
- customer success outreach
- internal enablement
Common Goals
- adoption
- retention
- satisfaction
- upgrade
- customer education
MWMS Rule
Customer launches are used when the primary audience is already inside the customer base.
Market Launch
A Market Launch targets prospects, competitors’ customers, analysts, investors, partners, media, or a broader external market.
Common Activities
- campaign launch
- press release
- webinar
- social content
- paid ads
- sales outreach
- partner promotion
- product page launch
Common Goals
- awareness
- acquisition
- category positioning
- demand creation
- competitive displacement
MWMS Rule
Market launches require stronger positioning, messaging, campaign planning, and measurement than customer-only launches.
Internal Launch
An Internal Launch informs MWMS team members, AI Employees, collaborators, or internal operators about a new capability, system, process, or workflow.
Common Goals
- enable correct use
- prevent confusion
- align teams
- update procedures
- reduce operational drift
MWMS Rule
Internal launches may require no external marketing but must still include clear ownership and documentation.
Soft Launch
A Soft Launch releases a product, feature, or capability to a limited audience before full rollout.
Common Goals
- identify bugs
- gather feedback
- validate adoption
- test onboarding
- reduce launch risk
MWMS Rule
Soft launches are preferred when uncertainty is high.
No soft launch should occur without a feedback loop.
Beta Launch
A Beta Launch gives selected users access before full release.
Common Goals
- test usability
- validate product market fit
- collect testimonials
- identify missing features
- refine onboarding
MWMS Rule
Beta users must be selected intentionally, not randomly.
Beta feedback must be routed to Product Brain, Data Brain, and Strategy Brain.
Early Access Launch
An Early Access Launch gives selected customers or prospects access before public launch, often as part of relationship building, proof creation, or pre-launch pipeline generation.
Common Goals
- build early demand
- generate case studies
- validate buyer interest
- recruit launch partners
- create sales conversations
MWMS Rule
Early access must not overpromise incomplete functionality.
General Availability Launch
A General Availability Launch makes the product, feature, or package available to the intended full audience.
Common Goals
- market awareness
- full adoption
- revenue generation
- upgrade conversion
- broad customer access
MWMS Rule
General availability requires readiness across:
- product
- messaging
- support
- sales
- measurement
Launch Tier System
MWMS uses three launch tiers.
Tier One Launch
A Tier One Launch is strategically important and requires major cross-functional support.
Use When
- new product
- new revenue stream
- major market opportunity
- major positioning shift
- high executive visibility
- large business impact
Typical Requirements
- go to market strategy
- full messaging system
- dedicated launch plan
- sales enablement
- customer enablement
- paid and owned campaign support
- measurement dashboard
- leadership reporting
Tier Two Launch
A Tier Two Launch is important but does not require full market-wide launch intensity.
Use When
- major feature
- significant customer impact
- upgrade driver
- meaningful campaign opportunity
- broad existing customer relevance
Typical Requirements
- launch brief
- product page or section
- sales/customer enablement
- blog or content support
- email or customer communication
- performance tracking
Tier Three Launch
A Tier Three Launch is smaller, targeted, or primarily operational.
Use When
- minor feature
- customer-only update
- small enhancement
- limited audience impact
- parity update
- support-driven update
Typical Requirements
- internal note
- help content
- customer email if needed
- basic tracking
- support awareness
No Launch Classification
Some changes do not require a launch.
Examples
- bug fixes
- minor UI cleanup
- backend improvements
- small internal updates
- invisible technical corrections
Rule
Not every release is a launch.
Launching everything creates noise.
Classification Decision Table
| Question | Classification Output | Decision Impact |
|---|---|---|
| Is it standalone? | Product / Feature / Package | Defines strategic weight |
| Who needs to know? | Customer / Market / Internal | Defines audience |
| Is it complete? | Soft / Beta / Early Access / GA | Defines rollout risk |
| How important is it? | Tier One / Two / Three | Defines resource level |
| What outcome matters? | Revenue / Adoption / Awareness / PMF | Defines metrics |
Required Classification Output
Every launch must produce a Launch Classification Record.
Required Fields
- Launch Name
- Launch Type
- Audience Type
- Availability Type
- Launch Tier
- Primary Goal
- Supporting Goals
- Required Brains
- Measurement Owner
- Launch Risk Level
- Launch Decision
Cross Brain Integration
Product Brain
→ owns launch classification
Strategy Brain
→ defines positioning and audience
Finance Brain
→ validates pricing and monetization
Sales Brain
→ prepares customer-facing teams
Ads Brain
→ executes paid campaign support if needed
Content Brain
→ prepares content and organic communication
Operations Brain
→ manages execution coordination
Data Brain
→ defines measurement
HeadOffice
→ governs launch priority and escalation
Failure Modes Prevented
This framework prevents:
- treating all launches equally
- over-resourcing small updates
- under-resourcing major launches
- launching without clear goals
- market launches without readiness
- customer launches without communication
- soft launches without feedback
- GA launches without measurement
Drift Protection
The system must prevent:
- launch activity without classification
- campaigns before readiness
- launch tier inflation
- unsupported market launches
- unclear ownership
- measurement after launch instead of before launch
Operational Rules
Rule 1: Classify Before Planning
No launch plan begins before classification.
Rule 2: Match Effort To Tier
The launch tier determines activity depth.
Rule 3: Define Audience Early
Customer, market, and internal launches require different communication.
Rule 4: Validate Readiness
General availability requires product, messaging, sales, support, and measurement readiness.
Rule 5: Document The Decision
Every launch classification must be recorded.
Architectural Intent
This framework creates the first control gate in the MWMS Launch Operating System.
It ensures MWMS launches are:
- intentional
- correctly sized
- measurable
- aligned
- resourced appropriately
It transforms launches from:
→ reactive announcements
into:
→ structured growth events
Final Rule
If the launch type is unclear:
→ the launch must not proceed.
Change Log
Version: v1.0
Date: 2026-05-06
Author: HeadOffice
Change:
Created Launch Classification Framework defining how MWMS classifies product, feature, customer, market, soft, beta, early access, general availability, and tiered launches before planning execution.
Change Impact Declaration
Pages Created:
Product Brain Launch Classification Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
Product Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes