The platform the client bought after watching it work.

We built it to run our own crews on a €200m fibre programme. The operator saw it working on their own construction, and asked whether it could run everyone’s.

Two months from kick-off to live.

Build management map with a route picked out in red against the designed network, showing where the build is blocked
Fig. 1 — The platform answering a question: what cannot be built, and why

The work in figures

Src — programme records, July to September 2026
Kick-off to live2 months
Build partners onboarded5
Records migratedover 10 million
Premises tracked1 million
Platform users100+

How it started

BYNTGroup did not pitch this platform. While delivering construction on a national full-fibre programme, we built an internal GIS system to manage our own crews, our own progress and our own as-built records — because a build at that scale cannot be run on spreadsheets.

The operator saw it working on live construction. Not in a demo, not in a proposal, but on their own programme, producing their own data faster and cleaner than anything else on the job. They contracted BYNTGroup to build the same capability for every build partner on the programme — including our competitors.

The problem it solves

An operator running a national build through multiple contractors has a reporting problem long before it has a construction problem. Each build partner works in its own system, to its own data model, on its own reporting cycle.

Nobody can answer the question that actually matters — how many premises are genuinely ready for sale this week — without days of spreadsheet reconciliation, and by the time the answer exists it is out of date.

What we built

Five build partners migrated into a single ArcGIS Online platform, integrated with the operator’s own ArcGIS Enterprise environment.

Three parts. The migration — reconciling five incompatible schemas into one model without losing partner-specific detail, and bringing every partner’s site photography across with it. Then synchronisation — automated pipelines keeping the platform current against each partner’s external system, so data flows continuously rather than being re-imported. Then the layer everyone sees: operational dashboards giving the operator, and each partner, live visibility of build status against plan.

Build management platform architecture Five build partners' own systems feed automated synchronisation pipelines, which keep a single ArcGIS Online platform current. That platform integrates with the operator's existing ArcGIS Enterprise environment, and operational dashboards read from it — one view for the operator and for each partner. PARTNER SYSTEMS Build partner 1Build partner 2 Build partner 3Build partner 4 Build partner 5 Synchronisation automated, continuous ArcGIS Online one data model, every partner in it THE OPERATOR'S OWN ArcGIS Enterprise licences they already held WHAT PEOPLE SEE Operational dashboards operator, and each partner Configured on ArcGIS — not developed as bespoke software.
Build management platform architecture Five build partners' own systems feed automated synchronisation pipelines, which keep a single ArcGIS Online platform current. That platform integrates with the operator's existing ArcGIS Enterprise environment, and operational dashboards read from it — one view for the operator and for each partner. PARTNER SYSTEMS Build partner 1Build partner 2Build partner 3Build partner 4Build partner 5 Synchronisation automated, continuous ArcGIS Online one data model, every partner in it THE OPERATOR'S OWN ArcGIS Enterprise licences they already held WHAT PEOPLE SEE Operational dashboards operator, and each partner Configured on ArcGIS — not developed as bespoke software.
Partner systems → synchronisation → ArcGIS Online → the operator’s Enterprise environment and dashboards

Why it went live in two months

Because it was configured, not developed. The platform runs on ArcGIS rather than on bespoke software, which means there is no platform build programme in front of it.

BYNTGroup does not sell or upsell Esri licences. The platform runs on the client’s existing licences, or we help the client choose the right mix.

Dashboard showing service footprint, release status and third-party duct access route status as three donut charts
Fig. 2 — Footprint, release status and duct access, in one view
Dashboard showing total homes passed against homes passed designed, split by underground, overhead and multi-dwelling
Fig. 3 — Homes passed against homes designed, split by build type

What changed

Reporting moved from a reconciliation exercise to real time, or inside 24 hours from every build partner. The operator gets daily visibility of homes released for sale, and homes pending release after quality acceptance.

One view of the network instead of five fragmented systems — and every partner’s photographic evidence in the same place as the data it belongs to.

Build lifecycle map showing taps and splitters coloured by status across a residential area
Fig. 4 — Build lifecycle: every asset coloured by where it has got to

Where this goes next

The build underneath itFrom coax to full fibre52,300 homes constructed through inherited duct and overhead routes — the programme this platform was built to run.Read it What was added on topCatching defects before releaseQuality control deployed into the same environment, so defects sit next to build progress rather than in a separate silo.Read it

Talk to us about your build data

Tell us about the programme and we will come back with a practical delivery plan.

Start a conversation