Which revenue disappears rather than waits?

Which revenue disappears rather than waits?

Not every interrupted sale becomes backlog. Some demand is merely delayed; some shifts to a competitor, expires with time, triggers a contract right or changes a customer habit permanently. Treating all lost throughput as recoverable understates both continuity risk and the value of speed.

Segment revenue by recovery behaviour. Consider perishability of the need, ease of switching, contractual service levels, capacity to catch up, channel substitution, customer concentration and network effects. A delayed capital purchase may return next quarter; a missed travel night, urgent repair, auction or first subscription experience generally will not.

Build a duration curve from the customer backward. At each outage interval, estimate transactions deferred, cancelled and transferred, then include price concessions, penalties, churn, lower future share and the cost of reacquisition. NIST�s business-impact approach emphasises mission-essential functions and the broad consequences of loss, not availability metrics in isolation.

Recovery sequence should follow irreversible value, not simply technical convenience. Preserve minimum booking, payment or customer-communication capability where it keeps demand from leaving. Offer a controlled alternative and make commitments the degraded operation can honour. Accelerating a full restore may be less valuable than protecting the small moment when the customer decides to wait or walk.

After disruption, reconcile deferred orders separately from permanent loss and observe cohort behaviour over time. Update recovery objectives and economics with real evidence. Revenue resilience improves when management knows which demand can be recaptured, which requires immediate protection and which loss will continue long after systems are green.