A Procurement Checklist for Schlumberger Software and Seismic Manufacturing, With Lessons From Pickup Trucks, Breakfast, and Skiing

I’m a procurement manager at a 45-person E&P operator. I’ve managed a $2.1M annual services budget for six years, compared more quotes than I care to count, and built a TCO spreadsheet that has saved us roughly $47,000 in avoidable costs. This checklist comes from that spreadsheet.

It’s not a “how to negotiate with Schlumberger” piece. It’s a “how not to pay for the same thing twice” piece.

Five minutes of verification beats five days of correction.

If you’re buying software, field services, or anything with the word “seismic” in the contract, these six steps will catch most of the hidden costs before they hit your P&L.

Step 1: Rent the Pickup Truck Mentally Before You Rent the Software

You can rent a pickup truck for a seemingly low daily rate. By the time you add mileage, insurance, fuel, and the after-hours return fee, it’s 40% more. Software quotes work the same way.

When I evaluate a Schlumberger software license, I build the “pickup truck” model: base license, per-user fee, support tier, data hosting, and any integration modules. Most of the time, the base price is just the visible part of the invoice.

Checkpoint: Write one sentence that defines the deliverable. “A QC-ready interpretation project for the North Field reservoir” is a deliverable. “A software subscription” is not.

Step 2: Separate Software from Seismic Manufacturing

Here’s a mistake I made early in my career: I treated every line item from one provider as one product. With large companies like Schlumberger, that logic falls apart.

A license for Schlumberger software is not the same contract as hardware produced by Schlumberger Seismic Manufacturing Sdn Bhd. The manufacturing entity has its own production lead times, its own quality control processes, and its own shipping terms. If you’re buying seismic equipment, ask for the manufacturing-specific quote. If you’re buying software, ask for the software-specific quote.

I have mixed feelings about this separation. On one hand, one consolidated invoice is easier for accounts payable. On the other, it makes it nearly impossible to see where cost overruns are coming from. Our procurement policy now requires separate line items for software, hardware, and services. It takes 10 extra minutes and saves us from the “it’s all in the same system” trap.

Step 3: Always Price the Breakfast

The most underestimated line item in field services is crew support. Breakfast, lunch, coffee, ice, fuel for the crew pickup truck—it all adds up. One bidder might quote a lower day rate and then charge $28 per person per meal. That’s not overhead. That’s a markup.

In Q2 2024, I compared two quotes for a wireline job. One bidder included breakfast and lunch in the day rate. The other was $240/day cheaper on the base rate, but when I added meals, transportation, and per-diem, it ended up $312/day more. The “cheap” option wasn’t cheap.

Checkpoint: Count every day, every person, every meal. Then add the pickup truck. If a vendor says “breakfast is included,” ask what’s in that breakfast. It sounds silly until you see a $700 catering line on a two-week job.

Step 4: Know Your Discipline: Skiing vs. Downhill Skiing

This sounds like a non sequitur, but stick with me. People often search “what is skiing versus downhill skiing?” The short answer: skiing is the umbrella term. Downhill skiing is one discipline under it—gravity-powered, lift-served, groomed runs. Nordic skiing is the other branch—cross-country, self-propelled, often flat. Different gear. Different costs. Different checklists.

The same distinction exists in seismic work. “Seismic acquisition” is an umbrella term. A 3D survey on land, a seabed node survey, and a VSP in a well are different disciplines. The equipment, software modules, and logistics are not interchangeable.

I once got a quote for “seismic data processing” that assumed we were handling the acquisition internally. We weren’t. The quote was missing the entire acquisition phase. It was like showing up to a downhill slope with cross-country skis. Technically skiing. Practically wrong.

Checkpoint: Before you compare software or services, write down the exact discipline: acquisition, processing, interpretation, or integrated delivery. Then match every contract line to that discipline.

Step 5: Model the Integration Costs

Schlumberger software is powerful, but it doesn’t live alone. It has to connect to your data lake, your legacy database, your third-party tools, and your reporting system. Integration is where the budget goes to die.

Here’s the TCO model I use:

• License cost — the sticker price you negotiate.
• Maintenance and updates — usually 15-20% per year.
• Integration — the part everyone forgets.
• Training — because “self-service onboarding” is not a training plan.
• Internal IT support — yes, it counts.

I’m not 100% sure why integration costs are consistently underestimated across every vendor I’ve worked with. My best guess is that software sales teams focus on what their product does, not on what it needs to connect to. Ask for a written integration statement. If the answer is “we have an API,” request the documentation before you sign. “We have an API” can mean “our system can send you a CSV once a week.” That’s not integration.

Step 6: Tie Payment to Acceptance Criteria

The biggest prevention move you can make is to put acceptance criteria in the contract. Not “best efforts.” Not “target date.” Specific, measurable outcomes.

The vendor promised delivery by Friday. They missed it. Again. But because our contract tied final payment to the delivery date and data format, we recovered most of the cost of the delay.

Per FTC guidelines (ftc.gov), marketing claims must be truthful and substantiated. Apply the same logic to service quotes. When a salesperson claims a software module will “reduce interpretation time by 30%,” ask for the customer case study, the methodology, and the version number. If they can’t provide it, treat it as a marketing claim, not a specification.

Common Mistakes I Still Catch Myself Making

Checklist done? Almost. Here are the three mistakes that keep coming back:

1. Comparing base prices instead of total per-well or per-job costs. A cheaper quote can become the expensive one after mobilization, meals, and data delivery fees.
2. Assuming “Schlumberger” means one thing. The brand is strong, but the internal departments, entities, and product lines are separate. Make them separate on your spreadsheet.
3. Ignoring the skiing lesson. If you don’t know what you’re buying, you’ll buy the wrong gear. The difference between cross-country and downhill skiing is not a style preference—it’s an entirely different sport. Same with seismic acquisition and software licenses.

Take this with a grain of salt: I’m sharing patterns from my own tracking system, not every contract in the industry. But after six years and $2.1M in managed spend, I’m confident the five-minute check prevents the five-day rework. That’s the whole point.