> **ARCHIVED — HISTORICAL RECORD ONLY (archived 2026-07-18).** Retained for reference; do not treat as current design guidance.

# GeoLynx Market Expansion Plan

> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.

**Goal:** Identify the industries best positioned to adopt GeoLynx, rank them by development effort required, and define the specific modifications needed to enter each market.

**Architecture:** GeoLynx's core engine — linear infrastructure planning, land/property rights management (wayleaves), spatial routing, premises registers, and lifecycle project tracking — is directly transferable to any industry that builds or manages physical infrastructure across third-party land. The wayleave module is the most differentiated asset; in other verticals it maps to easements, wayleave licences, access agreements, and site leases. Terminology and asset schemas vary; the underlying workflows are structurally identical.

**Tech Stack:** PHP/PostgreSQL/PostGIS/pgRouting/Leaflet/OpenLayers — no fundamental changes required for any tier. All vertical work is configuration, schema extension, and UI terminology.

---

## Core Transferable Value

Before scoring each vertical, these are the GeoLynx capabilities that transfer with zero or minimal change:

| GeoLynx Capability | What it maps to in other verticals |
|---|---|
| Interactive GIS map with infrastructure layers | Any physical asset on a map |
| Wayleave negotiation & sign-off workflow | Easements, access licences, site leases, wayleave (identical concept in utilities) |
| Premises register (UPRN, MDU/SDU) | Any addressable asset register — properties, sites, cabinets, substations |
| Project lifecycle (Prospecting → Complete) | Any capital project with planning/build phases |
| Automatic cable routing (pgRouting) | Pipe routing, duct routing, track alignment |
| Strategic distance analysis | Coverage gap analysis, proximity to existing assets, competitor overlap |
| Network topology (Cytoscape) | Any network graph — water pressure zones, power ring mains, gas spur networks |
| Audit trail & journal | Regulatory compliance in any licensed utility |
| GeoPackage / PDF / Excel export | Standard across all infrastructure sectors |
| Land Registry integration | UK-wide — directly relevant to any infrastructure owner acquiring land rights |

---

## Tier System

| Tier | Description | Estimated dev effort to first usable product |
|---|---|---|
| **T1 — Near-zero lift** | Same infrastructure type, same workflow, same regulatory pattern. Rename terminology, minor schema changes. | 4–8 weeks |
| **T2 — Low lift** | Same planning/rights workflow; different asset type or spatial model. Schema additions, new map layers, adjusted UI modules. | 2–4 months |
| **T3 — Medium lift** | Conceptually aligned but requires a new primary module or significant domain logic change. | 4–8 months |
| **T4 — Stretch** | GeoLynx provides a platform foundation but 50%+ of domain logic is new. Not a straightforward vertical extension. | 8+ months |

---

## Tier 1 — Near-Zero Lift

### 1A. Water & Wastewater Networks

**Why:** Water utilities plan and build pipe networks across the same physical geography as fibre operators. They manage:
- Pipe runs (= cable runs), chambers (= cabinets), connection points (= premises)
- Land access rights called **easements** — legally and operationally identical to wayleaves
- A phased capital project lifecycle from feasibility → design → build → commission
- Regulatory compliance bodies (Ofwat, DWR Cymru, Scottish Water) with the same audit requirements as Ofcom

GeoLynx's auto-router already calculates least-cost paths across a network; water planners use exactly this for trunk main and distribution main routing.

**Modifications required:**

| Module | Change |
|---|---|
| Terminology | "Cable" → "Main/Pipe", "Duct" → "Trench", "Cabinet" → "Chamber/Valve", "Fibre" → "Bore/Diameter", "Wayleave" → "Easement", "Premises" → "Connection point / Property" |
| Asset schema | Add pipe diameter, material (MDPE, iron, UPVC), pressure zone, flow direction to the geometry attributes |
| Fibre Allocation tab | Replace with **Pressure Zone / Flow Allocation** — assign pipe segments to pressure zones |
| Routing cost model | Add cost parameters for trench depth, road reinstatement, rock breaking instead of civils/PIA weighting |
| Reporting | Add flow capacity, leakage metrics, burst history fields |
| Map layers | Reference layers for OS water infrastructure, flood zones, aquifer protection zones |

