Who Becomes a BUTLER Client — and Why It Is Almost Always About More Than a “Smart Home”

An owner buys a way of living, an architect a design that survives the build, a builder a schedule that holds. How three different briefs meet in one house.

I am sometimes asked: who is your client?

There is a standard answer: owners of villas and apartments, architects, interior designers, construction companies, developers. Over the years I have found that it explains almost nothing, because each of them comes to us for an entirely different result.

The owner is not buying technology. They are buying a particular way of living.

The architect is not buying equipment. They are buying the chance to keep their idea intact.

The construction company is not buying a “smart home”. It is buying a predictable technical partner who will not wreck the schedule.

Our job, somehow, is to bring these three worlds together in one building. That, to my mind, is where real integration begins.

Sometimes a client knows exactly what they want. Usually they have lived in well-made houses or in hotels where the technology is done properly; it may not be their first home. They already know what they find comfortable, and what exists only in a manufacturer’s glossy presentation.

They may arrive with a finished interior design, and then that design is our brief. We have already been told what life inside this space should be like: where the family has breakfast, how they receive guests, where they listen to music, how they watch films, what the house should look like in the evening, what should be on show and what should disappear from the interior altogether.

From there our work begins: propose the technical ways of getting that result and explain the difference between them; choose the equipment, design the infrastructure, tie the engineering systems together; install; program. And after handover, tune everything once more — no longer to the drawings, but to the actual person.

Because between “the Evening scene is in the design” and “I genuinely like being here in the evening” lies a considerable distance. The last ten per cent almost always appears after people have begun to live in the space.

That is why, to the end client, we are not selling a smart home. We are trying to build the way of living they had in mind when they first started the project.

With architects the relationship is built very differently. A good architect does not usually need another equipment salesman. They need an engineering partner who can understand the idea and not destroy it with technical constraints of their own — and sometimes help build the thing that, at first glance, nobody can see how to build.

Hide the projector. Send the screen up into the ceiling or down into the joinery. Make a structure that moves. Integrate the audio so that it does not break up the interior. Conceal a vast amount of engineering behind a space that looks simple to the person standing in it. These are the projects I like most.

Because the job of a good engineer here is not to be the first to tell the architect:

“That can’t be done.”

First we need to understand why they want it done that way; only then do we look for the answer. Sometimes it is obvious. Sometimes we have to develop a one-off mechanism. Sometimes we have to explain that the idea is feasible but will be paid for in reliability, serviceability, acoustics or cost — and then the team makes a conscious decision.

The engineer must not defeat the architect, nor the architect the engineer; the project must win. — Nikolai Atapkov, founder of BUTLER

So what an architect buys from us is not KNX, Lutron, Crestron or another beautiful panel on the wall. They buy the chance to say: “Here is what I had in mind. Help me make it real.”

Construction companies and main contractors look at the same building differently again. They have a programme, a sequence of works, dozens of subcontractors, dependencies between them, and a handover date. If the architect’s first duty is to the idea, the builder’s is to the process. So for a builder, a good integrator is not only a strong engineer. It is a predictable contractor.

A builder needs to know when we come on site; what has to be ready before we do; what has to be done after us; when the conduit and back boxes go in; when the cabling starts; when the distribution boards and racks are assembled; when the equipment arrives; when programming begins; when commissioning happens; when we hand over.

And most important of all: if something changes, it must be known in advance — not when five other subcontractors are already standing on site waiting for a decision.

For a main contractor, a large part of our value is simply that we are easy to understand. Who is responsible for the project; which revision of the drawings is current; what has been approved; which questions are open; which decisions are blocking the work; what is needed from the architect, from the client, from another contractor; and exactly where we stand against the overall programme.

This sounds far less glamorous than a motorised screen vanishing into a ceiling. On a real site it is often what matters more.

I have seen superb technical specialists who could barely function inside a large project: no way to get a date out of them, no documentation, no clarity about who answers for the result, everything resting on one person and their memory. For a construction site that is a dangerous model, because a small contractor can cause a very large delay.

So what a construction company buys from us is, above all, less uncertainty. We have to be easy to slot into the programme and easy to manage, and our part of the project must never suddenly become everybody else’s problem. That too is engineering — only not the engineering of equipment.

Process engineering.

And this is where it gets interesting, because the owner, the architect and the builder very rarely see the same question the same way.

The owner says: “I don’t want anything visible here.” The architect replies: “Of course.” The engineer starts working out equipment dimensions, ventilation, service access and cable routes. And the builder looks at the calendar and asks: “When do I need to know this? Because we close that ceiling in two weeks.”

Each has their own truth, and all of them can be right at once. If the engineer thinks only about engineering, the interior suffers. If the architect thinks only about the interior, the result may be unreliable or impossible to service. If the site thinks only about the deadline, it builds on time something that will later have to be redone. And if the client changes their mind too late, the whole thing starts to come apart at once.

So our role sits between these parties. Sometimes we defend the architect’s idea against the contractor; sometimes we explain the physics to the architect; sometimes we tell the client that what they now want is possible but will move the budget and the schedule. And sometimes we simply gather everyone in one room and settle in twenty minutes a question that would otherwise hang for two weeks.

The more complex the project, the more our work turns from supplying equipment into managing the interfaces — between people, systems and decisions.

There is a category of client apart from all the others. They own property in several countries, have been through dozens of construction projects and know precisely what the words “reliability”, “service” and “responsibility” are worth. Some have an in-house technical team, and we work alongside it.

