About Rivolq
We built Rivolq because good teams were deciding blind.
Background
Built by people who have sat in the rooms where these decisions happen.
We came up through facility management, capital planning, and infrastructure consulting, watching the same failure repeat across universities, hospitals, and city portfolios: smart teams, real urgency, no structured way to turn what they knew into something leadership could act on. Rivolq closes that gap.
Facility risk is knowable. Most teams just haven't structured it yet.
The data already exists. Maintenance logs, inspection records, ages, weather exposure. What is missing is the layer that turns those records into a ranked sequence of consequence. We built Rivolq to close that gap, not to replace the people who already understand the systems.
The real problem isn't awareness. It's the language.
Your team rarely lacks intuition about what is aging or vulnerable. What they lack is a format that travels outside the operations office. A language finance, governance, and executives can act on. Our outputs are designed to survive that trip.
Deferred maintenance is a sequence problem, not a backlog problem.
Most teams frame deferred maintenance as a pile of work. The more useful frame is: what moves first, what can wait, and what happens if you get the order wrong? That question needs risk-weighted prioritization. Not a longer spreadsheet.
Team
Operators, engineers, and capital-planning veterans.
A small, senior team of operators, data scientists, and capital planners from the environments we serve. You will meet the founders and advisors directly during pilot conversations.
Facility intelligence & capital planning
Years across healthcare and higher-ed capital cycles — the people who have sat across the budget table when these calls get made.
Asset-risk modeling & simulation
Survival-analysis and simulation systems for industrial asset portfolios, engineered to make the compound risk model defensible.
Multi-campus facility operations
Former directors of facilities who now run onboarding — from raw data intake to the first capital recommendation.
Advisors
Advised by facility directors, CFOs, and infrastructure leaders across hospital systems, university campuses, and municipal portfolios.
They stress-test the methodology and tell us when an output would not survive a board meeting. Names shared under NDA during pilot conversations.
Security & data
Your facility data is treated like the sensitive infrastructure record it is.
Encrypted in transit and at rest, behind least-privilege access controls.
We never sell your data — and never train shared or public models on it.
Security and access reviewed with your team before every pilot.
Work orders, preventive maintenance, asset records, and request intake. The daily operating layer for teams that need cleaner operations before anything else.
Six principles. One operating mode.
Every recommendation comes with the reasoning behind it. Your team should be able to defend any output in a governance review without calling us first.
We would rather leave you with one useful facility model and a clear next step than sell a broad rollout before the value is proven in a single building.
We use models and automation where they make decisions clearer, not harder to inspect. The methodology is documented and open to scrutiny.
The software has to be useful to the people closest to the systems, not just impressive in a strategy deck. Daily workflow and decision support reinforce each other.
We design for the moment your facilities report lands in front of a CFO or board member. That audience needs numbers, consequence, and a defensible sequence. Not jargon.
The data, reports, and models we build for your environment belong to you. That stays true whether you expand to a full deployment or not.
You keep the data, reports, and pilot deliverables created for your environment.
We optimize for decisions that hold up in governance, finance, and leadership review.
We would rather narrow scope well than oversell a rollout that is not ready yet.
The point of the platform is clarity under pressure, not software theater.
If this sounds like the kind of rigor your team deserves, we should talk.
That might mean CMMS for the daily workflow, a pilot for a first-facility decision package, or a broader walkthrough for risk, reporting, and capital planning. We'll figure out the right starting point together.
