> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps.md).

# For ISPs

Mobile launch guidance for broadband operators evaluating branded mobile.

This starter kit walks an ISP from initial evaluation to launch readiness. It is built for broadband operators exploring branded mobile with Reach. Use it to decide whether mobile fits your market, your team, and your economics.

The guide starts with the business case. It then moves into the leadership decisions that shape launch speed and results. From there, it shows how Reach runs the platform, where your team stays involved, how to take the offer to market, and how the financial model works.

By the end, you should be able to answer:

* Why mobile matters now for your subscriber base.
* What launch model fits your team and goals.
* What needs to be true before you go live.

### What this guide covers

1. [Deciding on Mobile](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/deciding-on-mobile.md)
2. [What to Know Before Launch](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/what-to-know-before-launch.md)
3. [Launching with Reach](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/launching-with-reach.md)
4. [ISP Responsibilities](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/isp-responsibilities.md)
5. [GTM Strategy](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/gtm-strategy.md)
6. [Commercials](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/commercials.md)
7. [Next Steps](https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/next-steps.md)

{% hint style="info" %}
Use this guide in order. Each section builds on the last and moves you from go or no-go to a launch plan you can execute.
{% endhint %}

{% hint style="info" %}
Questions or clarification? Email us at <hi@reachplatform.com>.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reachplatform.com/starter-kit/starter-kit/for-isps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
