Custom smart building software development
Appfront builds custom software that makes the data from your building usable: climate systems, energy meters, occupancy sensors, access control and lighting come together in one view per building, floor and zone. Not a dashboard for the sake of it, but a system that flags deviations, routes faults to maintenance and turns consumption into something you can act on. Get in touch if you'd like to discuss your situation.
What is smart building software?
Smart building software is the layer above your building installations. A building usually already has a building management system for climate, a separate access system, energy meters from the grid operator and perhaps occupancy sensors from a pilot. Each system has its own screen and its own supplier. The software we build pulls those sources together, brings them into a single data model and creates one picture from them.
The difference from an IoT platform lies in scope. An IoT platform is generic: register devices, receive data, run rules, regardless of where those devices are. Smart building software is explicitly built around the building as the unit — floors, zones, rooms, installations and the people who work in them. That structure lives in the model, not in a generic tag structure you have to devise yourself.
Appfront builds this as custom software, with open protocols towards your installations and API integrations towards your maintenance and property systems. That way you remain the owner of your building data instead of it getting locked into a single installer's portal.
One model for the entire building
Floors, zones, rooms and installations in a single structure, so every measurement has a place and you can compare between zones, buildings and years.
Deviations instead of metres
Not another screen full of numbers, but signals: this zone is using energy outside office hours, this air handling unit is working against itself, and it has been too warm here for three days.
Passing it on to maintenance
A signal is only useful if someone acts on it. Alerts are automatically sent as a work order to your maintenance provider or property management system.
Smart building or IoT platform? Where the line falls
In practice these two overlap, and Appfront has a page on each. The distinction is organisational rather than technical: where does your challenge sit?
The building as the starting point
You manage one or more properties and want to steer comfort, energy consumption, occupancy and faults at building level. The data model follows the layout of the building, and the users are facilities managers, property managers and maintenance providers.
Devices as the starting point
You have a fleet of devices or machines, wherever they are, and want to read them out and control them. Then look at building an IoT platform or, for the industrial side, at AI & IoT solutions.
Our development process for your building software
A building cannot be unlocked all at once. We start with the data sources that already exist and build outward from there.
We take stock of which installations, meters and sensors are in place, which protocols they speak, who owns which system and what data can actually be extracted. The last point often turns out worse than hoped, and we would rather know that upfront.
We design the building model, the alerting rules and the screens for administrators and users, and determine which integrations are needed towards maintenance, property and reporting.
We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer the work based on what your team actually needs in practice, rather than on a specification written months earlier.
A controlled go-live with validation and a safety net, followed by ongoing management, monitoring and further development as your building portfolio or installation estate changes.
What custom smart building software concretely delivers
What makes sense differs per portfolio. These are the components we build most often.
Integration with building installations
Reading out climate, lighting and access installations via the protocols your installer supports, or via the API of the existing building management system. An integration with an IWMS such as Spacewell also falls under this.
Energy and consumption insight
Consumption per building, floor and zone, set against opening hours, outdoor temperature and occupancy. This makes visible which part of the consumption is genuinely needed and which part simply runs on.
Occupancy and space utilisation
Insight into which spaces are actually used, as a basis for reconfiguring layouts, disposing of floor area or adjusting cleaning and climate regimes.
Fault signalling
Rules that recognise deviating behaviour, such as an installation that keeps running or a zone that persistently falls outside its comfort band, and automatically raise an alert with context.
Reports from occupants
A simple entry point through which employees report a fault or a comfort complaint, linked to the zone they are in, so that a report immediately reaches the right installation.
Reporting and accountability
Reports on consumption, comfort complaints and fault resolution, usable for internal management and for obligations around energy registration and sustainability.
Typical use cases in practice
Smart building software delivers the greatest value where multiple properties, multiple systems and multiple stakeholders come together.
Office portfolios
Organisations with several office locations that want to compare comfort and consumption between properties and find out which floor area is actually being used.
Property managers
Managers who run properties for multiple owners and need to account, property by property, for how installations perform and how quickly faults are resolved.
Healthcare and education
Institutions with many rooms, fluctuating occupancy and strict comfort requirements, where climate complaints directly affect the core process.
Industry and logistics
Buildings where climate, cooling and energy use are tied to the production process, and where a fault costs more than just comfort.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology we use
Smart building software stands or falls with getting data out of systems that were not designed for it. The precise choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack your own team can manage and develop further, without dependence on per-user licences.
Why choose Appfront for your building software?
Appfront builds custom software for a wide range of organisations across the Netherlands. With building software, the work doesn't start with the dashboard but with the question of what can actually be extracted from your installations. We do that inventory first, because that is where most projects run into trouble.
We deliberately build on open protocols and keep your data in your own environment. A building lasts for decades and installers change; your building data should not have to move along with whichever supplier happened to connect it first.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box: transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence fee.
Also explore our wider services around custom software, an IoT platform and property management software. Unsure about the approach? Get in touch.
Security and privacy in your building software
Building systems are an attractive target because they often run for years without updates and sometimes sit directly on the internet. Appfront builds to the OWASP ASVS and keeps the integration with installations strictly separated from the user layer, with least-privilege access and network segmentation as the starting point.
Occupancy and access data can be personal data as soon as it can be traced back to an employee. We design so that traceability only exists where it is functionally needed, document the data flows for your record of processing activities, and take GDPR and the works council's co-determination rights into account.
More on our security approach: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail for viewing and changes
- Secrets in a secure vault, not in code
- Documented data flows for your record of processing activities
- Separate network path to building installations
Frequently asked questions about building smart building software
Answers to the questions we are asked most often.
Software that brings the data from your building installations, meters and sensors together into a single model per building, floor and zone, and turns it into usable signals: unusual energy consumption, comfort outside the target range, installations not doing what they should. It is the layer above the installations, not the control itself, which remains with your building management system.
No, and that is usually not sensible either. A building management system controls the installations and is certified for that purpose. We build the layer above it: retrieving data, combining it with other sources, flagging issues and passing them on. Control can be arranged in consultation with your installer, but we start with reading data, which delivers value fastest and does not touch the safety of the installation.
Often, yes, but it is the first thing we investigate. Some installations speak an open protocol, some offer an API, and some reveal nothing without the installer's involvement. In the last case there are usually alternatives, such as standalone meters or sensors. We map this out before anything is built, so you don't pay for an integration that turns out not to be possible.
That varies by property and we make no promises about it. What we see in practice is that the first insight almost always reveals something nobody knew: installations running through the night, a zone that has been heating and cooling against itself for months, rooms that are structurally empty. What that is worth depends on what you do with it.
Occupancy sensors that only count whether a room is in use do not process personal data. As soon as you make workstations traceable to individuals, through a login, badge or camera, that changes and GDPR rules apply, including the duty to inform and, in some cases, the consent of the works council. We prefer to design so that traceability is not needed.
This is often the most valued feature. A simple way to report that it is too cold or that the lighting isn't working, linked to the zone where someone is sitting, produces better alerts than an email to the facilities mailbox, and it shows whether complaints coincide with what the sensors are measuring.
Yes, and that is usually the key point. The model is built at portfolio level, so you can compare properties on energy use, comfort complaints and fault handling. You add new properties without any development work being needed.
There are good platforms, and if your installed base is modern and uniform, you can get a long way with one. Custom development pays off when your portfolio is mixed, when you need to integrate with systems such a platform doesn't support, or when you don't want to depend on a single vendor for access to your own building data. If an off-the-shelf package fits better, we'll say so.
Ready to get your smart building software built?
Tell us which properties are involved, which installations are in place and what you currently cannot see. We're happy to help you think through scope, integrations and the first version. A no-obligation first conversation will give you a clear picture of what is possible and whether custom development makes sense in your situation.