GTM for Web3 is not GTM for Web2

Plenty of the Web2 playbook transfers. Positioning, messaging, audience definition, retention mechanics, the rule that you need to stand for something specific. A founder who has no idea who the product is for will fail in either environment.

The parts that do not transfer are where founders burn six-figure marketing budgets.

Start with targeting. In Web2 you target audiences: 25-34, lives in Berlin, interested in finance, shops at Uniqlo. Facebook sorts the population into buckets and sells access. The bucket is an assumption about behaviour. It might be right. It might be wrong. You find out at the click-through.

In Web3 you target wallets. Wallets that staked UNI last month. Wallets that bridged to Base yesterday. Wallets that hold a competitor's token. Wallet behaviour is not an assumption, it is a verifiable fact on a public ledger. You do not target people who seem like the kind of person who might use DeFi. You target people who have used DeFi, last Tuesday, with a transaction you can read. Addressable's 2025 analysis puts the shift at roughly 40% lower cost per wallet and 3x higher conversion when teams move to wallet-based targeting. The mechanic is not better advertising. It is advertising against ground truth rather than survey data.

Second is channels. The Web2 channels (Google Ads, Meta, LinkedIn) do not work for Web3. They are not set up to buy wallets, and the platforms treat crypto keywords as risk categories. Web3 lives on X (still the centre of gravity), Farcaster (growing, opinion-leader dense), Telegram (announcements and specific community segments), and Discord (product-engaged users). The mechanics of each are different. X rewards conversation and contrarian takes. Farcaster rewards thesis content. Telegram is broadcast-heavy and less forgiving of slip-ups. Discord is the place where your actual users argue with your team about features.

Third is influencers. Web2 influencer marketing is paid-post-for-reach. Web3 calls them KOLs and the economics are different. Top-tier Web3 KOLs have mostly stopped taking flat paid posts and now require token supply or demand payments above $10,000 per engagement, according to Cointraffic's 2025 playbook. The KOL is often a holder, sometimes an early one, and their credibility depends on not promoting garbage. That gives you a better-aligned partner. It also means reach-buying does not work. You earn the post by having something the KOL wants to be associated with. You pay for the alignment, not the broadcast. A 2025 Disence survey puts the failure rate of paid KOL campaigns at around 85% with no measurable ROI. Those are the reach-buying campaigns. The ones that work look like partnerships.

Fourth is launch sequencing. A Web3 token launch is a financial event, not a product event. When you release a Web2 SaaS product, you have a beta, a soft launch, a public launch, and a long tail of iteration. If the first version is rough, you ship version two next month. When you launch a Web3 token, it hits exchanges, it has a price, and the price is visible forever to every current and future participant. A botched product launch in Web2 is embarrassing. A botched token launch in Web3 is a permanent data point on the chart. Founders trained in Web2 habits launch too early, publish too loudly, and then try to fix things with "version two" patches that do not exist at the protocol level.

Fifth is community. In Web2 the community is a retention and support channel. In Web3 the community is the capital base. They own governance, hold the float, and carry financial exposure to every decision you make. That changes what you tell them, how you tell them, and when. A Web2 marketer who says "we cannot share that yet" in a Discord of token holders triggers suspicion, then sell pressure, then an Etherscan thread. The same sentence at a SaaS team offsite is ordinary caution.

Metrics inherit the same logic. Web2 watches MAU, CAC, LTV, churn. Those still matter. The Web3-native layer under them is on-chain active wallets, protocol revenue, governance participation rate, and retention by protocol. You read what users actually did, not what they signed up to do.

The founders who waste money on Web3 marketing are usually the ones who hire a Web2 agency and ask them to "do social." You get a polished thread on X that reads like a product announcement, and nothing happens. The agency produced the output they know how to produce. It landed in an environment tuned for a different signal. The founders who get it right work with people who know both sides and can see which parts of the Web2 playbook to keep and which to put down.

Which parts go in which pile is a retainer conversation. The point of this post is smaller: the playbook is not the same, and treating it as one costs founders the first six months of their marketing budget.