Schlumberger Houston vs. Schlumberger Surenco S.A.: What a White Contract Taught Me About Total Cost

Which Schlumberger entity should appear on your service agreement—Schlumberger Houston or Schlumberger Surenco S.A.?

If you want a single, universal answer, this article will disappoint you. There isn't one. The right answer depends on your well count, your operating complexity, your local legal exposure, and—a factor that rarely gets discussed—how much review time you actually have before the rig schedule forces a decision.

I've spent 11 years as a contracts and materials lead for independent E&P operators in Latin America. I've personally made (and documented) enough contracting mistakes to total roughly $1.8 million in wasted budget. Some were small, avoidable mistakes. Most involved the phrase 'white contract.' Now I maintain our team's pre-signature checklist, and this is the framework I wish I'd had from day one.

What I Mean by 'White Contract'

A white contract is not a formal legal term, at least not in the oilfield. What I mean is a signed agreement with structure but not specifics: rate columns left blank, scope descriptions vague, dates marked 'TBD.' It looks efficient at signature. It gets expensive at reconciliation.

To be fair, a white contract can work. But it works only when both sides have the same definition of the blank spaces. That requires leverage, legal support, and time. If you don't have all three, the blanks get filled by whoever has the upper hand later—usually the party that's already on location.

According to SLB's public website (slb.com), the company operates in more than 100 countries. That scale means 'Schlumberger' is not one uniform contracting entity. The legal entity you sign with determines which tax, labor, and logistics rules apply. And that difference shows up in your final cost.

Scenario 1: One Exploration Well and a Hard Budget

If you are a small operator running a single exploration well, your leverage is low, your legal review capacity is low, and the cost of an error is enormous. This is not the time for master agreements.

Use a locally registered Schlumberger entity, such as Schlumberger Surenco S.A., with a fixed-scope, fixed-price statement of work. The scope should fit on one page: these services, these rates, these deliverables, these dates. If it can't fit on one page, you haven't defined the work well enough.

Why Surenco rather than Schlumberger Houston? Because a local entity is built for local permits, taxes, customs, and response times. Houston can offer a global rate, but the 'global' rate doesn't include customs brokers, currency conversion, or a supporting engineer flying in from another country. By the time all that is added, the global rate is not the total cost.

This is where I made my first serious mistake. In 2019, I signed a white contract for a one-well job. The rate sheet had a blank row for 'interpretation package' (note to self: blank rows are not a technicality). I knew I should get written confirmation of the rate, but I thought, 'we've worked with these teams for years—what are the odds?' The odds caught up with me when the addendum arrived: $52,000 for services I thought were included.

That was not the worst part. The worst part was the 11-day delay while we fought the invoice. The rig was waiting. The rig cost more per day than the addendum.

The price you see on the quote is not the price you pay. The price you pay is the quote plus the addenda plus the waiting time plus the credibility you lose when you ask for more budget.

Scenario 2: A Multi-Well Program With a Mid-Size Contract Team

If you have a 3- to 10-well program and at least one person whose actual job is to read and enforce contracts—or rather, whose job is to read, enforce, and stop pretending the commercial team will do it later—you can start using a hybrid approach.

Let a Houston-based master agreement carry the global pricing and technology terms. Let a local operational contract with Schlumberger Surenco S.A. carry field execution. This is where total-cost-of-ownership thinking starts to matter.

A few years ago, I compared two quotes for a mud logging program. The Schlumberger Houston quote had a lower hourly rate. The Surenco quote was roughly 8% higher on the line item—but it included local mobilization, customs handling, and a bilingual field engineer. Houston's quote had none of those.

I assumed 'same technical standard' also meant the same commercial conditions. Didn't verify. Turned out each entity had different tax, logistics, and risk adders. The spreadsheet pointed to Houston. My gut pointed to Surenco. I went with the spreadsheet. Then the mobilization fee showed up, followed by two separate transportation charges.

