> 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

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 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.bigindie.games/our-strategy.md?ask=<question>&goal=<endgoal>
```

`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.