Sample report · Telecom
We re-derived a published figure from the public record.
A carrier's finance team needs quarterly subscriber economics turned into a board-ready report. We typed in T-Mobile's published ARPA of $146.28 and ~30.76M average accounts, and withheld the revenue. The app came back with $13.50 billion in quarterly postpaid service revenue — matching T-Mobile's reported $13,502M to within 0.02%.
The situation
Published subscriber economics, turned into a board-ready report.
A carrier's finance / IR team — or an analyst checking them — needs the quarterly subscriber economics turned into a board-ready performance report. The factbook publishes ARPA (average revenue per account) and the account base, and separately the postpaid service revenue.
We used T-Mobile's Q4 2024 factbook as a reconcile test: type ARPA and the account base into the app, withhold the revenue, and see whether it recovers the reported figure. Honest framing: ARPA is defined as revenue ÷ accounts ÷ months, so this is a consistency / traceability reconcile — proof the app's arithmetic ties to the filing, not the derivation of an independent quantity. The app is never given the revenue.
What we supplied
Only public inputs — each one sourced.
We fed the two figures a user reads off the factbook and omitted the revenue, telling the app to derive it from accounts × ARPA.
| Input | Value | Source |
|---|---|---|
| Network type | 5G Standalone (SA) | T-Mobile is the US 5G SA leader |
| Subscriber segment | Consumer postpaid | — |
| Postpaid ARPA | $146.28 / month / account | Q4 2024 factbook |
| Avg postpaid accounts | 30,762,500 | Avg of 30,631K / 30,894K (factbook) |
| Postpaid phone churn | 0.92% | Q4 2024 factbook |
Source: T-Mobile Q4 2024 Investor Factbook · download the source document we used.
The report
The finished, board-ready output.
This is the actual rendered report — interactive charts and all. Nothing was edited after generation.
Reconcile
Our output vs. the published figures.
| Metric | Published | Ours (computed) | Match | Note |
|---|---|---|---|---|
| Quarterly postpaid service revenue | $13,502M | $13,499.8M (monthly × 3) | ≈ explained | 0.016% — app never given revenue; we withheld it |
| Monthly postpaid service revenue | $4,500.7M | $4,499.9M (30,762,500 × 146.28) | ✓ exact | App derived it from accounts × ARPA |
| ARPA | $146.28 | $146.28 | ✓ | Carried through |
| Avg postpaid accounts | 30,762,500 | 30,762,500 | ✓ | Carried through |
The ~$2M (0.016%) gap is the (beginning + ending) / 2 account average we fed vs T-Mobile's true period-average count — a real-user approximation, openly noted. This is a consistency/traceability reconcile: ARPA is definitionally derived from revenue, so recovering revenue proves the app ties to the filing. Network metrics (latency, throughput, uptime) the factbook didn't supply were generated as labeled operational estimates.
Build the same report from your own numbers.
You supply the figures you already have, and every number comes back labeled by where it came from — so you can put your name on it and show your work.
Generate your report — $20