> For the complete documentation index, see [llms.txt](https://docs.bigindie.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bigindie.games/our-strategy.md).

# Our Strategy

Games first. Zero crypto friction. Real revenue.

The gaming market is much bigger than Web3. Our strongest opportunity is to reach regular gamers first by building games that are easy to access, visually strong, fun to play, and designed around systems that keep players engaged.

Players should not need wallets, tokens, blockchain knowledge, or any Web3 steps to enjoy our games. The game experience comes first.

Revenue can come from proven gaming business models such as in-game purchases, cosmetics, progression items, upgrades, passes, ads, and other game-related monetization.

Instead of depending only on token speculation, BIG Indie Games aims to create a real revenue engine. A structured part of net income generated by our games will be used to support the $BIG ecosystem through buy-backs and treasury growth.


---

# 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.bigindie.games/our-strategy.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.