Company
The measurement and the money should not be two different systems.
Basin Thread builds the Well Intelligence Platform. The bet is that the valuable part of field software is not the telemetry — it is carrying the measurement all the way through to the number the business runs on.
The problem we picked
Cloud SCADA is a solved and competently served market. What is not served is the gap between what the field measured and what the books say.
- Field systems record what an instrument reported. Accounting systems record what got booked.
- They always disagree a little, and no shared object represents the disagreement.
- So it gets resolved monthly, by hand, by whoever has the most patience.
Why it is worth owning
Reconciliation cannot be bolted on afterwards, because it depends on provenance that has to be captured at the moment of measurement.
- You cannot reconstruct which lab result a volume rested on after the fact.
- A platform that captures provenance at the source can answer questions a downstream tool never can.
- That makes reconciliation a property of the measurement layer, not a reporting feature.
Why manual capture is the wedge
Most wells are not fully instrumented and will not be next year. A platform that only understands telemetry only understands part of the field.
- Gauge sheets, strapping tables and hauled loads are where the uninstrumented majority is measured.
- Treating that as a first-class measurement path, not a data-entry form, is unusual.
- It is also the most checkable claim we make — anyone who has done the work recognises whether it was built by someone who has.
How we build
The engineering commitments are visible in the product and are not negotiable when they are inconvenient.
- It fails closed. No fabricated continuity, ever.
- Missing is never rendered as zero.
- Nothing is silently restated behind someone who already acted on it.
- We do not claim certifications we do not hold or metrics we have not measured.
Where things stand
Basin Thread is «TODO: confirm» — founding date, location and team size have not been supplied, and this page will not invent them. That is the same standard applied to the rest of the site: where a fact is not established, it is marked rather than filled in with something plausible.
The thesis, stated plainly
Two competent categories exist today. Cloud SCADA vendors sell field connectivity, alarming and control, and do it well. Production accounting vendors sell the books. Between them sits the reconciliation, and it is performed by people in spreadsheets because neither side owns it.
We think the side that should own it is the measurement side, for one structural reason: reconciliation needs provenance, and provenance can only be captured when the measurement happens. By the time a volume reaches an accounting system it is a number without a history. Any tool downstream of that point is reconstructing, not verifying.
That is why the platform is built as SCADA first and reconciliation second, rather than as a reporting layer with a field connector attached.
Why now
Two things changed. Publish-subscribe telemetry over constrained cellular made it economic to connect the long tail of sites that could never justify a polled connection. And a phone in every pumper’s pocket made the uninstrumented tanks reachable without a hardware programme.
Together those mean full-field measurement coverage is now achievable for an operator who could previously only instrument the top twenty wells. Coverage is what makes reconciliation meaningful — reconciling a fifth of the field against the books does not settle anything.
Investors and partners
If you are looking at this from the investment or partnership side rather than as an operator, there is a separate and quieter path:
get in touch.
We would rather have that conversation directly than through the operator demo funnel.
See it against your own wells.
A demo runs against synthetic data first, then against a read-only connection to your system of record if you want to see real numbers.