From thermostat to connected system: how to explain it to your client

Installers know how to explain to a colleague what changes when you go from a thermostat to a connected system: a controller, a sensor per zone, weather compensation, data logging. To the client, though, those words mean little. They want to know three things: will they be more comfortable, how much will they spend, and will life get more complicated.

This article is for installers proposing a connected heating system to homeowners and small businesses. It gathers the questions we hear most often and the way we think it is right to answer them.

Clients don’t buy a protocol

The first rule is to talk about results, not technology. Modbus, Zigbee, Home Assistant are words that reassure technicians and scare clients. It works better to start from a problem the client recognises:

• the children’s room that is cold in the morning;
• the study that becomes an oven in summer;
• the bill that is high for no obvious reason;
• the holiday home that is freezing when you arrive in winter.

Then explain what changes for that problem. “Every room will have its own temperature, and you’ll see it on your phone” is a sentence clients remember. “We’ll install Zigbee sensors with Node-RED logic” is not.

The four questions they always ask

In our experience the questions come back almost word for word. It pays to have a short, true answer ready for each.

How much does it cost? It comes first, and the honest answer is a range, not a number. It depends on how many zones are needed, what is already there and how much of the plant room goes under the new controller. It helps a lot to show what stays untouched: boiler, pipes, floors. And it helps to talk about cost over time, not just the purchase, as we did in the article on the ten-year cost of a control system: no subscription means the price paid today is the final price.

Is it complicated to use? The answer is in the app: the rooms, the temperatures, a button for Comfort and one for Eco. Those who want to do more can; those who don’t, needn’t. And existing thermostats, if they work, can stay, as in configuration A0.

What happens if the internet goes down? This is the question that says most about a system. With a local system the answer is: nothing, the house stays in control, you only lose access from outside. It is worth saying clearly, because many clients have had different experiences with cloud devices. Remote access, if needed, goes through a private network, as explained in the article on remote control without the cloud.

Where does my data go? More and more clients ask. A local system’s answer is simple: it stays at home, on the controller in the panel, and nobody sees it without the owner’s permission. For those who want to know more, there is the article on where thermostat data ends up.

What to show

Images convince better than words. Three things to show during the site visit or in the quote:

1. The app on a phone, using a demo system or screens from an existing installation, with its owner’s permission. The client sees straight away what they will have in their hand.
2. A temperature chart from a similar home, with the rooms rising and falling differently. It shows in an instant why one thermostat is not enough.
3. A simple diagram of the system before and after, even hand-drawn: the rooms, the manifold, the panel. The client understands where the work will happen and for how long.

What to promise, and what not to

Trust is lost with one wrong promise. Some things can be promised safely: every room at its own temperature, schedules from the app, a house that stays in control without the internet, no subscription.

Others cannot. Savings above all should not be promised as a precise figure. You can say that research points to 10–20% on average compared with a single thermostat, that it depends a lot on the home, and that you will measure it together with the system’s data. It is more honest, and in the long run more convincing. As we wrote in the article on going from one to eight zones, in a small, uniform home the benefit can be modest, and it is better to say so up front.

The hardest objections

Then there are objections that come up less often, but are harder.

“My brother-in-law says open source isn’t secure.” You can answer that free software runs bank servers and large companies’ systems, and that a building system’s security depends mainly on how it is installed: a separate network, personal passwords, planned updates.

“And what if you stop trading?” It is the most serious question, and the best one for an open system. The system stays with the client, with the diagrams and configuration handed over: any other installer who knows Home Assistant can take it over.

Handover day

The explanation doesn’t end with a signed quote. Handover day is when the client decides whether they will actually use the system. Half an hour spent setting the schedules together, showing where consumption appears and explaining whom to call if something goes wrong is worth more than any advanced feature. A client who understands the system recommends it to others.

A few weeks later

A phone call or a visit two or three weeks later closes the loop. Look at the charts together, adjust the schedules, answer the questions that came up through use. For the installer it is also the right moment to find out whether the client is happy, and to propose, where it makes sense, the next step: energy monitoring, remote access, an extra zone.

The video to send before the site visit

To help with this explanation we made the second video in our series, which you can watch below. In under a minute it shows a system with thermostats each working on their own, and turns it into a connected system, with the links to Brick lighting up one at a time. Many installers send it to the client a few days before the site visit: they arrive at the meeting with the questions already clearer.