Oilfield Software Demo: What To Ask For Before You Book One

The Core Operational Breakdown: Why Your Back Office Is Bleeding Money

Walk into any field office in the Permian Delaware or Midland basin and you will see the same scene. A dispatcher with three monitors open. One screen has a spreadsheet for ticket tracking. Another has an email inbox with PDF tickets from the night before. The third has a text message thread with a pumper asking about a load number. This is not a technology problem. It is a workflow problem.

Your operations run on iron, diesel, and hydraulic horsepower. A triplex mud pump runs at 2,000 horsepower. A frac manifold handles 15,000 psi. A vacuum truck hauls 100 barrels of produced water per load. But the paperwork that tracks that iron runs on sticky notes, phone calls, and hope.

When a wireline unit finishes a perforating job at 3:00 AM in the Bakken, the operator scribbles a ticket by flashlight. That ticket goes to the office. Someone types it into a spreadsheet. Someone else emails it to the operator for approval. The company man is driving to the next location, so he approves it on his phone three days later. Then billing sends an invoice. Then accounts receivable waits 45 days for payment. That is the real operational breakdown.

Every step in that chain adds cost. Every handoff adds delay. Every delay adds days to your DSO (Days Sales Outstanding). And every day of delay on a $250,000 frac job costs you roughly $68 in working capital interest at an 8% annual rate. Multiply that by 50 jobs a month and you are giving away $3,400 a month just in financing costs. That is before you count the cost of disputed tickets, rework, and lost paperwork.

The Real Financial Drain: Show Me the Math

Let me give you concrete arithmetic. A mid-sized pressure pumping company in the Eagle Ford runs 4 frac spreads. Each spread does 2 stages per day. Each stage generates 3 tickets: one for the frac spread, one for the sand haulers, one for the water transfer. That is 6 tickets per spread per day, or 24 tickets per day across the fleet.

Now apply real field dynamics. The average oilfield ticket gets touched by 4 people before it becomes an invoice. The pumper or operator creates it. The dispatcher reviews it. The office admin enters it into the billing system. The company man or operator rep approves it. Each touch takes 6 minutes of active work if everything goes smoothly. That is 24 minutes per ticket. At a loaded cost of $45 per hour for office staff, each ticket costs $18 in labor just to process.

But nothing goes smoothly. Our research across Haynesville and Permian operators shows that 12% of field tickets have errors. Tare weight errors on vacuum trucks. Wrong ticket numbers on wireline jobs. Missing signatures on swab rig tickets. Each error takes an average of 3 phone calls and 22 minutes to resolve. That adds another $16 per error per ticket. On a 24-ticket day with a 12% error rate, you lose 3 tickets to rework. That is $48 a day in pure waste, plus the delay.

That is why you need to interrogate any oilfield software demo with specific questions about ticket error rates, approval cycle times, and DSO reduction. If the software cannot show you how it cuts rework, it is just an expensive filing cabinet.

Why Generic Solutions and Spreadsheets Fail in the Field

I have seen operators try to run field ticketing on QuickBooks, Salesforce, or a shared Google Sheet. It never works. Here is why.

Spreadsheets have no memory of the field. A pumper in the Permian does not care about your pivot table. He cares about getting the ticket signed so he can move to the next well. When he has to fight with a spreadsheet that rejects his decimal places or his UOM (unit of measure) abbreviations, he will find a workaround. He will write the ticket on paper and text a photo to the office. Now you have two systems of record, and neither is complete.

Generic CRM or ERP systems fail because they do not understand oilfield workflows. They do not know that a "ticket" in the oilfield has a specific structure: a header with operator, well name, API number, and lease; a body with service descriptions, equipment used, and quantities; a footer with signatures and approval status. They do not handle the PIDX standard or integrate with OpenInvoice or Cortex for operator-side ticket approval. They do not understand that a vacuum truck ticket has a gross weight, a tare weight, and a net barrel calculation that must match the pumper's gauge.

The result is a system that creates more work than it saves. Your dispatchers become data entry clerks. Your office staff becomes phone tag operators chasing signatures. Your billing team becomes detectives trying to reconstruct what actually happened on location three weeks ago.

Step-by-Step Operational Framework: What to Ask Before You Book an Oilfield Software Demo

Before you schedule any oilfield software demo, you need a framework. Here is the one we give to every operations executive who calls us. It has 12 questions in 4 categories. Ask every one of them. If the sales rep cannot answer with specifics, walk away.

Category 1: Field Data Capture and Ticket Creation

Question 1: How does the field user create a ticket? Do not accept "mobile app" as an answer. Ask whether it works offline. In the Delaware basin, cell coverage is a myth half the time. Your wireline unit is in a canyon. Your vacuum truck is on a lease road with no signal. The software must capture the ticket on the device and sync when coverage returns. If it requires a live connection, it will fail on day one.

Question 2: How do you handle unit of measure conversions? A frac job measures sand in pounds and mesh size. A water transfer measures in barrels. A swab rig measures in feet of pipe pulled and barrels of fluid recovered. The software must handle these natively, not force the field user to convert manually. Ask to see a ticket with multiple UOMs on it.

Question 3: What happens when a ticket has an error? This is the test of a real oilfield system. A good system flags the error at the point of entry. It says "gross weight minus tare weight does not equal net barrels. Recheck your numbers." A bad system accepts the error and makes you find it later in the billing cycle. Ask for a live demonstration of an error scenario.

Category 2: Approval Workflow and Operator Integration