Every decision is checked against engineering, operation and local regulations. If the owner’s comfort calls for a non-standard answer, nobody hides the risks: they are discussed, the responsibility is allocated, the decision is documented.

In the most advanced of these set-ups there is also centralised monitoring of the entire property portfolio. A leak, a tripped breaker, a lost connection, an air-conditioning fault, a room drifting out of its temperature band — the technical team knows before anyone in the building has realised that something is wrong.

For a single apartment such infrastructure can look excessive. For someone with dozens of properties around the world, the arithmetic is entirely different. This is no longer a smart home. It is property management: protecting the investment, controlling the risks and — perhaps most valuable of all — not having to deal personally with an endless stream of domestic problems.

I consider that one of the highest forms of real luxury. Not a gold switch. Not the most expensive processor. The ability simply to live your own life, knowing that the space around you is working as it should.

I have never much liked the word luxury — more on what luxury really means in a smart home. For one person it is a serious stereo system the whole living room is built around; for another, no visible technology at all. One wants the most elaborate lighting automation; another wants four buttons that make sense, good curtains and the right climate. Both are right.

So I would sooner compare our work to a good tailor’s. You can buy very expensive cloth. You can buy beautiful buttons. You can even take the pattern of the finest suit in the world. None of it means the suit will sit well on you. First you understand the person; only then do you choose the tools.

We had an instructive example at a shisha lounge in Dubai, where we did the automation and the audio system. The project works well, the client is happy, and the best proof is that we have since started work on their next one — a second lounge, this time in Abu Dhabi.

But ask our inner perfectionist whether the sound on the ground floor could have been even better, and the answer is simple:

Yes.

We knew the options. We proposed them. But the project had its architecture, its budget, its deadlines and a specific commercial purpose. For the client the space had, above all, to create an atmosphere: to look beautiful, to work reliably, to hold the right feeling of the place. Nobody had asked for an audiophile laboratory.

That is an important professional skill. Not every project has to demonstrate everything the engineer can do. We do not work for our own technical ego; we work in the client’s interest, with the client’s money and inside the client’s priorities: show what is possible, explain the consequences, get the best result inside the agreed constraints. Sometimes the technically perfect answer is simply not the best one for the project — and that is fine.

There are a great many integrators on the market: some have been around for decades, others appear every year. Sometimes a strong engineer leaves a good company, takes a few projects along and sets up alone. Sometimes a strong company really does come of it. Sometimes not — because there is a vast distance between knowing how to program a system and being able to deliver a finished result, reliably, on a complex site. And the words have almost stopped meaning anything.

Custom installation. Premium. Luxury. Turnkey. Engineering. Service.

Everyone says roughly the same thing, so a glossy presentation rarely tells you what will happen two years after the contract is signed. The difference shows later. In the documentation. In the cable labelling. In who spotted the clash before installation began. In how neatly the rack is built. In who checked the temperature limits of the underfloor heating so that an expensive timber floor is not ruined a season later. In who thought about what happens when the power goes off. In how quickly, three years on, another engineer can work out why one sensor has stopped working. And in whether anyone answers the phone at all three years on.

On one recent project more than a dozen other trades and consultants were working around us. On projects like this it is very easy to start believing you are the centre of the universe. The truth is the opposite: however professional our team, we are one element in a very large system. And the result does not go to the integrator. It goes to the client.

So the ability to work with others often matters more than the ability to prove you are the cleverest specialist in the room.

Many years ago I was strongly influenced by the owner of a construction company. He had put enormous effort into standards: how to work, how to accept work, how to check it, how to document it, which details were acceptable and which had to be redone.

Some of the specialists who had worked for him later did projects on their own. The same people. The same hands. The same skills. Yet somehow the quality came out different — because the system had gone. Nobody checked. Nobody set the bar. Nobody demanded that something be redone when it was, formally, “fine as it is”.

That is one of the main lessons I took into BUTLER. The value of a company must not live in the head of one talented engineer.

People come. People go. The company remains.

So the real value is the combination of people, experience, documentation, standards and control, and the internal expectation of what the result should be. The client almost never sees that work. They see its consequences.

Two years on. Five. Sometimes ten.

By classic business logic, that is. We love the product too much — sometimes more than is useful for our own commercial efficiency. We really do care what the rack looks like once a cupboard door has closed on it. How legible the drawings are. What a person will feel when they press one button in the evening. How neatly a system is built that no guest will ever see.

Of course a company has to make money; without profit there is no strong team and no investment in training, tools, documentation and service. But in our segment I see no other long-term path: first the product has to be good. The product becomes a reputation. The reputation becomes the next project. And the next project is the chance to do something better still.

It may be a property owner — but then they are not buying technology from us. They are buying a particular way of living. It may be an architect — but then they are not buying equipment. They are buying the ability to keep their idea and see it built. It may be a construction company — but then it is not buying a smart home. It is buying predictability, accountability and a partner who can be slotted into a complex process.

Each has their own interests, their own risks, their own frame of reference. Our job is to make sure that, at the end, all three get what the project was started for. The owner has a space they genuinely enjoy living in. The architect looks at the finished interior and sees the original idea, not a set of engineering compromises. The builder has handed over on time and does not remember us as the contractor who once stopped the site.

That, I suspect, is the real definition of a good integrator. Not the number of brands on the website. Not the number of functions in the app. Not even the amount of technology inside the house. But the ability to take a complex project, in which different people want different things, and bring it to the point where everything simply works as it should. Everything else — brands, protocols, programming, kilometres of cable and hundreds of pages of documentation — is only tools.

And if, once the project is finished, the client stops thinking about any of it, we have most likely done our job properly.