Re-evaluation of the RadicleDAO Stack

Thanks for taking on this initiative @shelb_ee !

After joining a few calls, I had some thoughts on criteria for assessing these tools. These are more general around tools (not governance specific) and in no particular order:

  1. Maintenance: Who will be responsible for managing the business relationship / maintenance of the tool? How difficult is it to maintain? What needs to be maintained by Radicle vs their team? How hands on or hands off is the team in managing ongoing features or development?
  2. Product: If they are working with other teams, other than the number of DAOs they’re working with, do they have other metrics for how their product improves xyz? For example: What is the retention of DAO teams using their product? How long does it take for orgs to set up and get it running? What are some other features have been requested? What other features are in the pipeline? Is there a timeline for that?
  3. Product Usefulness: Do we need any special features or requests? How long will that take to build? Will it cost us extra?
  4. Costs: How much does it cost to use their tools / product? How does that scale (ie. if it’s charged per user)? What kind of changes will Radicle need to do to adopt to the tooling? Is it possible to plug into an existing flow (ie. content is coming from git based repo)?
  5. Values Aligned: Can this be open sourced? In case the company fails, does the interface and/or data live with Radicle?
  6. Startup Company Risk: How new is their product, have they found PMF, how likely is it that their company/project will survive? If they pivot their product, how will it affect Radicle?
1 Like