> 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/investment-from-isp.md).

# Investment from ISP

Set the budget for device subsidies, offers, marketing, training, and launch support. Mobile is not a zero-cost initiative. It does not need a huge budget, but it does need a real one.

The single most important financial decision before launch is how much you will invest. Your budget sets the ceiling for the launch offer, device support, marketing reach, and team readiness.

### Budget factors

| Investment category              | What the budget covers                                                                              | Why it matters                                                            |
| -------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Device subsidies**             | Discounted or free devices at activation.                                                           | Directly drives attach rate. Usually the highest-ROI year-one investment. |
| **Launch offers and promotions** | Free months, discounted plans, and port-in credits.                                                 | Creates urgency and drives early subscriber volume.                       |
| **Marketing and awareness**      | Digital, email, in-store, and outbound campaigns to your broadband base.                            | Gets the offer in front of the customers most likely to convert.          |
| **Platform customizations**      | Branded storefront, custom workflows, and deeper BSS/OSS integration beyond the turnkey default.    | Improves the launch experience and supports unique operating needs.       |
| **Training and enablement**      | Rep training, certification, and ongoing coaching. Reach provides materials. The ISP provides time. | Ensures the team can sell, support, and retain customers well.            |

### How to think about the budget

A defined budget helps leadership answer:

* How strong the launch offer can be
* Whether subsidized devices are possible
* How much awareness can be built before launch
* How well the team can be trained

{% hint style="danger" %}
You do not need a large budget to launch. But you do need a defined budget. ISPs who go into launch without a committed investment number consistently underperform those who do.
{% 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/what-to-know-before-launch/investment-from-isp.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.
