> 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/what-to-know-before-launch.md).

# What to Know Before Launch

Decisions leadership should align on before launch.

> Most delays happen because leadership leaves core decisions unresolved.

### The 12 decisions to make before launch

Work through these as a leadership team.

Each decision now has its own page.

1. [End Goal](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/end-goal.md)
2. [Carrier of Record](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/carrier-of-record.md)
3. [Network Choice](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/network-choice.md)
4. [Deployment Model](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/deployment-model.md)
5. [Device Strategy](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/device-strategy.md)
6. [Key Offers at Launch](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/key-offers-at-launch.md)
7. [Agent SPIF](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/agent-spif.md)
8. [Investment from ISP](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/investment-from-isp.md)
9. [Sales Channel Strategy](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/sales-channel-strategy.md)
10. [Sales and Field Training](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/sales-and-field-training.md)
11. [Customer Care Model](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/customer-care-model.md)
12. [Internal Ownership](/starter-kit/starter-kit/for-isps/what-to-know-before-launch/internal-ownership.md)

{% hint style="warning" %}
Most launch delays trace back to one of these decisions being left unresolved or assigned too late.
{% endhint %}

### Leadership checklist

Before moving forward, make sure you can answer:

* What are we optimizing for first?
* Who owns launch internally?
* How much are we investing?
* What is our day-one offer?
* How will we sell mobile?
* Who handles care and escalation?

If those answers are clear, move on to [Launching with Reach](/starter-kit/starter-kit/for-isps/launching-with-reach.md).

{% 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/what-to-know-before-launch.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.