# Observability ROI calculator

Estimate what better observability saves in engineering time and revenue, against what it costs.

## How it works

Faster detection and diagnosis shorten every incident. The saving is the hours not spent, by the people involved, plus the revenue not lost while users were affected.

```
saving = hours saved × (people × hourly cost + revenue per hour) − tool cost
```

## Questions

### Where does the speed-up come from?

Mostly from less time spent finding the cause: traces, logs and metrics in one place instead of guessing.

### What isn’t counted?

Fewer incidents overall, less burnout and fewer escalations, which usually make the real return higher.

## Related tools

- [Speed vs revenue calculator](https://powertraces.com/tools/speed-vs-revenue)
- [SLA credit calculator](https://powertraces.com/tools/sla-credits)
- [Funnel drop-off calculator](https://powertraces.com/tools/funnel-drop-off)
- [A/B test significance calculator](https://powertraces.com/tools/ab-test-significance)

[All tools](https://powertraces.com/tools)