Compliance software pricing that ignores how many devices you actually have is either overpriced for a single building or unworkable for a group. Tell us your sites, your device count and your users, and you will get a firm number — along with both the cloud and the on-premise figure so you can compare honestly.
Your existing device list imported and structured, rather than a blank database and good luck.
Existing Excel check points brought across, so your rounds stay the rounds your team and your auditor know.
Set up against the cycles your standards, insurer and fire authority actually hold you to.
WhatsApp, email and SMS routing and escalation paths set up with you, not left as a default.
Onsite and remote, until your safety team is genuinely running it rather than tolerating it.
So new joiners and shift staff can be trained later without booking another session.
Nothing switches over until your team confirms it is ready.
Dedicated portal, email, WhatsApp and phone, plus monthly review meetings.
Deployed the way your IT policy requires, including inside your own network.
Pricing depends on three things: the number of sites, the number of fire devices in the register and the number of users. A single building with a few hundred devices is a very different proposition from a twenty-site group with several thousand, so a published per-user price would be misleading in both directions. Tell us those three numbers and you will get a firm quote.
Both models are available. Cloud deployment is typically subscription; on-premise installation on your own server is typically a licence with an annual support component. Which is cheaper over a five-year horizon depends on your device count and your IT policy, and we will show you both figures rather than steer you.
Device register setup with your existing list imported, your checklists imported from your current Excel formats, configuration of frequencies and alert rules, three months of hands-on handholding onsite and remote, video-recorded training sessions, and end-user sign-off before go-live. Up to six months of post-go-live support is included.
Implementation is quoted as part of the proposal rather than added afterwards as a surprise. What varies is the size of the register you are starting from and whether you need help tagging the building physically.
Yes, and most do. Prove the cycle on one plant, hospital block or warehouse, then extend the same categories, checklists and frequencies to other sites. Because it is one platform sharing the same device, area and user masters, adding a site is a configuration exercise rather than a migration project.
User counts factor into the quote, but the pricing conversation is usually driven by device count rather than headcount — the register is what determines the size of the system. If you have many occasional auditors, say so, because that changes the shape of the right answer.
Sites, devices and users. We will come back within one business day with both the cloud and the on-premise figure.
