Hey! As someone who has been working on the DAO app you mentioned with the Virto team, I can tell you we made lots of efforts to reach an audience interested in this kind of DAO tooling, but we kept running into the same dead end.
At least for us, the issue was that we weren’t solving a real problem. We were just adding complexity with our unfinished UI, which stayed that way because we couldn’t get real organizations to actually want to use it.
It could be an awesome tool to manage organizations, with all the actions you mentioned (I’d especially highlight identity, treasury management, socials, and storage, since those were exactly the features we were planning to add, along with decision-making). Yet we weren’t able to find the right audience.
As for project teams, Polkadot already provides vesting to schedule transactions.
If the flow is:
-
Communication via Discord
-
Getting funds from Kusama/Polkadot governance
-
Using vesting to manage payments
Then there’s not really a problem to solve for those project teams.
But as I say this, I have another thought. This year, I went to an event at Crecimiento, a coworking space in Argentina mostly attended by blockchain-related people, and one key insight I got was how slow medium-to-large companies are when it comes to making decisions.
As I’m also a lawyer, this idea came to me:
A system where decisions made on-chain could have the force of law for the organization.
That way, to make a decision they’d only need to:
-
Submit it on the forum where all members with voting rights have access
-
Set a voting period
-
Once voted, that decision becomes binding for the organization, meaning they must carry out what was approved in the proposal
-
The proposal automatically executes (e.g. if they need to buy something, the funds are automatically sent; if they need to pay someone, that transaction is automatically made)
Of course, you’d still need to find people who actually have this problem, who want to test the product, and the funds for the team to build it.
I’m also not sure how beneficial this would be for the ecosystem, whether it would bring more or less traction, and that’s something to consider when asking for funding.
Virto didn’t continue down that path mainly due to a lack of funding and clear insights to justify it at the time. But personally, I still, it’s a direction with strong potential, especially if there’s a group of users genuinely interested in testing and shaping it before the project starts.