**Priority score:** 9/10 — Largest addressable market after telecoms, identical legal/regulatory pattern, existing pgRouting engine handles hydraulic network topology.

---

### 1B. Gas Distribution Networks

**Why:** Identical to water in structure. Gas distribution operators (Cadent, SGN, Northern Gas Networks, Wales & West Utilities) plan low-pressure and intermediate-pressure distribution mains with:
- Pipe routing along roads and across private land (easements)
- Tier-based asset hierarchy: transmission → distribution → service pipe → meter
- A regulated asset base with strict Ofgem audit requirements

**Modifications required:**

| Module | Change |
|---|---|
| Terminology | As per water, plus "Service Pipe" layer, "Governor" (= cabinet), "Meter Point Reference" (= UPRN equivalent) |
| Asset schema | Gas-specific: operating pressure (LP/MP/IP/HP), material (PE, steel, CI), cathodic protection status |
| Safety compliance fields | Add gas escape risk flag, excavation permit reference, confined space flag to project records |
| Routing | Add "road reinstatement tier" (A-road vs residential) to the cost weighting |
| Wayleave → Easement | Rename; gas operators use the same legal instrument |

**Priority score:** 8/10 — Smaller market than water but very high regulatory documentation burden makes the audit/journal features particularly valuable. RIIO-2 price controls create strong demand for cost tracking tools.

---

### 1C. Electricity Distribution Networks (DNOs / IDNOs)

**Why:** Distribution Network Operators (National Grid ED, Scottish & Southern, Northern Powergrid) and Independent DNOs build underground cable networks and overhead line networks that are spatially and operationally very close to fibre. The wayleave concept is identical — overhead lines require tree-cutting wayleave agreements with landowners.

**Modifications required:**

| Module | Change |
|---|---|
| Terminology | "Cable" → "HV/LV Cable", "Cabinet" → "Substation/Pillar", "Duct" → "Conduit", "Premises" → "Supply point / MPAN" |
| Asset schema | Voltage level (HV/LV/EHV), conductor cross-section (mm²), phase configuration, fuse rating, transformer capacity (kVA) |
| Wayleave module | Add tree/vegetation cutting wayleave sub-type (used for overhead lines) alongside standard land access |
| New: Overhead Line layer | Pole assets with span lengths, sag calculations — distinct from underground cable |
| Routing | Add overhead vs underground routing mode; overhead line follows road/field edges, not ducts |
| Reporting | SHEPD/DNO-specific: CI/CML (Customer Interruptions/Minutes Lost), fault rate reporting |

**Priority score:** 8/10 — DNOs are under significant Ofgem pressure to digitalise asset management. The overhead line wayleave module is a unique selling point.

---

### 1D. District Heating Networks

**Why:** An emerging UK market (Heat Networks Zoning Bill 2024) where operators plan and build insulated pipe networks to serve blocks of flats and commercial buildings — exactly the MDU-heavy premise type GeoLynx already handles best. Operators need:
- Wayleave/easement agreements for pipe routes through buildings and private land
- MDU connection tracking (already the primary use case in GeoLynx)
- A project lifecycle matching the multi-year capital project pattern

**Modifications required:**

| Module | Change |
|---|---|
| Terminology | "Cable" → "Flow/Return Main", "Fibre allocation" → "Heat metering / energy sub-metering" |
| Asset schema | Pipe insulation type, operating temperature, flow rate (kW), heat meter serial numbers |
| New: Energy metering tab | Track heat meter installations per premise (parallel to fibre allocation) |
| Reporting | Heat delivered (MWh), decarbonisation metrics, SAP/EPC ratings per premise |

**Priority score:** 7/10 — Smaller market today but fastest growing infrastructure sector in UK. Early market entry opportunity. Government mandating Heat Network Zoning from 2025 will drive software adoption.

