When a Client Asked for Halogen Bulbs – And Why I Talked Them Out of It

It was a Tuesday morning in early 2024 when the email came in. A property manager I'd been working with for about a year wanted a quote for lighting a new office build-out. The spec sheet was straightforward: 200 track heads, GU10 base, halogen bulbs. Nothing fancy. But then I saw the delivery timeline – six weeks out – and the budget number. Something didn't sit right.

I'm a quality inspector at a lighting distribution company (we're a Philips partner, among others). My job is to review every fixture, driver, and control package before it reaches the customer. Roughly 300 unique items a year, on average. I've rejected about 18% of first deliveries in 2024 due to specs being off – wrong color temp, driver mislabeling, beam angle discrepancies. That experience has taught me one thing: stick to what you know, and know when to say no.

The Halogen Trap

The spec called for 50W halogen GU10 bulbs. At first glance, fine. But I knew this project was going to run 12+ hours a day – an office, not a boutique. Halogen would mean high heat, frequent replacements, and energy costs that'd blow the building's budget by year two. The client hadn't factored any of that in. They'd just copied what they'd used in their last space (which was a retail store with much shorter operating hours).

Everything I'd read about commercial lighting said LED is the obvious choice for long-duration spaces. But in practice, I've seen buyers resist because of upfront cost or because they 'always used halogen.' This was a classic case of conventional wisdom vs. real-world inertia. I had to make a decision: just quote what they asked for, or push back?

I called the property manager. 'You're going to hate this,' I said, 'but I think you should scrap the halogen spec and go with Philips MR16 LED instead. And while we're at it, add a Zigbee controller so you can dim and schedule each track independently.'

'We don't do that as a standard offering – here's a specialist who can design the control system for you.' That honesty cost me the controls part of the sale, but it earned me a partner relationship.

The Pushback

He wasn't convinced. 'LED is more expensive per unit, and I've had bad experiences with color consistency on dimming.' Fair concerns. I'd seen that too (circa 2020, some early MR16 LEDs flickered like crazy on standard triac dimmers). But Philips' MR16 line – specifically the 5.5W 36° 3000K version – had come a long way. I offered to send him a demo unit and a halogen equivalent for side-by-side comparison. (I even paid the shipping out of my own pocket – $18.50, which, honestly, felt worth it.)

Three days later he called back. 'Okay, you were right. The LED looks better, runs cooler, and I can't see any flicker even at 10%. But the controls part – can you do the whole Zigbee integration?'

Admitting Limits

Here's where the 'expertise boundary' kicked in. Our company is great at fixtures and drivers, but complex Zigbee control system design – especially integrating with building management systems and third-party locks (they mentioned wanting Zigbee locks for access control) – that's not our core strength. We could spec the Philips Hue-compatible drivers and the controller, but the full network design? We'd be stretched.

I told him straight up: 'This isn't our specialty. But I know a firm that lives and breathes Zigbee lighting controls – they've done similar projects for 50,000-square-foot spaces. The cost increase for bringing them in was about $3,200 on a $22,000 project, but their satisfaction scores ran 34% higher. And when they made a mistake on a different job, they fixed it without charge. That says something.'

He took the recommendation. That honesty – admitting we didn't own every piece of the puzzle – actually made him trust me more on the parts we did own.

The Retrofit in Action

Fast forward to installation day (June 2024). They went with 180 Philips MR16 LED units (the 5.5W, 3000K, 36° beam) and 20 track heads with the Zigbee-controllable driver modules. I inspected the batch myself – checked color temperature variance across 10 samples (average delta was within 50K, well under the 200K industry tolerance). The Zigbee pairing went smoothly, and the client was able to set schedules via the Philips Hue app and also connect to their existing Zigbee locks for occupancy-based lighting.

The result? They cut energy consumption by 78% compared to halogen (based on their first two months' utility data – verified by the building's sub-meter). And the property manager told me last week that the only maintenance so far has been one driver replacement (which we handled same-day).

What I Learned

This project reinforced something I'd suspected for years: the best vendors aren't the ones who say yes to everything. They're the ones who know their lane and stay in it. The firm that did the Zigbee controls sent me a thank-you note (not that they needed to) – they appreciated not having to compete with us for the whole scope.

I also learned that clients often default to what they know (halogen) because they're afraid of the unknown (LED drivers, Zigbee, commissioning fees). By giving them real comparisons – side by side, not just spec sheets – I could overcome that fear. And by being honest about what we didn't do well, I built credibility for everything else.

Bottom line: if you're specifying lighting for a commercial project, don't settle for 'what we've always used.' And if your supplier claims to be an expert in EVERYTHING from halogen to smart locks – that's a red flag. Specialists exist for a reason.

(As of January 2025, that property manager is now rolling out the same system across three more buildings. Total LED fixtures purchased: 540 units. Not bad for a Tuesday morning email.)