Skip to content

Research & development

Some problems can't be bought. Those are the ones we investigate.

A lot of important operational problems fall between the categories — too specialised for an off-the-shelf product, too tied to real operations for a conventional agency, and too uncertain for a fixed-scope contract. We investigate those, test what's actually viable in real conditions, and turn the strongest approaches into systems that can be used and owned. Applied, evidence-based, and connected to delivery — not research for its own sake.

How it works

Understand, prove, operationalise.

Research and delivery aren't separate services — they're a continuum. The same discipline that de-risks an uncertain problem is the one that ships an ownable system at the end of it.

01

Understand

Investigate the operation, the constraints, and the underlying problem. What's really going on, what's been tried, and whether there's even a viable technical answer. Output: findings, requirements, a feasibility read.

02

Prove

Explore the uncertain part before committing to a build. Experiments, proofs of concept, and field prototypes tested against real conditions — so we know what's viable, not just what's plausible.

03

Operationalise

Turn a validated approach into a reliable, documented system the client can run and own. Research that ends in a report isn't the model — ours ends in something usable.

Where we go deep

The problems we keep coming back to.

Environmental & atmospheric modelling

Accelerating scientific computing and dispersion modelling workflows — and the hardware that runs them — for environmental consulting.

Field sensing & distributed monitoring

Resilient telemetry across mixed protocols and remote sites, with commissioning and diagnostics that hold up in the field, not just the lab.

Environmental & operational data systems

Normalising, brokering, and making sense of messy operational and sensor data — LIMS-style systems, pipelines, and reporting that stay traceable.

Maintainable, client-owned software

Treating documentation, handover, and long-term operability as engineering problems in their own right — the discipline behind everything we ship.

AI in operations, applied responsibly

Where retrieval, triage, and automation genuinely help — used because they fit the work, with the failure states exposed and a human accountable.

How we talk about it

We say exactly how mature something is.

Research shouldn't be dressed up as deployed capability. When we write about a piece of work, it carries one of these labels — so experiments are never mistaken for production systems.

01

Exploring

Problem framed; investigating approaches

02

Testing

Building experiments or proofs of concept

03

Validating

Prototype under real-condition trial

04

Operationalising

Turning a validated approach into a system

05

Deployed

Running, owned by a client or operator

Bring us a difficult problem.

If you have an important operational problem with no clean answer — and you want a straight read on whether it's technically and commercially viable — start with a conversation. A Discovery Sprint is where feasibility gets established.