Thanks for the vote of confidence, @Larry_Cucumber! Personally, I am (as @chimaera likes to say) willing and able to go all the way and put myself at the service of the project and the community. I reckon investing in growth is the right approach for Pickle at this point, as there’s been proof of product-market fit, we need to work on our acquisition, activation, and retention on an ongoing basis. We have a loyal and strong community that wants to contribute, as they’ve shown in times of progress as well as hardship. Basically …
As far as a suitable budget, I think at the moment the scope would be my role rather than a budget for compensation of the many community members who deserve or require it to commit time in development, community-building, and evangelism (i.e. memelords). I think for any role, good market-based compensation is a proper starting point based on the demands of the role. For this role of leading the growth efforts in a protocol of Pickle’s profile, at its current juncture, I am suggesting $2,000/week which works out to the $104k/year mark. I think splitting that between stables-Pickle say 2:1 would align incentives with the community as well as vesting. Think of muh family …
These funds will go to:
- Developing and managing a Growth process: an iterative, data-driven approach to reach the organization’s goals by experimenting and compounding on what works, open to the whole community to participate in. This also involves goal-setting that is product-oriented and informs the product roadmap: its strategic, technical, and UX components.
- Managing design, engineering, and marketing resources that are specifically focused on engaging the community of users. These resources are deployed in tasks ranging from optimization of a certain aspect in the Growth funnel (e.g. search engine optimization for awareness) or delivering user-facing collateral like website pages, or content in a publishing platform, or engagement in social media platforms.
- Conducting research into the usability, accessibility, and scalability of the product as a whole, through direct interaction with its users.
- Contributing to the management of the communications, partnerships, and community of the protocol.
- Contributing to the development and management of the documentation of the protocol, its governance process, and its brand identity.
As you can probably guess, eventually this will take more than one man in the great landmass of Asia, which is why it is important to get set up with the process so we can start articulating what we aim to do in each sprint before the community can get involved in a meaningful way.