The demo usually goes well. A dashboard loads, a chart shows heating performance floor by floor, and the owner can picture the building being run from one screen. Then someone asks how the software will work with the controls already installed in the building, and the meeting slows down. That question comes up a lot in building software, because so many of the buildings are old. Vendors of energy optimization and analytics software sell to owners whose heating, ventilation, and air conditioning (HVAC) controls date back years, sometimes decades.
According to the European Commission, around 85% of buildings in the EU were built before 2001, and 85 to 95% of today’s buildings are expected to still be standing in 2050. In most cases, new software has to work with whatever equipment is already there.
Tom Novotny is CEO of Finnish company Nobody Engineering, which lets newer digital services read and write data in the legacy HVAC controls already running in buildings. He says the trouble easily emerges before anyone signs, before anyone has checked what the existing controls will allow. According to Novotny, after hundreds of connected buildings, his team has a repeatable process for dealing with different systems.
Three Buildings Out of 200
Ville Ilkkala, the company’s founder, found out how hard this can be before the company built its current product. In an early pilot, a city wanted to connect around 200 of its buildings to the team’s original software platform.
“It was less a moment of sudden certainty than a fairly painful discovery,” he says. “We managed three. The software wasn’t really the obstacle. We were running into old controllers, closed interfaces and an industry in which everyone had become accustomed to the difficulty of accessing building automation.”
Swapping out the old systems wasn’t an option either. “The owners didn’t have the capital to replace them, and in many cases there was no good reason to,” Ilkkala says. The pilot became the company’s founding story: instead of building another application, the team set out to solve the connection to old controls.
Why Contracts Come Before Checks
Novotny traces the habit of signing first and checking later to how buildings are run. Owners have spent years handing their controls over to installers and maintenance contractors. The people who know what is installed and who can grant access often don’t work for the owner at all.
“Not all owners can easily run a check, so I guess they often default to hoping it’ll work out, or they get overpromised and oversold by service providers keen to close a deal,” he says. “And then a project or an extra bill comes. Incentives are simply not aligned.”
Some of the confusion comes from the word “compatible.” An app that can read a few values from a control system can’t necessarily do everything it did in the demo. Even the readings can take work. One building labels a data point one way, the next uses different names or units, and someone has to figure out what each one means before the software can use it. That mapping is integration work just as much as the physical connection is. It rarely comes up in the sales pitch.
Several Parties Have to Agree
The people who have to say yes are often not the ones buying or using the software. One contractor maintains the controls. Someone else controls access to the building network. And a facilities manager thinking about changes to the plant will read the same proposal very differently from a colleague comparing software subscriptions.
Asked where disputes between owners, integrators and software vendors tend to start, Novotny won’t speak for the other parties. “Issues easily arise at handoffs,” he says. In his experience, a shared connection layer cuts down on those handoffs. One supplier looks after the link between the building’s controls and the software, so the software provider doesn’t have to take on controls integration that sits outside its own expertise. When something breaks, it’s clearer whose problem it is.
Paying for the Same Connection Again
This is where Novotny parts ways with the usual advice to write tighter proposals. In his view, a clearer scope helps but doesn’t change how integration gets paid for. Under the usual model, new applications come with its own integration project and its own invoice, so it’s not uncommon that an owner who adds a second or third service ends up paying to connect to the same controllers again.
Novotny compares it to consumer electronics before the smartphone. “In a way, building software today is still bought like a camera, a tape recorder and a radio in the 90s. Each is its own device,” he says. With a shared connection layer, he adds, it can be bought “like one iPhone: connect the building once, and every app runs on it.”
The first connection still takes work: someone needs access to the building’s controls and has to set up the link. After that, a new application runs on the connection that is already there instead of arriving with its own integration project, and the owner isn’t paying for the same work again.
A Retail Building in Stockholm
Take a retail property in Stockholm that ran on an aging Trend Controls system, with little local support for that equipment. Sally R, which makes optimization software for commercial buildings, needed reliable data from the system but had no interest in taking on the controls integration itself.
As Novotny tells it, the options were a long and expensive upgrade of the legacy system or connecting the equipment as it stood. According to the company’s published case study, the connection took days. An edge device went in next to the existing system, and the controls stayed where they were. Sally R provided the application. Nobody Engineering’s infrastructure handled everything from connecting the building to translating the old system’s data into something the software could work with.
Other buildings will have different controllers. Novotny says their infrastructure can connect to more than 75 control systems so far, and that an unfamiliar model mostly means a new addition to their integration library they do on their own cost instead of the customer’s.
What Changes When a Building Is Connected Once
Novotny’s suggestion to software providers is to stop selling integration as part of every deal. He points to Sally R as an example. Instead of building a separate integration for every property, the company connected its software to the shared layer once and relies on Nobody’s infrastructure, with the per-building controls saving everyone’s time. That lets Sally R concentrate on optimization, and every building connected this way is ready for the next service it sells.
For owners, the change shows up in the next purchase. They still pay for the connection layer itself as an ongoing service, which is a fraction of the cost to an integration project, but they no longer commission a new controls integration each time they add an application.
The demo shows what the software can do. What it takes to get it running depends on the building, and in Novotny’s view, owners should only have to find that out once.

