Growth CU July Community Update

Getting together in person, and enjoying a well thought and smoothly executed offsite led by Ange, Abbey, Sally, and Louie sparked conversations around cross team alignment and most of all how can we hold each other accountable without the feeling of being under a corporate structure. We loved meeting in person, and looking forward to meeting the team again.

Today we are using a slightly new format after gathering feedback from different teams. We will share some of our high level objectives for the next quarter, and talk about the actions we are taking towards them.

Radicle Code Collab

  1. Recruitment - Helping find 4 new core developers that join the Link team. Nassar Link
  2. Research + Feedback - Bring feedback from initial segments on use cases and demand for SS code collaboration tooling. Also, capture and share issues and blockers as developers try to use Radicle. Lucas, Matt, Nassar


  • Recruitment: Nas had a few good conversations and will be investing more time in sourcing more people.
  • Research + Feedback: We finalized the Early User Program which consisted in getting Developer DAOs interested in decentralized and self-sovereign code collaboration to test our stack. The ask was to get a team to install the CLI, bring team members to code collaborate and share feedback via discord and in 4 different calls. We built a pipeline of around 50 people, out of which 27 started the process, and 13 finalized. All of these people shared feedback that we put on a GitHub Instance in which the team could analize and decide what to do.
    • Main areas of feedback where:
      • CLI instalation process needed some improvements (which based on my understanding, the team has already fixed)
      • Bug Reports
      • Documentation
      • Ideas around discoverability and mirroring repos.
    • Documents:
    • Next Steps:
      • After delivering this feedback and a few conversations with Alexis, we understand that the team is working hard on commenting and other features to be able to dog-food radicle (use it internally).
      • We agreed that Growth will continue reporting bugs when we get them, and exploring the FOSS community to understand how people within this vertical would prioritize the product roadmap.
        • The FOSS community came back into the radar after an SFC blog post encouraging projects to Ditch GitHub. A summary of those events and how this impacts us can be found here:Radicle and the FOSS community [synopsis]
        • We created a with 40 projects, and started contacting people in them. After they respond, we share theseQuestions doc with the intention to understand how they would prioritize certain features and how they currently collaborate.

Drips Protocol

  1. Sales - Drive integration of protocol by 10 applications - Luke, Nassar, Matt Drips
  2. Research + Feedback - Bring feedback from initial segments of the market on use cases and demand for protocol + issues and blockers in protocol and tooling around it. This can be shared in the unstructured format as currently done via the drips pipeline . Also more structured and aggregated feedback around each new segment or release. Nassar, Matt, Luke
  3. Awareness - Grow awareness of the protocol by supporting marketing contributors - 5 mentions in content per month is our starting goal. - Maddy, Nassar Marketing


  • Research + Feedback: The Growth team worked on Drips - v0.2 and DAOs, which is a document outlining our learnings from conversations with different DAOs and two main user personas: DAO operators (treasury managers, team leads) and Contributors (Full-time, variable time, grant/bounty-funded). The outcome was a protocol overview, and where we think the Drips protocol can excel. This was also a document that helped the growth team organize its ideas, and lead to interesting conversations with the drips-dev team. Our goal is always to gather information, organize it, find patterns and share with the team.
  • Sales: Drips is getting closer to being deployed on Testnet (in August) with a subgraph and SDK that are somewhat mature and hopefully on Mainnet (in September).
    • The North Star is to onboard 10 DAO Tooling platforms by the end of 2022. As in any launch, the road will be bumpy, but we have a team that went through this, and is getting prepared to do it again. We will focus on the following aspects to get started:
      • Create a pipeline of projects - based on a target list we already have.
      • Pitch and talk tracks including objections and main selling points. We started the reachout via twitter.
      • Create templates and sequences to do this at scale
      • Coordinate with Dev-Rel and Marketing on material that will support top of the funnel and onboarding processes.
      • Find a technical person that will help with onboarding - We have a few candidates.

Dev Rel Team

  1. Recruitment - Outreach and onboarding of high-quality dev rel talent. One dev rel lead, one dev rel core team contributor, and then 2-4 community contributors. - Cami, Nassar
  2. Strategy and formation support - Help team form and build strategy to start growing awareness, bringing feedback, and supporting developers as they work to build on Drips. The output being an established team that’s working directly with the DAO with clear objectives and budget. Cami, Nassar Community


  • Recruitment: The team is now almost ready to start creating content. The past month has been around building the team, which now consists of Cami, Ruth, MG, and Nas, and there are two new contributors that will be starting this month.
  • Strategy: Cami, and Nas have been working on a strategy that can be found here. The next steps are to start building a community of developer educators that serve the ecosystem and support radicle teams to attract, educate and support developers as they try use our tools.
  • Nas presented at “The Growth Summit” what’s our strategy to build Open Protocol Ecosystems. Below you can find the different talking points.
    • Engage Developers through mediums like: Workshops, Hackathons, Podcasts, etc.
    • Focus on developer education and experience by providing top class: Docs, tutorials, support, SDKs and more
    • These two things will lead to ideas, and we will incentivize builders to convert them into products through grants, service, partner network and more.
    • We will then incubate + fund them
    • Finally partner and do token swaps with them.

Ecosystem Cohort Programme

  1. Setup beta support programme - Building structure and programmes for supporting developers and entrepreneurs that we feel would add value to our ecosystem. Initially, this will probably be a structured programme that supports teams building DAO tooling, developer tooling, and open source software at each stage of their development. more details outlined here. Output should be having a cohort programme setup that we take out to our community. Nassar, Ruth, Maddy Grants programme
  2. Supported Projects - aim to complete a single cohort of 10 projects taken through our cohort programme. Nassar, Ruth, Maddy gran


  • Setup Strategy for Beta Support Programme: Ruth, Lindquest, and maddy have been building a strategy for supporting entrepreneurs we want building in our ecosystem from prototype to funding. They should have a first draft of strategy read in the next week or so. Ruth worked on building out the entrepreneur support programme at UCL, maddy is building a dao for educating VCs on web3, Lindquest has been working across web3 and currently works with Animoco as well as advising a few incubators. Excited about what this team do together.


  • Funded 3 months of new Dev-Rel team with multisig for cami to coordinate funds for Dev-Rel team and bounties.