Built by the people who run the QSRAs.
SOMA Risk Studio isn't a tool a software house built and hoped a risk team would want. It's built by the risk team — practitioners who run quantitative schedule risk analysis on UK strategic infrastructure for a living, and who got tired of the workflow fighting them.
Founded by Adam O'Neill, lead practitioner — 15 years in Project Controls on UK strategic infrastructure.
The judgement calls are made by people who've had to defend them.
A risk tool is a stack of judgement calls: which check is a blocker and which is a warning, where a constraint is material to the result, when a correlation matrix is too far from valid to trust, how honest to be about what per‑decile attribution can and can't see.
Get those calls wrong and you either wave through a bad number or drown the analyst in noise. We make them the way we'd make them on a live scheme — because we do make them on live schemes, in front of clients, assurance teams and, increasingly, the regulator. The product inherits that instinct, and it's the reason a less experienced analyst can lean on it safely.
Three things we hold ourselves to — and how we know we do.
Honest before easy
We've told our Tier‑1 client three times in 18 months that what they asked for would slip a release. Each time they thanked us. That's what "trusted to deliver" looks like when nobody's looking — and it's the same instinct that keeps unproven claims off this website.
The relationship is the product
The person who picked up the phone on day one is the person who picks it up on day 600 — and the person whose name is on the release notes. No account team, no inbox triage, no being passed around.
Every release earns its place
Risk Studio ships continuously because the team building it runs QSRAs for a living. Every release closes a real problem we hit on a real scheme that week — not a roadmap item dreamed up away from the work.
Domain fluency is necessary. It isn't sufficient.
Knowing QSRA cold is what makes the judgement calls right. Building it like production software is what makes them safe to rely on. Risk Studio is held to a bar that a defensible tool needs and most in‑house tools never get near.
- 10,000+ automated tests, run on every commit, with zero errors against the canonical release audit. The maths, the validators and the exporters are pinned by regression — a change that would move a number has to prove itself first.
- Versioned, continuously delivered — the current release is V2.12.1, and every module, filename and on‑screen string reads its version from one source of truth. No drift between what the tool says and what it is.
- Audit‑first by design — every run is captured in an HMAC‑chained log and re‑runnable to byte‑identical output. Defensibility isn't a feature bolted on at the end; it's the spine the rest hangs off.
- The consultancy stands behind it — SOMA Project Controls Ltd, a UK‑registered company (D‑U‑N‑S® 232556078), Middlesbrough. The same people who answer the phone are the people who own the code.
Because we'd run hundreds of QSRAs by hand and knew exactly what was broken.
Spreadsheets that didn't validate themselves. Safran round-trips that ate three days a period. Four different framework checklists run inconsistently across schemes. We weren't theorising — we were the team doing the work, and we knew what the workflow should feel like instead.
300+ versioned releases later, Risk Studio is in production across a major UK infrastructure delivery programme. Every feature on the roadmap started as a complaint we made on a Tuesday afternoon. That's how it stays useful — and that's how we kept it ours to fix.
Talk to the person who builds the product.
We don't have a sales team. The person who picks up the phone is the person who runs your account — and the person whose name is on the Risk Studio release notes.
Company details & policies.
Registered office
SOMA Project Controls Ltd
C/O Fortis Accountancy Services Ltd
Middlesbrough
TS3 8TF
United Kingdom
D-U-N-S® 232556078
Policies
Read our Privacy policy and Terms of use. For a data processing addendum or the procurement pack, email hello@somaprojectcontrols.com or visit the resources page.