---

## Tier 2 — Low Lift

### 2A. Wireless / 5G Tower Operators (TowerCos)

**Why:** TowerCos (Cellnex, Wireless Infrastructure Group, MBNL) acquire sites, negotiate leases with landowners, manage planning permissions, and track build-out. The site lease workflow is a direct analogy to wayleave. They also need proximity analysis (coverage planning) and competitor mast mapping.

**Modifications required:**

| Module | Change |
|---|---|
| Wayleave → Site Lease | Rename; add lease term, annual rent review, break clause fields |
| New: Coverage/Propagation layer | Basic Fresnel zone visualisation or integration with an RF planning API (e.g. SPLAT!) |
| Asset schema | Mast height, structure type (lattice/monopole/rooftop), power supply type, backhaul type |
| New: Planning Permission tracker | Adds a planning application status workflow alongside the lease workflow |
| Routing | Less relevant (no linear network); disable or repurpose for fibre backhaul routes to mast sites |
| Distance analysis | Repurpose for coverage gap analysis: "which postcodes are >X metres from nearest mast?" |
| Reporting | Site acquisition pipeline, lease expiry dashboard, planning success rate |

**Development effort:** 10–12 weeks

**Priority score:** 7/10 — Strong UK market with ongoing 5G rollout. The site lease / land rights module is the primary value driver. Coverage modelling adds complexity.

---

### 2B. EV Charging Network Operators

**Why:** EV charge point operators (Pod Point, Osprey, bp pulse, Gridserve) are deploying at scale and need to:
- Select sites based on proximity to demand (homes, motorways, retail)
- Negotiate land/access agreements with site owners (= wayleave)
- Track grid connection works as a project lifecycle
- Manage premises lists of charging locations

**Modifications required:**

| Module | Change |
|---|---|
| Wayleave → Site Agreement | Rename; add revenue-share terms, dwell time, exclusivity clause |
| New: Grid Connection module | Track DNO application status, connection offer voltage/capacity, acceptance and build |
| Asset schema | Charger type (AC/DC), power rating (kW), connector standards (CCS/CHAdeMO/Type 2), utilisation data |
| Distance analysis | "Sites within 1000m of motorway junction", "areas underserved by rapid charging" |
| Reporting | Utilisation rate, uptime %, sessions per day, revenue per site |
| Map layers | Reference layers for OZEV/ZAP-MAP public charge point data, grid constraint maps |

**Development effort:** 10–14 weeks

**Priority score:** 6/10 — Fast-growing market. OZEV grants create same dynamic as BDUK (government-funded rollout requiring compliance documentation). Grid connection tracking is the new module with most complexity.

---

### 2C. Rail Infrastructure (Network Rail / HS2 Contractors)

**Why:** Rail projects involve linear infrastructure planning, land access negotiations (the Rail Access Licence is legally similar to wayleave), complex multi-contractor project management, and strict audit requirements. pgRouting's graph model is applicable to track alignment planning.

**Modifications required:**

| Module | Change |
|---|---|
| Wayleave → Land Access Licence / CPO | Add Compulsory Purchase Order workflow alongside negotiated access |
| New: Track alignment layer | Railway-specific geometry constraints (cant, gradient, radius) as attributes on line features |
| Asset schema | Rail type, sleeper material, signalling zone, PICOP reference, possession number |
| New: Possession/blockade planning | Track line closures required for works — a distinct project sub-type |
| Project workflow | Extend to include Network Rail governance stages (GRIP 1–8) |
| Reporting | Regulatory: NR/L2/INI compliance, RAIB incident flag |

**Development effort:** 3–4 months

**Priority score:** 5/10 — Lucrative contracts but long sales cycles, NDA-heavy procurement, and bespoke requirements per project. Better suited as a subcontractor tool than a SaaS product.

---

### 2D. Highways & Local Authority Street Works

