Put the next site, upgrade or fibre route where the customers and the revenue are, and show afterwards what the money did.
Network, customer and economic data rank sites, capacity and coverage gaps together, the operator's change authority approves the investment, and the result is verified against the forecast.
For Network planning, technology strategy and finance teams deciding where capital goes next.
A capital round has fewer sites in it than the network needs, and the candidates are ranked by technical severity alone.
The sites that go first, the evidence behind the order, and the proof that the investment paid.
The sites ranked by customers, revenue and cost togetherConsidered
A capacity change on an existing site instead of a new oneConsidered
Rehoming traffic while the site waitsConsidered
No investment, where the forecast does not justify itConsidered
Before anything reaches the customer: Telemetry quality, topology match, finance approval, maintenance freeze and change policy checks pass.
What would reach them: Hand the ranked recommendation to the change authority with its evidence; build only what the authority approves. On Planning workbench.
The sites that go first, the evidence behind the order, and the proof that the investment paid.
A capital round has fewer sites in it than the network needs. The candidates are ranked by technical severity, and nobody can say afterwards what the money did.
The sites ranked by customers, revenue and cost together
A capacity change on an existing site instead of a new one
Rehoming traffic while the site waits
No investment, where the forecast does not justify it
What it does
Three things it helps you decide or do.
Rank sites, upgrades and coverage gaps by customers, revenue and cost together
Site, capacity, 4G and 5G upgrade, fibre and FWA rollout, congestion and coverage-gap prioritisation read the same telemetry, demand forecast and cell-level revenue attribution.
site_or_cell_id
timestamp
traffic
throughput
latency
loss
utilisation
alarms
coverage
affected_customers
revenue_aggregate
capex_or_opex
action_outcome
Recommend, and let the change authority decide
Add capacity, rehome traffic, schedule a change or reject the investment: the recommendation goes to the change authority with its telemetry snapshot and topology version, and a maintenance freeze or a pending finance approval holds it.
Observe
tune
dispatch
add capacity
rehome traffic
schedule change
communicate
reject investment
escalate
Verify the benefit after the change
The KPI before and after, the controller's response and finance validation are kept with the recommendation, so CAPEX benefit and site profitability are measured rather than assumed.
Telemetry snapshot
topology/version
recommendation
approval/change ticket
controller response
before/after KPI
finance validation
The journey
Rank the next sites by the customers and revenue behind each gap
No demonstration is configured for this product yet.
Network planning, technology strategy and finance teams
Step
What the customer experiences
What the operator does
The momentThe moment that started it.
A capital round has fewer sites in it than the network needs, and the candidates are ranked by technical severity alone.
Reads telemetry and topology for each candidate, the demand forecast and cell-level revenue attribution, cost per site and finance's approval position, maintenance freezes and change policy.
The decisionThe decision to be made.
Nothing reaches the customer yet.
Ranks candidate sites by the customers, revenue and cost behind each gap, with the demand forecast, and recommends the order.
The safeguardsThe conditions that stop it.
Still nothing. No action is sent until every check has passed.
Hand the ranked recommendation to the change authority with its evidence; build only what the authority approves. Reaches them on Planning workbench, in English.
Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.
The demand forecast is built on a quarter with a festival in it, and the top-ranked site is empty by the time it is built.
The before-and-after KPI shows the miss, the forecast's window is corrected with the evidence, and the finance validation records the site's actual benefit rather than the forecast's.
The resultThe change it made.
What changed for them is what is counted; nothing else is claimed.
Traffic, revenue and experience at the built sites against the forecast that justified them.
Costs: Implementation + annual licence by network scale/use case; optional managed analytics; verified savings only with agreed finance baseline
If it fails: Default to observe/recommend; never make unapproved network change; open incident; preserve last-known-good config and audit trail
05
Measurement approach
The measure that shows it helped.
Matched site/cell comparison, stepped-wedge rollout or before/after with seasonality controls; technical and economic acceptance criteria
Measured on: Service experience; utilisation; incidents; MTTR; repeat fault; avoided congestion; cost; energy; affected customers; incremental/retained value
Nothing has been observed for this product. Every line above is the record's own design intent; measurement begins in a pilot's validate stage, on your systems, with the comparison agreed first.
The business side
The change
Traffic, revenue and experience at the built sites against the forecast that justified them.
Running cost
Implementation + annual licence by network scale/use case; optional managed analytics; verified savings only with agreed finance baseline
Use network, customer and economic data to support capacity expansion prioritisation, with operator-approved actions, change controls and post-action verification.
Identify eligible records for 4g upgrade prioritisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Identify eligible records for 5g upgrade prioritisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Use network, customer and economic data to support fibre rollout prioritisation, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support fwa expansion prioritisation, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support congestion hotspot prioritisation, with operator-approved actions, change controls and post-action verification.
/d/HT-0349
HeuriTel Coverage Gap PrioritisationDecision definitionHT-0350
Use network, customer and economic data to support coverage gap prioritisation, with operator-approved actions, change controls and post-action verification.
Identify eligible records for underserved revenue pool, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Use network, customer and economic data to support high-value customer network protection, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support competitor coverage defence, with operator-approved actions, change controls and post-action verification.
/d/HT-0353
HeuriTel Acquisition Zone PrioritisationDecision definitionHT-0354
Identify eligible records for acquisition zone prioritisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Use network, customer and economic data to support network demand forecasting, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support cell-level revenue attribution, with operator-approved actions, change controls and post-action verification.
/d/HT-0356
HeuriTel Network Experience to ChurnDecision definitionHT-0357
Identify customers with a defined near-term churn risk, select only economically justified retention actions, and measure incremental saves against a holdout.
Identify eligible records for capex benefit measurement, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0358
HeuriTel Site ProfitabilityDecision definitionHT-0359
Use network, customer and economic data to support site profitability, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support spectrum utilisation opportunity, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support energy-aware capacity planning, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support event capacity planning, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support rural coverage prioritisation, with operator-approved actions, change controls and post-action verification.
Four stages, and what has to be true before the next one starts.
12-16 weeks for decision support; closed-loop automation requires additional change, safety and vendor certification. A team of 8 roles, named in the record rather than promised.
01
Scope
One use case, one value unit and a denominator finance has agreed to. Without these there is nothing a later result can be compared against.
Select scenario
define action authority
baseline
02
Connect
The attributes mapped from your systems, and the decision and outcome interfaces working in both directions.
map topology/telemetry
integrate tickets
03
Validate
Eligibility agreed, a dry run with nothing sent, then a controlled pilot with a holdout that is actually respected.
build detection/ranking
shadow
operator-approved pilot
04
Operate
The live loop: decide, check, execute through your systems, capture what came back, and measure against the control.
Collect
validate topology
detect/forecast
quantify impact
recommend
human/controller approve
execute
verify service/economic result
learn
Who does it. 1 network solution lead · 1 network SME · 1 data engineer · 1 ML engineer · 1 OSS integration developer · 0.5 QA · 0.5 DevSecOps · 1 coordinator
Four states are tracked, and each is assessed against your systems.
Readiness is assessed per client: nothing is offered as pilot-ready until your data, your integration and your authority have been checked.
Readiness
Needs client data and integration review
The client’s data and integration position.Runtime / build state
Target product definition
What exists as running software.Surface state
Not audited
Whether this product shows the entry anywhere.Client status
Not assessed
Where a named client has reached.
Next steps from here.
22 definitions sit under Network Investment & Intelligence. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.
What can the network itself do for a bank, an agency or a planner?
CAMARA & GSMA Open Gateway APIsLet a bank or an app verify a number, a SIM change or a location from the network itself, with the customer's consent recorded.
Fraud, Identity & Customer ProtectionStop the SIM swap, the takeover and the subscription fraud before the money moves, and let the fraud system make the call.
