> 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/why-the-timing-matters.md).

# Why the Timing Matters

Why the mobile bundle is proven and why regional ISPs can now launch with lower complexity.

## The market has been moving for a decade. The window for regional ISPs is now.

The strategic case for mobile is not new. What changed is who can execute it. Large cable operators proved the bundle model first. Now regional ISPs can launch with far less complexity. That makes this the practical window to act.

{% stepper %}
{% step %}

### 2016–2018: Cable giants move first

Comcast launches Xfinity Mobile. Charter launches Spectrum Mobile. Both target existing broadband subscribers exclusively. Early attach rates are modest but churn impact is immediate.
{% endstep %}

{% step %}

### 2019–2021: The bundle thesis is proven

Comcast and Charter report dramatically lower churn among bundled households. Industry analysts begin recommending MVNO as a defensive strategy for all broadband operators.
{% endstep %}

{% step %}

### 2022–2023: MVNO tooling matures.

Platforms like Reach emerge specifically for regional ISPs. Launch complexity and cost drop significantly. The first wave of regional ISPs goes live.
{% endstep %}

{% step %}

### 2024-2025: Regional ISPs began scaling.

MVNO penetration accelerates. Competitive pressure from FWA intensifies. ISPs without mobile begin showing measurably higher broadband churn.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
ISPs are proving mobile at scale—Comcast and Charter have each reached \~30% penetration of their broadband base, according to Comcast FY2025 earnings and Charter Q4 2024 results.
{% 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/deciding-on-mobile/why-the-timing-matters.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.