Your pumper scribbled gauges on a greasy sheet Tuesday. It got mailed in Friday. Admin re-keyed it Monday. By the time you look at the numbers, the well that died last week has been dead for nine days. That gap (two to three weeks behind reality, on a business where the revenue check is the score) is the problem oil and gas production software is supposed to solve, and most of the products sold into this market make it worse before they make it better.

Oil and gas production software captures daily well production volumes from the field, turns those volumes into reports, and feeds every downstream system (allocation, accounting, regulatory filings) that depends on accurate numbers. For independents (a handful of wells up to 2,000+), it is the foundational layer. If it breaks, everything else breaks with it.

This post is for you if:

  • Your production data is running more than 48 hours behind reality and you want to know what it costs to close that gap.
  • You run anywhere from 15 wells to 2,000+ and you are stuck between “Excel is held together with tape” and “the enterprise suite wants $300k.”
  • Your back office is re-keying paper gauge sheets into spreadsheets at 9 p.m. and you are tired of paying for that twice.
  • You want the honest read on mobile capture tools, spreadsheets, and enterprise suites before you sit through another 45-minute demo.

If you want a sales pitch, close the tab. If you want the straight version from people who talk to independent operators for a living, keep reading.

What Oil and Gas Production Software Does

Production software sits between three groups of people who rarely talk to each other in plain English: pumpers in the field, admin in the office, and engineers or owners looking at the numbers. The job of the software is to make those three groups agree on what happened yesterday and let each of them see the piece they need.

The core workflow looks the same across every real product in this category.

  1. A pumper visits a well or battery and records production volumes (oil, water, gas), tank gauges, run tickets, injection volumes, chokes, pressures, downtime, and any notes worth keeping.
  2. That data moves from the field to a central system. In a modern tool this is a phone or tablet syncing over cellular. In a legacy setup it is paper gauge sheets faxed, mailed, or hand-delivered to the office.
  3. Admin or the office reconciles the field data against run tickets, tank strappings, and sales nominations.
  4. The software emits whatever the business needs next: daily production reports, monthly state filings (TX RRC PR, OK OCC 300R, and similar), allocation splits, revenue decks, decline curves, engineering dashboards.

Anything a production software vendor sells you that is not part of that loop is either a feature for a different category (accounting, SCADA, data management) or a nice-to-have. Evaluate based on the core loop first, then decide if the extras matter.

For a full map of how production software relates to adjacent categories like accounting and allocation, see the oil and gas software overview.

The Three Real Categories Operators End Up Choosing Between

The market has hundreds of products. The honest picture is that they fall into three camps. You will end up in one of these regardless of what the sales rep calls it.

Category 1: Spreadsheets (and paper)

Most small operators start here and many stay longer than they should. Pumpers call or text in numbers, a relative of the owner types them into Excel, someone prints the monthly and signs the state form by hand.

It works when: you run 1 to 10 wells, you know every pumper by their truck, your reporting obligations are simple, and nothing gets lost because only a handful of people touch the file.

It breaks when: you grow past roughly 15 to 25 wells, hire a second or third pumper, start taking on non-operated interests, need to split production across owners, or miss a state filing because someone was on vacation. The failure is never one catastrophic event. It is a slow erosion where errors compound until you realize the numbers you trusted for three years were wrong by several hundred barrels a month.

Category 2: Mobile production software (field-data-capture tools)

This is the category where GreaseBook lives. A pumper opens an app on their phone or tablet, records well data as they gauge, and the office sees it within minutes. The data flows into reports, allocation, and state filings without being re-typed.

It works when: you run roughly 5 to 1,000 wells, you have at least one pumper (contract or employee), your wells are conventional (rod pump, ESP, plunger, gas lift, injection), and you want the office to see production in near-real-time without building your own data pipeline.

It breaks when: your wells are predominantly high-volume horizontals with real-time SCADA already in place, your company runs on enterprise ERP suites that demand native integration (SAP, Oracle Oil and Gas, Quorum), or your pumpers refuse to touch a phone. The last one is less common every year, but it is still real.

Category 3: Enterprise production suites

Pak Energy (formerly WolfePak), Peloton, Enertia, Quorum, and a handful of others sit at the top of the market. These are platforms that bundle production, accounting, land, and sometimes reserves and regulatory into one stack. They are serious tools built for serious budgets.

It works when: you have 1,000+ wells, a dedicated IT department, a controller who wants one vendor to call for everything, and six figures a year of budget earmarked for software plus implementation plus training.

It breaks when: you are a small or mid-size independent (anywhere from a handful of wells to a few hundred) who was sold the enterprise dream by a good salesperson. The implementation takes 9 to 18 months, the annual cost is a meaningful percentage of your revenue, and 80 percent of the features sit unused because your operation does not have the people or the scale to use them. Every year the upper-mid independent market reads the same story: company buys the big suite, company eventually migrates back down to a tool that fits.

