> 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/local-services.md). # Local Services **Replace:** TaskRabbit, Thumbtack, Handy *** ## Before * Platforms take 15% from every job * Providers limited to platform's client pool * Geographic matching is weak ## With Candao * Direct matching (no platform extraction) * Hyperlocal Ghost matching with neighbors * Providers set own rates ## Why Users Join * Cheaper services (no middleman tax) * Support local providers directly ## Why Partners Win * Growth-based rewards + direct revenue * Community becomes repeat customers *** ## 💰 The Numbers **A $100 cleaning job = $100 earned — no 15% platform tax.** > *Here's how it could work: Ana, a house cleaner in Barcelona, asked "Why should an app in San Francisco take 15% of every job?" Now her Ghost matches her with neighborhood clients. Zero cut.* --- # 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/local-services.md?ask=&goal= ``` `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.