Skip to content
Ultramar Labs
IndustriesResearched concept

Custom software for oilfield service companies

Field ticket → sign-off → invoice, without losing tickets between the wellsite and the office.

The operating cycle
  1. Service request
  2. Schedule & dispatch
  3. Crew & equipment
  4. Field work & JSA
  5. Customer sign-off
  6. Ticket review
  7. Invoice
What we hear most often

Tickets lost between field and office

Paper tickets come back hours late, missing photos, materials, and a signature.

Slow ticket-to-invoice

Billing waits on re-keyed field data and manual approvals.

Equipment & crew visibility

No single view of what crew and equipment is assigned where.

Offline reality

Crews work where there's no signal — records must capture offline and sync later.

Where the gaps usually appear

The handoff most likely to fail is field sign-off → ticket review — where paper tickets, photos, and approvals go missing between the wellsite and the office.

RecordField ticket & JSACaptured on paper or photos at the wellsite, then re-keyed hours later.
ApprovalCustomer sign-offCollected in the field and often missing, illegible, or delayed.
SystemDispatch ↔ accountingThe dispatch board and billing don't share data, so it's entered twice.
PeopleDispatch · crew · operator · billingFour roles touch one job with no shared, current view of it.

What Ultramar might do — no prebuilt vertical product

KeepYour accounting, rate agreements, and price lists.
ConnectDispatch, field tickets, and billing into one flow.
ExtendA customer or operator portal for status and sign-off.
BuildAn offline-friendly field-ticket app when nothing fits.
Capability demonstration · Fictional data

Field ticket to office-ready record

Dispatch a job, complete an offline field ticket with evidence and sign-off, and produce an invoice-ready packet.

Try it yourself
Capability demonstration · Fictional data
Complete

Interactive example with fictional data. No live vendor accounts are connected here. For your business, we confirm software access and supported actions before building the workflow.

Basin's tools — now connectedDispatch appCrew group textPhone camera rollJob spreadsheetQuickBooksnothing replaced · nothing retyped

Billing

same day

Job packet · WO-3307

Time & materials
6.5 hrs · 2× seal kit, 1× gauge
Safety
JSA attached
Evidence
2 photos
Signature
J. Whitfield, on site 2:38 PM
Exception
0.5 hr overtime — approved by Carla, office
INV-2291 created in QuickBooks · ready to sendnothing retyped

Margin on WO-3307 · 18%quoted 31%

  • Hours6.5 actual vs 6.0 quoted−$180
  • Materials2nd seal kit — flange worse than expected−$240
  • This month3 jobs over quote, all at Wellsite 12's rate−$1,310

Your dispatch app knows the hours. Your books know the rate. Only one record knows whether the job made money — today, while you can still price the next one.

Without this, so far · illustrative

2 retypes4 calls~78 min

Month-endSpreadsheet vs QuickBooksToo late to act

Today: margin shows up at month end, when the bookkeeper reconciles the spreadsheet with QuickBooks — too late to price the next one differently.

  1. Job dispatched
  2. Ticket captured
  3. Customer signs
  4. Exception reviewed
  5. Invoice-ready
  6. Margin, while it still matters

The ticket that just arrived is also the margin: 6.5 hours against 6.0 quoted, plus a second seal kit — this job came in at 18% instead of 31%. Three jobs did that this month, all on the same customer's rate.

Now you drive: press each button yourself, playing both the field crew and Basin office.

Try it yourself →
What could change
  • A field-ticket app that works offline
  • A customer or operator portal for status and sign-off
  • A reporting layer over your existing accounting
  • An integration connecting dispatch, tickets, and billing

Not sure where to start? That's what the Working Session is for.

Bring the workflow that frustrates you most. Within 24 hours you get a written Brief with two or three concrete directions and our recommended first move.