> For the complete documentation index, see [llms.txt](https://docs.eitherway.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eitherway.ai/documentation/launchpad/supported-launch-paths.md).

# Supported Launch Paths

The Eitherway Launchpad supports three primary launch paths.

#### 1. Product-first launches

A team builds or deploys an application first, then introduces a tokenized economic layer around that product.

This is the preferred path.

The reasoning is simple: launches tend to be stronger when there is already a real product, use case, or user flow behind them. Product-led launches usually create better alignment between utility, user activity, and market participation.

#### 2. Token-first launches

A team launches the token first, uses it to coordinate early liquidity and community formation, and develops the product layer over time.

This path is supported because some teams choose to use the token as the first coordination layer for building an ecosystem, then expand the product around it as traction grows.

#### 3. External product launches

A team with an existing product built outside Eitherway uses the launchpad as its token issuance and liquidity coordination layer.

This allows external teams to access the launch infrastructure and ecosystem mechanics of the Eitherway Launchpad without needing to have built the product directly on Eitherway itself.

All three paths are supported.

The platform’s preference remains product first, because product-led launches generally create stronger alignment between utility, user activity, and market participation. But the launchpad is designed to remain flexible enough to support different routes to market, depending on the team, the product, and the stage of the ecosystem.


---

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

```
GET https://docs.eitherway.ai/documentation/launchpad/supported-launch-paths.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.