**Why:** Local authorities manage street works coordination (S50/S278 licences), utility reinstatement, and highway infrastructure assets. The project/works lifecycle mirrors GeoLynx's planning → build workflow. NRSWA (New Roads and Street Works Act) compliance creates an audit burden that GeoLynx's journal system directly addresses.

**Modifications required:**

| Module | Change |
|---|---|
| Wayleave → S50 Licence / S278 Agreement | Rename; add licence fee, bond amount, traffic management plan |
| New: Works Promoter module | Track multiple utilities working in the same street (coordination duty under NRSWA) |
| Asset schema | Highway maintainable/adoptable status, road category (A/B/C/unclassified), reinstatement category |
| New: Permit scheme integration | API connection to Elgin/One.network for permit submission |
| Map layers | OS Highways, Ordnance Survey MasterMap Highways Network |
| Reporting | FPN (Fixed Penalty Notice) risk, defect rate, lane rental charge tracking |

**Development effort:** 3–4 months

**Priority score:** 5/10 — Very large potential market (all 400+ UK local authorities) but public sector procurement is slow and price-sensitive. One.network is an established incumbent.

---

## Tier 3 — Medium Lift

### 3A. Renewable Energy (Wind & Solar Farm Developers)

**Why:** Onshore wind and solar developers must assemble land options across multiple landowners, manage planning applications, coordinate grid connection projects, and build out infrastructure — all geographically-led workflows. The land option/exclusivity agreement is a legal instrument close to wayleave.

**Modifications required:**

- New: **Land Option module** — track option period, strike price, landowner negotiation stages (close to wayleave but with financial modelling)
- New: **Planning Application tracker** — local planning authority correspondence, S106 obligations, EIA stages
- New: **Yield/capacity modelling integration** — export site boundary GeoPackage to WindFarmer/PVSyst and import results
- Extended distance analysis — "premises within 2km visual impact zone", "grid connection distance from substation"
- New reporting: irradiance maps overlay, constraint layers (AONB, flood zone, aviation)
- Wayleave → Option Agreement (with different financial terms schema)

**Development effort:** 5–7 months

**Priority score:** 4/10 — High strategic interest but land option financial modelling and planning workflow are genuinely new domain logic. Strong growth market; worth a Phase 2 roadmap position.

---

### 3B. Oil & Gas Pipeline Operators

**Why:** Onshore pipeline operators (National Gas Transmission, Perenco, Ineos) plan pipeline routes, negotiate rights of way (identical to wayleave), and manage construction projects across third-party land. Regulatory compliance (PSSR, COMAH) creates an even heavier audit burden than Ofcom.

**Modifications required:**

- All Tier 1 water/gas changes, plus:
- New: **COMAH / PSSR safety case fields** — regulatory reference numbers, safety zone radii as map layers
- New: **Pigging / inspection programme** — track in-line inspection runs, anomaly records per pipeline segment
- New: **Cathodic protection monitoring** — asset attribute on each pipe segment
- Rights of Way / Deed of Easement workflow replaces wayleave (substantively similar but with permanent vs temporary distinction)
- Routing: add slope stability, watercourse crossing, SSSI buffer constraints to the cost model

**Development effort:** 6–8 months

**Priority score:** 3/10 — Very high compliance value but niche market, long procurement cycles, and strong competition from specialist PODS/GIS tools (ESRI Utility Network, Smallworld). Not a short-term priority.

---

## Summary Ranking

| Rank | Vertical | Tier | Dev effort | Market size | Priority |
|---|---|---|---|---|---|
| 1 | Water & Wastewater | T1 | 4–8 weeks | Very large | 9/10 |
| 2 | Gas Distribution | T1 | 4–8 weeks | Large | 8/10 |
| 3 | Electricity Distribution (DNOs) | T1 | 6–8 weeks | Large | 8/10 |
| 4 | District Heating | T1 | 4–6 weeks | Growing | 7/10 |
| 5 | Wireless / 5G TowerCos | T2 | 10–12 weeks | Large | 7/10 |
| 6 | EV Charging Networks | T2 | 10–14 weeks | Fast-growing | 6/10 |
| 7 | Rail Infrastructure | T2 | 3–4 months | Medium | 5/10 |
| 8 | Highways / Local Authority | T2 | 3–4 months | Very large | 5/10 |
| 9 | Renewable Energy | T3 | 5–7 months | Large | 4/10 |
| 10 | Oil & Gas Pipelines | T3 | 6–8 months | Small/niche | 3/10 |

