The real cost of emergencies in real-world products

We call them emergencies because they feel exceptional. The pipe that burst. The elevator that stopped. The generator that failed at the worst possible time.

But spend enough time in operational environments — real ones, where physical assets interact with real constraints and real humans — and a pattern emerges. The emergency wasn't exceptional. It was inevitable. The only thing exceptional was the timing.

Most failures in physical systems follow a curve. There's a period of normal function, then a period of degradation that's barely perceptible, then a visible symptom, then failure. We tend to experience only the last two stages. The degradation happens silently, and by the time someone notices the symptom, we're already close to the edge.

This isn't a metaphor. It's engineering. The bathtub curve — a standard reliability model used in mechanical and electrical engineering — describes failure rates over the life of a system: high early on (infant mortality), low during normal operation, and rising again as components age. The middle period, where failure rates are low, is where most operators live. And because they rarely experience failures, they underestimate what's building underneath.

When I started working on Flix Home — a platform for managing real estate assets — I thought the problem was maintenance request management. Track tickets, assign technicians, close tickets. Software for something that was being done in WhatsApp and spreadsheets.

I was wrong about the problem. Or rather, I was looking at the symptom and calling it the disease.

When a property goes down — a unit becomes uninhabitable, a system fails, a space becomes unusable — the visible cost is obvious. Revenue stops. Repair costs money. Someone has to manage the crisis.

But the visible cost is almost always the smallest part.

The real cost of downtime in a property portfolio has several layers:

Lost revenue during idle time. A rented unit with a persistent water damage issue sits empty during repair. This is measurable and gets tracked. Most managers are aware of it.

Emergency service premiums. A repair done under time pressure, through whoever picks up the phone at 10pm, costs two to three times more than the same repair done through a scheduled, competitive process. Nobody tracks this comparison. It just shows up as "maintenance costs."

Management time and stress. A property manager handling an active emergency isn't managing anything else. Their attention shifts entirely to the crisis. Other issues accumulate. Decisions that should be made get postponed.

Tenant satisfaction and retention. A tenant who experiences a badly managed emergency doesn't just complain about the emergency. They start noticing everything else. Retention drops. Turnover is expensive.

Reputational and regulatory risk. In managed portfolios, persistent maintenance failures carry legal and compliance implications.

When you add these layers together, the actual cost of a single unmanaged emergency is often five to ten times what shows up on the maintenance invoice.

Nobody tracks stress. It doesn't appear in financial statements or operational dashboards. But in real-world products: the ones that involve physical systems, human operators, and unpredictable environments, stress is one of the most important signals in the system.

High operator stress means something is wrong with the system design. Either the system produces too many surprises, the operator has too little information to anticipate problems, the tools they use require too much manual effort, or the processes aren't absorbing variation the way they should.

In practice, I've seen property managers operating in a state of permanent low-grade emergency. Not because their properties are unusually problematic, but because the information they have access to is reactive by design. They find out about problems when tenants complain. They find out about asset degradation when something breaks.

This isn't a character flaw. It's a systems failure.

W. Edwards Deming, whose work on quality and systems thinking shaped modern manufacturing and operations, had a useful formulation: "A bad system will beat a good person every time." The insight is that most operational failures aren't caused by individuals making poor decisions. They're caused by systems that structurally prevent good decisions from being made.

The maths of preventive maintenance is not complicated. For most mechanical and electrical systems, scheduled preventive maintenance costs significantly less than reactive repair. The UK's Building Research Establishment has documented this consistently: the ratio between preventive and reactive maintenance cost is typically somewhere between 1:3 and 1:5, depending on the system type.

That means for every pound spent on prevention, you avoid three to five pounds in reactive repair.

So why do most organisations still operate reactively?

The honest answer is visibility. Prevention costs are visible and immediate. You schedule a service, you pay the invoice, the cost appears in this month's budget. The failure you prevented — and everything that failure would have cost — doesn't appear anywhere. It's a counterfactual. It never happened.

The reactive cost, by contrast, arrives as an emergency. It feels like an exceptional event. It gets categorised as an unfortunate exception rather than a predictable outcome of not preventing it.

The solution is system design: build processes and tools that make the cost of inaction visible before the inaction produces consequences.

The failure you see — the component that stops working, the asset that needs emergency attention — is almost never the real failure. The real failure happened earlier, quietly, in the absence of a system that would have caught the signal.

In complex systems, this is called "drift into failure" — a concept developed by Sidney Dekker, a systems safety researcher whose work on human factors and accident investigation has influenced aviation, healthcare, and industrial operations. Dekker's central argument is that most catastrophic failures don't have a single cause. They accumulate through small normalised deviations that each seem manageable individually, until they combine into a failure that looks sudden from the outside but was predictable from the inside.

In property management, this drift looks like deferred maintenance. A seal that's degrading. A filter that hasn't been changed. A piece of equipment that's been working "well enough" for three years past its recommended service interval.

This is the problem Flix Home is built to address. Not maintenance tickets — visibility. The infrastructure that allows the people managing assets to see the state of what they're managing, before problems become emergencies.

Most businesses don't have a maintenance problem. They have a visibility and anticipation problem.

The emergencies are symptoms. The cause is operating without enough information, early enough, to make preventive choices instead of reactive ones.

The cost of that gap isn't just financial. It's the accumulated stress, inefficiency, and lost potential of an operation running permanently behind its own problems.

Building systems that shift that balance — from reactive to anticipatory — is one of the most underrated improvements any asset-heavy operation can make. Not because it's glamorous, but because the compounding effect of fewer emergencies, over time, is significant in ways that don't show up until you measure what was prevented.

And most people never measure what was prevented.