Go-to-Market in Web3 New Mindsets Tactics Metrics
Go-to-Market in Web3 New Mindsets Tactics Metrics
Web3: New
Mindsets, Tactics,
Metrics
https://future.a16z.com/go-to-market-in-web3
Every company faces some version of the “cold start problem”: How do you
get started from nothing? How do you acquire customers? How do you create
network effects — where your product or service becomes more valuable to
its users as more people use it — that create incentives for even more
customers to sign up?
Go-to-market differs in each of the quadrants, and can span everything from
traditional web2-style strategies to emerging and experimental strategies.
Here, I’ll focus on the upper right quadrant (decentralized team with token)
and contrast it with the lower left quadrant (centralized team with no token) to
illustrate the difference between web3 and web2 GTM approaches.
Decentralized with token
First, let’s look at the upper right quadrant. This includes organizations,
networks, and protocols with unique web3 operating models, which in turn
require novel go-to-market strategies.
Many DeFi projects follow a path where the protocol is first developed by a
centralized development team. Following the launch of its protocol, the team
often seeks to decentralize the protocol in order to increase its security and to
distribute management of its operation to a decentralized group of token
holders. This decentralization is typically accomplished through the
simultaneous issuance of a governance token; the launch of a decentralized
governance protocol (typically a decentralized autonomous organization, or
DAO); and the granting of control over the protocol to the DAO.
This decentralization process can involve many different structures and entity
forms. For instance, many DAOs do not have any legal entity affiliated with
them and operate solely in the digital world, while others use multi-signature
(“multisig”) wallets that act at the direction of the DAO. In certain cases,
nonprofit foundations are established to oversee future development of the
protocol at the direction of the DAO. In nearly all cases, the original developer
team continues to operate, in order to act as one of many contributors to the
ecosystem created by the protocol as well as to develop supplemental or
ancillary products and services. (This white paper contains more details on
legal frameworks for DAOs, from taxation and entity formation to operational
issues and considerations.)
So what does go-to-market look like here? Take the example of Dai, the
algorithmic stablecoin issued and governed by MakerDAO. One goal for most
algorithmic stablecoin issuers such as MakerDAO is to generate more usage
of their stablecoin in the financial ecosystem. The go-to-market motion is
therefore to have it: 1) listed on cryptocurrency exchanges for retail and
institutional trading; 2) integrated into wallets and applications; and 3) accepted
as payment for goods or services. Today, there are over 400 Dai markets, it
is integrated into hundreds of projects, and it is accepted as a form of payment
through major commerce solutions like Coinbase commerce.
How did they do it? MakerDAO initially accomplished this through a more
traditional business development team that was driving many early
partnerships and integrations. However, as it increased its decentralization,
the business development function became the responsibility of the growth core
unit, a sub-community of Maker token holders often referred to as a SubDAO.
Additionally, since MakerDAO is decentralized and its protocol’s operation is
trustless and permissionless, anyone can generate or buy Dai using the
protocol. And because Dai’s code is open source, developers can integrate it
into their apps in a self-service manner. As time went on and the protocol
became more self-service — with better developer documentation and more
integration playbooks — other projects were able to build off that at scale.
The more critical metrics to track, therefore, are areas such as number of
unique token holders; community engagement frequency and sentiment; and
developer activity. Additionally, since protocols are composable — able to be
programmed to interact with and build on each other — another key metric
here is integrations. Number of and type of integrations track how and where
the protocol is used in other applications, such as wallets, exchanges, and
products.
For social, culture, and art DAOs, go-to-market means building a community
with a specific purpose — sometimes even starting as a text chat between
friends — and growing it organically by finding other people who believe in
that same purpose. But isn’t this “just a group chat” or just like traditional
crowdfunding on Kickstarter, for instance?
No, because while organizers of traditional web2 crowdfunding projects may
also have a clear purpose, they have to be much more clear about the means
of achieving that purpose top-down. The project originators typically outline a
detailed breakdown of how funds raised will be used, a clear product
roadmap, and a comprehensive timeline. In the web3 model, the purpose is
paramount, but the methods are often figured out later — including how funds
will be used, the product roadmap, and the timeline.
For instance, with ConstitutionDAO, the purpose was buying a copy of the U.S.
Constitution; for Krause House, the purpose is buying an NBA team and
pioneering fan governance of a team; for LinksDAO, it is creating a virtual
country club with a community of golf enthusiasts; and for PleasrDAO, it is for
collecting, displaying, and creatively adding/sharing back to the community
NFTs to represent culturally significant ideas and movements.
Game DAOs
Today, most web3 games, whether play-to-earn, play-to-mint, move-to-earn, or
another type, closely resemble popular web2 counterparts — but with two key
distinctions:
But unlike in web2, purpose and community lead. For instance, Loot, a game
that started with content first before moving to gameplay, is an example of
purpose and community, rather than product, driving GTM. Loot is a collection
of NFTs, each known as a Loot bag, which have a unique combination of
adventure gear items (examples include a dragonskin belt, silk gloves of fury,
and an amulet of enlightenment). Loot essentially provides a prompt — or
building block primitive — upon which games, projects, and other worlds can
be built. The Loot community has created everything from analytics tools to
derivative art, music collections, realms, quests, and more games, inspired by
their Loot bags.
The key idea here is that Loot grew not due to an existing product that users
flocked to, but because of the idea and lore it represented — an open,
composable network that welcomed creativity and incentivized users through
tokens. The community makes the product — it’s not the network making the
product in hopes it will attract a community. As such, a key metric here would
be the number of derivatives, for instance, which could be considered even
more valuable here than traditional metrics would.
GTM motions for Layer 1 blockchains and
other protocols
In web3, Layer 1 refers to the underlying blockchain. Avalanche, Celo,
Ethereum, and Solana are all examples of Layer 1 blockchains. These
blockchains are all open source, so anyone can build on top of them, replicate
or alter them, and integrate with them. Growth of these blockchains comes
from having more applications built on top of them.
Additionally, protocols can be built on top of other L1s or L2s, with the
Uniswap protocol, for example, supporting Ethereum (L1), Optimism (L2), and
Polygon (L2).
These examples and mindsets all focus on the upper right quadrant,
decentralized networks with tokens — broadly speaking, the current most
advanced examples of web3. However, depending on the type of
organization, there is still a fair amount of blending of web2 GTM strategies
and emerging web3 models. Builders should understand the range of
approaches as they begin to develop their go-to-market strategy, so let’s now
take a look at a hybrid model that blends web2 GTM with web3 GTM
strategies.
I’m providing an overview in this article to help explain the difference between
web2 and web3 go-to-market strategies, but it’s important to note that
developer-focused outreach and developer relations — including developer
documentation, events, and education — is also very important here.
Marketplaces and exchanges
Other companies in this quadrant lean on the relatively familiar-to-consumer
models of marketplaces and exchanges, such as peer-to-peer horizontal NFT
marketplace OpenSea and cryptocurrency exchange Coinbase. These
businesses generate revenue — the “take” — based on a transaction fee
(typically a percentage of the transaction), which is similar to the business
models of classic web2 marketplaces such as eBay and Amazon.
For these types of companies, revenue growth comes from growing the
number of listings, the average dollar value of each listing, and the number of
users of the platform — all of which lead to increased transaction volume,
while benefiting users in terms of variety, marketplace liquidity, and more.
GTM tactics
Now that I’ve shared an overview of key mindsets and example use cases,
let’s take a look at specific go-to-market tactics often seen in web3
organizations. These are the core ingredients, not a complete playbook, but
can still help builders entering and exploring the space understand the tactics
and options.
Airdrops
An airdrop is when a project distributes tokens to users to reward certain
behavior that the project wants to incentivize, including testing the network or
protocol. These can be distributed to all existing addresses on a given
blockchain network, or targeted (such as to specific key influencers); often,
they are used to solve the cold start problem — to bootstrap early adoption,
award or incent early users, and more.
In 2020, Uniswap airdropped 400 UNI to anyone who had used the platform. In
September 2021, dYdX airdropped DYDX to users. More recently, ENS
conducted an airdrop to anyone with an ENS domain (a decentralized .eth
domain); the airdrop was conducted in November 2021, but anyone who
owned an ENS domain before October 31, 2021, was/is eligible (until May
2022) to claim $ENS tokens, which provide holders with governance rights
with respect to the ENS protocol.
In the non-fungible token space, airdrops for NFT projects are also growing in
popularity to help with giving more people access and other reasons. One
recent notable airdrop was from the Bored Ape Yacht Club, a collection of
10,000 unique NFTs; on August 28, 2021, BAYC created the corresponding
Mutant Ape Yacht Club. Each of the BAYC token holders received a mutant
serum, allowing them to mint 10,000 “mutant” apes, and additionally a new
10,000 mutant apes became available for new entrants. Because there were
different types of serums, serums could only be used once, and since a Bored
Ape could not use multiple serums of the same tier, serums added a new
scarcity model.
The rationale behind the creation of the MAYC was to “reward our ape holders
with an entirely new NFT” — a “mutant” version of their ape — while also
allowing newcomers into the BAYC ecosystem at a lower tier of membership.
This maintains accessibility to the broader community, while not diluting the
exclusivity of the original set or having those original owners feel like their
contributions were downgraded. (Another way of addressing accessibility is
with NFT fractionalization, where an NFT has multiple owners.) The MAYC floor
price, or lowest listed price for a MAYC, is consistently lower than the BAYC
floor price, but owners essentially have the same benefits.
These airdrops were done retroactively to reward NFT holders or network and
protocol users (as was the ENS airdrop), but airdrops can also be used as
a proactive GTM motion to generate awareness for a specific project and to
encourage people to check it out. Since information is public on the
blockchain, a new project can airdrop to, for example, all the wallets using a
specific marketplace, or all the wallets holding a specific token.
In any case, projects should clearly articulate their overall token distribution,
breakdown, and plans before conducting the airdrop. There are many
examples of airdrops being used for nefarious purposes and of airdrops gone
wrong. In addition, airdrops of tokens can be deemed to be securities offerings
in the United States, so projects should consult counsel prior to engaging in
any such activity.
Developer grants
Developer grants are grants made from a protocol’s treasury to individuals or
teams who are contributing in some way to improving the protocol. This can
serve as an effective GTM mechanism for DAOs, since developer activity is
such an integral part of a protocol’s success. Examples of projects and
protocols with developer grants include Celo, Chainlink, Compound, Ethereum,
and Uniswap.
But grants can be given for everything from protocol development to bug
bounties, code audits, and other activities beyond coding. Compound even
has a type of grant related to business development and integrations, funding
any integrations that grow the usage of Compound. An example of this is their
funding of a grant that integrated Compound with Polkadot.
Memes
Viral images with text overlays are another GTM tactic for web3 organizations.
Given the complexity and breadth of the cryptocurrency ecosystem and the
short attention spans of social media users, memes allow information to be
rapidly conveyed. Memes can also signal belonging, community, goodwill, and
more in a highly information-dense way.
The NFT project Pudgy Penguins, a collection of 8,888 penguins, started due
to its meme-ability. The primary drop of the collection sold out in 20 minutes,
and the collection was featured in major media outlets, which in turn helps
mainstream such projects. The social display and community element of
“PFP” (profile picture) collections — in web3 this is coming about as NFTs
displayed as an owner’s profile picture on social media — also allow for this
virality. Twitter recently rolled out a feature allowing users to prove their
ownership of an NFT via hexagonal-shaped profile pictures linking to
OpenSea’s API.
***
So what does this all mean for web3 founders? The biggest mindset shift is
moving from planning to something more like gardening.
In web2 companies, founders not only set a top-down vision but are
responsible for growing a team and planning and executing against that
vision. In web3, founders take on more the role of a gardener, helping
cultivate and nurture potentially successful products but also setting up the
space for it all to happen. While web3 founders still set the purpose of the
organization, and its initial governance structure, the governance structure
itself might quickly lead to new roles for them. Instead of optimizing for
headcount growth or revenue and profitability, founders might be optimizing
for protocol usage and quality of community. In addition, following any
decentralization, founders must adapt to environments in which no
hierarchical power structures exist, and where they are one of many actors
championing the success of a given project. As such, prior to decentralizing,
founders should ensure that they are setting up their project for success in
such an environment.
I witnessed some of this firsthand when I was chief of staff to Tony Hsieh,
former CEO of Zappos.com, an e-commerce company now owned by
Amazon. The company experimented with more decentralized (compared to
only top-down) governance structures beginning in 2014, including the self-
organized management system known as “holacracy.” Holacracy involved a
hierarchy of work rather than of people, and had mixed results. But Hsieh
offered a useful metaphor when comparing his role as being the cultivator of a
greenhouse of plants (in the holacracy model), rather than being the best
plant. He had said he needed to be the “architect of the greenhouse” — setting
the right conditions to enable all the other plants to flourish and thrive.
Today, Alex Zhang, Mayor of Friends with Benefits (FWB), the social DAO
with a fungible token, echoes the sentiment, describing that his job “is not to set
a top-down vision” but to facilitate the creation of “frameworks, permits, and
regulations for community members” to approve and to build on top of. Where
a web2 leader would be focused on updating the product roadmap and driving
toward new product launches, Zhang considers himself more of a gardener
rather than a top-down builder. His role includes watching the FWB
“neighborhood” (in this case, Discord channels) and curating it by retiring
channels with little traction and helping support and grow channels that have
momentum. By creating a framework for these channels — and playbooks for
channel success (such as a mix of activity, clear leadership, and governance
structures) — Zhang becomes more of an educator and communicator.
So much more is possible here; we have yet to see what more is possible as
more people embrace crypto and decentralized technologies and web3
models. Traditional web2 GTM frameworks are a useful reference, and offer
some helpful playbooks — but they are just a few of the many frameworks
available for web3 organizations. The key difference to remember is that the
goals, growth, and success metrics of web2 and web3 are often not the same.
Builders should start with a clear purpose, grow a community around that
purpose, and match their growth strategies and community incentives — and
with them, the go-to-market motions — accordingly. We will see a variety of
models emerge, and look forward to observing and sharing more here.
Thanks to Justin Paine, Porter Smith, and Miles Jennings for their
contributions to this article.
Posted February 4, 2022