I Buy Lighting for a Living. I Don't Pretend to Know Everything About It.

If a lighting supplier promises “everything,” I start subtracting. The vendor who says “this isn't our strength—here's who does it better” earned my trust for everything else. The vendor who says “yes” to every request gets a second look. Maybe a third. Then I usually walk.

I'm a procurement manager at a 130-person facilities management company. I've controlled an equipment budget of roughly $180,000 a year for six years, and lighting is a big part of that spend. I've negotiated with dozens of vendors—maybe fifty, I'd have to count—and documented every order in our cost tracking system. I'm not an electrical engineer. I'm not a smart-home integrator. I don't know how to make an LED driver dimmable after it's been installed. And I've never pretended otherwise.

Why I stopped asking vendors to be experts in everything

When I audited our 2023 spending, I found that most of our budget overruns didn't come from high unit prices. They came from “covered” services that weren't covered. That “free setup” offer actually cost us $450 more in hidden fees. The “we can handle that too” contractor charged us for a sub that should have been included. The pattern was always the same: a vendor who claims broad capability is less likely to document what's outside their capability.

Why does this matter? Because in procurement, the cost isn't just the line item. It's the change order after the fact. It's the coordination you didn't plan for. A specialist who knows their limits reduces that risk.

I have mixed feelings about one-stop shops. On one hand, consolidation is convenient. On the other, I've seen “one source for everything” become “one source for finger-pointing” when something breaks. I'd rather have three vendors that each know their lane than one vendor that claims to know all three.

What I actually look for in Philips lighting products

This is why I keep coming back to Philips for many lighting orders. Not because they're the only brand, but because their product specs are consistently published. The Philips Hue color bulb, for example, is one of the few products I'll specify without a lengthy evaluation. The product page says it uses Zigbee, the wattage is clear, and the compatibility list is documented. I can verify what I need to verify without asking the vendor to be a lighting magician.

One caveat: Philips makes more than lighting. I once had a client ask if a Philips LED TV could be used as a digital menu board. That's not my territory, and it's not lighting. The brand's TV line may be fine—I have no reason to doubt it—but I don't want to be the guy who spec'd a TV for a commercial application without an AV specialist looking at burn-in and control. That's the same discipline: know what you're buying, and don't use a brand's reputation in one category as a blanket approval for another.

The Zigbee question is not a lighting question

Here's a question I get often: “Can I use a Zigbee plug with the Philips Hue bridge?” My honest answer: it depends on the plug, and I'd have to check the compatibility list. That sounds less confident than “yes, of course.” But it's more reliable.

A Zigbee plug can be a cheap way to make a dumb lamp switchable in a Zigbee IoT setup. But “works over Zigbee” doesn't automatically mean “works with Philips Hue.” The protocol is not the same as the ecosystem. The Philips Hue color bulb uses Zigbee, but the Hue bridge uses a specific implementation of it. Just because a device is Zigbee-certified doesn't mean it will pair without a firmware issue. I've learned this the hard way by making assumptions based on protocol names instead of spec sheets.

Honestly, I'm not sure why some vendors refuse to admit this. My best guess is that “Zigbee” sounds technical enough to impress a customer. But real expertise means knowing the difference between a standard and a product's behavior. I can tell you what a Zigbee plug should do in theory. I'll still check the official compatibility list before promising anything.

Dimmable drivers: the easiest way to sound dumb

The phrase that makes me cringe is “how to make LED driver dimmable” typed into a search bar six months after the install. Usually this comes from someone who already installed non-dimmable drivers and now wants “on/off” to mean more. My answer: don't retrofit unless the fixture and driver are designed for it. That's not a procurement decision; that's electrical engineering territory.

I can tell you what I do from a buying perspective. I look for drivers that are listed as dimmable in the spec sheet—0-10V or DALI, depending on the system. I ask the manufacturer or rep to confirm compatibility with the control system. But I can't tell you which wire to move or whether the heat dissipation is adequate. This gets into electrical code territory, which isn't my expertise. I'd recommend consulting a licensed electrician before you do anything.

Is that a cop-out? Maybe to someone who wants a single answer. But part of being a credible buyer is knowing when to say “I don't do that.” The moment you pretend to know everything, you own the risk. I'd rather own a relationship than a mistake.

So why buy Philips at all?

Some might say I'm contradicting myself. If expertise boundaries are so important, why buy from a brand with a broad portfolio?

Fair question. I don't buy “Philips” as a category. I buy specific Philips SKUs that have clear scopes and documented specs. The brand doesn't need to be a generalist for me—it just needs to publish enough information to make my evaluation safe. The Philips Hue color bulb has a spec sheet. The Zigbee details are public. That's what I care about.

I also appreciate that Philips reps have, at least in my experience, been willing to say “that product isn't the best fit” rather than pushing a mismatch. That's rare. When a vendor tells you what they don't do, it makes you trust what they do. It's the same reason I keep a list of electrical contractors who don't pretend to handle HVAC control logic. They shine in their lane.

Don't mistake brand size for vendor scope

The last thing I'd say—and this is the argument I keep repeating to my own team—is to check the vendor's boundaries before you check their price. A supplier who says “we're not the right partner for that part of the job” is not failing you. They're saving you from a bad assumption.

I've made the mistake of picking the “convenient” option because it meant one invoice and one point of contact. Then the project stalled, and no one wanted to own the defect. The rework cost more than any savings. Now my procurement policy requires a written scope of work that explicitly says what isn't included. Every time. It doesn't matter if it's a $4,200 annual contract or a $180,000 quarterly program—if the vendor can't define their limit, I can't trust their quote.

So here's my advice, unsolicited: in your next lighting conversation, ask what the vendor doesn't do. If they can't name something, they haven't thought about it. If they say “we don't do that, but this person does”—well, that's the person I want to buy from. The brand's reputation isn't a blank check. The spec sheet is the real source of truth.

That's my view. Simple.