How we work
A small firm that delivers like a large one, because the work is built on software.
Our engagements are bespoke. The engine underneath them is not. That is how fixed-fee, two-week diagnostics are possible on thousands of hectares.
Templum
The engine.
Templum is our delivery platform — the field of observation we mark out before reading what passes through it.
01
Ingest
Adapters for public and commercial satellite catalogues, drone orthomosaics, vehicle-mounted capture and field forms. Everything lands in one catalogue with provenance.
02
Resolve
Alignment, cloud and quality masking, time-series construction and a QA gate before any analysis runs. The single source of truth is a deliverable, not a by-product.
03
Analyse
Event impact, phenology, change and activity detection, forecasting. Models are fine-tuned per engagement; methods are written down and shipped with results.
04
Deliver
Interactive maps, map series and reports from one house template. Exports in open formats so nothing is locked to us.
Lituus
The collection method.
Lituus is how we design and run data collection: sampling design first, sensor choice second, logistics third.
Design
Stratify the area by what we already know from satellite; decide where ground truth changes the answer and where it doesn't.
Sensor
Satellite where it is sufficient, drone where resolution changes the decision, field capture where only a person can see it. Commercial imagery only when it pays for itself.
Logistics
Certified operators, flight and capture specifications, consent and access, QA at handover. We own the specification and the quality, not the aircraft.
Agentic delivery
Why it is fast.
Every repeatable step in the engine — ingesting an area of interest, running a pipeline, producing a QA report, drafting a deliverable — is a documented procedure that software agents execute under our supervision. The people on an engagement spend their time on the judgement calls: what the data can and cannot say, and what you should do about it.
Nothing client-confidential is sent to a third-party model without an explicit decision to do so, recorded in the engagement. Area-of-interest geometry, imagery and results stay in infrastructure we control, per client, with signed access.
Standards
- — Every analysis ships with methods, data sources and a validation table.
- — Open formats only: GeoPackage, GeoParquet, Cloud-Optimised GeoTIFF, PDF.
- — Background IP (the engine) stays with us; engagement outputs are yours.
- — Open-data attribution on every output; commercial data licensed to the client.