> For the complete documentation index, see [llms.txt](https://wp.candao.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.candao.io/use-cases/app-factory.md).

# App Factory

**Replace:** Traditional dev agencies, venture-funded startups

***

## Before

* Building an app requires large upfront capital
* Founders move slowly or die before product-market fit
* Dev costs dominate early budget

## With Candao

* Partners commit to Zero Fee + alignment bond ($1,000+ CDO)
* 360° community contributes: build, design, market, operate
* AI acceleration reduces cost and time-to-market

## Why Users Join

* They're not "users" — they're participants in what they use
* Better products built by aligned communities

## Why Partners Win

* Lower capex + faster iteration + growth-based rewards
* Community becomes an engine, not an audience

***

## 💰 The Numbers

**Build faster at lower cost — community execution vs. $50k+ agency fees.**


---

# 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, and the optional `goal` query parameter:

```
GET https://wp.candao.io/use-cases/app-factory.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
