It was a Tuesday morning in early 2018. I was six months into my role, fresh out of training, and I had my first real shot at a retrofit specification. A small auto repair shop, maybe 2,000 square feet, wanted to upgrade their old fluorescent shop lights to LED. Simple job. Standard equipment. But I managed to turn it into a $3,200 learning experience.
The client had a budget of about $1,500 for materials. They needed new LED fixtures, maybe a couple of emergency lighting units, and some basic controls. I was determined to impress them—and my boss—with a 'proper' ABB solution. I pulled out all the stops: I specified our top-tier ABB emergency lighting with full IoT connectivity, a complex zoned control system, and even threw in a few lighting contactors 'just because.' I thought I was building something future-proof.
The order came back at roughly $4,700 for materials. The shop owner nearly choked on his coffee. I spent 45 minutes on the phone explaining the 'long-term value' and 'platform integration.' Honestly, I was trying to justify my own over-engineering. The client wasn't buying it. They wanted lights that worked, a backup for an outage, and nothing that required a degree to operate.
Two weeks later, we lost the job. The owner went with a competitor who spec'd a basic LED bulb replacement kit and a couple of standalone emergency units. Total material cost? Under $900. He was happy. We looked like the vendor who couldn't listen.
I had to write a report on the lost opportunity for my manager. That's when the penny dropped: I had a beautiful plan, but it was completely disconnected from the real need. The client wasn't running a factory with a complex shift schedule. He just wanted his mechanics to be able to see what they were doing and not trip over extension cords if the power went out.
The lesson stuck. I remember the e-mail I sent to myself that afternoon: 'Not every job needs the whole ABB Ability platform. Sometimes they just need a light switch.' It sounds obvious. But when you're new, you think adding more features is better. It's not. It's just more expensive.
The Real Cost of Showing Off
That failed proposal cost us more than just the lost sale. It damaged the client's trust. We'd spent weeks building a relationship, and then I blew it by trying to upsell a system that was way too complex for their needs. They called us 'the expensive company' for months after that.
I learned to ask a very simple question on every small project: 'What is the absolute minimum this setup needs to do?' For a small shop, the answer is usually: provide general light, meet code for egress, and be easy to maintain. That's it.
This is where I feel strongly about something. Small clients, the ones with $1,000 budgets, they deserve a solution that fits their problem, not a showcase of what a vendor can theoretically do. They are not 'lesser' clients because their order is small. In fact, the small jobs often teach me more about efficient design than the big ones. Today's $1,500 client could be next year's $15,000 client—if you treat them right. I've seen it happen: a vendor friend of mine took a small bakery order seriously, and three years later, that baker opened two more locations and gave him the whole lighting contract.
If you are doing a small ABB equipment retrofit package for a local business, here is a checklist I now use for every proposal under $3,000: First, confirm the core need. Is it just replacing old lights, or is there a specific problem like glare or shadowing? Second, resist the urge to add smart features. Just because you can doesn't mean you should. Third, always give a bare-bones option. The client might not even ask for the premium quote. I now always include a 'budget-friendly' line item using standard components like a basic UA spotlight for task areas, rather than a complex system.
One more thing—and I learned this after another small mistake about a year later. If the client asks about a stop light switch or any single component, treat that question with respect. Don't immediately assume they need a whole new control module. Sometimes, they just need to replace a broken part. I once spent an hour designing a completely new control loop for a single-bay garage, only to have the client say, 'No, the switch is just stuck. I need a new one.' Cost me half a day of billable time.
That's the thing. The small jobs expose your weaknesses fastest because you can't hide behind a big budget. You have to listen carefully and design tightly. It forces you to be a better engineer.
The Fix: A Simpler Path to Retrofits
These days, I approach abb lighting retrofits differently. Instead of asking what technology I can use, I ask what problem I have to solve. For the small jobs, the solution is almost always simpler than I think.
Take our standard package for a mechanic's shop: we provide a set of high-bay LEDs (basic, no dimming unless requested), a few emergency exit signs, and a simple contactor to create a local override for the lighting panel. That's it. The ABB components are still there—they are reliable and code-compliant—but we don't over-scale them.
I've personally documented seven major mistakes in my career so far. This first one, the auto shop, is still the most humbling. It taught me that the best design is not the one with the most features. It's the one that fits the use case. And it taught me to respect the small client's intelligence. They know when you're trying to sell them something they don't need.
If you are new to specifying industrial lighting, take it from someone who has the scars: start with the problem, not the product catalog. Your client—and your project margin—will thank you.