For a deeper look at how operators actually rank the tools in category 2 and 3, see our best oil and gas production software breakdown. If budget is the blocker and you want to know what free or low-cost options actually exist, read oil and gas production software free.

What Production Software Actually Costs

Pricing in this category is genuinely opaque because most vendors refuse to publish numbers. Here is the honest range based on what operators report.

Tier Typical cost What you get
Spreadsheets $0 plus your time Excel, paper, a shared drive, and the assumption that nothing important breaks
Mobile production software $15 to $40 per well per month, all in Pumper app, office dashboard, core reports, state filing prep, basic allocation, support that actually answers the phone
Mid-market suites $50 to $200 per well per month, plus $10k to $50k implementation Production plus allocation plus accounting plus land, custom integrations, user training included
Enterprise suites $200+ per well per month, plus $100k to $500k+ implementation Everything above plus custom workflows, dedicated account team, multi-year contracts

A mid-size independent (say 50 wells) paying $25 per well per month for mobile production software spends $15,000 a year. The same operator looking at an enterprise suite is quoted $300,000 to $600,000 all-in for the first three years. The math decides the category for most independents before any feature comparison happens.

What to Look For If You Are Buying

Most of the evaluation checklists floating around the internet were written by vendors to win RFPs. The operator-side checklist is shorter and more honest.

1. Can a pumper who has never used your software before be productive in under 10 minutes? If the answer is “we have a great 3-day training program,” that is a red flag. Real pumpers have three wells to get to and no patience for software that fights them. The tools that win in the field are the ones that work like a phone, not like a SAP module.

2. What happens when cell service drops? Any honest vendor will tell you the app has to work offline, queue the data locally, and sync the second signal comes back. If the demo only runs in a boardroom with wi-fi, ask how it behaves at a battery with no bars. You will spend half your field time in dead zones and you cannot afford to lose numbers.

3. How fast does the office see field data? The whole point of mobile production software is that office and field stop being on a two-day lag. If the data shows up in the office the next morning instead of in real time, you bought something that is closer to a paper replacement than a production system. That may still be fine, but price it accordingly.

4. Who do you call when something breaks at 6:30 AM on a Tuesday? Production software is operational infrastructure. If the vendor’s support is email-only or routes through three tiers before a human answers, that is a problem when a pumper cannot log in at shift change. Ask for the actual phone number of the support line and call it during the demo.

5. What does it cost to leave? Ask explicitly: if I decide to migrate in 18 months, what does my data look like on the way out? Operators who cannot answer this question discover at the wrong moment that their three years of production history is locked inside a proprietary format.

Amateur vs Pro: How Operators Buy Production Software

The amateur… The pro…
Picks the platform the sales rep pushed hardest in the boardroom demo Runs a 30-day pumper trial on real wells, in real cell dead zones, before signing anything
Treats the accounting vendor’s production module as the production system Runs a dedicated production app and integrates it with whatever accounting platform the back office already pays for
Signs a 3-year contract to get the “best price” Won’t sign past 12 months without a field-tested track record
Stays on spreadsheets three years past the breaking point because “we’ll migrate later” Migrates the week the second pumper is hired and the error rate starts climbing
Assumes SCADA on the best wells means the rest of the wells are covered Plugs SCADA-sourced data and pumper-entered data into one production layer so office and field see the same numbers

The best operators we see do not win by owning the fanciest platform. They win by picking a tool that pumpers will actually open on the second Tuesday of March, then integrating it cleanly with the accounting suite.

What To Avoid Before You Buy

  • Don’t fall into the Bolt-On Trap. Whatever accounting platform your back office runs (OGsys, Wolfpak, Bolo, SSI, Pac Energy on the mid-range tier, or P2, Quorum, W Energy at the next level up), the production module bolted on to it is jack of all trades, master of none. It was built for the accounting workflow, not for a pumper in a truck at 5 a.m. Run a dedicated production app and feed clean data into the accounting suite you already run.
  • Don’t let the Paper Lag decide your pricing. A vendor quoting enterprise prices to replace paper gauge sheets is selling overhead, not a solution. The math for mobile production software on an independent operation lands in the $15 to $40 per well per month range. Anyone much higher than that is selling the wrong tier.
  • Don’t pick on price alone. A production app that loses two run tickets a month costs more than the one twice the price that doesn’t. Cheap that fails in a cell dead zone is the most expensive kind of cheap.
  • Don’t skip offline mode. Any vendor whose demo only runs on boardroom wi-fi is hiding what happens at a battery with no bars. Offline capture with auto-sync is a requirement, not a feature.
  • Don’t buy for the company you wish you were. A 50-well independent does not need the platform built for 5,000-well majors. Size the software to the operation you actually run.

