# 6 Roadmap

Capybobo's path forward: validate the complete path on our own game first, then gradually open up as industry infrastructure.

{% stepper %}
{% step %}

#### Phase 1: Product Validation — 2025 (Completed)

The Capybobo game launched and has been operating continuously, with core gameplay and monetization models validated by the market — accumulating over 2.33 million registered users and $3.59 million in revenue (see 1.4). $PYBOBO token launched and community airdrop initiated. This phase completed the 0-to-1 validation: real users, sustained revenue, and a foundation for the protocol to build on.
{% endstep %}

{% step %}

#### Phase 2: Protocol Integration — 2026 Q3

The Capybobo game launched and has been operating continuously, with core gameplay and monetization models validated by the market — accumulating over 2.33 million registered users and $3.59 million in revenue (see 1.4). $PYBOBO token launched and community airdrop initiated. This phase completed the 0-to-1 validation: real users, sustained revenue, and a foundation for the protocol to build on.
{% endstep %}

{% step %}

#### Phase 3: IP Extension — 2026 Q3-Q4

From being remembered in the game to being carried outside of it. Launch AI-chip-embedded Capybobo designer toys and wearable devices, extending characters from the digital world into the physical world with offline interaction and cloud sync. Simultaneously initiate IP-derived commercial paths: brand collaborations, merchandise, and content licensing. This phase marks where character value begins to transcend the game itself.
{% endstep %}

{% step %}

#### Phase 4: Protocol Opening — 2027 Q1

From proprietary product to industry infrastructure. Developer SDK officially opens, allowing third-party games to integrate the Capybobo Protocol and share the AI engine, on-chain assets, and LP infrastructure. More game characters enter the ecosystem, building a cross-game IP asset network.
{% endstep %}
{% endstepper %}

#### .

<br>


---

# Agent Instructions: 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:

```
GET https://doc.capybobo.io/6-roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.