The Developer-Owned Operations Platform

Your contractor knows
what happened today.
Now you do too.

ROAM gives offshore wind developers an independent, real-time record of every task, permit and milestone on their project. It is built to be the contemporaneous evidence that delay claims, payment applications and audits turn on.

Twelve modules, one record
Progress
Permit to Work
Weather & Workability
Tasks
Personnel
Documents
Assets
Tickets
QHSE
Inspections
Operations Hub
Dashboard
July 2026
Web platform delivered
Q1 2027
Mobile app planned, coming soon.
Why Developers Use ROAM

The record that de-risks your build.

Offshore wind disputes are settled on evidence. ROAM captures an independent, developer-owned record as a by-product of daily work — so you hold the answer before the claim arrives.

Delay claims met with your own record

Your LD entitlement is only worth what you can prove. When the contractor applies for an extension of time, the whole argument turns on what caused the delay and who owned it. ROAM is built to give you a contemporaneous record made as the work happened, not a reconstruction assembled after the claim lands.

Pay against proof

Check every milestone claim against the operational record before the money leaves, rather than eighteen months later in front of an adjudicator. To illustrate: on a £600m contract, a 2% milestone error is £12m.

Ready for regulators, insurers and lenders

A contemporaneous safety and operational history, held in a system you control from day one, ready for the day a regulator, an insurer or a lender asks to see it.

Where ROAM stands

What is built, and what is not yet.

Join the field trial
Built

Web platform

Delivered in July 2026 with twelve modules. It is now being hardened with our development partner.

In final testing

Integrations

Azure AD sign-in, Vortex Mundus weather data, SharePoint documents and Mitti.

Now

Field trial recruiting

We are pre-launch, with no customers yet. Design-partner places are open.

Platform Modules

Every module builds the same record.

The audit trail is a by-product, not a report written afterwards. That only works because ROAM runs the work itself: the permits, the tasks, the inspections, the weather calls.

Nine more, all feeding the same record

Tasks Personnel Documents Assets Tickets QHSE Inspections Operations Hub Dashboard
Explore the full platform
How It Works

One record, written as the work happens.

The record is built while the work is done, not assembled from memory afterwards. It exists because ROAM is the system the job runs through.

01

Plan & Configure

Set the project up once: roles, rules, thresholds, workflows. After that ROAM holds everyone to it, on every site, every day.

02

Permit & Execute

Where a task type requires a permit, the work is checked against weather limits and competency before anyone starts. The Authorised Person stays in charge of every suspension, and each one is logged.

03

Monitor & Report

You see what the contractor sees, at the same time they see it, across safety, productivity and risk.

Permit workflow, illustrated
Task created & assigned
Personnel & competency verified
Weather window checked
Permit issued & approved
Work executed & logged
Permit closed
Each step is timestamped and linked to the assets and people involved.
Questions developers ask

Straight answers before the demo.

Will my contractor have to work in it?

Not on day one. You can start with the record alone, kept by your own team: progress, weather, documents, personnel and assets. Running permits and tasks through ROAM is a second step, agreed with your contractor.

Who owns and hosts the data?

You own it. ROAM runs on Microsoft Azure. Sign-in through your own Azure AD and document storage in your own SharePoint are in final testing.

How is it priced?

Per project, per year, by project capacity and the modules you use. Never per seat.

What does a pilot involve?

Three months on one of your projects, with the fee credited against the first year if you continue. How design partnership works.

12
Modules, every one feeding the same record
4
Integrations in final testing: Azure AD, Vortex Mundus, SharePoint and Mitti
3
Design-partner places open before launch

The next dispute is coming. Have the evidence ready.

See how an independent, developer-owned record would be configured for your project — and what it protects you from.