Quantifying Downtime Risk Exposure

The problem this solves

The budget is frozen, and only projects with a payback under six months get approved. Your solution reduces outages, but the buyer’s case says “improves reliability,” and reliability has no line in the budget. Without a number for downtime risk exposure, your project competes against revenue work and loses.

Executives do not fund the absence of a problem. They fund the avoided cost of a problem they can picture. Your job as a Sales Engineer is to make that cost visible, per hour, in a form a finance lead can challenge line by line.

Build the hourly cost from three layers

Unplanned downtime costs more than lost transactions. Estimate each layer separately so the customer can accept some and dispute others without throwing out the whole model.

• Direct loss: revenue or throughput that stops while the service is down, taken from the customer’s own hourly averages.
• Contractual penalty: service-level credits and refunds owed under existing agreements. Ask for the contract clauses, not a guess.
• Reputational and recovery cost: support surge, engineer overtime, churn risk on affected accounts. Mark this layer clearly as the softest.

Present the layers in that order, firmest first. A buyer who agrees to the first two has already agreed to most of the case.

Use their incidents, not industry averages

Generic outage statistics invite the answer “we are not that company.” Instead, ask for the last three incident reports: duration, systems affected, who was pulled in, what was refunded. Three real incidents give you an average duration and a frequency, and both come from the customer. Multiply frequency by duration by hourly cost, and you have an annual downtime risk exposure built entirely from their data.

Show the range and the reduction you can defend

Give a low, expected and high case. Then claim only the reduction your evidence supports, such as a proof of value that shows failover completing in minutes rather than hours. If you cannot show a reduction in their environment, say what you measured and what remains an assumption. Overclaiming here is the fastest way to lose a skeptical finance reviewer.

What this means for the SE

Ask who owns the incident log and the SLA contracts before the readout, and get them in the room. When operations confirms the hourly figure, the number stops being yours and becomes theirs.

Decision and check

Take the case to the economic buyer only when three tests pass: every layer cites a customer source, the low case still beats the six-month payback line, and an operations owner has signed off on the hourly figure. If the low case fails, narrow the scope to the systems with the worst downtime risk exposure and rebuild the model there.

This is part of the 80% of Solution Engineering that stays constant whatever the product. The SE Ignite curriculum teaches these mechanics for free, so you can practice them before your next deal.