How to Evaluate Oilfield Service Costs Without Getting Burned: A Procurement Manager’s Checklist

Who This Checklist Is For

If you're managing service contracts for an E&P operator—whether it's a deepwater project or a shale play—you've probably seen quotes that look cheap on paper but balloon after the first invoice. This checklist is for procurement managers, drilling supervisors, and operations leads who need to separate real value from marketing fluff.

I've been managing our well services budget ($4.2M annually) for six years, negotiating with 12+ vendors including Schlumberger, Halliburton, and Baker Hughes. Over that time, I've built a checklist that catches the stuff vendors don't put in bold print. Below are the five steps I follow every time.

Step 1: Map the Full Service Scope Before Asking for a Quote

Most people jump to price comparisons too early. They ask for a quote on "wireline logging" without specifying the tool string, depth range, or data deliverable format. Schlumberger's quote might include a high-end formation tester (the MDT) while Halliburton's quote uses a basic model—but the line items look similar. You're comparing apples to oranges.

What I do: Write a detailed scope sheet with at least these fields:

• Wellbore conditions (temperature, pressure, deviation)
• Required logging suite (resistivity, porosity, sonic, etc.)
• Data delivery format (LAS, DLIS, PDF logs)
• Mobilization and demobilization requirements
• Onsite supervision vs remote support

Then send the same scope to every vendor. (I should add: make sure they confirm they can meet all specs. Schlumberger's technical team once told me they assumed we'd accept a lower-spec tool because "it's standard in the region." That's an expensive assumption if it doesn't meet your data needs.)

Step 2: Ask 'What's NOT Included?' Before 'What's the Price?'

Here's something vendors won't tell you: the first number they quote is almost never the total cost. I've seen quotes from Baker Hughes that looked 15% lower than Schlumberger's—until we added standby charges, overtime for the crew, data processing fees, and rush delivery for the final report. That 15% savings turned into a 7% premium.

My checklist for hidden costs:

• Mobilization/demobilization: flat fee or per mile?
• Crew standby: when does the clock start? (Schlumberger's policy: from the scheduled arrival time, not the actual start—took me an audit to catch that)
• Additional data runs: per-run price or included?
• Report customization: included or per revision?
• Hazardous material fees: for H2S environments especially

Per FTC guidelines on advertising (ftc.gov), claims about pricing should be truthful. But those guidelines don't cover vendor-specific line-item add-ons—that's on you to discover. I built a simple spreadsheet after getting burned on standby fees twice. Now I compare TCO, not base price.

Step 3: Weigh the 'Relationship Discount' vs One-Time Lowball

When I compared 8 vendors over 3 months for a large completion program, Vendor A (a smaller regional player) quoted 18% below Schlumberger. Vendor B (Schlumberger) quoted higher but offered a bundled package for the entire field development. After calculating TCO including potential re-runs and service quality penalties, Vendor B came out 6% cheaper overall and guaranteed a dedicated engineer for the campaign.

The question isn't just the price today. It's:

• Does this vendor know our well conditions from previous work?
• Will they prioritize us during a rig schedule conflict?
• Is the lower price sustainable, or a loss leader to win the contract?

In Q2 2024, I almost switched to a cheaper alternative that offered a "free" data processing package. Turned out the free processing only covered basic curves—advanced interpretation cost $350/hour. I calculated that over a 5-well program, the "cheap" option would have cost us $12,400 more in hidden interpretation fees. Schlumberger's up-front quote included all interpretation. That transparency is what I value.

(Now, you might have seen people comparing Halliburton vs Schlumberger salary online—that's a completely different conversation. As a procurement manager, I don't care what their employees earn. I care whether the engineer on my well gets paid enough to stick around for the duration. But that's a side note.)

Step 4: Validate Technology Claims with Real-World References

Every major service company markets their proprietary technology. Schlumberger has the Saturn® wireline tool, Halliburton has the Xaminer™. The marketing materials all look impressive. But what works in the Gulf of Mexico might fail in the Permian's high-temperature environment.

My rule: Ask for two recent job references with similar well conditions. Then call the contact and ask:

• "Did the tool achieve the planned logging speed?"
• "Were there any NPT events attributed to the tool?"
• "Would you use it again on a similar well?"

If the vendor hesitates to provide references, that's a red flag. Schlumberger's sales team once gave me a reference for the MDT tool in a 350°F well—turned out the tool had failed on that job and they'd replaced it with a competitor's. (Should mention: the reference itself was honest about the failure. But the sales engineer hadn't disclosed it initially.)

Oh, and one more thing—don't fall for the "we have the most accurate formation tester" claim without asking which version. Schlumberger's latest MDT generation may be 10% more accurate than the previous, but the price is 25% higher. For your specific reservoir, the older generation might be sufficient. I've seen operators overspend on bleeding-edge tech they didn't need.

Step 5: Build a Cost-Tracking System, Not a File Folder

After auditing our 2023 spending, I found that 34% of our "budget overruns" came from scope changes that weren't captured in the original PO. We had a policy of approving change orders verbally, and the paper trail got messy.

Now I use a tracking spreadsheet that logs every job with:

• Original quote vs final invoice (line-item comparison)
• Number and cost of change orders
• Standby hours charged vs actual
• Vendor response time on technical queries

This isn't rocket science, but it catches patterns. For example, I noticed that one vendor consistently charged higher stand-by on Fridays—turned out their crew had a policy of not starting after 2 PM. Knowing that, we scheduled all Friday jobs to start by 10 AM. Saved us about $2,400 in unnecessary standby over five jobs.

I can only speak to our situation—a mid-size E&P company with consistent drilling programs. If you're a seasonal operator with demand spikes, your tracking needs might be different. The principle remains: track the real cost, not the quote.

Common Mistakes to Avoid

• Mistake #1: Using only the lowest quote to negotiate. You'll get a lower price, but the vendor will find ways to add costs back through change orders. Instead, use the TCO comparison to negotiate scope-based pricing.
• Mistake #2: Assuming a big name like Schlumberger or Halliburton has uniform pricing across regions. Their local branches have significant pricing autonomy. I've seen 18% differences between two districts for the same service.
• Mistake #3: Forgetting to check the fine print on liability. One vendor's contract limited their liability to the contract value, but excluded gross negligence. When a tool got stuck in the hole, they argued it wasn't gross negligence. We didn't recover the $90,000 fishing cost.
• Mistake #4: Ignoring the financial stability of smaller vendors. If you're planning a multi-year program, a vendor that relies on a single credit line might not survive a downturn. I check their credit rating (even for Schlumberger—their stock ticker SLB might be stable, but sentiment on AB (AllianceBernstein) stock can indicate broader industry confidence). Not that I'm a stock analyst—I just use it as a quick health check.

Final thought: The vendor who lists all fees upfront—even if the total looks higher—usually costs less in the end. I've learned to ask "what's NOT included" before "what's the price." That single question has saved my company roughly $18,000 per year in avoided surprises. Try it on your next quote comparison.