The Surface Problem: An $8,000 Gap Between Quotes
Six years ago, I took over purchasing for a mid-sized electrical distributor getting into smart lighting. The first big task: a 150-fixture office retrofit. I sent the spec to five vendors. The quotes came back with a spread of $8,000.
Same fixture count. Same control protocol on paper. My cost-controller instinct said take the lowest bid. That's what I was hired to do, right?
That instinct cost us $1,200 in rework on a single wall box, plus a bruised relationship with the electrical contractor. It also pushed me to track every lighting dollar we spent for the next six years. That spreadsheet—78 purchase orders, roughly $180,000 in cumulative spending—taught me more about the real cost of smart lighting than any vendor presentation ever did.
The Deep Cause: The Quote Is Not the Price
Here's the thing I eventually learned: the lowest quote is usually the most expensive one to accept. Not because the vendor is dishonest. Because nobody asked them to include the stuff that actually costs money.
When I compared those five bids line by line, the low bidder had simply left things out. No commissioning hours. No compliance documentation. No mention of who programs the controls or what happens when a sensor doesn't respond to the switch. That's not a bad vendor—that's a vendor who quoted exactly what the spec asked for. The spec said "Zigbee-compatible switch, LED driver, motion sensor." It didn't say "engineered as a system with documented compliance and a single point of accountability."
I've watched this pattern repeat across 20+ projects, from bulk recessed lighting orders to small sensor rollouts. The gap is never in the hardware price. It's in integration, documentation, and accountability—three things you can't see on a spec sheet but you'll definitely pay for eventually.
The OEM vs. Private Label Gap
One of the biggest budget killers in this space is the assumption that "OEM" and "private label" mean the same thing. They don't. And the difference shows up in nasty ways.
An OEM light switch is built to the original manufacturer's specification. You're paying for the engineering behind it, the compliance testing, the field performance data. A private label product takes an existing design and puts a different brand on it. That can be a perfectly reasonable deal if the underlying product is solid and the documentation carries over. But it's a different product, with different support and traceability.
I've seen distributors quote a private label switch on a project that spec'd OEM because the parts "look identical." Then the compliance audit happens, the paperwork doesn't line up, and the whole fixture schedule gets delayed. That's not a product failure—it's a specification failure. And it gets billed to someone.
My rule now: before approving any substitute, I ask for the documentation. If the supply chain can't show compliance paperwork within 24 hours, the substitution gets rejected. That one rule has prevented more expensive surprises than anything else I've done.
The "Everything's Compatible" Trap
Here's the other silent cost driver: assuming that Zigbee is Zigbee, and anything with the same logo will work together. I'm not 100% sure how this myth got started, but it's sort of true... until it isn't.
Early on, we used a sourcing strategy that looked smart on paper: buy recessed fixtures in bulk from one supplier, order motion sensors from a specialized motion sensor distributor, and get switches from a vendor offering a better unit price. Three vendors. Three invoices. Three support channels. Each product worked fine in isolation.
We saved about 11% on hardware. Then we spent those savings and then some on commissioning hours getting everything to behave as one system. The sensor manufacturer blamed the switch firmware. The switch manufacturer said the sensor was out of spec. The fixture supplier stopped picking up the phone once the lights were delivered.
That's how I learned about the cost of accountability. When no single party owns the outcome, the outcome becomes your problem.
The Price of Not Fixing This
Let me give you the actual numbers from my spreadsheet, because the data tells the story better than my opinions.
Between 2019 and 2024, I logged 78 purchase orders for smart lighting components. They fell into two camps:
Camp 1: One accountable system supplier. Higher unit prices on average, but the quote included programming, documentation, and a person who actually answered when a sensor wouldn't pair. These projects came in at or under budget 9 times out of 10.
Camp 2: Best-price component sourcing. Independent vendors for each piece. This is where my early mistakes lived. These projects exceeded their initial budget by an average of 14%—and the overrun almost always appeared after installation. Engineering hours. Troubleshooting. Compliance follow-ups. None of it showed up in the original PO.
Do the math: 14% overrun on a project where you thought you saved 11% on hardware. The "cheap" approach cost you 25% more in total. I didn't see it until my spreadsheet turned impressions into numbers.
I still kick myself for not building that spreadsheet earlier. If I had, we would have skipped our two most painful projects—one with a $2,800 engineering overrun, another with a full day of onsite troubleshooting that was never billed but definitely cost us a client's trust.
Risk Weighing: When I Almost Repeated the Mistake
A couple years in, I was comparing quotes for a 40-switch order. The cheap route saved $2,400. The risk: repeating the integration mess. I kept asking myself—is $2,400 worth potentially eating $3,000 in engineering hours if the system doesn't cooperate?
The expected value said go for it. The worst case wasn't catastrophic. But the thought of making the same mistake twice... I couldn't justify it. We took the higher quote. The project came in clean. Zero integration issues.
I'm not sure that proves anything. But it reinforced a bias I've come to trust: prevention is almost always cheaper than correction.
What Actually Fixed It
Look, I'm not going to tell you that every project needs one vendor for everything. That's not realistic, and honestly, it can hurt your pricing leverage. But after six years and 78 POs, here's what I'd tell my year-one self:
- Name the system owner at the quote stage. If a project involves controls plus fixtures, someone has to own the integration. Put it in the scope. If nobody owns it, you own it by default.
- Ask every vendor what's not included. That answer is worth more than the quote itself. Commissioning, documentation, after-sales support—the good vendors list these explicitly. The rest leave them out for a reason.
- Verify documentation before you order, not after. Whether it's OEM or private label, fixtures or sensors, get the compliance paperwork checked upfront. Energy codes like ASHRAE 90.1 and California Title 24 keep tightening requirements, and the DLC qualified products list is a solid reference point for commercial lighting. As of January 2025, several states have started requiring even stricter documentation for lighting retrofits. A 24-hour check at the front costs nothing compared to a compliance delay at the back.
- Track closeout cost, not just PO cost. My simple spreadsheet—vendor, date, category, final cost including change orders—became the most useful procurement tool I own. It turned my gut feelings into actual data.
When we finally standardized on an integrated platform, a Savant smart lighting system kept winning the cost comparison. Not because the hardware was the cheapest—it wasn't. Because the quote included commissioning, documentation, and support. The spreadsheets made that obvious in a way vendor pitches never did. If you're sourcing a savant lighting system or any integrated alternative, ask the same questions I listed above. The answer decides whether your project comes in under budget or becomes another cautionary tale.
Here's the bottom line: the 12-point checklist I created after my third mistake has saved me an estimated $8,000 in potential rework since 2022. All it costs is 20 minutes of verification before signing the PO.
There's something satisfying about a project that gets through closeout without a single surprise invoice. It doesn't happen by accident. It happens because the spec was right, the documentation was checked, and someone was accountable for the outcome.
In my experience, that's worth more than any 11% hardware discount.