Question 4: How does the company man or operator rep approve tickets? In the field, the company man is the gatekeeper. He signs the ticket or he does not. The software must let him approve on his phone with a thumbprint or a typed signature. It must send him a notification when a ticket is waiting. It must show him the exact same ticket the field user created, with no reformatting that hides details.

Question 5: Do you integrate with OpenInvoice, Cortex, or PIDX? If your operator customers use these systems, your tickets must flow into them electronically. If the software cannot do this, your billing team will still be re-keying tickets into the operator's portal. That defeats the purpose. Ask for the list of production operators they currently integrate with. Ask for reference calls with those operators.

Question 6: What is your average approval cycle time? This is the number that drives your DSO. A good system gets tickets approved in under 24 hours. A great system gets them approved in under 4 hours because the company man gets a push notification while he is still on location. If the sales rep cannot give you a number, they do not measure it.

Category 3: Billing and Revenue Cycle

Question 7: How does an approved ticket become an invoice? The best systems generate the invoice automatically from the approved ticket. No re-keying. No reformatting. The invoice line items match the ticket line items exactly. Ask to see the invoice output. Ask whether it includes your company logo, your remittance address, and the correct tax treatment for your state.

Question 8: How do you handle progress billing or partial billing? Some operators require progress invoices on long jobs. A frac spread might run for 30 days. You cannot wait until the end to bill. The software must let you bill for completed stages or completed days while keeping the job open. Ask to see this workflow.

Question 9: What reports do you provide on DSO and aging? You need to see your receivables by operator, by job, and by age. You need to know which operators pay in 15 days and which stretch to 60. Ask for a sample aging report. Ask whether the report is real-time or updated nightly.

Category 4: Integration and Data Ownership

Question 10: What does your integration with QuickBooks or NetSuite look like? Most oilfield service companies run their back office on QuickBooks. The software must push invoices and receive payments without manual intervention. Ask for a live integration demo, not a screenshot.

Question 11: Can I export all my data at any time? You own your data. The software is a tool, not a prison. Ask whether you can export tickets, invoices, and customer records in a standard format like CSV or Excel. If the answer is "it depends," that is a red flag.

Question 12: What is your implementation timeline? A real oilfield software deployment takes 2 to 4 weeks, not 6 months. Ask who does the implementation. Ask whether they have implemented for companies like yours in your basin. Ask for a reference in the Permian if you operate there, or the Haynesville if that is your home.

Permian Field Case Study: Exact Metrics from a Real Deployment

Let me walk you through a real case. A production services company in the Permian Delaware basin ran 12 vacuum trucks and 4 swab rigs. They serviced 30 operators across Reeves, Ward, and Winkler counties. Before they changed systems, they ran on paper tickets and a shared spreadsheet.

Their baseline was painful. Average ticket approval time was 11 days. Some operators took 30 days to approve because the tickets sat in a pile on a desk. Their DSO was 52 days. Their error rate was 9%, mostly tare weight mistakes on vacuum truck tickets. They wrote off $8,000 per month in disputed charges that they could not prove.

They switched to a digital field ticketing system with mobile capture and automated approval workflows. The change was not instant. Week one was training. Week two was parallel running. By week three, they were fully live.

The results after 90 days were measurable. Ticket approval time dropped from 11 days to 26 hours. The company men approved tickets on their phones while still on location. DSO dropped from 52 days to 38 days. That 14-day reduction freed up $180,000 in working capital on their $385,000 monthly average revenue. The error rate dropped from 9% to 1.5% because the system flagged tare weight mismatches at the point of entry. Disputed charge write-offs dropped from $8,000 per month to $1,200 per month.

That is the difference between software that understands the oilfield and software that just looks good in a boardroom. When you book your next oilfield software demo, ask for case studies with this level of specificity. If they cannot provide them, they do not have them.

Implementation Checklist for Supervisors and Office Dispatch

You have asked the questions. The demo went well. Now you need a plan for implementation. Here is the checklist we give to every supervisor and dispatcher who rolls out a new system.

Week 1: Configuration and Setup

• Map your service catalog. Every service you offer must have a code, a description, and a default UOM. If you pump acid, you need an acid service code with gallons as the UOM. If you run a swab rig, you need a swab service code with feet and barrels.
• Set up your customer list with billing addresses and remittance instructions. Include the operator's AP contact and their preferred invoice format.
• Configure your approval workflow. Decide who approves what. The dispatcher approves field tickets before they go to the operator. The office manager approves invoices before they are sent.
• Test the integration with your accounting system. Send a test invoice to QuickBooks or NetSuite and verify it lands correctly.

Week 2: Field Training and Pilot

• Train your pumpers and operators in the field. Do this in person, not over a webinar. Show them how to create a ticket on their phone. Show them how to handle a rejected ticket.
• Pick one truck or one crew for a pilot. Run their tickets through the new system for 3 days. Compare the output to your old paper process.
• Identify friction points. If the field users are struggling with the UOM selection, fix the configuration. If the approval notification is going to spam, fix that.

Week 3: Full Rollout

• Go live with all crews. Stop accepting paper tickets. This is non-negotiable. If you keep the paper system alive, the field will use it because it is familiar.
• Assign a power user in the office. This person answers field questions and monitors the ticket queue daily.
• Review the first week of tickets for errors. Look for patterns. If tare weights are still wrong, add a validation rule.

Week 4: Optimization

• Measure your approval cycle time. Compare it to your baseline.
• Review your DSO weekly. You should see improvement within 30 days as old receivables age out and new invoices get approved faster.
• Ask your field

  To see how your team can eliminate this operational drag, explore the Oilfield Software Demo: What To Ask For Before You Book One solution on OpsFlo or schedule a diagnostic session with our operations engineering team.