Argus Built on the pad,
because that is where it hurt.
Argus started as an internal tool. A field engineer was driving between wells to read numbers off a drive display, and losing a shift of production every time a pump tripped at 2 a.m. and nobody knew until the morning round. The first version existed to stop that happening on the wells he looks after. It still runs on them.
Built inside a working field.
We would rather say it.
The producing wells in the case study belong to a heavy-oil operator in Trinidad, where the founder also works as the site's field engineer. That is not an arm's-length customer reference and we do not present it as one.
What it does mean is that the software was shaped by consequences rather than by a specification. Every alarm exists because something happened at 2 a.m. and the alarm did not. The torque-creep detection exists because a well sanded up slowly enough that fixed thresholds never fired. The field log's offline queue exists because Starlink blinks.
The next fields will be somebody else's, and we will label those differently when they arrive.
Small team.
Short answers.
Four people.
One of them is on the pad.
Put your field online.
First well live in days, not quarters.