-
I'll Just Say It: "We Do Everything" Is a Red Flag
-
The Year the "Full Package" Fell Apart
-
When the Line Goes Down, I Need Depth, Not Breadth
-
"We Don't Do That" Was the Most Confident Sentence I've Ever Heard From a Vendor
-
But What About Administrative Convenience?
-
Final Word: Boundaries Are a Sign of Competence
I'll Just Say It: "We Do Everything" Is a Red Flag
I manage procurement for an industrial automation company—roughly $400,000 in annual spend across a dozen or so vendors. PLCs, sensors, panel components, cabling, the whole ecosystem. Processing 60-80 orders a year means I hear a lot of vendor pitches. And if there's one phrase that makes me instinctively start evaluating backup options, it's "we can handle everything for you."
That's not how I started out. When I took over purchasing in 2020, I actually believed the ideal vendor was one that could cover all our needs in a single phone call. It sounded efficient. It sounded like what a good procurement manager should want. It took a near-disaster on a major project to flip my thinking completely.
Here's my position now, and I won't soften it: a supplier who claims to handle everything is riskier than one who openly admits their limits.
The vendors who point at a job and say "that's not our strength—but here's who does it better," have turned out to be my most reliable partners. This is the hill I'll die on.
The Year the "Full Package" Fell Apart
In 2022, we went through a major control system supply review. One vendor came in with a slide deck that had our CFO practically glowing: "Full automation package." Controllers, HMIs, networking, installation, programming, lifetime support. All in-house, they claimed. No third parties, no coordination headaches, no finger-pointing.
It was exactly the kind of consolidation story that finance teams love.
Two months into the engagement, we discovered the "in-house" controllers were rebranded hardware manufactured by someone else entirely. The "in-house programming team" was a subcontractor in a different time zone who had never touched our legacy systems. Integration meetings became a conference-call circus between three companies—none of whom felt responsible when things stopped working. The project ran six weeks late. I spent a very uncomfortable meeting with our VP—or rather, I was summoned into a meeting where the VP asked pointed questions I couldn't answer well.
Per FTC advertising guidelines, claims like "full-service" or "complete package" are supposed to be truthful and substantiated (the full business guidance is at ftc.gov/business-guidance). But legal standards are a floor, not a practical safeguard. In the real world, nobody files a complaint over a slick customer deck. The only defense is asking sharp questions before signing: whose hardware actually ships? Which engineers do the work? What certifications do they hold? Who answers when a module fails at 2 a.m.?
Here's what I found: specialists answer those questions quickly. Generalists get uncomfortable.
When the Line Goes Down, I Need Depth, Not Breadth
There's a procurement principle that I think gets lost in the pursuit of supplier consolidation: downtime has a price tag, and vendor response time is part of the cost.
Our plant floor runs a mix of Omron PLC controllers—CP2E units on primary lines, CP1L for smaller stations, NX and NJ series for motion-heavy processes. When a module fails, I need someone who can identify the fault and ship a replacement same-day. The specialist distributors we work with can, because they've seen these exact failure modes dozens of times. They know a failing output on a CP2E looks different from a faulty communication module. They keep spare PLC modules in stock. They don't need to "open a ticket with the OEM" and call me back in three business days.
I don't have hard data on average resolution times across supplier types—wish I'd tracked that metric from day one. But anecdotally, across hundreds of orders and support calls, my sense is that specialists resolve issues in about a third of the time that generalists do. When a production line is idle, that difference is measured in dollars, not just minutes.
This is also why our engineering team defaults to specifying Omron PLC modules in new designs. It's not brand loyalty. It's knowing that the modules they spec—whether NX, CJ, CP1L, or CP2E—sit inside a coherent ecosystem, supported by people who know that ecosystem deeply. When an engineer has a question about a PLC module, they get an answer that comes from experience, not from a product catalog.
The "everything vendor" has a bigger catalog. But when you need a specific PLC module to keep a line running, deep and narrow beats shallow and broad. Every time.
"We Don't Do That" Was the Most Confident Sentence I've Ever Heard From a Vendor
I keep a mental file of significant vendor moments. The top entry is from a supplier who straight-up told me what they couldn't do.
A few years back, we were evaluating safety PLC options for a SIL-rated application—one of those projects where functional safety expertise is absolutely non-negotiable. A vendor on our shortlist made industrial controllers. Good products. Competitive pricing. Solid reputation. Midway through the technical deep-dive, their lead engineer said something that brought the meeting to a standstill:
"Functional safety isn't our core expertise. If you need a safety-certified PLC for this application, you should work with a specialist. We can integrate with their hardware afterward, but we shouldn't be your primary supplier for this piece."
I remember sitting there, waiting for the catch. There wasn't one. He named a competitor who was genuinely better at safety PLCs, and he made that recommendation unprompted.
That vendor won the bulk of our non-safety PLC business that year. They still hold it today. Their five-minute admission of limitation made every other claim they made more credible. It was a masterclass in confidence through vulnerability. I've since learned to interpret "we'll handle that too" as a yellow flag, and "we don't do that, but here's who does" as a green one.
(Should mention: this is why we've built our safety PLC supply around dedicated functional-safety specialists. The overall system is a portfolio of experts, not a single "everything" vendor. And yes, it takes more work to coordinate. It also keeps production lines running.)
But What About Administrative Convenience?
I hear that argument a lot, and our CFO genuinely believes it. Fewer vendors means fewer purchase orders, fewer invoices, fewer quarterly reviews. It's administratively tidier. I'm not going to pretend there's zero value in that.
But I've also lived through the single-point-of-failure version. When one of our multi-line vendors restructured internally, suddenly our "single point of contact" was a phone number in a dead department. Nothing got answered. Support tickets vanished into a voicemail labyrinth. We didn't recover for months.
The one-stop-shop model made sense in an era when automation systems were simpler and one supplier could plausibly know every component. That era ended years ago. Today's control systems span safety, motion, networking, process control, and more—each requiring its own depth of expertise. No single supplier can genuinely be world-class at all of them. The ones who claim otherwise are either overconfident or hoping you don't ask enough questions.
And my internal customers? The maintenance team doesn't thank me for reducing vendor counts. They thank me when a replacement CP2E module ships out the same day. The engineers don't celebrate consolidated invoicing. They celebrate when someone answers their PLC programming question with actual knowledge. Nobody in our plant has ever told me "I appreciate that we cut our vendor list." But I've had many handshakes over "that supplier solved our problem in a day."
Final Word: Boundaries Are a Sign of Competence
If you're new to buying industrial automation equipment, or if you're in a role where you're evaluating suppliers for any specialized product, take this from someone who's been burned enough times to have strong opinions: ask every vendor about their limitations, and be cautious of the ones who don't seem to have any.
Ask: What are you the best in the world at? What do you refer out? What's the last project you declined?
The vendors who can answer those questions specifically and without hesitation are the ones who know their craft. The ones who say "we do everything" are, in my experience, usually hoping you won't inspect the seams.
Give me a specialist with clearly defined boundaries over a generalist with endless promises. That's been my procurement philosophy for the last three years, and it hasn't let me down yet.