How to Price an Oilfield Job: The Rate Structure That Decides Your Margin

Second in a series on the oilfield job playbook. The same job can be priced three different ways and produce three different margins. Most companies pick one out of habit. The ones that price on purpose keep more of what they earn.

In the first article of this series, I made the case that an oilfield job is a chain that runs from the first quote to the final paid invoice, and that the companies who win are the ones who never drop it. The first link in that chain is pricing. It is also the link that most companies treat with the least intention.

Here is the uncomfortable part. The same job, with the same crew, the same equipment, and the same days on location, can be billed three different ways and leave you with three different margins. Per day. As a flat job price. Or per unit of work, like per run or per stage. None of those is wrong. But choosing one without understanding what it does to your invoice, your risk, and your margin is how a profitable scope quietly becomes a break-even one.

This article is about building a pricing structure on purpose: the layers it should have, the full menu of rate types available to you, how the model you pick changes the invoice, and the practices that keep your billed rate matching your agreed rate every time.

Good oilfield pricing is not a single number. It is a hierarchy, and each layer does a specific job.

The price book is the baseline. This is your standard catalog: the day rates, periodic rates, standby rates, service and per-run rates, mobilization and demobilization charges, minimum charges, repair rates, consumables, and replacement or sale prices for everything you offer. A controlled rate book is what lets you quote consistently and invoice the same day a ticket is approved, because every rate already has an agreed value. When the rate book is loose, every quote becomes a negotiation from scratch, and every invoice becomes a guess.

The customer agreement sits on top of the price book. This is where negotiated terms for a specific client or basin get locked in: discounts, rate overrides, package pricing, escalation rules, and the exceptions that always come up, like emergency callouts, subrentals, and non-standard consumables. The agreement should carry effective and expiration dates and a single active version per customer or contract, so there is never ambiguity about which rate applies on a given day.

The job-level price sits on top of the agreement. This is the operational contract, the service agreement or work order that ties an agreed price to a specific scope, location, and set of start and stop rules. It has the highest priority. When a competitive job needs a one-time rate to win it, that lives here, at the job level, without rewriting the customer agreement or the rate book underneath it.

The priority rule is what makes the whole structure usable: the job-level price overrides the customer agreement, which overrides the rate book. The most specific rate wins. The practical payoff is that a salesperson can win a competitive job with a sharp number, and the system still knows exactly what to bill, because the job rate flows down into the ticket and the invoice automatically. Nobody re-keys a rate from memory. That single discipline, making rates flow downhill rather than getting retyped at each stage, removes one of the most common and least visible causes of billing disputes.

Most companies use two or three rate types and forget the rest exist. Here is the full set worth having configured and ready.

Day rate. A fixed daily charge per unit. The workhorse of equipment rental. Simple, transparent, and the default for open-ended or equipment-heavy jobs.

Periodic rate. Weekly or monthly rate breaks. On a long rental, the per-day cost should step down automatically once the unit has been out past a defined threshold. This protects the customer relationship on long jobs and should be a rule, not a manual favor someone remembers to apply.

Standby rate. A reduced rate for equipment or crew that is committed but idle, waiting on the customer. Standby should always carry a reason code and a timestamp, because undocumented standby is where rental companies quietly give away money.

Package or bulk price. A single fixed price for a defined bundle of equipment, labor, and consumables, or for an entire job scope. Predictable for the customer, and efficient to invoice, but it shifts overrun risk onto you if the scope moves.

Per-service or per-run rate. A charge tied to a unit of work rather than to time: per run, per stage, per descent, per job. This is how a lot of activity-based oilfield services are actually priced, because the customer perceives value in the work performed, not the hours the tool sat on location.

Volume and tiered pricing. Rate reductions that kick in by quantity or frequency, for master accounts and high-utilization customers.

Time-limited or promotional pricing. Defined-period discounts for a customer group, used for seasonal campaigns or retention, with a built-in expiry so they do not become permanent by accident.

Mobilization and demobilization. Transport and setup, charged by trip, zone, or mileage band. Worth defining precisely, because vague mob terms are a frequent source of disputed line items.

Minimum charges. A floor that protects you on small jobs and short rentals, so a half-day call-out does not cost you money to service.

Replacement and sale pricing. The values that apply when equipment is damaged, lost in the hole, or sold outright. These are not rental rates, they are recovery rates, and they need to be agreed in advance so a claim is not a negotiation under pressure.

Subrental pass-through. Third-party equipment you rent in to cover a job, passed through with your agreed markup and tracked against the job so the cost is recovered correctly.

