> For the complete documentation index, see [llms.txt](https://docs.foreprotocol.io/fore-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foreprotocol.io/fore-protocol/whitepaper/business-model/go-to-market/go-to-market-strategy.md). # Go-To-Market Strategy Our go-to-market strategy is underpinned by solving real-world problems for our users, and data is critical in understanding the user and their needs. We are using thousands of data points to understand personality traits, interests, demographics, online behavior, and protocol behavior to: * Identify prospective users who are most likely to convert * Optimize marketing and product to overcome barriers to conversion * Convert prospects into users (and users into players) * Continually reduce cost of acquisition We are striving to build a complete view of our users and prospects in order to achieve the most intelligent targeting possible – connecting their demographics and regional data, their online behavior and interests, their betting behavior (on the platform), and their wider financial behavior (all transactions carried out on the blockchain). FORE Predict is the first platform to be able to connect these different data points to enable an all-encompassing view of our users. --- # 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://docs.foreprotocol.io/fore-protocol/whitepaper/business-model/go-to-market/go-to-market-strategy.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.