About Rivolq
We built Rivolq because the best facility teams were making critical decisions with incomplete information.
The gap is rarely intuition. The gap is converting what operators know into decision language that finance, governance, and executive teams can act on.
Background
Built by people who have sat in the rooms where these decisions happen.
We came up through facility management, spending planning, and infrastructure consulting. We watched the same decision failures repeat across universities, hospitals, and city portfolios for years.
The pattern was always the same. Smart teams, real urgency, but no structured way to turn what they knew into something finance and leadership could act on. So we built Rivolq to close that gap. Not as a theory, but as a working system grounded in the environments we came from.
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.
Small, focused team. Every founder and advisor has spent years inside the environments we serve: healthcare, higher education, municipal operations, and mission-critical infrastructure.
Founder & CEO
Product · Strategy
Background in facility intelligence, capital planning, and infrastructure consulting across healthcare and higher education.
Founding Engineer
Risk Engine · Data
Previously built survival analysis and simulation systems for industrial asset portfolios. Focused on making the compound risk model defensible.
Head of Pilots
Operations · Deployment
Former director of facilities at a multi-campus healthcare system. Leads onboarding from data intake through first capital recommendations.
Advisors
Advised by facility directors, CFOs, and infrastructure leaders across hospital systems, university campuses, and municipal portfolios.
Our advisors keep the product honest. They are the people we built Rivolq for — they stress-test the methodology, challenge the outputs, and tell us when a recommendation would not survive a board meeting. Advisor names and affiliations shared under NDA during pilot conversations.
CMMS
Rivolq 01Work orders, preventive maintenance, asset records, and request intake. The daily operating layer for teams that need cleaner operations before anything else.
Risk Intelligence Engine
Rivolq 02A compound model that combines age, maintenance history, weather exposure, Weibull survival analysis, and Monte Carlo simulation to produce dollar-denominated asset risk scores. With auditable drivers behind every recommendation.
Digital Twin
Rivolq 03A 3D-referenced model of your facility with every asset mapped to its physical location. The spatial context that makes risk scores and spending sequence defensible.
Scenario Planning
Rivolq 04Side-by-side scenarios with budget optimization and board-ready output. The final step from analysis to a decision your leadership can act on.
Six principles. One operating mode.
Explainable by default
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.
Pilot first, promise later
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.
No black-box posturing
We use models and automation where they make decisions clearer, not harder to inspect. The methodology is documented and open to scrutiny.
Operationally grounded
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.
Outputs that hold up outside operations
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.
You keep everything
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.