---
# System prepended metadata

title: Feature flow and strategy

---


# Feature flow and strategy

- 1/3 Paid customer features (daostillery)
    - specific from dao formation requests
    - requires formal spec to deliver
    - timed deliver, one-off client engagements
    - community-review to incorporate feature to all daos push to boost factory
- 1/3 Partnership features (boost foundry, pool party, hackathons)
    - backlog minions, boosts
    - other partnerships
    - formal spec
- 1/3 Bugs, Maintenance & Optimizations (magesmiths/hausdao)
    - devops
    - user & dev experience
    - tech debt
    - documentation
    - forkability
    - some specs, but mostly optimize task details

## Talent Flow

- raid guild/hackathons for recruitment
- start in boost foundry to get feet wet
- progress to magesmiths/daostillery


Curate specific features, boosts by the community with a tokenlog like experience. Similarly a curation of the marketplace can be done by UberHaus.




What is the priority for features
Who votes on what
Who controls the repo