> 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/deciding-on-mobile/modeling-the-opportunity.md).

# Modeling the Opportunity

Use this framework to build your own 3-year model. Reach will build a custom model for your specific subscriber base — ask for it.

<table><thead><tr><th width="73.90625">Step</th><th width="261.25390625">Input</th><th>Example (15,000-sub ISP)</th></tr></thead><tbody><tr><td>1</td><td>Total current broadband subscribers</td><td>15,000 subscribers</td></tr><tr><td>2</td><td>Apply penetration targets by year</td><td>Year 1: 3–5% → 525 subs | Year 2: 6–8% → 1,050 subs | Year 3: 9–12% → 1,575 subs</td></tr><tr><td>3</td><td>Apply lines per household (2.2x)</td><td>1,575 households × 2.2 = <strong>3,465 lines by Year 3</strong></td></tr><tr><td>4</td><td>Apply revenue share per line</td><td>Revenue share by plan mix and commercial terms</td></tr><tr><td>5</td><td>Add VAS upside</td><td>Device protection + other VAS typically add 15–25% on top of base revenue share</td></tr></tbody></table>

{% hint style="success" %}
**Reach builds a fully customized P\&L model for every prospective partner** — including ISP-specific attach rate scenarios, plan mix assumptions, and VAS upside. Request yours before making a final decision.
{% endhint %}

## Model the Opportunity in Real Time

Reach's MVNO Business Case tool lets you configure your broadband base, pricing, and cost structure — and see your full P\&L, dashboards, and charts update instantly. No analyst required. Built for CXOs and senior leadership teams evaluating a mobile launch.

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

## What It Models

{% columns %}
{% column %}
📊

#### 5-Year P\&L

Subscriber growth, revenue, network costs, marketing spend, device store economics — all in one model.
{% endcolumn %}

{% column %}
📈

#### Live Dashboards

Subscriber growth curves, mobile penetration rate, marketing spend vs. revenue, and broadband bundle savings — updated as you configure.
{% endcolumn %}

{% column %}
⚙️

#### Full Configuration

Set your Carrier of Record model, configure your broadband base, define your plan lineup, and see residual per subscriber.
{% endcolumn %}
{% endcolumns %}

## Get Access

Request access to the Reach MVNO Business Case tool — built for ISP leadership teams evaluating a mobile launch.

[Click here to request access](mailto:hi@reachplatform.com?subject=MVNO%20Business%20Case%20Tool%20%E2%80%94%20Access%20Request\&body=Hi%20Reach%20team,%0D%0A%0D%0AI%27d%20like%20to%20request%20access%20to%20the%20MVNO%20Business%20Case%20tool.%0D%0A%0D%0ACompany:%0D%0AName:%0APhone:%0D%0A%0D%0AThanks)

{% 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/deciding-on-mobile/modeling-the-opportunity.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.