> For the complete documentation index, see [llms.txt](https://versus-x.gitbook.io/versus-x/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://versus-x.gitbook.io/versus-x/recipe-for-success/target-audience.md).

# Target audience

Versus-X is designed to serve a broad spectrum of players, each with their own motivations, habits, and expectations. Rather than building for a single niche, the platform caters to three distinct audiences unified by one thing: the desire to compete, wager, and have fun. By segmenting our audience based on playing behavior and motivation rather than the platform they use, Versus-X positions itself to capture value across the full range of the gaming and iGaming market. In a world where anyone with a smartphone and ambition has the tools to compete, Versus-X offers a platform where skill alone can create real opportunity.

**iGaming enthusiasts:** Players who enjoy the thrill of wagering but want the outcome to depend purely on their own abilities rather than luck, external events, or someone else's performance. These are users who are frustrated with the current landscape of online wagering, where traditional betting offers no control over outcomes and pay-to-earn gaming models require financial investment before any meaningful results can be achieved. Both leave skilled players at a disadvantage. Versus-X offers a fairer, more engaging, and more rewarding alternative where experience and strategy translate directly into earnings.

**Casual mobile gamers:** The everyday player who enjoys a few quick rounds of Pool or Golf during a commute, on a break, or against friends with modest stakes. They value accessibility, short session times, and a low barrier to entry. What makes Versus-X compelling for this audience is that the games they already enjoy playing to pass the time can now also earn them money. A casual session on the bus or during a lunch break is no longer just entertainment, it's an opportunity to walk away with real winnings. This audience is massive in scale and represents the bulk of mobile gaming revenue globally. For Versus-X, they are the foundation of a healthy, active player base and the most likely group to drive organic growth through social play and word of mouth.

**Competitive gamers:** Experienced players with a background in gaming who are looking to monetize their skills at a serious level. Typically playing on PC, they gravitate toward high-stakes multiplayer matches and tournaments with significant entry fees. This segment drives the competitive prestige of the platform, populates the top of the leaderboards, and attracts spectator interest, which in turn fuels content creation and community engagement.

By recognizing and serving the motivations of these three groups, Versus-X creates a layered ecosystem where casual players keep the community vibrant, competitive players raise the bar, and iGaming enthusiasts accelerate growth. Together, they form the foundation of a sustainable and scalable gaming economy.


---

# 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://versus-x.gitbook.io/versus-x/recipe-for-success/target-audience.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.