launch-mode-decision

name	launch-mode-decision
description	When deciding how to launch a Web3 project (visibility timing + community formation), apply two paired decisions in sequence — stealth vs public build (visibility) and pre-token community vs token-led community (formation order). Wrong sequencing creates either premature exposure or community without coordination. Especially useful for protocol launches, token-driven ecosystems, and any product where network effects matter.
composition_level	atom
extraction-lens	principle
source_attribution	Matt Bond (Hivemind Library)
license	pending-consent
status	candidate

Launch Mode Decision

When to use

• Pre-launch decision-making (visibility + community)
• Repositioning an existing project that's stuck on adoption
• Evaluating whether stealth made sense in retrospect
• Deciding whether to delay public exposure to keep building credibility

When NOT to use

• Post-launch optimization work
• Non-network products without ownership/governance layers
• Projects with no token component AND no community-formation requirement

Two paired decisions

This skill makes two decisions that are usually conflated:

1. Visibility: stealth vs. public build
2. Community formation: pre-token (culture-first) vs. token-led (utility-first)

Each has different conditions. Choosing wrong on one usually surfaces a coordination problem 6-12 months later.

Decision 1: Stealth vs Public Build

Choose stealth when

• Complex technical development requires focused execution without distraction
• Regulatory uncertainty requires careful positioning and legal navigation
• Core concept viability hasn't been proven yet
• Team is still building credibility and partnerships in professional contexts

Underlying logic: execution clarity and technical viability must precede community exposure.

Choose public build when

• Community feedback meaningfully improves product fit
• Network effects are essential to the value proposition
• Cultural elements are core to success (not secondary marketing)
• Speed/momentum matter more than stealth advantage

Underlying logic: community participation is infrastructure, not marketing.

Decision 2: Community Formation Sequence

Choose pre-token (culture-first) when

• Cultural identity is central to product success
• Long-term alignment is required
• Trust must precede financial participation

5-step ordered sequence:

1. Genesis Narrative Creation — clear origin story, mission, cultural positioning
2. Core Contributor Attraction — quality-focused early community building, not quantity metrics
3. Ritual and Culture Establishment — regular practices that create belonging and shared identity
4. Cultural Artifact Development — memes, language, references that reinforce community bonds
5. Value Demonstration — proof points that justify token launch and community investment

Outcome: community belief and alignment exist before financial incentives are introduced.

Choose token-led (utility-first) when

• Token utility is immediately clear at launch
• Governance participation is functional from day one
• Incentives directly drive ecosystem growth

5-step ordered sequence:

1. Immediate Utility Delivery — token provides clear, demonstrable value from launch day
2. Incentive Alignment Systems — token mechanics reward desired community behaviors consistently
3. Community Governance Integration — token holders meaningfully shape direction and priorities
4. Organic Cultural Evolution — community develops authentic culture through participation
5. Ritual Development — practices emerge naturally from token utility and governance

Outcome: economic participation accelerates community formation and ecosystem coordination.

Failure modes (from source)

• Stealth fails when: network effects are required early; competitors gain community momentum first
• Public build fails when: product isn't ready for scrutiny; token utility is unclear; regulatory positioning is fragile
• Pre-token community fails when: community lacks clear purpose or incentives during the long pre-token phase
• Token-led community fails when: token launches without clear utility; incentives attract extractive (not aligned) participants

Decision output

Return:

1. Visibility mode (stealth or public build) with the conditions that pointed to it
2. Community sequence (pre-token or token-led) with the conditions
3. The 5-step ordered progression for the chosen sequence
4. Named risks / failure modes to monitor in the chosen path

If conditions for both visibility modes look split, flag the project as needing more clarity before launch decision is final — don't force a choice. Common when team disagrees internally about whether the product is "ready."

Pairing guidance

The two decisions usually pair as:

• Stealth + pre-token → deep technical infrastructure with strong cultural identity
• Stealth + token-led → rare; usually only valid when token utility is mechanical (not coordinative)
• Public + pre-token → consumer-facing brands needing belief before monetization
• Public + token-led → token-governed ecosystems where utility is immediate

If your situation pushes toward an unusual pair (e.g., stealth + token-led), examine whether you've correctly classified one of the two decisions.