Oil & gas · Custom software

Custom software for oil and gas operations

Most software sold into field operations assumes connectivity, and the field does not have it. What follows is predictable: crews keep using paper because paper works at the location, and the office receives it weeks later. Offline capture is not a feature here. It is the precondition for anything else being adopted at all.

Start a buildIndustry overview
08Internal tools · Data pipelines
Custom software08
Internal toolsData pipelinesAutomation
Oil & gasIllustrative

Custom software

Internal tools, document and data pipelines, and automation.

Custom software · Oil & gasOne pairing of the matrix
Service
Custom software
Industry
Oil & gas
Covers
Service companies · Working-interest operators · Field & wireline · Midstream services
Architecture
Unchanged from every other vertical — only the breaks differ
Engagement
A defined build, or run under management

What usually breaks

Before anything gets built.

The same failures recur across oil & gas. Strygon maps the specific system before proposing anything, but these are the ones worth checking for.

Paper in the field

Tickets are written by hand at the location and travel back in a truck. Anything illegible, lost, or disputed three weeks later is revenue the company already spent to earn.

Coding after the fact

Costs get coded to the well, lease, or AFE by someone in the office guessing from a ticket, long after the person who did the work could have said.

Invisible until month end

Spend against an AFE is only knowable once the period closes, so an overrun is discovered when it is far too late to do anything about it.

Recurring in oil & gasObserved pattern · the specific system still gets mapped

The approach

What Strygon does about it.

Custom software, aimed at those failures specifically rather than at a generic checklist.

01Custom software
Offline is the default state, not the error stateCustom software
01
Part of the scoped build

Offline is the default state, not the error state

Tickets are captured, signed, and held on the device with no connection assumed, then released the moment signal returns. Nothing waits on a bar of service.

02Custom software
Coded by the person who did the workCustom software
02
Part of the scoped build

Coded by the person who did the work

Well, lease, and AFE coding happens at the point of capture, by the crew who know what the work was, rather than by someone in the office reading a ticket a fortnight later.

03Custom software
Approvals travel with the ticketCustom software
03
Part of the scoped build

Approvals travel with the ticket

Signature and supervisor approval live on the record itself, so a disputed ticket is answered from the system instead of from a folder in a truck.

The approach for this pairingScoped in writing before work starts

What gets built

Concrete deliverables.

Everything in custom software, applied to how oil & gas actually runs.

All of custom softwareIndustry overview
Internal tools and dashboards
Document and data processing pipelines
Roles, permissions, and an audit trail of who changed what
Payment, subscription, and invoicing workflows
AI-assisted automation where it earns its place
API integrations between systems that don’t natively talk
In scopeScoped in writing before work starts

Also for this industry

Other parts of the same system.

CRM & automation
CRM & automation03
Pipeline architectureSpeed-to-lead
Applied hereIllustrative

CRM & automation infrastructure

Service work is won on relationships and a callback. The pipeline is usually a phone and a memory, and it does not survive the operator's procurement cycle.

Read the crm & automation read
Accounting & financial ops
Accounting & financial ops11
Invoicing & ARReconciliation
Applied hereIllustrative

Accounting & financial operations

Ticket to invoice is measured in weeks, and every day of that is money the company already spent to earn sitting uncollected.

Read the accounting & financial ops read
Local & private AI
Local & private AI01
Self-hosted inferenceRetrieval on private data
Applied hereIllustrative

Local & private AI models

Handwritten tickets, scanned reports, and daily logs are the record. Reading them is exactly the work a model is good at, and exactly the data an operator will not send anywhere.

Read the local & private ai read

Start

Start with what’s broken.

Send the situation in a paragraph. Strygon comes back with a read on what’s likely wrong and what it would take to fix, before anyone talks about price.

Most builds start withleads dying in an inbox., three half-finished pipelines., follow-up nobody owns., numbers that never agree., four vendors blaming each other.

Or email hello@strygon.com

What to send
A paragraph. What broke, and where it shows up.
What comes back
A read on what is likely wrong and what fixing it takes.
Price
The last conversation, not the first