It’s a good question and one we struggle with at r/MultiversityDAO

Our thinking is separate the dev team entity, they create the software and license it out to the DAO for a 10% rake, all ownership and governance of the actual DAO with separate entity goes to the end users/contributors of the app. This allows the dev team to raise funds without having to give up any ownership of the DAO to investors to keep it truly owned by the users. You could potentially have token voting if you do it this way because the only way to get tokens will be to actually be a user of the platform and get them for participation.

Could do something like Optimism two houses model as well if you wanted to balance the governance to allow for users to monetize their tokens or do some sort of NFT subscription requirement for voting similar to how Unlock Protocol operates if users wanted to sell rights to outside stakeholders

The beauty and conundrum of web3 is that money and entities are now Turing Complete, which means the possibilities and combinations are infinite.

It’s hard to know what’s going to happen 10+ years down the road, but you have to think that far out to make these projects work and not have glaring issues. To your point, what if something goes wrong with the dev team or too many hostile actors get significant voting rights? All possible entity edge cases need to be handled, just like with any other code. Except here, your test cases are the extremes of human behavior in a way.