This is the part most worth sitting with, because it is where pricing stops being administrative and starts being strategic. Take one job and run it through three models.

Picture a downhole tool string on a ten-day well intervention. Same equipment, same crew, same ten days.

Priced per day, at an illustrative six hundred dollars per unit per day, the rental bills around six thousand dollars before mobilization, and your invoice is a clean delivery-to-return rental line. If the job runs long, you keep earning. If it ends early, you stop. Your revenue tracks time on location.

Priced as a flat job, the same scope might be sold as a single five thousand dollar package. The customer loves the predictability and signs faster. But now you carry the risk: if weather or the well adds three days, you absorb them unless you wrote a change-order trigger into the scope. The invoice is one line, and your margin lives or dies on how well you scoped the job.

Priced per run, if the work is four runs at an illustrative eighteen hundred dollars per run, the same physical job bills around seven thousand two hundred dollars, and the invoice ties to documented runs rather than to days. The customer pays for work performed, and a slow day on location does not cost you revenue, but a job that needs fewer runs than expected earns you less.

Same crew. Same iron. Same ten days. Three invoices, three risk profiles, three margins. The numbers above are illustrative, but the lesson is not: the pricing model is not a billing detail, it is a commercial decision about who carries the risk and how your revenue behaves when the job does not go to plan.

And it goes one level deeper. The same unit on the same job can carry more than one price across its time on location. The active days bill at the day rate, the days it sat waiting on the customer bill at the standby rate, and a long stretch converts to the periodic rate. One rental, one job, several rates, because the billing reflects what the equipment was actually doing on each of those days.

The model you choose decides the shape of the invoice, the cadence of billing, and what the customer is even able to dispute.

A day-rate job produces a rental invoice across a billing period, with prorating for partial periods, periodic breaks on long rentals, standby splits where they apply, and a clear off-rent date that stops the clock. The thing to watch is the gap between the agreed off-rent rule and the physical return, because that gap is either billed correctly or given away.

A flat-price job produces a single clean line, which is efficient, but it pushes all the discipline upstream into scoping. Any work beyond the scope has to flow through a change order, or it becomes free work that erodes the margin you priced.

A per-run or per-stage job produces an invoice where the count of documented runs is the invoice. The field ticket is not just supporting paper, it is the billing instrument, which means a missed or unsigned run record is missed revenue with no clean way to recover it after the fact.

Across all three, the same principle from the first article holds: the rate has to inherit. When the agreed price flows from the agreement into the quote, into the ticket, and into the invoice without anyone retyping it, billing matches intent. When it does not, you get variance, and variance is what customers reject and what stretches the time it takes you to get paid. Pricing structure and days sales outstanding are connected more tightly than most operators realize. A clean, inheriting rate structure is a cash-flow tool, not just an accounting one.

A few disciplines separate companies that price on purpose from companies that price by reflex.

Match the model to the work and the customer. Price by day when revenue should track time and the job is open-ended. Price as a package when the scope is well-defined and the customer values predictability, and write the change-order trigger before you sign. Price per run or per stage when the customer perceives value in work performed and the activity, not the calendar, is what varies.

Run one active agreement version per customer, with dates. Effective and expiry dates remove the ambiguity about which rate applied on which day, which is exactly the ambiguity that fuels disputes.

Gate the discounts. Any rate below a margin threshold should route through an approval, with an audit trail of who changed the price and when. Discounting is a decision, not a reflex, and it should leave a record.

Make rates inherit, never re-key. The agreed rate should flow downhill into the ticket and the invoice automatically. Manual re-entry is where variance is born.

Set the rules, not the favors. Periodic breaks, standby reductions, and minimums should be configured rules that apply automatically, not things a billing clerk remembers to do on a good day.

Define the billing trigger for every model. Day rate starts on confirmed delivery. Per-run bills on the documented run. A package bills on milestone or completion. Decide this up front so the field knows what to capture.

Reconcile before you release. Validate the billed rate against the agreed rate before the invoice goes out. This three-way check, rate against terms, quantity against tickets, serials against what shipped, is what earns first-pass approval and keeps your cash cycle short.

Measure realized rate, not just list rate. Track what you actually collected against what you listed, and margin by pricing model, so you learn which models protect your margin and which quietly erode it.

Pricing is the first link in the job chain and the one with the most leverage, because it is decided before a single tool moves and it governs everything that gets billed afterward. The Price book, the customer agreement, and the job-level price are the structure. The rate types are the menu. The model you choose for a given job decides who carries the risk and how your revenue behaves when reality diverges from the plan. Price by design, make the rate inherit all the way to the invoice, and you protect margin you would otherwise never see leave.