Although I’m not sure about stat: “3 similar DAOs have support budgets that are publicly available and all offer similar support services for ~$4,500/month vs. ShapeShift’s $28,500/month.”
Hey , I’ll show where you can see the data itself and with links to the daos.
Tyler:
A look into 20 other comparable services, protocols, and DAOs has been collated here for a point of reference.
I have also screen snipped the file incase you dont want to dig, and included the links as well.
Thanks for sharing these links. It wasn’t that I didn’t see them or review them, it’s that I don’t know if it’s a fair comparison or a claim I agree with (“3 similar DAOs”). One reason being, the Uniswap support proposal discussion is from 2 years ago. I imagine the cost for support has increased since then with their demand, and they still aren’t offering the level of support I think their stature of product deserves (probably an opportunity to offer them some services 1f609 ) -
Beyond you being influenced by a number of people (, and ),
please remain within the realm of accuracy. I have not “influenced” on this at all. I was unaware of his initiative/viewpoint on this matter until it was already in proposal form. I learned about it after you did, in fact.
Perhaps you could avoid all the character insults against Tyler, and debate the data and analysis in his post?
I’m still reviewing this data/analysis and have not formed an opinion on the matter yet.
I’d like to request that we keep moving forward with the complex and epic responsibility of running the ShapeShift DAO. In order to move forward here are 3 requests I’d like to make for the next 48 hours:
A new forum discussion around the different types of levels of support the community and contributors want to offer for the Customer Support Workstream to review and consider as we continue to evolve our services to fit the needs of our product offerings. With the goal of defining a few styles by the end of the month to work with.
As promised in the recent budget cut report, an additional discussion will take place within the Customer Support Workstream to manage the current staffing/responsibilities at the end of July. This has always been common practice and will continue to be as we move forward. (this isn’t quite an action for the next 48 hours, but instead an acknowledgement)
While the intentions of the Ops proposal were ultimately to save money for the ShapeShift DAO, I would like to see both sides of this debate succeed by saving money, but also offering the best solution for our product, users, and culture. I, too, want the best solution for this current era of our organization. “The best solution” should be discussed in the new forum post before we put forth permanent changes that could have lasting effects on the DAOs product, personnel, culture, and reputation.
Through this discussion we can hopefully piece together some suggestions on “styles” of support that best suit this stage of our DAO’s life. Overall, I do believe the style of team we have now is quite fitting for the complex needs of our product offerings and the constant changes we always see and will see in the coming months. The talent and tribal knowledge we have during evolutionary times like this should be protected and celebrated.
I would like my 6.5 years of customer support experience to be trusted because of the solid, happy team I’ve built and managed, as well as our goal-hitting history.
As a reminder, I will be leaving on maternity leave within the next 4-5 weeks. I will have a full report on who will be in charge of what within the workstream while I’m away. I will not be participating in any debates or discussions while I am away. It is important to me that this is respected. It’s also crucial for current contributors, to future talent, our culture, and the DAO’s reputation to see my leave managed successfully.
I’m happy to honor the requests that you have made above. Thank you for remaining civil and respectful in this heated discourse.
I look forward to contributing to a new forum thread aimed at measuring and refocusing our services provided to find the right balance of meeting the needs of our users, and justifying the stable coin emissions for the services provided to do so. I believe that we both are very close in our desires for optimization and DAOing it right, and I hope collaboration is a way to continue to address some of the insights covered in the data and research of this proposal.
My intentions with this proposal have always been around what I and my workstream can do within our power to make the most meaningful impact to our bottom line. , we’ve both been through bear markets with ShapeShift before and know how deep the knife has had to go in the past to save the organization. Based on the feedback from the community so far, I’m not sure if the exact same playbook needs to be followed to meet this bear market now with Support and Operations.
I hope we can continue to be honest about what tools we have at our disposal in case our saving measures are lacking in keeping a runway beneath us. This has been one of my deepest fears and motivators in developing this data collection and proposal presentation. If we all are happy for 6-8 months and then close up shop cause we ran out of money we failed the DAO and all FOX holders.
The DAO has become unnecessarily hostile over the last week or two and I have to recognize my part and this proposals part in that. I never wished for this to be received as anything more than a data driven approach to analyzing spend and measuring it relevancy to our product suite, customer base, and dire market conditions.
This proposal while filled with data and a suggested solution, was presented to start the discussions and not be the only possible solution. It is not immune to the process of being changed and reshaped with community feedback.
I hope we can work together , both in a new forum post and in future calls before your leave so we can realize our full potential and survive to the next bull and beyond. Your requests move the discussion forward and I greatly appreciate that.
Let’s close this thread down and start a fresh conversation built around productive solutions.