The surprise wasn't the total. The surprise was that the regional entity was actually cheaper on an all-in basis. Local knowledge has a dollar value. On a multi-well program you need both the global technology and the local knowledge. The trick is keeping them in the right places.

A white contract at this scale should be limited to the master terms: payment terms, insurance limits, confidentiality, liability. Everything operational belongs in a statement of work. If someone says 'don't worry, that's covered by the master agreement,' ask which page. If they can't name it, it's not covered.

In Q1 2023, I had 48 hours to award a call-off before the rig slot closed. Normally I would have checked every addendum, but there was no time. I signed a tightly scoped SOW instead of a white contract. The extra hour of checking saved us $18,000 later.

Scenario 3: Large, Multi-Year Campaigns With Dedicated Commercial Support

Now the counterintuitive part: a white contract can be the right choice for a large operator with a multi-year campaign—but only if the blanks are limited to variables you have already priced.

Big campaigns need integrated execution. Wireline, mud logging, drillplan, completion, production optimization—when these services come from the same accountable party, coordination problems shrink. Schlumberger Houston can provide global account management, technical assurance, and technology roadmaps. A local entity like Schlumberger Surenco S.A. can provide permits, logistics, and in-country execution.

A master agreement that sets commercial principles is acceptable when you have volume and a contracts team to track the details. What most people miss is escalation. A white contract without escalation language looks good in year one and painful in year three. Labor costs move. Fuel moves. Security costs move. If your contract doesn't say how those changes are calculated, you will negotiate rates while a rig is standing still. That is not negotiation; that is a request for money.

So when I say a white contract can work, I don't mean a blank contract. I mean a contract with a filled-in rate card, an escalation formula, a change-order process, and a deadline for completing unfinished statements of work. The 'white' part should only be the parts you have agreed to leave for later, not the parts you forgot.

How to Draw a TCO Map That Catches White-Contract Blind Spots

Before you send anything to legal, take a blank sheet of paper and draw four boxes. This is the practical part—and yes, this is literally 'how to draw a' cost map that keeps you out of trouble.

1. Contract price: quoted rate, day rate, per-mile rate, per-run rate.
2. Access cost: mobilization, demobilization, customs, permits, transportation, taxes, visas.
3. Execution cost: supervision, data deliverables, standby time, fuel, water, cuttings handling, remote support.
4. Risk cost: the cost of being late, being wrong, or stopping work. Include your rig day rate, team time, and lost production.

Write a number in every box. If a box has 'TBD' or 'ask your account rep,' you are drawing a white contract. Decide, before signing, who will fill that blank later.

Think of it like the 2026 Winter Olympics skiing events. Teams don't choose skis based only on the sticker price. They match the ski to the snow conditions, the athlete, the temperature, and the support team that travels with them. A service contract works the same way. The cheapest line item can be the most expensive choice when conditions change.

Which Scenario Are You Actually In?

If you're not sure which path fits, use this test.

• Fewer than 2 wells per year and no full-time contracts lawyer? You are scenario 1. Use a local entity, fixed scope, fixed price, and skip the white contract entirely.
• 3 to 10 wells and at least one person tracking contracts? You are scenario 2. Use a Houston master agreement for global pricing, local SOWs for execution, and keep white-contract clauses out of operational documents.
• Multi-year, multi-rig program with a dedicated commercial team? You are scenario 3. Set up a white contract with a rate card, escalation formula, and quarterly TCO review. But call it what it is: a framework agreement with agreed blanks, not a blank check.

One more thing: update the TCO map after every major job. The point is not to be right forever. The point is to catch the cost that only appears after the fourth invoice. In the last 18 months, we've caught 47 potential errors by doing this before signature.

I've learned this the expensive way, and I'd rather you not repeat it. The next time someone hands you a white contract, take the extra hour. Draw your boxes. Fill in the blanks. If you can't fill in the blanks, don't sign.