> 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/faqs/benchmarks-and-business-case-faqs.md).
# Benchmarks & Business Case FAQs
Attach rates, churn impact, and benchmark inputs.
{% hint style="info" %}
Details available under NDA. [Request one now](mailto:hi@reachplatform.com).
{% endhint %}
How has adding mobile to the bundle impacted broadband uptake rates and churn?
The data doesn't lie — and it's better than what most operators model going in. Across 25+ ISPs live on the Reach platform: broadband churn drops 20–40% for bundled households, port-in share exceeds 50% within 6 months of launch, and the average household takes 2.2 mobile lines. Observed outcomes from the Reach network — not industry averages, not analyst projections.
[Request an NDA to learn more →](mailto:hi@reachplatform.com)
Can you share off-the-shelf benchmarking?
On attach rates: partners see 5–10% attach at point of sale on new internet connections with basic sales training. ARPU and margin profiles vary by market and pricing strategy — we share the full benchmarking tool with partners who are ready to model the opportunity.
[Request an NDA to learn more →](mailto:hi@reachplatform.com)
---
# 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/faqs/benchmarks-and-business-case-faqs.md?ask=&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.