Facility Management software
Facilities is judged on the things that did not happen.
Nobody notices the lift that kept working or the fire system that stayed certified. They notice the failure, and by then the question is not what broke but whether you can produce the service record. A facilities system is a compliance file that happens to also dispatch work.
What it replaces
- Complaints arriving by phone, email and corridor, with no record of what was promised or when.
- Planned maintenance in a wall calendar, skipped in a busy month and never caught up.
- Vendor performance assessed by whoever answers fastest, with SLAs in a contract nobody measures against.
- Statutory certificates in a folder, their expiry known to one person who is on leave when the inspector arrives.
What we build
The parts that make it a system.
Scoped to what you run. A module you do not need is not a discount we withhold — it is work nobody does.
Helpdesk and work orders
Requests from a QR code on the equipment, a portal or email; triaged, assigned, tracked to closure with time stamps that make an SLA measurable rather than aspirational.
Planned preventive maintenance
Schedules per asset with checklists, auto-generated work orders, and a compliance view showing what was skipped — the report that matters more than the completion rate.
Vendors, contracts and SLAs
AMC contracts with scope and renewal dates, response and resolution measured per vendor, and invoice validation against what was actually attended.
Statutory compliance records
Fire, lift, electrical and pressure-vessel inspections with certificates, expiry alerting well ahead of the date, and an evidence pack that can be produced in minutes.
Where AI actually helps
And where it does not.
Two defensible uses. Classifying and routing inbound requests — including the ones that arrive as a photo and three words — removes the triage bottleneck. Grouping repeat faults on the same asset finds the chronic problem that individual tickets hide. Predictive maintenance in a building services context is mostly vendor marketing unless the plant is genuinely instrumented, and most is not.
Integrations
What it has to talk to.
A system that does not reach the ones you already run creates a second place to type things, which is the problem you started with.
- BMS or IoT sensor feeds, where the building has them
- Access control and visitor systems for the security side of the estate
- Accounting for vendor invoices and maintenance cost per site
- WhatsApp or email as a request channel, since occupants will not install an app
The limits
What we do not do here.
Including, on several of these pages, telling you not to buy a build at all. That advice has cost us work. It has also stopped projects that would have failed in month three, which is cheaper for everyone.
- We do not provide facilities management as a service, staff a helpdesk or hold vendor contracts. This is the system your team or your FM provider runs.
- We do not do BMS controls integration that writes back to plant. Reading data is a project; controlling equipment is a safety-rated discipline with a different insurance profile.
- Space planning and CAFM floor-plan editing are a specialist product area. We integrate with one rather than build a drawing tool.
In practice
Where this shows up.
Commercial and retail property
Multiple tenants raising requests against shared services, so the record has to separate landlord obligation from tenant responsibility — which is a billing question as much as an operational one.
Institutional campuses
Hospitals, campuses and hotels run continuously with statutory inspection regimes, so the compliance calendar leads and the helpdesk follows.
How it runs
Fixed scope, fixed price, working software each sprint.
01
Discovery
A call, then a written read of the problem — what it costs today, what would have to be true for software to fix it, and whether we're the right people.
02
Proposal
Fixed scope, timeline and price. No open-ended discovery phase billed by the hour.
03
Build
Agile sprints with something running at the end of each one. You see progress in the product, not in a status deck.
04
Ship & support
Cloud deployment, production monitoring and a maintenance arrangement that starts before launch, not after the first incident.
Related
Systems that usually come up in the same conversation.
Most of these share data with each other. Where two are in scope we would rather build one system than two that sync.
Property Management
Units, tenants, leases, rent and maintenance in one system — with the money side reconciled rather than remembered.
Asset Management
Every asset with a location, a custodian, a maintenance history and a real book value — from purchase to disposal.
Task Management
Work assignment and tracking embedded in your own process, for teams that need workflow rules a generic board cannot express.
Tell us what your Facility Management system would have to handle.
Pick a time that suits you. Tell us the problem, and we'll tell you honestly whether we're the right people to solve it.