Skip to content

Proposal Writing for DAOs

Guide to proposal writing for daos


How to write proposals that pass and actually get implemented.

Section titled “How to write proposals that pass and actually get implemented.”

Most rejected proposals fail not because the idea is bad but because the proposal is unclear, poorly scoped, or doesn’t address community concerns.

Clear, specific, descriptive. “Fund Community Garden Phase 1” not “Garden Stuff.”

What are you proposing? What will it cost? What will it achieve?

Why is this needed? What problem does it solve? What evidence supports this?

Exactly what will be done. Deliverables, timeline, responsible parties.

Detailed breakdown. How much, for what, paid to whom.

How will we know this worked? Measurable outcomes.

What could go wrong? How will you mitigate?

Before writing a formal proposal, discuss informally. Get feedback. Gauge support.

Talk to potential supporters. Address concerns before the vote, not during.

If you know someone will object, address their concern in the proposal itself.

  1. Too vague: “We’ll improve community engagement”, how?
  2. No budget: Proposals without numbers can’t be evaluated
  3. No success criteria: How will we know if this worked?
  4. No timeline: When will each deliverable be completed?
  5. Surprise proposals: Springing proposals without prior discussion

Draft your proposal. Share it informally. Iterate based on feedback. Then submit formally.