A Derrick Supplier Who Says No Gets My Purchase Order

I’ll start with my conclusion: I don’t want a derrick supplier who says yes to everything. After years of purchase orders for drilling equipment, I’ve learned that a confident yes is often just a deferred problem. The supplier who tells me where a package does not fit is the supplier I trust.
I’m not an engineer. I’m the office administrator for an 80-person drilling services company in West Texas. I manage about 50 to 80 POs per year—roughly $1M in direct spend—across 8 or 9 vendors. I report to operations and finance, so I need every decision to hold up on paper, not just on a sales call.
When I took over purchasing in 2020, I made the classic new-buyer mistake: I treated a derrick as a one-line item. We received a quote for a replacement derrick that was about $37,000 lower than the incumbent. I was already imagining what the savings could do for our maintenance budget. Then the details came out. Actually, they didn’t come out until after we asked questions.
The low quote didn’t include the documentation package or the structural review we needed. It did include a line that said “certified,” but it didn’t specify which certification or what it covered. We paid about $6,400 later to correct that gap. If I remember correctly, the final difference between the two vendors was less than $3,000. The lesson wasn’t that the low-priced vendor was dishonest. The lesson was that I hadn’t defined the full scope of what I was buying.
A cheap derrick quote is not always a complete derrick quote
The first check I now make is not price. It’s completeness. A derrick is not just a mast with a load rating. It is a structure that has to survive your site, your loads, your inspection process, and your operational timeline. Most buyers focus on rated hook load and price, and completely miss the other conditions that determine whether that structure will work.
Here is the list I now include in every derrick RFQ:
- Rated static hook load and the operating conditions behind that rating.
- The design standard we expect, typically API 4F for drilling and well-servicing structures.
- Wind load and seismic assumptions.
- Which documents are included—not just the word “certified.”
- Transport, erection, and fit-up with the existing substructure.
What most people don’t realize is that a quote can be technically accurate and still incomplete. A vendor might give you a mast that meets the load number but doesn’t include the engineering backup that your insurance company, regulator, or internal safety team will ask for later. At that point, the cheap quote is no longer cheap. It’s just a change order waiting to happen.
Why I stopped making assumptions
In 2021, a salesperson told me, “We’ve been building these for twenty years. Don’t worry about the paperwork.” I knew I should send detailed drawings before approving the quote, but we were rushing. I skipped that step because it felt like extra friction. That was the one time it mattered.
The first shop drawing came back with the wrong base footprint. It wasn’t malicious. The vendor simply worked from a standard template instead of our actual site drawings. We lost two weeks and paid for a new review. The supplier was embarrassed, I was embarrassed, and my operations manager was not gentle about it.
Honestly, I’ve never fully understood why some good suppliers avoid putting “not recommended” in writing. My best guess is that they worry about losing an order. If someone has better insight, I would love to hear it. But I now treat a vendor who can name a limitation as more credible than one who says “we can make it fit” without asking a single question about the site.
The over-spec trap is real
Here is the less obvious side of the same argument: I can also overspec a derrick. Extra capacity feels responsible. It feels like future-proofing. In 2023, I nearly recommended a heavier derrick than we needed because it seemed safer. The problem was that it didn’t fit our existing substructure without a costly extension. It also required a heavier transport plan and longer inspection intervals.
I don’t have hard data on industry-wide over-spec patterns, but based on our own internal reviews, the bigger structure would have added roughly $18,000 to the project before installation. The contractor who pointed this out didn’t get the larger order. Actually, he got the better relationship. He told me where that package would be wrong for our site. That is the kind of honesty I’m willing to pay for.
What I do when a supplier says yes too easily
If a supplier says yes to every question without asking for drawings, site conditions, or a purchase order, I slow down. A good sales engineer should be able to answer this question: “Is there any case where you would not recommend this model?”
If the answer is a fast no, I lose confidence. Not because the equipment is bad, but because the salesperson is not thinking critically about the application. The most useful calls I’ve had were the ones where the supplier said things like, “That pad can’t take the wind load in that configuration,” or “If you need that much clearance, you’d be better off with a different package.”
That sounds counterintuitive. We hire suppliers to say yes. But in a derrick purchase, yes is only useful when it is based on actual site conditions. A yes that comes before the questions is just a marketing statement.
Price still matters
None of this means price doesn’t matter. I’m the person who has to explain budget overruns. Price matters a lot. But the lowest first quote only wins if it covers the complete scope.
In Q4 2024, we requested quotes for a derrick-related package and received five proposals. The range was roughly $228,000 to $318,000. The lowest quote did not include documentation or third-party inspection that the other proposals included. After the vendor added those items, the spread narrowed to about $30,000. We chose a vendor in the middle because their scope was clearly defined and their sales engineer asked questions before quoting. Pricing referenced here is from our own RFQ and may not reflect current market rates.
My bottom line
I don’t have hard data on how many derrick purchases go wrong industry-wide, and I don’t think any office administrator sees the whole market. What I can say anecdotally is this: every difficult project I remember followed the same pattern—vague yes, assumptions, late clarification, and then surprise costs.
I’d rather have a supplier tell me no before the purchase order than discover at the site that the derrick doesn’t fit the substructure or the certification doesn’t meet the requirement. That is not a weakness. It is the strongest signal of competence I get in procurement.
So if you’re a derrick supplier, don’t sell me a generic yes. Ask me what site condition, what load case, and what documentation I need. Tell me where your package would be a problem. That is the vendor who earns the purchase order.
Note: This article is based on my own procurement experience, not engineering advice. Product specifications, API standards, and prices should be verified against current documentation before any purchase decision.