The Challenge

Camman Lighting was relying on an order configuration system that had become difficult to maintain and scale. Every fixture in the catalog, well over a hundred of them, had its own standalone form, even though most fixtures shared the same underlying options: the same wiring, the same color schemes, the same lamping choices. The only real difference between most of them was the physical design.

That sprawl wasn’t a customer-facing problem; clients never touched these forms directly. Maintaining the system fell largely on Brian, an engineer at the time who managed the website alongside his other responsibilities. Any change to pricing, finishes, or product options had to be replicated across however many forms it affected, making updates time-consuming and increasingly difficult to manage.

Earning Trust

The relationship started with a problem Camman couldn’t easily solve on its own. A software update had broken PDF generation across the site, preventing agents from generating the specification documents they relied on every day. Darin’s first step was determining why the system had failed.

Diagnosing the issue meant tracing the problem back to changes in the underlying software and identifying where the existing templates had fallen out of sync. Once identified, the fix itself was contained: the lighting fixture forms were all different, but the PDF output ran through a single, standardized template, so the correction only needed to be made once.

That quick, clean resolution mattered beyond the immediate fix. By restoring a critical workflow quickly, without requiring a costly rebuild, Darin established the kind of trust that turns a one-off repair into an ongoing relationship, one that continues more than seven years later.

With PDF generation restored, the focus shifted from fixing the immediate problem to finding a better long-term approach. Instead of treating the broken PDF as an isolated issue, Darin took a closer look at the broader system and found that the real challenge wasn’t document generation at all. It was the growing complexity required to maintain more than a hundred separate forms that were largely doing the same job.

The Real Problem

Fixing the PDF issue surfaced the larger problem underneath: 131 separate forms, each handling a fixture that mostly duplicated the options of dozens of others. Consolidating them into a single, scalable system had been considered before, but earlier attempts had hit a wall: at the time, Gravity Forms and its available add-ons weren’t capable of the dynamic, conditional logic a unified form would need.

That changed once Darin implemented the right software tools. Rather than continuing to patch a growing collection of individual forms, Darin recognized an opportunity to rethink the system entirely. The goal was no longer to maintain 131 separate forms more efficiently. It was to eliminate the need for them altogether.

The Solution

The rebuild centered on a single Gravity Forms-based configurator. Product information, pricing, finishes, sizing options, and configuration rules were centralized in a database, allowing one form to dynamically adapt based on the fixture an agent selects, including which options are even available given earlier choices. Instead of maintaining over a hundred duplicate forms, Camman could manage its entire catalog through one scalable system.

Rather than stopping with the configurator itself, Darin looked at the surrounding workflow and identified two additional sources of unnecessary maintenance, each requiring a custom tool.

One recurring bottleneck involved maintaining product data. Every time pricing or catalog information changed, Camman had to rely on a manual conversion process before updates could reach the configurator. Rather than accepting that ongoing dependency, Darin built a tool that lets Brian, now Camman’s Product Manager, upload the spreadsheet directly, identify changes automatically, and apply updates without developer intervention, with a backup taken automatically before anything was overwritten.

A second bottleneck involved specification documents. Instead of manually placing dozens of fields across more than a hundred PDF templates, a field-mapping tool reads an uploaded PDF, fills in the right values automatically, and lets Camman adjust the layout before saving.

The Results

The impact shows up in a few concrete ways.

Faster Updates

Product launches, pricing changes, and new fixture options can now be pushed into the system directly by Camman instead of requiring developer intervention for every change. A spreadsheet update that once took roughly two and a half hours to convert and apply can now be done by Camman in minutes.

Less Maintenance

With the configuration logic centralized in the system itself, there is far less routine maintenance required as WordPress and plugins evolve over time.

More Control

Routine updates that once required submitting a request, waiting for implementation, and paying for development time can now be completed internally in minutes.

Stronger Long-Term Partnership

Rather than reducing the need for outside help altogether, that shift freed up the relationship for larger improvements and automation projects Camman hadn’t previously considered.

“Darin dug into the existing code, learned how it worked and what the issues were, and explained to me in layman’s terms what was happening, why, and how he’d fix it. And he didn’t just fix it. He made it better.

Darin has a remarkable ability to listen and understand my requirements. He takes the time to explain the technical aspects and steps he’ll take to accomplish his work. He consistently delivers on his promises, and his work often exceeds my expectations.”

— Brian Mears, Product Manager, Camman Lighting

A Partnership That Continued to Grow

Over seven years, the relationship evolved from troubleshooting a broken PDF system to solving larger operational challenges, with Camman increasingly turning to Darin not simply to implement requested features, but to help identify better ways of working. Each improvement created opportunities for the next one, transforming the relationship from troubleshooting into ongoing problem solving, with Camman returning again and again to ask, “Can you make it do this too?”

Beyond Lighting Fixtures

None of this is specific to lighting fixtures, or even to Gravity Forms. The same pattern applies to any business running on a complex product catalog, configurable orders, or guided selection processes that have outgrown the tools managing them: manufacturers and distributors with large product lines, legal firms generating document packages from client intake forms, title companies producing complicated paperwork from structured data, and any operation where “the form” has quietly become the bottleneck.

In each case, the underlying need is the same: a system that doesn’t just collect information, but uses it, pulling the right options, applying the right logic, and generating the right output, without a developer in the loop for every change. When that system is built right, it doesn’t just fix what’s broken. It hands the business the tools to manage its own growth.