> For the complete documentation index, see [llms.txt](https://koova.gitbook.io/koova-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://koova.gitbook.io/koova-whitepaper/business-strategy/go-to-market-strategy.md).

# Go To Market Strategy

### Phase 1: Product-Led Growth

We start with a free tier for developers and self-serve onboarding. Community-driven adoption is our primary growth engine. We focus on building a great product that developers want to use.

### Phase 2: Partnership-Driven Growth

We partner with major platforms like Shopify and integrate with AI frameworks like Eliza and Autonomous. We also integrate with DeFi protocols to expand our reach.

### Phase 3: Enterprise Sales

We build a sales team to target large enterprises. We offer custom integrations and dedicated support for enterprise customers.

### Phase 4: Ecosystem-Driven Growth

We fund developers to build on top of Koova. We support community-built features and third-party proof types. The ecosystem becomes our growth engine.


---

# 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://koova.gitbook.io/koova-whitepaper/business-strategy/go-to-market-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.