Speaking Money, Not Nines
If you tell an executive "Availability dropped to 99.8%," they might shrug. Percentages are abstract. If you tell them "We have $50,000 of Revenue-at-Risk right now," they will act immediately — and give you the budget you need to fix it.
Revenue-at-Risk (RaR) is a real-time metric that estimates how much money the business is losing right now based on the current deviation from expected order volume. It translates a technical incident into a financial impact that every stakeholder understands.
The Formula
Revenue-at-Risk = Avg Order Value × (Expected Orders/min − Actual Orders/min)
Example:
- Normal rate: 100 orders/min
- Average order value: $50
- Current rate during incident: 20 orders/min
- Revenue-at-Risk = $50 × (100 − 20) = $4,000/min
After 15 minutes of this incident, you've lost an estimated $60,000 in revenue. Displaying this number on a shared dashboard — visible to engineering, product, and leadership simultaneously — creates a shared sense of urgency and eliminates the "how bad is it really?" conversation during an incident.
Implementing Revenue-at-Risk in Prometheus
If you're using Prometheus, you can derive this metric from your existing instrumentation: expose a simple counter of completed orders from your application, then build on it with recording rules — one computing orders-per-minute as a rate over a trailing window, a second computing revenue-at-risk as the deviation between that rate and a 7-day same-hour baseline multiplied by average order value, and an alert rule that fires once revenue-at-risk sustains above a dollar threshold for a few minutes, with a templated description that interpolates the live dollar figure into the notification.
The Organizational Impact
Beyond incident response, Revenue-at-Risk changes how engineering work is prioritized. When you can show that a recurring bug costs $12,000/month in lost revenue, it becomes a P1 fix — not a backlog item. Business observability gives engineering teams the language to advocate for reliability work in terms leadership understands.