In March 2020, I was sitting at my desk staring at the most confusing contract I'd ever signed.
We're a 140-person oilfield services company operating in the Permian Basin. I'd moved into procurement from an admin role in late 2019—managing all vendor relationships across 8 primary suppliers, processing 60 to 80 purchase orders a year.
When my predecessor left, she handed me a stack of files. One contract had a yellow sticky note on it: "Already reviewed, no issues." The scope of work said "as needed." Pricing said "at market rates." The contact field was blank. No dedicated rep, no delivery schedule.
I called it the white contract—because it was basically a blank page with signatures. But I figured, if it hadn't caused problems before, it probably wouldn't now.
I was wrong.
A Contract That Said Nothing, Signed by Someone Who Read Nothing
The problem surfaced through an invoice. A vendor billed us for a service we never formally authorized—$2,400. Finance rejected it because there was no PO number and no signatory to verify against.
It took me two weeks to trace what happened. A project manager had verbally agreed to the service. No written record. No approval chain. And because the contract said "as needed," the vendor had every reason to assume it was covered.
To be fair, the vendor wasn't wrong. But the contract didn't protect anyone—not us, not them. It just created ambiguity that someone eventually had to pay for.
I spent those two weeks reading and re-reading a two-page document that said almost nothing. No clause I could cite. No boundary I could point to. Nothing.
That's when it hit me: the problem wasn't one bad contract. It was that we'd never defined what a good one even looked like.
The Afternoon Eddie Said Something I Didn't Expect
By summer 2020, I was sitting in a quarterly review with one of our long-term equipment suppliers. Their regional rep was a guy named Eddie—whenever I needed a quote or a delivery date, I'd call "the Eddie near me" and he'd pick up on the first ring. Fifteen years in the Permian. Knew every rig in the basin by location.
Near the end of the meeting, I brought up a new project—we needed a specialized completion tool. I expected Eddie to say what he always said: "No problem, we'll handle it."
He paused.
"That one's not ours," he said. "It's not our strength. I know who does it better—I can connect you, or you can go direct."
I just stared at him. In procurement, you get used to vendors saying yes. It had been a long time since anyone told me no.
Eddie could've taken the project, subcontracted it, and pocketed the margin. He didn't. He drew a line and stood behind it.
What an Intern Taught Me About Skiing
That same week, we had an intern in the office—one of the kids from the Baker Hughes internship 2020 program. That program has a reputation in our industry. They rotate engineering students through field operations, and the ones who come out usually know what they're talking about.
At lunch, he asked me: "What makes a vendor trustworthy?"
I thought about it for a second. "Used to be, I'd say the ones who can do everything. Now I think it's the ones who know what they can't do."
He laughed. "That's literally the first thing they teach us. What is skiing? It's knowing which slope not to go down."
I'm not sure the analogy holds up perfectly, but I got the point. A vendor who admits their boundary makes me more confident handing them the work they do claim.
The Number That Changed How I Evaluate Vendors
By 2025, my evaluation process looks completely different.
Now the first thing I check is a vendor's capability map—not the marketing version that says "one-stop shop for everything," but the specific, verifiable version. The second thing I check is whether they're willing to write what they don't do into an RFP response. That single act tells me more than any case study.
I also cross-check claims against public data. The Baker Hughes rig count 2025 is a good starting point—it tells you how many rigs are actually running, which regions are growing, which are slowing down. If a vendor claims heavy activity in an area where the rig count has been flat for six months, that's worth a follow-up question.
According to Baker Hughes' published rig count data (as of January 2025), the U.S. land rig count sits around 580, with the Permian Basin accounting for nearly half. That number won't tell you who's the best vendor—but it helps you figure out who's telling the truth.
Why I Trust 'No' More Than 'Yes'
After that quarterly review, Eddie connected us with a specialty vendor who became our go-to for completion tools. Eddie's company remained our primary equipment supplier. But more importantly, the way I talked to him changed. I stopped asking "Can you do this?" and started asking "Is this your strength? If not, who should I call?"
He always gave me a straight answer. Sometimes it was "Yeah, we've got this." Sometimes it was "You're better off going elsewhere." That honesty did more for my trust than any brochure ever could.
Granted, not every procurement scenario works this way. If you're under a tight deadline, you might not have time to vet five vendors and map their competencies. But in oilfield services, a wrong completion tool can cost six figures. Spending a few extra days to find the right specialist is cheap by comparison.
The white contract taught me more than just "read the fine print." It taught me that vague boundaries are a risk to everyone. And a vendor willing to say "that's not our strength" is often the one you should trust with everything else.
In my experience, expertise has a boundary. And trust starts exactly there.