> 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/phase-four.md). # Phase Four **CONVERT USERS TO PLAYERS** Acquiring active ‘players’ is critical to driving revenue, and is the final step in our user acquisition funnel. While every participant in the FORE ecosystem is valuable, players bring the revenue necessary to grow the protocol and reward participants, with players expected to make up 80% of the core user base. Post protocol launch in Phase Three, targeting will expand to include Crypto Bettors in order to ensure a sustainable flow of revenue and volume of betting in line with our growth projections. User insights, conversion rates, and acquisition costs from activity carried out in phases one, two, and three will be used to optimize acquisition of this audience to drive highly-targeted and cost-effective outreach. --- # 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/phase-four.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.