> 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/commercials/understanding-your-cost-structure.md).

# Understanding Your Cost Structure

Mobile has a very different cost structure from broadband. There is no significant capital investment — costs are primarily variable and operational.

## **Fixed / One-Time Costs**

* **Platform Setup:** $0 for out-of-the-box plan
* **Add-On Features:** SSO, branded app hosting, SFTP, and other add-ons have one-time fees (see next slide)
* **Sales Training:** Internal time cost — typically 2–3 days of your team's time before launch
* **Marketing and Launch Materials:** Website updates, email templates, print materials — budget $2,000–$10,000 depending on scope

## **Variable / Ongoing Costs**

* **Rep SPIFs:** $25–$75 per line activated. Biggest variable cost in Year 1.
* **Device Subsidies:** $50–$150 per subsidized device depending on promotion. Model payback: 6–9 months.
* **Customer Support Labor:** Estimate 20–30% higher support volume for first 2 months post-launch.
* **Monthly Maintenance Fee:** Applies from Month 4 if milestone is not met. Stops when milestone is achieved.

{% 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/commercials/understanding-your-cost-structure.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.