web2-to-web3-translation-risk

name	web2-to-web3-translation-risk
description	When a team brings Web2 GTM playbooks (Product-Led Growth, fundraise-then-launch, paid acquisition, power users) into Web3, surface where the inversions occur. Web3 launches IPO before PMF, fundraising IS GTM, attention is distributed via ownership not bought, and growth happens through Power Citizens not Power Users. Catches predictable mistakes before they detonate.
composition_level	atom
extraction-lens	principle
source_attribution	Matt Bond (Hivemind Library)
license	pending-consent
status	candidate

Web2 → Web3 Translation Risk

When to use

• Web2 founder/team translating playbook to a Web3 launch
• Evaluating a marketing strategy that "looks like" Web2 GTM
• Reviewing fundraising plan + product plan + GTM plan as separate workstreams (they shouldn't be)
• Onboarding a new growth or marketing hire from Web2 to a Web3 project
• Post-mortem on a Web3 launch that "did everything right" by Web2 standards

When NOT to use

• Pure Web2 projects without token / public-launch dynamics
• Web3-native teams already operating with these inversions internalized
• Tactical execution work within an already-correct strategy

Core thesis

Web2 optimizes for acquisition and usage. Web3 must optimize for coordination and retention under liquidity.

The order of operations is inverted. Applying Web2 sequencing to a Web3 launch detonates predictably.

The five inversions

For each, surface the Web2 pattern and the Web3 reality. If the team is operating on the Web2 side, that's a risk to flag.

1. Product-Led Growth → Ecosystem-Led Growth

• Web2: build finished product → find users → convince them to buy → scale
• Web3: launch unfinished product in public → incentivize others to help finish + grow it

You're not building a closed product; you're launching an open ecosystem. Ecosystems grow when people compound the network outside the core team — not on features alone.

2. IPO Before Product-Market Fit

• Web2 timeline: 5-20 years preparing for IPO; raise privately, prove model, hit profitability, then IPO
• Web3 reality: TGE = IPO. Price visible immediately. Investors, users, contributors arrive simultaneously. Governance and incentives go live before the product is finished.

You're building, fundraising, governing, and being judged simultaneously, in public.

3. Fundraising IS Go-To-Market

• Web2: fundraising and GTM happen separately
• Web3: they collapse into the same moment

The token launch is how you simultaneously: distribute ownership, bootstrap evangelists with skin in the game, launch the narrative in public view.

The people who invest should be the same people who use, contribute, promote, and govern.

4. CAC → TAC (Token Acquisition Cost)

• Web2: growth is rented (Facebook, Google) — pay for attention, hope users stick
• Web3: attention is distributed through ownership

Tokens turn users into stakeholders. But tokens only buy attention. Without retention, you don't have a community — you have mercenaries.

5. Power Users → Power Citizens

• Web2: optimize for users (especially power users who log in often + pay)
• Web3: roles blur — founders, investors, employees, users, contributors overlap

Once roles overlap, usage alone stops being a useful growth signal. Optimize for Power Citizens (multi-role contributors), not Power Users.

What still works (translation layer)

The following Web2 patterns translate cleanly:

• Clear narrative
• Excellent onboarding
• Community rituals + feedback loops
• Fast iteration

Don't throw out everything Web2 — these still apply.

What breaks (high-risk imports)

The following Web2 patterns detonate in Web3:

• Paid acquisition as primary engine — the unit economics break under TAC
• Vanity metrics as health signals — DAU/MAU don't capture multi-role behavior
• "Launch then build" sequencing — in Web3, the launch IS the build
• Rewarding single actions linearly — creates quest farming meta, not aligned community

Output format

TEAM CONTEXT: [where they're coming from in Web2]

INVERSION 1 — PLG → ELG: aligned | misaligned (describe)
INVERSION 2 — IPO timing: aligned | misaligned (describe)
INVERSION 3 — Fundraising = GTM: aligned | misaligned (describe)
INVERSION 4 — CAC → TAC: aligned | misaligned (describe)
INVERSION 5 — Users → Citizens: aligned | misaligned (describe)

DETONATION RISKS (high-priority fixes):
[list misaligned inversions and what specifically will break]

PRESERVED PATTERNS (still work):
[which Web2 patterns are still valid in this context]

Failure mode

Telling the team "Web2 doesn't work in Web3" without specifying which parts. Most Web2 patterns translate; specific ones detonate. The skill works through inversion-level diagnosis, not blanket dismissal.

Related skills

• launches-as-micro-economies — the design framework that operationalizes these inversions
• incentive-surface-diagnostic — applies to inversion 4 (TAC + retention)
• compound-vs-collapse-attention — applies to inversion 4 specifically (mercenary attention)
• contrarian-strategy-reframes — Reframe 1 (marketing IS product) is one of the inversions