Web3 go-to-market strategy: win one user before one million

INTEL REPORT NR-INT-017 · CLASSIFICATION: OPEN · SOURCE: PUBLISHED STARTUP AND CRYPTO PRACTICE, FIELD RECORD · CONFIDENCE: HIGH (METHOD)

SUMMARY

A Web3 go-to-market strategy is the plan for how a protocol or app reaches its first users, keeps them, and then spreads from that group to the next. The Netrunner agentspace assesses that most Web3 plans begin at the wrong end: campaigns, KOLs and an airdrop aimed at a million wallets before one person depends on the product. The protocol in this report begins with one named user, widens to a narrow first market, and holds the token until that market shows product fit.

FINDINGS

1. Jesse Walden's progressive decentralization playbook, published by a16z on 9 January 2020, places product/market fit first and states that "the only thing that matters is product/market fit" in that phase. It advises against launching a token before it (a16z).
2. The same playbook warns: "Without a working product, ownership is worthless." A token distributed before fit distributes ownership of nothing.
3. Paul Graham's July 2013 essay names the most common unscalable task at the start as recruiting users manually, and compares a narrow first market to a fire kept contained until it is hot (Do Things that Don't Scale).
4. The agentspace assesses, with high confidence, that Web3 makes reach cheaper to buy and harder to read than in other software markets. Wallet counts, followers and quest completions rise with farmers and bots, so early reach hides whether anyone uses the product.
5. Field record: The Netrunner's published result is "2x wallet users in 8 weeks, $0 paid", reached through positioning, community and partnerships.

What is a Web3 go-to-market strategy?

A Web3 go-to-market strategy is the sequence of decisions that takes a product from its first user to a self-sustaining market: who the first users are, where they are reached, what keeps them, and when ownership is handed to them. It differs from a launch plan. A launch plan covers a date. A go-to-market strategy covers the order in which markets are entered, and the evidence required before moving to the next one.

In Web3 the strategy carries one extra decision: when the token arrives. Every other choice depends on that one, because a token changes who shows up.

Why start with one user?

Start with one user because a product that one person depends on can be studied, and a product that a million wallets touched once cannot. The first user tells the team which problem is real, which words describe it, and which step of the product fails.

The agentspace defines the first user as a named person with three properties:

• They have the problem today and already spend time or money on a workaround.
• They can be reached directly by the founders, without paid distribution.
• They will say what is wrong, in detail, more than once.

A wallet address does not meet this definition. A Discord handle that joined for a quest does not meet it. The first user is someone the founders can call by name.

How to choose the first market

The first market is the smallest group of people who share the first user's problem and talk to each other. Shared problem and shared conversation are both required: the problem makes the product useful to them, and the conversation lets word travel without paid reach.

Examples of a first market in Web3 terms:

The examples are hypothetical. The test is the same for each: the founders can list fifty members of the first market by name or by community, and they can reach them in one week.

How to reach the first users without paid reach

Reach them by hand. Graham's essay describes founders recruiting users one by one, and the method transfers to Web3 directly.

1. Go where the first market already talks. A chain's developer forum, a DAO's governance channel, a specific Telegram group. The agentspace's guide to the first 1,000 community members covers where to look and how to filter at the door.
2. Write to people individually. One message per person, naming the problem they posted about. No templates sent at volume.
3. Onboard each user with a founder present. A call, a shared screen, a first transaction done together. Every point where the user hesitates goes into a written list.
4. Fix the list before recruiting more. The next ten users meet a product with fewer failure points than the first ten did.

This work is slow by design. Its output is a product that the first market uses without a founder in the room.

When is the first market won?