---

## Common Platform Changes (Prerequisites for Any Vertical)

Before entering any new vertical, these platform-level changes reduce the per-vertical effort for all subsequent markets:

### P1. Configurable Terminology / White-Labelling

Currently, labels like "Wayleave", "Fibre", "Cabinet", "Premises" are hardcoded across PHP templates and JS files. A per-tenant terminology config table would allow:

```sql
CREATE TABLE users.terminology_overrides (
    company_id   bigint REFERENCES users.companies(company_id),
    term_key     varchar(60),   -- e.g. 'wayleave', 'cable', 'cabinet', 'premises'
    term_label   varchar(80),   -- e.g. 'Easement', 'Main', 'Chamber', 'Connection Point'
    PRIMARY KEY (company_id, term_key)
);
```

This lets a water company see "Easement" everywhere a telecoms company sees "Wayleave" without a code fork.

**Effort:** 2–3 weeks (schema + PHP helper function + JS label injection at page load)

---

### P2. Configurable Asset Attribute Schema

Currently, infrastructure attributes (cable type, duct width, fibre count) are hardcoded columns. A dynamic attribute system would allow per-vertical custom fields on map features and project records without schema migrations per customer:

```sql
CREATE TABLE config.custom_field_definitions (
    field_id     bigserial PRIMARY KEY,
    company_id   bigint,
    entity_type  varchar(40),  -- 'project', 'asset', 'wayleave', 'premise'
    field_key    varchar(60),
    field_label  varchar(80),
    field_type   varchar(20),  -- 'text', 'number', 'select', 'date'
    options      jsonb         -- for select types
);
```

**Effort:** 4–6 weeks (schema + PHP CRUD + JS dynamic form rendering)

---

### P3. Vertical / Industry Selector at Company Setup

A simple `industry_vertical` field on `users.companies` drives which modules, terminology overrides, map layers, and report templates are shown to that tenant. Defaults all existing companies to `telecoms`.

```sql
ALTER TABLE users.companies
    ADD COLUMN industry_vertical varchar(40) NOT NULL DEFAULT 'telecoms';
-- values: 'telecoms' | 'water' | 'gas' | 'electricity' | 'heat_network' | 'ev' | 'towerco'
```

**Effort:** 1 week (schema + admin UI company editor)

---

## Recommended Execution Sequence

```
Phase 1 (Q2–Q3 2026):  Platform prerequisites (P1 + P3)
Phase 2 (Q3 2026):     Water vertical (uses same wayleave/easement engine, largest market)
Phase 3 (Q3–Q4 2026):  Gas + Electricity DNO (incremental on water base)
Phase 4 (Q1 2027):     District Heating (MDU-native use case, emerging regulatory mandate)
Phase 5 (Q2 2027):     TowerCos or EV (choose based on sales pipeline signals)
```

---

## Notes on Sales Strategy

- **Water/Gas/Electricity:** Target smaller independent operators and contractor consultancies first — large incumbents (Thames Water, Cadent) have long procurement cycles and may have existing GIS investments. Tier 2/3 contractors doing the physical build work are faster to sell to and influence platform adoption upward.
- **District Heating:** Early market with few established software players — first-mover advantage is available.
- **TowerCos:** Independent TowerCos (WIG, Cornerstone) are acquisition-hungry and move faster than MNOs. Site acquisition teams are the buyer persona, not IT.
- **EV:** Target charge point operators receiving LEVI/OZEV funding — the grant compliance documentation requirement creates a forcing function for structured software adoption (same dynamic as BDUK drove GeoLynx telecoms adoption).