When Technology Fails Who Pays? Contractor or Client?

In this episode of Hard Hat Chat, Justin Smith, CEO of Contractor+, and Gerritt Bake, CEO of Build PRO, dig into the question every contractor dreads when a smart device starts blinking: when technology fails, who actually pays? Smart thermostats, app-controlled lighting, cloud-connected everything, when any of it glitches, the finger-pointing starts and the contractor is always the first phone call. This one matters because the trades are getting more digital every year, and nobody's drawn the line yet.Here's the trap. Homeowners don't separate physical installation from digital function. You wired it perfectly, followed every spec, and the moment a firmware update or a dead sensor acts up, the client says, "But it worked fine until you left." Everything works fine until it doesn't, that's how all technology behaves. Meanwhile the manufacturer blames the install, the app blames the network, and the cloud server blames "unexpected downtime." Six entities that don't talk to each other, and the contractor is left negotiating a peace treaty between all of them.Then there's the Wi-Fi, the silent villain in half these stories. The thermostat's offline, the doorbell lags, the smart fan won't respond, and the contractor gets blamed for a router older than the house. The guys also draw a sharp line between failure and malfunction. A failure is physical: a part broke, you can hold it. A malfunction is software acting weird, and there's nothing to point to. You can't hold a glitch in your hand, so the client stares at you like you're making excuses.The real cost is callback culture. Homeowners think callbacks are free; contractors know they burn fuel, labor, and time on problems that'll repeat with the next update. Worse, fixing every glitch for free teaches the client that free IT support is part of your job and good luck escaping that once it's set. Justin and Gerritt land on the fix: clear scope, plain-spoken disclaimers, and service agreements that say out loud, "We install the hardware, the manufacturer controls the software." Responsibility should follow causality, not default to whoever the client met in person.🔧 In this episode, you'll learn how to:Separate physical installation from digital function when talking to clientsRecognize the difference between a true failure and a software malfunctionProtect yourself with disclaimers that name what's outside your scopeStop absorbing the cost of cloud outages and connectivity issuesAvoid becoming unpaid IT support for systems you didn't buildCommunicate the boundary out loud instead of burying it in fine printBuild service agreements that make callbacks paid when it isn't workmanshipIf you've ever eaten the cost of a glitch that was never your fault just to dodge a bad review, this episode is the playbook you've been waiting for.