{"id":461,"date":"2022-11-03T17:56:05","date_gmt":"2022-11-03T17:56:05","guid":{"rendered":"https:\/\/www.growth-dao.com\/?p=461"},"modified":"2022-11-28T15:06:43","modified_gmt":"2022-11-28T15:06:43","slug":"web3-go-to-market-strategy","status":"publish","type":"post","link":"https:\/\/www.growth-dao.com\/2022\/11\/03\/web3-go-to-market-strategy\/","title":{"rendered":"7 Steps to Web3 Go-to-Market Strategy Success"},"content":{"rendered":"\n

In the new era of Web3, there are many new, shiny Web3 growth levers to push and pull. To add to that, there are some old marketing tricks and strategies that simply won’t work in this new world. Here I walk you through how to launch a successful Web3 go to market strategy for 2022 and beyond.<\/p>\n\n\n\n

What is <\/em>a Web3 go-to-market strategy anyway?<\/h2>\n\n\n\n

In its simplest form, a Web3 go-to-market strategy is a plan of action as to how you take your Web3 project from ideation through to scaling into the market. It\u2019s worth noting there are different structures Web3 projects can choose from. Some remain relatively centralised, others decentralised. Some utilise tokens, while others opt not to. So, of course, some of the ideas I mention below are not going to be applicable to each and every Web3 project. <\/p>\n\n\n\n

Some people have been throwing around \u201cgo-to-community\u201d as an alternative to go-to-market, but frankly, I\u2019m not a fan of that term. Firstly it just sounds weird. Secondly, how can you \u201cgo-to\u201d community? It doesn\u2019t even make any sense. The logic of building a community as part of your Web3 go-to-market strategy is certainly solid, I\u2019m just not convinced on that term. <\/p>\n\n\n\n

Our go-to-market steps to success: Web3 style<\/strong><\/h2>\n\n\n\n

Note: the steps I outline below are not necessarily going to be implemented in the order you read them in. This order assumes the Web3 project starts relatively centralised with some key decision makers and a bit of investment. But, other projects may start with (3) and already have an early community launched where they might then go and vote on steps (1) and (2). Also, some people might rejig when the right time to build the tech stack, or even build it in parallel to other steps. <\/p>\n\n\n\n

1. Define the why <\/h2>\n\n\n\n

Whether it\u2019s a Web2 or Web3 project there must be a clearly defined WHY. This goes back to Simon Sinek\u2019s thesis \u201cstart with why\u201d. Any project must have an underlying motivation and reason for why they want to change the world. <\/p>\n\n\n\n

This exercise should start with your vision, and how you see the world in the future. Trying to put actual numbers and being detailed about this future is best. It should be something you and the project collaborators can actually visualise. From this, you can build out your mission statement, which is the underlying reason you are doing this project. This statement will outline at a high level how you will achieve the vision you\u2019ve set out.<\/p>\n\n\n\n

Once you\u2019ve defined your vision and mission it\u2019s going to be important to outline specific goals you want to achieve with the Web3 project. This will likely come in the form of targets, broken down across time that will help you to keep a finger on the pulse of how you are progressing based on what you initially set out.<\/p>\n\n\n\n

During this strategic phase of your go-to-market it\u2019s also going to be important you do plenty of customer research to validate your vision of the world. You don\u2019t necessarily need people to buy into the future vision, but you need to validate whether people feel a pain point strongly enough they will join your project (or I should specify join and pay in some way). This means you need to really understand your target audience and you need to thoroughly research the pain point you are trying to solve for them. This work will help you build a product or service based on real-life research into a real-world problem.<\/p>\n\n\n\n

A final, but important part of this step is to build out your initial, hypothesised value proposition. It\u2019s hypothetical because this could change over time. You might speak to more potential customers in your target audience and realise your messaging was off, or you might realise adoption of the product or service wasn\u2019t where you were expecting, so you might end up pivoting your proposition. This can be fluid, but it\u2019s important to outline what you think is your value proposition from the get-go. <\/p>\n\n\n\n

From the value proposition statement and your customer research, you can start to build out your positioning strategy, so where you sit compared to other competing solutions. As a quick side note, don\u2019t just think of direct competitors, like Coke vs. Pepsi, this of tangential competitors like coffee, sweets or other snacks.<\/p>\n\n\n\n

In summary, in this first stage I\u2019d recommend planning:<\/p>\n\n\n\n