Who This Guide Is Not For

This page is written for independent and mid-sized operators running conventional wells. It is not the right guide for everyone.

Pure data-engineering shops whose bottleneck is already wrangling historian data from thousands of continuous SCADA tags should be looking at production data management software and historian tools as their primary investment, with mobile production software layered on top to catch the human-verified side (run tickets, tank gauges, downtime notes) that SCADA cannot see. Horizontal shops that run SCADA on their top producers still plug GreaseBook in as the centralized production layer. That combination is common.

Heavy SCADA environments where automation and remote monitoring already cover your top producing wells should evaluate this category as a complement to SCADA, not a replacement. Mobile production software captures the human-verified side of operations (run tickets, tank gauges, maintenance notes) that SCADA still cannot see.

Enterprise ERP shops already standardized on SAP, Oracle, or Quorum should evaluate production tools inside that ecosystem first. The integration cost of bolting on a non-native tool usually outweighs the feature gap.

Pure royalty owners and non-operators do not need production software. You need allocation reports from your operator and a way to read them, which is closer to production allocation software.

How Production Software Fits Into the Rest of the Stack

Production software is the front door to every other data-driven decision in your operation. What it feeds:

  • Allocation: daily per-well volumes are the input to commingled allocation and revenue splits. See production allocation software for the downstream piece.
  • Accounting: volumes times prices equals revenue. Bad volumes equal bad revenue. Accounting software is only as honest as the production numbers feeding it.
  • Regulatory filings: monthly state forms (TX RRC PR, OK OCC Form 300R, ND NDIC Form 5, and similar) are built directly from production volumes. See oil and gas regulatory production reports for the state-by-state map.
  • Engineering: decline curves, type curves, and forecasting all start from a clean production history. Garbage in, garbage out.
  • Data management: if you run enough wells, you eventually want a historian or a warehouse. See production data management software for what that looks like.

The pattern: production software is the layer everything else reads from. Get it right first, then worry about the rest.

Field-side guides that teach the numbers your software captures

Production software is only as honest as the data the pumper writes into it. These guides cover what that data actually describes at the tank battery.

Frequently Asked Questions

Is Excel still a legitimate option for production tracking?

Yes, for roughly 1 to 15 wells with a single pumper and a tolerant regulatory environment. The failure points are growth, turnover, and the month you hire your second pumper. Most operators stay in Excel three years longer than they should, then spend a painful quarter migrating out of it.

How long does it take to roll out mobile production software?

Honest range: 1 to 3 days for a small crew (a few pumpers, a few dozen to a couple hundred wells) with good cell coverage. Longer if you have complex allocation, multiple partners, or a pumper crew that rotates frequently. Any vendor quoting a 6-month implementation for a small operation is selling you enterprise overhead you do not need.

Do I have to change how my pumpers work?

The right mobile tool maps to how a pumper already works. Gauge the tank, note the run ticket, record the pressures, move to the next well. The change is replacing paper with a phone, not redesigning the field workflow. If your pumpers push back hard on a tool, it is usually the tool’s fault, not the pumper’s.

What happens to my 10 years of Excel history when I switch?

Real production vendors import historical volumes during onboarding. Ask for the import process in writing before signing anything. If the vendor cannot describe how your historical data arrives inside their system, that is a signal they expect you to type three years of history manually.

Will production software file my state reports for me?

It prepares the data in the format the state wants and often exports directly to the regulator’s portal. The actual filing is still your responsibility, because regulators require an operator-of-record signature. The software eliminates the data wrangling, not the regulatory relationship.

About the author: Greg Archbald is the founder of GreaseBook. He built the product from inside the oil patch and has spent 15+ years on the operator side of oil and gas technology.

The Short Answer

If you are running more than 15 wells and still on spreadsheets, you are paying in errors, re-work, and late reports what the software would cost you in dollars. If you are running fewer than 15 and the current system works, there is no urgency. If you are a small or mid-size independent looking at enterprise suites, stop, and look at mobile production software first.

GreaseBook sits in category 2 and is designed for small and mid-size independents (anywhere from a handful of wells to 2,000+). It is not the right tool for a 10,000-well major or a company that has already standardized on an enterprise suite. For everyone else, it is worth a 10-minute look.

Two minutes. No sales call, no pushy follow-up.

If GreaseBook lands and the fit turns out wrong inside year one, the 200% money-back guarantee refunds you twice the contract price. That is how confident we are in the pumper-adoption bar.

P.S. This page is not for running a major or a midstream asset. No hard feelings. If you are still deciding, the quiz gives you a straight answer in the time it takes to refill your coffee.