> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/introduction/readme/who-should-use-this.md).

# Who Should Use This

Trustless Work is built for developers, platforms, and agents who want **more control and automation** over when funds are released.

### Platforms using stablecoins

Examples:

* Gig and freelance platforms (milestone payouts)
* B2B tools using USDC for global settlement
* Rental and booking platforms (security deposits)

Why it fits:

* Reduce fraud
* Automate releases and disbursements
* Lower operational cost

### Builders and product teams

Examples:

* Solo devs or small teams prototyping dApps
* DAO tooling, donation platforms, on-chain marketplaces

Why it fits:

* Plug-and-play escrow logic
* Start on testnet, then go live without re-architecting

### Enterprise use

Examples:

* Platforms with escrow-like flows but no escrow infrastructure
* Teams replacing costly custodial services with on-chain escrow

Why it fits:

* Less legal and operational risk than custody
* Programmable, auditable escrow behavior

### Next steps

* Build your first flow: [Developer Quickstart](broken://spaces/Dg2e2YCRmNlhCnxxmEb6/pages/bknsGrFeT0G5xw1ebl4u)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlesswork.com/trustless-work/introduction/readme/who-should-use-this.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.