A Dealer Network Multiplies a Sale. It Can't Create One.

From 2022 to 2025 I was the connective tissue of the go-to-market for an IoT hardware system that was launched to market through a dealer channel. To be honest, I wasn’t the “channel manager” — but I worked the trade-show booths and generated hundreds of leads across ten-plus industry events. I wrote the training decks, the spec sheets, the technical requirements — and delivered them in person to rooms holding a dealer’s CEO, their sales lead, and their engineer at the same table. I traveled to activate 16 showrooms. I walked clients’ homes to spec where IoT hardware went and how other systems tied into the smart controller. I commissioned the software on-site and integrated it into Crestron and Lutron automation controllers. I joined sales calls as the dealer’s technical closer. And when something broke months later, I was the one who picked up. I also sat between our in-house software team and a third-party firmware shop, triaging every integration issue to the right place.

End to end, we put the system into 178 projects through 70-plus dealers. By any enablement standard, we did the job well — the white-glove service worked.

And it still wasn’t enough to make the product a market success. What I learned was this:

The job was never the dealers. It was the end-user pitch. We assumed that if we trained dealers well and armed them with collateral, they’d sell. But no collateral fixes a value proposition the buyer doesn’t feel. Our pitch — healthier air, cleaner water, better lighting, all automated through sensors and software — landed well with someone in Southern California who’d lived through a wildfire season, or anyone who’d personally been through a water scare. To a a typical end-user who’d never felt the problem, it was a feature nobody asked for. A dealer can’t transmit a conviction we hadn’t first proven ourselves. That’s the rule I’d put on a wall: whether you sell through a partner or direct, the person writing the check has to feel the value outweighs the cost. If you can’t make that case yourself, your dealers can’t either — and they have far less skin in it than you do.

White glove can’t scale. Standardization can. One dealer put our system into 115 of those 178 projects. The only reason that worked: every project was a near carbon copy — same network topology, same automation system, same install pattern. I trained that integrator once, had him build a demo in his own showroom, and he rolled the rest out with almost no hand-holding. White-glove service is only justified when margins are premium; it will never get you from 1 to 1,000. If you can’t systematize the path from 1 to 100, FTE cost eats every dollar of margin.

And some things were never in my control. We were building into projects during COVID, when our target market slowed and Crestron lead times stretched past 50 weeks. You can run a flawless enablement motion and still be throttled back by timing and supply chains — especially when your product is pegged to a third-party system whose availability and reliability you don’t control.

If you own the product, you own the knowledge — even on projects you don’t own.
One of our installations was for a client who owned a development of 39 homes, every one running our connected-hardware system that I’d helped put in. The dealer who’d sold and installed it had just walked off the project after a falling-out with the client.

The client called and said:

I’ve got 39 homes with your system, and no one left to service them.

He was right to be angry. Maintenance was contractually the dealer’s job, and the dealer was gone. But we owned the product. Those systems had to run for their full lifecycle — and the install history of all 39 had just walked out the door inside one person’s head.

I thought the 39-home handoff would be a maintenance packet and troubleshooting steps. It became a full reconstruction: transferring project knowledge a departed dealer had never sufficiently documented, interfacing directly with a client I’d never sold to, and standing up an entirely new service provider from scratch — pricing, procurement, training, the works — just to keep installed systems alive. Dealers don’t document for your benefit. If you’re the product owner, you need a system to preserve that knowledge before the first deployment, not after a partner walks.

So if I stood up a channel again tomorrow, three things come before I sign a single dealer:

1. Prove the end-user sale myself first. Know the buyer cold — what resonates, what doesn’t, and exactly why they write the check.
2. Own the knowledge from day one. Build the documentation and handoff system before the first deployment, because the partner who holds it today may be gone tomorrow.
3. Standardize the deployment so you can scale economically. Find the repeatable install pattern early and build for it — same topology, same configuration, same playbook — so a trained partner can replicate it without you in the room. White glove proves the model works; standardization is what lets it pay for itself.

I’m building a SaaS product solo now. And the discipline from all this is the part I kept: I won’t think about partners until I’ve proven, with my own hands, that the end customer will pay. The channel was never the hard part. Believing it could do a job that was always ours — that was the hard part.