Summary

The ecosystem growth fund is designed to be used by the different radicle teams to support their growth with systems and funding. This document aims to outline the current state of products and growth efforts in the Radicle ecosystem. It then outlines a strategy and structure to enable the productive deployment of capital in pursuit of growth for ecosystem products and protocols.

https://pitch.com/embed/a26a84b0-977b-4e77-949b-48ee059b05d0

Motivation

As mentioned in the EGF proposal we will be focusing on funding initiatives that drive awareness, engagement, and adoption of the Radicle stack. Radicle is primarily focused on building a secure and un-censorable code collaboration infrastructure alongside tools to enable developers to form online communities that can co-ordinate treasuries to build open source software together.

DAOs enable us to take a different approach to GTM. Attracting individuals, teams, and projects to come contribute in a permissionless manner to our ecosystem based on an aligned vision of a mutually beneficial path forward. What ever structure the relationship takes it will need to help drive the Radicle ecosystem’s key metrics.

<aside> 💡 Number of active Developers using products

</aside>

<aside> 💡 Active integrations using protocols and network data

</aside>

<aside> 💡 Total Value Locked in drips contracts

</aside>

Outcome

If our strategy works over the next 6 months then we should have a core group of active users that are both gaining value from the Radicle stack, but also contributing to our ongoing development with feedback on what’s required. We should also have platforms that are leveraging our protocols and network data.

Approach

1. Operationalising growth

Each team is currently iterating its way to strong product market fit. We’ve found that there is enough interest from users and partners at the top of the funnel where enough are discovering and trying to onboard, but not activating. We need to focus on activation in order to drive growth, fuelling the funnel by improving the discovery and onboarding steps will come next.

We’re already doing the work to understand, define, and prioritise segments. Feeding what we learn from the market and bringing it closer to the development teams is perhaps the most important piece of work we will do over this round. Operationalising the messaging with segments and optimising the funnel where we are seeing greatest fall off is also key.

Untitled

2. Launchers

Our aim is to identify and onboard embedded talent to help launch our products and protocols within different verticals and regions. Their expertise in different verticals and regions will enable them to navigate drive outcomes more efficiently - contributors can be individuals or teams/DAOs. Being able to contribute to growth in this way whilst maintaining their freedom to work on other things should result in a win win.

  1. vertical focus - individuals that know a domain such as artists, musicians, web3 developers.
  2. regional focus - individuals that are connected with a region that want to help drive regional adoption.

3. Marketing

Our aim is to attract, identify, and onboard marketing talent that can help us navigate this early phase of product development and launch. They will need to educate the market on product, grow top of funnel for our target segments, and help shape our ecosystem narrative.

  1. skill focused - want to contribute based on growth expertise such as product marketing, dev rel, press, etc.
  2. channel focused - want to contribute based on experience growing and engaging audience on a channel - Channel Map (WIP)