Launch

Launch is the go-to-market workspace for turning a product release into an operating plan. It is designed to keep messaging, audience-building, channel execution, launch-day tasks, and review learning in one connected flow.

Overview

The Overview tab is the control panel for Launch. It gives you a quick read on whether your launch actually looks operational instead of just aspirational.

Key signals:

• Launch countdown: How close you are to the target date.
• Waitlist setup: Whether the pre-launch audience machinery is configured.
• Risk watch: Missing launch date, no primary channel, no analytics, weak launch plan, or weak review follow-through.
• Upcoming tasks: The next owned launch actions that need attention.
• Channel experiment snapshot: Which channel tests are active or still only ideas.

Why it matters:

• Launches usually fail because messaging, channels, and execution planning drift apart.
• The overview reconnects those pieces and helps you spot operational gaps early.

Tips:

• Use the overview before launch day, not just after.
• Treat warnings as action items, not decoration.
• If the task list is thin, the launch is probably not ready yet.

Positioning

The Positioning tab is where you define the story the launch is built on.

Key fields:

• Audience
• Problem
• Value proposition
• Differentiation
• Proof points
• Messaging direction
• CTA

Why it matters:

• Channel execution gets noisy fast if the product story is weak.
• Positioning should be stable enough that the launch assets all tell the same truth.

Tips:

• Resolve the core message before you expand channels.
• Keep the value proposition tied to a real audience pain.
• If proof is weak, the launch narrative should stay modest and specific.

Waitlist

The Waitlist tab is about building demand before the launch event.

Key fields:

• Target launch date
• Waitlist target
• Landing page URL
• Building channels
• Outreach
• Community engagement
• Nurture approach

Why it matters:

• A waitlist is useful only if it represents real audience learning and pre-launch intent.
• This phase shows whether you have actual audience infrastructure or just hope.

Tips:

• Track the source and quality of interest, not only raw signups.
• A landing page with no follow-up plan is incomplete.
• Use this phase to test whether the message converts before launch day.

Channels

The Channels tab is where you decide where the product will actually meet the market.

Key fields:

• Primary channel
• Supporting channels
• Analytics setup
• Experiment ideas
• Channel experiments
• Owners
• Success criteria

Why it matters:

• Trying to launch everywhere at once usually means weak execution everywhere.
• Structured channel experiments help you learn instead of just publish.

Tips:

• Pick a primary channel before adding too many secondary ones.
• Give each experiment a metric and a decision path.
• If analytics are missing, the review phase will be mostly guesswork.

Launch Day

The Launch Day tab is the execution layer for the actual release window.

Key fields:

• Launch date
• Launch team
• Launch readiness inputs
• Structured launch tasks
• Owners
• Due dates
• Blockers

Why it matters:

• Launch-day plans fall apart when tasks are implicit or live only in someone’s head.
• This tab should convert the launch into owned work across pre-launch, launch-day, and follow-up stages.

Tips:

• If a task has no owner, it is not really part of the plan.
• Review blockers before launch week, not during it.
• Use the task tracker as the source of truth once execution starts.

Review

The Review tab captures the learning loop after the launch.

Key fields:

• Iteration plan
• Double-down channels
• What worked
• What did not
• Surprises
• Next actions

Why it matters:

• Launch is not the finish line. The review is what converts activity into learning.
• A weak review means the next release starts from fuzzy memory instead of evidence.

Tips:

• Review while details are still fresh.
• Tie conclusions back to channels, message, and launch execution.
• The best review output is a prioritized next action list.

Documents

The Documents tab generates the launch outputs from the workspace data.

Current document types include:

• Positioning Statement
• Waitlist Copy
• Launch Checklist
• Press Kit
• Post-Launch Report

Why it matters:

• Documents should reflect the live launch plan, not sit apart from it.
• Better source data produces better launch assets.

Tips:

• Generate after the trackers and phases are credible.
• Regenerate when positioning or execution assumptions change.
• Treat generated docs as editable working drafts.