Built for the operational reality of fire safety compliance.
FLOS is a compliance-first operating system for UK fire safety contractors. It connects planned maintenance, inspections, defects, remedials, certificates, and evidence into one controlled workflow, so the proof is always there when someone asks for it.
Who built this
You'll deal with the people who build it, not an account manager.
Aaron Ogunniya
Co-Founder and CEO
I have spent 13 years as a business analyst and functional consultant, designing operational systems for organisations where the process, not the software, was usually the thing that was broken. Recruitment at REED, on a programme replacing four core legacy systems. Healthcare staffing at Acacium Group. Social housing at L&Q and VIVID, then field and vehicle operations at British Car Auctions and Creative Car Park. I'm currently engaged with Southern Housing on their Awaab's Law programme, leading the process identification and future state modelling for how a hazard gets reported, classified, put right and evidenced inside a legal deadline.
Most of that work wasn't really about software. It was about the gap between what a system records and what actually happened on site, and who is left holding the evidence when somebody asks. Fire and building safety is one of the nine hazard types in that model, which is this same problem seen from the landlord's side of the contract rather than the contractor's.
I kept meeting the same thing in fire safety. Every contractor already has a system. Almost none of them trust the evidence coming out of it, and they're right not to.
I own the commercial side of FLOS: pricing, customers, and the standards work that decides what the product has to enforce.
Premjit Singh
Co-Founder and Technical Lead
I have spent 15 years building the systems organisations get audited on. Five and a half of them at Capita, replacing a legacy platform used by more than nine hundred people, then the auto-enrolment compliance declaration for The Pensions Regulator, Homes England, Severn Trent, and social housing at Sage Homes and L&Q. I have been a Microsoft Certified Dynamics 365 and Power Platform Solution Architect since 2020.
Almost all of it has been in places where somebody official checks the records. It's the same problem in a different building. The organisation is usually doing the work properly, it just can't prove it, and by the time that surfaces it's too late to fix.
Fire safety is that problem with the volume turned up, because the record is the only thing standing between a contractor and the consequences.
I own the build: the architecture, the engineering, and how the compliance rules get enforced rather than merely recorded. I also bring the delivery and support capability behind the product, onshore and offshore, so the roadmap and the support line don't rest on two pairs of hands.
Between us that is more than twenty years of building the systems organisations get audited on. None of it in fire safety until now, which is why we started by going and looking at somebody's actual data rather than by writing software.
Why we built it
We didn't start with software. We started by sitting down with a nine-person fire safety contractor and going through twelve months of their own data, job by job.
They're well run. They pay for one of the best-known platforms in the market. And in twelve months, planned maintenance completion had fallen by more than a third without anyone noticing until clients started chasing. Thousands of remedial tasks had been raised with almost no structured detail attached to any of them. A substantial amount of quoted remedial work had either expired unchased or been built and never sent.
None of that was anybody's fault. The tools did what they were asked. The problem was that no part of the process owned the gap between an engineer finding a defect and the client getting proof it was fixed. That gap is where the money goes, and it's where the evidence goes too.
FLOS is built to own that gap. Compliance status is derived from the records underneath it rather than typed in by a person. A certificate is blocked while a critical defect is open, and there's no override, because the moment there's an override that's the button everybody presses at 4pm on a Friday.
Where we are, plainly
FLOS is new. ANP Pro Solutions Ltd was incorporated in May 2026, and we're working with a small number of contractors as founding partners rather than selling broadly.
That's a deliberate choice and it cuts both ways.
What you get: a rate fixed for the life of your licence, direct access to the two people building the product, and real influence over what gets built next. When you tell us something is wrong, you're telling the people who can change it.
What you don't get: a decade of other people's implementations behind you, or a support desk with a rota. If you'd rather buy something with a thousand customers already on it, that's a reasonable thing to want, and we aren't that yet.
We're not fire engineers. We don't claim to be. What we know is how to build the systems that have to hold up when somebody checks, and we learned this sector by sitting with people who work in it.
We're taking five founding partners. Once those five are in place, the window closes.
The problem isn't technical competence. It's operational control.
Most fire safety contractors we spoke to are technically capable. Their engineers know the standards. Their coordinators work hard. But the operational system around that capability is often fragmented.
PPM visits slip, and only become visible when a client chases. Engineers complete the work, but certificates and reports take longer than they should. Defects get found on site, but the follow-up into quote, approval, remedial job, and final evidence breaks down somewhere in between. When a client, insurer, or auditor asks for proof, the evidence exists, but it's scattered across systems, emails, spreadsheets, WhatsApp messages, and PDF folders.
Meanwhile, contractors are paying for software they're only partially using. The system doesn't hold the process together. People do. And that creates risk. That's the gap FLOS is designed to close.
The golden thread of fire safety delivery.
FLOS is designed around a single core principle: every job, inspection, defect, certificate, and report should be connected, traceable, and explainable.
We call this the golden thread.
The golden thread is a continuous loop connecting Contract, Site, Asset, Planned Maintenance, Inspection, Defect, Remedial, Certificate, Compliance Evidence, and back to the start. The thread never breaks.
When this chain holds, contractors can account for every obligation, every finding, every piece of follow-up work, and every output, without reconstructing it from memory or chasing files across systems. When it breaks, compliance risk and revenue leakage both increase. FLOS is built to keep that chain intact.
What good looks like.
Compliance should be traceable, not reconstructed.
When an auditor or responsible person asks for evidence, it should take seconds, not hours of digging through folders and chasing engineers.
Defects shouldn't disappear after an inspection.
Every defect found on site should flow automatically into a structured remedial workflow. Nothing should fall through the gap between the engineer leaving and the coordinator picking it up.
Certificates should come from structured evidence.
Not from disconnected admin effort, cut-and-paste PDFs, or someone’s best recollection of what happened on site.
PPM should be controlled before the client has to ask.
Overdue planned maintenance is a compliance risk and a client relationship risk. The system should flag it before it becomes a problem, not after.
Systems should support real operations, not create more workarounds.
If contractors are working around their software rather than through it, the software isn’t doing its job.
Built for contractors who take compliance seriously.
FLOS is designed for owner-managed and growing UK fire safety contractors delivering services across fire alarms, emergency lighting, extinguishers, remedials, planned maintenance, and compliance reporting.
The sweet spot is businesses with operational complexity: multiple sites, multiple engineers, multiple service lines, and clients who expect professional evidence and clear reporting.
If you're managing PPM schedules on spreadsheets, chasing certificates manually, losing remedials between inspection and quote, or struggling to produce audit-ready packs quickly, FLOS is built for you.
We're aligned to the standards your clients expect:
Let's talk about your operation.
If any of this sounds familiar, whether it's PPM leakage, slow certificates, lost remedials, scattered evidence, or systems you're working around rather than through, we'd like to show you what FLOS can do. We're working with a small number of contractors as founding partners. If you'd like to be one of them, book a call and tell us where your current operation breaks down. That's where we'll start.
Book a Demo