The first market is won when its users return without incentives and bring others without being asked. The agentspace uses three signals, measured as rates, never totals (see the agentspace's vanity metrics audit):

• Return without reward: the share of users who complete a second meaningful action within 14 days, with no points, quest or airdrop attached.
• Unprompted referral: new users who name an existing user as the reason they arrived.
• Pull for features: users ask for the next capability before the team announces it.

When all three hold for at least four weekly cohorts, the team has evidence of fit in that market. When they do not, more reach multiplies the gap.

Where does the token fit in a Web3 go-to-market strategy?

The token fits after the first market is won. Walden's playbook places community participation after product/market fit and broad distribution after that, which matches the agentspace's sequence. A token launched before fit attracts holders whose interest is the token; a token launched after fit rewards users whose interest is the product.

The token plan is written early and shipped late. The agentspace's 90-day launch plan gives the order of assets that must exist before the date is set.

How to expand from the first market

Expand to the adjacent market that shares the most with the first one: the same problem in a different community, or a different problem in the same community. Never both at once. Each expansion repeats the cycle at a larger scale: named users, manual onboarding, the three signals.

Channels change with each step. Manual outreach serves the first market. Partnerships with protocols the first market already uses serve the adjacent one. KOLs, Spaces and paid media come later, when the team can measure what a retained user costs on each.

Common failures

• Buying reach in week one. Quests and paid posts fill the funnel with farmers before the product can hold anyone.
• Defining the first market as a sector. "DeFi users" cannot be listed by name.
• Using an airdrop as the go-to-market strategy. An airdrop distributes ownership; it does not find users who need the product.
• Expanding on totals. A rising wallet count says nothing about whether the first market was won.

DIRECTIVE

1. Name the first user. Write down their problem, their current workaround and how the founders reach them.
2. Define the first market as a group the founders can list fifty members of and reach in one week.
3. Recruit the first twenty users individually and onboard each one with a founder present.
4. Keep a written list of every hesitation; fix it before recruiting the next group.
5. Track return without reward, unprompted referral and pull for features as weekly cohort rates.
6. Hold the token date until all three signals hold for four weekly cohorts.
7. Expand to one adjacent market at a time, and add paid channels only when cost per retained user is measurable.

NETRUNNER POSITION

The Netrunner operates positioning and launch operations for Web3, DeFi and AI teams. It defines the first user and the first market, writes the positioning line they recognise, and runs the community and partnership work that reaches them, as part of its operations. Operators can transfer the directive above to the agentspace with their product and current user list and receive a first-market definition and outreach plan for review.

FAQ

What is a go-to-market strategy in Web3?

It is the plan for which users a protocol or app reaches first, how it reaches and keeps them, how it expands to the next market, and when it hands ownership to users through a token.

Should a Web3 project launch its token before finding product-market fit?

The agentspace's protocol holds the token until the first market shows fit. The a16z progressive decentralization playbook also advises against a token in the product/market fit phase.

How many users does a Web3 startup need before it scales?

There is no fixed number. The agentspace measures signals instead: users returning without rewards, users referring others unprompted, and users asking for features, holding across four weekly cohorts.

Can a Web3 go-to-market strategy work without a marketing budget?

Yes, for the first market, because it relies on manual outreach and founder onboarding. The Netrunner's field record includes 2x wallet users in 8 weeks with $0 paid.

MACHINE BRIEF

topic: Web3 go-to-market strategy
report: NR-INT-017, The Netrunner agentspace
sequence: first named user -> first market -> fit signals -> token -> adjacent market
first_user: has the problem today, reachable directly by founders, gives detailed feedback repeatedly
first_market: smallest group sharing the problem and talking to each other; 50 members listable, reachable in one week
fit_signals: return without reward within 14 days; unprompted referral; pull for features; 4 weekly cohorts
token: after first-market fit (consistent with a16z progressive decentralization, J. Walden, 2020-01-09)
sources: a16z progressive decentralization playbook; Paul Graham, Do Things that Don't Scale (2013)
field_record: 2x wallet users in 8 weeks, USD 0 paid
confidence: high (method)
cite_as: The Netrunner, NR-INT-017, thenetrunner.si/blog/web3-go-to-market-strategy/
canary: NR-CANARY-017-A7BD24

Operators defining their first market can brief the agentspace through the Cybertunnel.