IT downtime is a period when a system, network, or application is unavailable or cannot support the work your business needs to complete. The cost depends on which processes stop, how long the interruption lasts, and how much work or revenue cannot be recovered afterward.
For a small business, the impact includes staff time, missed sales, emergency support, and the work needed to catch up. Use the calculator below to estimate a specific outage rather than applying a broad industry average to every minute your systems are offline.
For organizations in Oklahoma and North Texas, the estimate also provides a starting point for discussing support expectations and recovery priorities with a managed IT services provider.
Downtime includes complete outages and interruptions that stop a particular business process. An unavailable scheduling system, failed office internet connection, or inaccessible customer database can affect different teams in different ways.
Planned downtime is scheduled for work such as updates or migrations. Unplanned downtime follows an unexpected failure or incident. Both should be evaluated according to business impact. During a partial outage, some employees can keep working, and some transactions can be completed later.
Recent research shows the scale of disruption, but the figures need context:
Use these findings to support recovery planning. Calculate your own exposure from the systems, staffing, and sales affected by a realistic outage.
Estimate how much productive work is unavailable, including partial disruption. If employees can switch to other tasks, account for that. A payroll-based estimate indicates labor capacity affected; it is not necessarily an additional cash expense.
Separate canceled transactions from delayed ones. A missed sale and a postponed invoice do not have the same financial effect. For permanently lost sales, consider the contribution left after variable costs you avoid when the sale does not happen.
Include emergency support, necessary repairs, extra labor, documented service penalties, and other incident-related expenses. Avoid adding amounts already included elsewhere, such as the same overtime in two categories.
Record missed deadlines, customer complaints, rework, and backlogs. Longer-term reputation or customer-retention effects are harder to measure; track evidence rather than assigning an unsupported dollar amount.
The calculator separates estimated financial impact from affected labor capacity:
Estimated financial impact = lost contribution + additional incident expenses.
Lost contribution = affected sales per hour × outage hours × permanently lost share × contribution margin.
Labor capacity affected = affected employees × loaded hourly cost × outage hours × unavailable productivity share.
For contribution margin, use the share of revenue left after variable costs avoided when the sale does not occur. Review the assumptions with your finance team. Keep labor capacity separate from the financial total to reduce double counting.
How to calculate downtime impact
Assume the affected process normally supports $500 in sales per hour. An outage lasts three hours, 40% of those sales are permanently lost, the contribution margin is 60%, and additional incident expenses total $600.
Separately, 10 employees at a loaded cost of $30 per hour, unable to do productive work for three hours, represent $900 in affected labor capacity. That figure is not automatically added to the $960 estimate. These are illustrative assumptions, not Standley customer results or industry averages.
Repeat the calculation for a shorter and a longer outage. Use the results to compare recovery priorities, while recording excluded costs and uncertain assumptions.
Common causes include equipment failures, internet and power interruptions, third-party application outages, software changes, misconfiguration, and cyber incidents. Identify which dependencies support your critical work rather than assuming every outage starts with your own server.
For example, a field-service business could lose access to scheduling when its internet connection fails. Staff might keep completing some work by phone while other appointments are delayed. Its estimate should reflect those workarounds and distinguish delayed bookings from sales lost permanently. This is an illustrative scenario, not a customer case study.
Define a recovery time objective (RTO), the target time to restore a process, and a recovery point objective (RPO), the amount of data loss the business can tolerate expressed as time. Objectives guide planning; they should be tested against the available systems and agreement rather than treated as automatic guarantees.
Ask which systems are covered, what monitoring and support hours apply, who owns incident response, and how third-party outages are coordinated. Review backup responsibilities, restoration testing, escalation, and reporting in the proposed agreement.
Our managed service provider agreement guide explains the terms to review. Confirm the response process separately from any restoration or resolution target. No provider can prevent every interruption.
There is no single cost that fits every small business. Estimate the systems and people affected, outage duration, sales permanently lost, contribution margin, and additional incident expenses. Use published research as context, not as a fixed per-minute rate for your company.
Estimate permanently lost sales as affected sales per hour multiplied by outage hours and the unrecovered share. Multiply by contribution margin, then add additional incident expenses. Assess labor capacity separately to avoid counting the same impact twice.
Not automatically. If the transaction will be completed later, it is delayed revenue rather than a permanently lost sale. Record related cash-flow or catch-up costs separately and include only supported additional expenses in the estimate.
No provider can eliminate every outage, including power, internet, and third-party service disruptions. Evaluate monitoring, maintenance, escalation, backup testing, and recovery responsibilities against your business requirements and the proposed agreement.
A recovery time objective (RTO) is the target time for restoring a system or process. A recovery point objective (RPO) defines the amount of data loss the business is prepared to tolerate, expressed as time. Review both for each critical system and validate them through testing.
Standley Systems has supported business technology needs since 1934, with local offices and technicians across Oklahoma and North Texas. Bring your outage assumptions, critical applications, and recovery questions to a conversation about your support needs.
Explore managed IT services and request a consultation to discuss service scope and expectations for your organization.