> 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/what-the-benchmarks-show.md).

# What the Benchmarks Show

Practical performance benchmarks from live ISP launches on the Reach platform.

## What the data actually shows

Reach has 25+ ISPs live on its platform across a range of sizes and markets.

{% columns %}
{% column %}

<h3 align="center"><mark style="color:$primary;">5–10%</mark></h3>

<p align="center"><strong>Attach Rate at Point of Sale</strong><br>On new internet connections with basic sales training</p>
{% endcolumn %}

{% column %}

<h3 align="center"><mark style="color:$primary;">20–40%</mark></h3>

<p align="center"><strong>Broadband Churn Reduction</strong><br>For bundled households across all Reach launches</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<h3 align="center"><mark style="color:$primary;">>50%</mark></h3>

<p align="center"><strong>Port-In Share</strong><br>Share of activations that are port-ins<br>within 6 months of launch</p>
{% endcolumn %}

{% column %}

<h3 align="center"><mark style="color:$primary;">2.2</mark></h3>

<p align="center"><strong>Mobile Lines Per Household</strong><br>Average across the Reach network</p>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
These are observed outcomes from the Reach platform, not industry averages or analyst projections.
{% endhint %}

* Attach rates on new internet sales typically land between 5% and 10% with basic sales training
* ISPs with strong SPIF programs and proactive outbound campaigns have exceeded 15% attach on new sales
* Broadband churn reduction (20-40%) is the most consistent finding across all launches — bundled customers simply do not leave
* Port-in rates exceeding 50% within 6 months indicate subscribers are consolidating from major carriers, not just adding a line
* Regional ISPs frequently outperform large cable operators on attach rate due to stronger local relationships and higher rep engagement

{% hint style="success" %}
ISPs with strong SPIF programs and proactive outbound campaigns have exceeded 15% attach on new sales.
{% endhint %}

## Modeling inputs for your business case

Use these planning inputs as a practical starting point:

* **Year 1 target:** 7% attach on new internet sales
* **3-year target:** 10% penetration of the total broadband subscriber base
* **Port-in assumption:** 60% of activations
* **Lines per household:** 2.2
* **Revenue modeling:** see [Commercials](/starter-kit/starter-kit/for-isps/commercials.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/deciding-on-mobile/what-the-benchmarks-show.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.
