> For the complete documentation index, see [llms.txt](https://docs.laso.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.laso.finance/laso-finance-metadao/why-metadao.md).

# Why MetaDAO

Since starting Laso Finance three years ago, we've received many inquiries to launch a token.&#x20;

We've never accepted, because most token launches:

* Focus on short-term token movements.
* Invite distractions from core business.
* Are at risk for team misusing funds, or rugging.
* Are divorced from the realities of the actual business.
* Either gives tokenholders no rights, or worse, devolves the business into a bureaucracy.
* Incentivizes teams to "rest and vest", not to execute.

[MetaDAO](https://www.metadao.fi/) has found a balanced solution through [decision markets](https://docs.metadao.fi/governance/overview) and [team incentivization](https://docs.metadao.fi/how-launches-work/sale#how-are-teams-incentivized).

We are confident that the MetaDAO launch will create the best alignment between investors, team, and most importantly, users.

We had many opportunities for private VC rounds. Instead, MetaDAO enables what we want for our users. The people who use the product should and will share the upside.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.laso.finance/laso-finance-metadao/why-metadao.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
