Choosing
field service software for an oilfield operation is not the same problem as choosing it for HVAC or elevator maintenance, and most of the buying advice online is written for those industries.
The differences matter. Your crews work where there is no signal. Your equipment gets rented, not just serviced. Your invoices have to satisfy an operator’s AP portal, not a homeowner. And a missing ticket costs you the revenue, not just the paperwork.
Here’s a process built for the oilfield version of the problem.
Step 1: decide who the system is for
It sounds obvious. It’s also where most evaluations go wrong.
A system chosen by finance optimizes for reporting. A system chosen by operations optimizes for dispatch. A system chosen by IT optimizes for integration. All three miss the same thing: whether a tech with cold hands will actually use it at 11 PM.
Put one field tech on the evaluation team. Not to vote on architecture. To complete a ticket on his phone during the demo, with the vendor watching. What he says afterwards tells you more than the rest of the evaluation.
Step 2: write the five workflows that matter
Every vendor demo covers the same generic path: create job, assign crew, complete work, invoice. Yours are messier than that.
Write down the five workflows your business actually runs. For most oilfield service and rental companies they look something like this:
- A rental going out, coming back dirty, getting cleaned and recertified, and going out again.
- A multi-well job where costs allocate by well and the invoice ties to the operator’s AFE.
- A job where the rate changed after the quote, and both parties agreed in the field.
- A ticket created with no signal at all, signed by the customer, synced hours later.
- A month-end close where every operational event has to be accounted for.
These five are your test script. Every vendor gets the same one.
Step 3: test offline properly
Every vendor claims offline capability. The claim means different things.
Ask specifically: what happens when two crews edit the same equipment record while both are disconnected? A vendor with a real answer describes their conflict resolution. A vendor without one changes the subject.
Then ask when GPS is captured, at ticket creation or at sync. If it’s at sync, your tickets will show the crew at the yard when the job was fifty miles away.
And ask whether signature capture works the same offline as online. Some systems quietly degrade.
If you can, put the app in airplane mode during the demo and complete a ticket. Two minutes of that is worth an hour of discussion.
Step 4: map the integration boundary
The most common implementation failure is not technical. It’s ambiguity about which system owns which data.
Get the answer in writing before you sign. The clean version: the field system owns operational events, what happened, when, on which unit, approved by whom. The accounting system owns posted financials, the general ledger, the audit trail. Data flows one direction on a defined schedule.
Ask which accounting systems have live production integrations today, not planned ones. Ask what syncs automatically and what needs a person. Ask what happens when a sync fails, and who finds out.
Step 5: check the operator side
Generic field service software fails this step completely.
Which operator portals does the system submit to natively? OpenInvoice and Cortex cover a lot of North America, but your customer list decides what matters.
What happens when an operator changes its requirements? Product update or paid project? Ask for an example from the last twelve months.
Does the invoice carry the supporting documentation the operator expects, attached, in the right format?
A supplier who submits cleanly gets renewed without a conversation. A supplier whose invoices bounce becomes the example the operator uses to prove they’re managing costs.
Step 6: price the whole thing
License fees are the visible number and rarely the deciding one.
Ask about implementation: how long, who does the work, what does it cost, and what does your team have to provide. Ask what happens if your fleet grows 30 percent. Ask what support costs after year one.
Then price the alternative. What does your current process cost in leakage, late write-offs, DSO drag, and the hours your controller spends assembling things by hand? For a mid-size rental company that number typically runs into the hundreds of thousands annually. The comparison is software cost against that, not software cost against nothing.
Step 7: check the references yourself
Ask for a customer with your specialization and roughly your size. Then ask to speak with them without the vendor on the call.
Three questions worth asking that customer:
- What took longer than you expected during implementation?
- What does the system still not do well?
- If you were choosing again, what would you ask that you didn’t ask?
Vendors give you references who will say yes. The useful information is in the second and third answers.
The shortlist
Run those seven steps and you’ll have two or three names, not ten. The specialization question and the operator portal question eliminate most of the market before you’ve sat through a demo.
Then pick the one that handled your five workflows best, not the one with the longest feature list. Depth in your work beats breadth in someone else’s.
