Something new to sell into the homes you already look after.
You are already inside these houses. You specified the racks, you pulled the wire, and you are the number the client calls when something stops working. What you cannot easily add to the proposal is a genuine chief of staff — a named, conversational household assistant that manages calendars, projects, documents, errands and family logistics, and happens to control the home as well.
That is what PrivateChief is, and it is not a product you have to build, stock, learn, or support. Register below, introduce the client, and receive a flat $1,000 when that household becomes a PrivateChief home. No tiers, no percentages, no codes for your client to remember.
We do the whole job: household design session, hardware specification, installation day, family onboarding, updates, monitoring and ongoing support. Nothing lands back on your service desk.
You are going to ask these first, so we will answer them first.
“Are you replacing the control system I just sold them?”
No. PrivateChief is a conversational layer that sits above the home, not a lighting or AV control platform. We do not quote keypads, we do not program scenes for a living, and we have no interest in the part of the job you are good at. The client keeps the system you installed and keeps you as their integrator.
Underneath, PrivateChief runs a private Home Assistant instance on the appliance in the home, so it reaches your stack the way Home Assistant does. The verified position for each major line is in the table below — including the two we cannot yet serve.
“Whose phone rings when it breaks?”
Ours. PrivateChief is a managed service with real engineers behind it — monitoring, updates, encrypted backups and support are included in the monthly fee the client pays us directly. You are not reselling it, not warrantying it, and not carrying it on your books.
You make an introduction to something you think is good. We take it from there, and you are told how it went.
The honest compatibility list, including the gaps.
PrivateChief runs a private Home Assistant instance on the appliance in the home. That is the device layer; the Chief, and everything the family actually sees, sits above it. It means we inherit Home Assistant's reach — thousands of devices across Matter, Zigbee, Z-Wave, Thread and IP — and also its limits, which we would rather you heard from us than discovered on site.
| Control4 | Supported. Home Assistant's Control4 integration reaches the controller locally on OS 3.0+ for lights, media rooms, shades and climate. Local only — remote 4Sight access is not a path. |
| Lutron | Supported. RadioRA 2, RadioRA 3, Caséta, RA2 Select and HomeWorks QSX — dimmers, switches, scenes, shades, fan control, sensors and Pico remotes. Note HomeWorks QS is not QSX, and is not covered. |
| Crestron | Case by case. There is no first-party integration; the working route is a community component over XSIG. We assess it per project rather than promise it. |
| Savant | No supported path today. If Savant is your core line, say so when you register and we will tell you plainly where that leaves us. |
Every house is still confirmed at the pre-installation survey — that is where we establish what is actually on the network, rather than what was on the invoice.
Three steps. The third one is a check.
See it working first. We would rather you did.
You are not going to put your name to something you have not seen, and we would not ask you to. Talk with Alfred — a demonstration Chief running a simulated home, in your browser, no signup — or book a private consultation and we will walk your team through the whole system.
If you would like the evidence on what smart-home capability is worth in a transaction, our research brief is at The Smart Home Dividend.