---
tags: Sudden Dapp, Public Haus, DAOhaus
---

# FAQ: Sudden Dapp

**Q:** **Why not just pay an app dev team $7500 every month?**
**A:** This system has the added benefit of revealing what the community wants to build and who should build it. Sudden Dapp includes a system that tightly couples building, promotion and community engagement.

Everything is coordinated so that people receive the right information at the right time.

**Q:** **Why not just do a hackathon?**
Hackathons are essentially bribing a large group of devs to try out a stack by paying the top 3.

Sudden Dapp does a lot more: We crowdsource ideas from our community, we spotlight three dev teams' journies to dapp completion, we create a governance rhythm of regular community engagement and we document and broadcast the whole process, creating a huge learning opportunity for everyone involved.

The end result is much more tangible and useful for PublicHAUS.

**Q:** **Isn't this a lot of governance overhead?**
**A:** Without a system like this one, the underlying complexity and overhead is still there, it is simply left unaddressed.

This game creates a regular governance rhythm and a simple and fun way to interact with PublicHAUS.

**Q:** **How long will the game take to set up and finish?**
**A:** We reserve 1 month to set up the guides and voting tools and then the game is played over 4 months.

**Q:** **Where do the builder teams come from?**
**A:** We will start calling for builders to sign up early and often. We expect most to be in our network already and also to pull in new builders from adjacent dev communities.

**Q:** **How are you handling the ops and logistics?**
**A:** We've given this a lot of thought and we have a role system and calendar checklist that covers all the details. We plan to use Hats to set up revokable roles and permissions. This will allow the game to exist without us if needed.

Here's the overview: