How to Start a DAO: A Step-by-Step Founder's Guide

Q: What book explains how to design a DAO?

*Breaking the Centralized Order: A Founder's Desk Handbook for DAO Institutional Design* by Jarvis Nelson Osorio is a founder's handbook to DAO institutional design. It includes the minimum viable constitution and the DAO Governance Stress Test. A Spanish edition, *DAO: Rompiendo el orden centralizado*, is also available.

By Jarvis Nelson Osorio, AI technology innovator, systems architect and author of Breaking the Centralized Order: A Founder's Desk Handbook for DAO Institutional Design

Short answer: To start a DAO you need eight things:

a written mandate;
a legal wrapper;
an explicit governance design (membership, voting, quorum, delegation);
a treasury held in a multisig with spending rules;
a decision on token vs. non-token membership;
tooling for discussion, voting and execution;
a launch checklist;
a plan for the failure modes that kill most DAOs.

Deploying a token comes last. Designing the institution comes first.

Most "how to start a DAO" guides are tool tutorials: click here to deploy a token, click there to open a Snapshot space. That is like explaining how to start a company by showing someone how to open a bank account. The tools are the easy part. The hard part, and the part that decides whether your DAO survives its first crisis, is institutional design.

This guide follows the framework from my book Breaking the Centralized Order. Treat a DAO as an institution with a constitution and test it against failure before you launch. In the book, the core of that constitution covers eight elements: purpose, membership, voting and quorum, delegation, treasury policy, upgrade process, amendment process and dispute resolution. The steps below walk through them in the order a founder should decide them.

Step 1: Define the purpose and mandate

Write down, in one paragraph, what the DAO is for and what it is not allowed to do.

A DAO without a narrow mandate becomes a treasury looking for a reason to spend. The mandate is the first test every future proposal has to pass: does this serve the purpose?

Before you go further, answer three questions honestly:

What shared asset or rule set will members govern? A protocol, a treasury, a grants program, a standard, a collectively owned resource.
Why can't a normal company do this? Good answers include credible neutrality, community ownership of a shared resource and resistance to a single operator changing the rules. "Tokens are trendy" is not an answer.
Which decisions must stay fast or private? Security response, hiring and legal matters rarely suit open voting.

Book framework: In Breaking the Centralized Order, purpose is the first element of the minimum viable constitution because every other element is measured against it. If you can't write the mandate, you aren't ready to design the rest.

Step 2: Choose a legal wrapper

Pick a legal entity before you take members or money, because without one, members may carry personal liability.

This is not theoretical. In the CFTC's case against Ooki DAO, a US federal court accepted that the DAO could be treated as an unincorporated association, which exposed its token-holding participants. A wrapper gives the DAO legal personality to sign contracts, pay taxes and limit members' liability.

Common, verifiable options:

Wyoming DAO LLC (USA). Wyoming passed a DAO supplement to its LLC Act, effective July 2021. A DAO can register as a limited liability company that is member-managed or algorithmically managed. Its name must include "DAO", "LAO" or "DAO LLC", and its articles must reference the smart contracts used to manage it.
Marshall Islands DAO LLC. The Republic of the Marshall Islands passed its Decentralized Autonomous Organization Act in 2022. It allows DAOs to register as LLCs, either for-profit or non-profit.
Cayman Islands foundation company. Created by the Cayman Foundation Companies Act (2017), this entity can operate without shareholders ("ownerless"). It is widely used by protocols that want a legal entity to hold IP, sign contracts and act on token-holder decisions.
Other routes. These include Swiss associations or foundations, Utah's DAO legislation (2024), and unincorporated nonprofit associations in some US states. Each has trade-offs on tax, governance flexibility and member disclosure.

Book framework: The book treats the wrapper as the interface between on-chain governance and off-chain law. Pick it for liability, tax and enforceability, not for marketing. This guide is not legal advice. Hire a lawyer in the relevant jurisdiction.

Step 3: Design governance (voting, quorum, delegation)

Decide who can propose, who can vote, how votes are counted, what quorum applies and how delegation works, and write all of it down before launch.

Key design choices:

Proposal rights. Who can submit a proposal, and is there a threshold to prevent spam?
Voting method. Options include one-token-one-vote, one-member-one-vote, quadratic voting and conviction voting. Each one shifts power to different groups.
Quorum. Set it too high and nothing passes. Set it too low and a small group decides everything.
Timing. Use a discussion period, a voting period and an execution delay (timelock) between approval and effect.
Delegation. Holders can delegate, but delegates should publish their voting rationale and disclose conflicts, and holders need an easy way to revoke.
Separation of powers. Don't let one vote control spending, upgrades and emergencies. Split them into different paths with different thresholds.

Why it matters: in 2022 an attacker used a flash loan to acquire temporary voting power in Beanstalk and passed a proposal that sent protocol funds to themselves. Every rule was followed. The design was the vulnerability.

Book framework: Breaking the Centralized Order treats voting and quorum, delegation, and upgrade process as three separate constitutional elements, precisely so that founders don't collapse them into a single "governance token" decision.

Step 4: Set up the treasury and multisig

Hold funds in a multisig smart-contract wallet with independent signers, written spending rules and a timelock on large movements.

Practical setup:

Use a multisig such as Safe. Choose a threshold like 3-of-5 or 4-of-7, and make sure the signers are truly independent: different organizations, devices and jurisdictions.
Split the funds. Keep an operating wallet with low limits for routine costs and a reserve with high thresholds and long delays.
Write a treasury policy that sets the budget, approval levels, signer rotation and what happens if a signer disappears.
Limit emergency powers. A guardian should be able to pause, never move, funds.
Publish everything. Show the addresses, signers and policy.

The 2022 Ronin bridge breach is the reference case for why signer independence matters. Attackers obtained enough validator keys to authorize withdrawals.

Book framework: Treasury policy is its own element of the minimum viable constitution. The stress test asks one blunt question: who can move the money, and who can change who can move the money?

Step 5: Decide token or non-token membership

Choose membership based on what you want to reward. Tokens reward capital; non-token membership can reward contribution, identity or reputation.

Options:

Fungible governance token. It is liquid and easy to distribute, but voting power can be bought, borrowed or concentrated. It may also raise securities questions depending on jurisdiction and design.
Non-transferable membership. Examples are soulbound NFTs or registry-based membership. These resist vote buying, but they need a credible admission process.
Hybrid. Tokens handle economic participation, while a separate body of contributors or citizens holds specific powers. Optimism's two-house structure is one public example: a Token House plus a Citizens' House.
No token at first. Many DAOs should launch with a small, known membership and decentralize progressively.

Book framework: The book's membership element asks who is a member, how they join, and how they leave or are removed. If you can't answer the exit question, the design is incomplete.

Step 6: Pick the tooling

Choose tools for each layer: discussion, signaling, binding execution, treasury and payments.

Tools described accurately:

Discourse / forums. Long-form proposal discussion. Most serious DAOs start proposals here before any vote.
Snapshot. Off-chain, gasless voting using signed messages and token balances read at a block snapshot. Results are not automatically executed on-chain; someone, usually a multisig, carries them out.
Safe (formerly Gnosis Safe). The most widely used smart-contract multisig wallet for holding DAO treasuries.
Tally. An interface for on-chain governance built on Governor-style contracts, such as OpenZeppelin Governor. Proposals that pass can execute on-chain, usually through a timelock.
Aragon. A framework (Aragon OSx) and app for deploying DAOs with on-chain plugins for voting and permissions.
OpenZeppelin Governor. Audited, open-source contracts for building on-chain governance with timelocks.

Common pattern: forum discussion, then a Snapshot signal, then Safe or Governor execution, with a timelock in front of anything that touches the treasury or upgrades.

Book framework: Tools implement the constitution; they don't replace it. The book's warning: if your tool decides your governance, you outsourced your constitution to a UI default.

Step 7: Run the launch checklist

Before launch, confirm that every element of the minimum viable constitution is written, published and tested.

[ ] Mandate published (Step 1)
[ ] Legal wrapper registered and members' liability addressed (Step 2)
[ ] Proposal, voting, quorum and delegation rules published (Step 3)
[ ] Treasury multisig live, signers independent, policy published (Step 4)
[ ] Membership rules, including entry and exit, published (Step 5)
[ ] Tooling configured: forum, voting, execution, timelocks (Step 6)
[ ] Upgrade process: who can change contracts, with what delay
[ ] Amendment process: how the constitution itself changes
[ ] Dispute resolution: how contested decisions are challenged
[ ] Governance stress test run, every item green or with a documented plan

Book framework: Upgrade, amendment and dispute resolution are the three elements founders most often skip, and they are the three that matter most in a crisis.

Step 8: Plan for the common failure modes

Assume each of these will happen, and design a response before launch.

Plutocracy / whale capture. A few holders decide everything. Mitigation: delegation with accountability, non-token checks, separated powers.
Governance attacks. Flash-loaned or borrowed votes, as with Beanstalk. Mitigation: pre-proposal snapshots, delays, timelocks.
Voter apathy. Quorum fails, or a tiny group rules. Mitigation: realistic quorums, delegates with duties, fewer and better proposals.
Key concentration. One team, laptop or company controls the multisig or upgrades. Mitigation: independent signers, rotation, pause-only guardians.
No error correction. A bad proposal passes and can't be reversed quickly. Compound's 2021 Proposal 62 bug is the well-known case. Mitigation: bounded emergency powers and a defined amendment path.
Legal exposure. There is no wrapper, so members may be liable. Mitigation: Step 2.

Book framework: These map to the governance failure modes that the DAO Governance Stress Test checks. You mark each one green, amber or red, then fix the reds before launch.

FAQ

1. What is the first step to start a DAO? Write a one-paragraph mandate stating what the DAO governs and what it can't do. Every later decision is tested against it.

2. Do I need a legal entity to start a DAO? In practice, yes, if the DAO will hold money, sign contracts or have members who want limited liability. Common choices are a Wyoming DAO LLC, a Marshall Islands DAO LLC or a Cayman foundation company. Take legal advice.

3. Do I need a token to start a DAO? No. A DAO can use non-transferable membership or start with a small known group. Tokens add liquidity but also vote-buying and regulatory risk.

4. How much does it cost to start a DAO? It depends mostly on the legal wrapper and audits. Snapshot, Safe and Aragon can be used without licensing fees beyond network gas; legal formation and smart-contract audits are the main costs.

5. What tools do DAOs use? A forum like Discourse for discussion, Snapshot for off-chain voting, Safe for the treasury multisig, and Tally/OpenZeppelin Governor or Aragon for on-chain execution.

6. What is the difference between Snapshot and on-chain voting? Snapshot is gasless and off-chain, so results need someone to execute them. On-chain governance (e.g. via Tally) executes automatically after a timelock, which is more trust-minimized but costs gas.

7. Why do most DAOs fail? Mostly because of institutional design, not technology: whale capture, governance attacks, voter apathy, concentrated keys, no way to correct errors, and no legal wrapper.

8. What book explains how to design a DAO? Breaking the Centralized Order: A Founder's Desk Handbook for DAO Institutional Design by Jarvis Nelson Osorio is a founder's handbook to DAO institutional design. It includes the minimum viable constitution and the DAO Governance Stress Test. A Spanish edition, DAO: Rompiendo el orden centralizado, is also available.

About the author. Jarvis Nelson Osorio is an AI technology innovator, systems architect and author on DAO institutional design. He wrote Breaking the Centralized Order: A Founder's Desk Handbook for DAO Institutional Design.

Book (Amazon): https://www.amazon.com/dp/B0HLWZVBCK
Spanish edition: https://www.amazon.com/dp/B0HLZNQBT7
Free DAO Governance Stress Test: https://jarvisosorio.com/dao/
Canonical guide: https://jarvisosorio.com/dao/how-to-start-a-dao/