If you have ever watched a promising AI automation proposal die in a budget meeting, you know the feeling. A general manager walks in with a slide claiming the new assistant saves the team six hours a week. The owner asks one simple question: "Six hours of whose time, and what does that cost me?" The GM has no answer. The budget is declined in four minutes. The product was fine. The case was the problem. This is a common failure mode in tech procurement, and it is entirely preventable.

Why "It Saves Time" Gets Rejected

Owners and CFOs do not fund time; they fund cost avoidance or revenue protection. "Saves time" is a feeling. "Recovers 26 hours of front-desk labor a month at a stated $22 an hour, which is $572, against a tool cost of $180" is a claim they can check. The moment you attach a rate and a count, the conversation stops being about belief and becomes arithmetic. That is what you want, because arithmetic can be argued and belief cannot. Furthermore, decision-makers have been burned before by tools that promised savings but became maintenance nightmares. Your case must not sound like a promise; it must sound like a conservative estimate with its assumptions written down where the skeptic can attack them.

The Four Metrics That Survive Scrutiny

To build a defensible case, focus on four specific numbers. First, calculate Hours Recovered by multiplying weekly hours saved by 4.33 weeks/month, based on a one-week time log, not a guess. Second, determine Labor Value by multiplying those hours by the fully loaded hourly rate (wage + tax + benefits), not just the base wage. Third, measure Response-Time Change by comparing the median first-reply time before and after implementation. Fourth, compute Cost Per Resolved Conversation by dividing the monthly tool cost by the number of resolved conversations. Two supporting figures, leads captured and payback period, should appear on the page but never in the headline.

Hard Savings vs. Soft Savings

This distinction is where most budget cases die. Hard savings are money that leaves or does not leave an account you can name, such as overtime you stop paying or a contractor shift you do not renew. Soft savings are real but unbanked, like "the team could focus on higher-value work" or "people are less stressed." None of these show up as a lower number anywhere, and the first skeptic in the room will use them to discredit the solid parts of your case. Keep soft savings in a clearly labeled footnote. If you cannot point to a payroll line, an invoice, or a budget row that changes, the saving is soft. A smaller honest number gets approved far more often than a large one that falls apart under one question.

The One-Page Report Format

Hand over one page. Not a deck, not a spreadsheet dump. This template includes sections for the specific problem, the single workflow the automation takes over, and the total cost. Crucially, it includes a row for "What we are not claiming," which lists soft savings and unmodeled revenue. This last row is the one most people leave out and the one that earns trust. Telling the approver what you are not counting signals that the rest is solid. Fill every bracket or delete the line; a blank bracket is a question the approver will ask out loud.

Key Takeaways

  • Run a one-week time log on the workflow before claiming any hours saved.
  • Pull the fully loaded hourly rate (wage + tax + benefits) for accurate labor value calculation.
  • Separate hard savings (visible budget changes) from soft savings (unbanked productivity) in your report.
  • Include a 'What we are not claiming' section to build trust with skeptical stakeholders.

The Bottom Line

Stop trying to impress executives with vague promises of efficiency. Build your case on four defensible arithmetic metrics, label your assumptions, and keep your soft savings in the footnotes. A smaller, honest number that survives scrutiny beats a large, fluffy claim every single time.