> For the complete documentation index, see [llms.txt](https://cascadia.gitbook.io/gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cascadia.gitbook.io/gitbook/use-cases/business-development-and-marketing.md).
# Business Development and Marketing
Companies have issues attracting users. Millions are spent each year on legacy marketing agencies or outdated practices, like indiscriminate airdrops. Cascadia empowers any individual to act as a marketing agent through dynamic smart contracts, which gauge the effectiveness, reach, and sentiment of a user’s social media posts about a project. High quality interactions are incentivized through permissionless token claims. The market opportunity here is tremendous. Disrupting the digital marketing industry by returning sovereignty to individuals has far-reaching implications both inside and outside of web3.
Users, not platforms, should own their personal data.
---
# 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://cascadia.gitbook.io/gitbook/use-cases/business-development-and-marketing.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.