On-Call ROI: Making the Case for Reliability Investment

On-call burden × engineer cost = real money. The ROI math is straightforward; most teams just never do it.

Why ROI math wins

'On-call sucks' is true and unfunded. The same conversation framed in dollars wins reliability budget every time; the math is simple and most teams just do not do it.

• Vibe loses. 'On-call sucks' does not survive a budget meeting; feature work always sounds more measurable.
• Numbers win. 'On-call costs $X per year and we can save Y%' converts the conversation to ROI.
• Defensible math. The inputs are observable: page count, time per page, engineer cost; the formula is multiplication.
• Solid ground. Once the number exists, the conversation moves from 'is reliability worth it' to 'which reliability work first'.

Four ROI inputs

• 1. Pages per quarter.
• 2. Engineer time per page.
• 3. Engineer fully-loaded cost.
• 4. Estimated reduction.

Spreadsheet pattern

The spreadsheet is the artefact that survives the meeting. Conservative numbers, defensible inputs, one tab per team; this is what funds the work.

• Worked example. 100 pages/quarter × 30 min × $200/hour = $10k/quarter; 50% reduction = $20k/year saved per team.
• Conservative inputs. Use the lower end of every range; aggressive numbers lose credibility on first scrutiny.
• Per-team breakdown. Aggregate the company total but keep the per-team math; teams see their own ROI.
• Hidden costs. Add context-switch cost (1.5x time-per-page) and morale impact qualitatively; do not pretend ROI is the whole story.

Executive engagement

Bringing the math once is not enough. Quarterly ROI reviews keep reliability work in the budget conversation rather than as a one-time pitch.

• Quarterly cadence. Bring the math to engineering leadership every quarter; do not wait for a crisis.
• Trended. Show ROI trend over the last 4 quarters; direction matters more than absolute number.
• Tied to asks. Each presentation includes a concrete ask (headcount, project, tooling); data without ask is decoration.
• Without it. Reliability work loses every prioritisation conversation against features that have measurable revenue stories.

Antipatterns

• No ROI math. Reliability work unfunded.
• Aggressive numbers nobody believes. Lost credibility.
• One-time pitch. Funding fades.

What to do this week

Three moves. (1) Apply this practice to your next on-call rotation. (2) Survey the team after one cycle. (3) Iterate based on feedback; the discipline is the cadence.