RKAZNBefore you automate anything, you should be able to answer one question in plain numbers: what does this actually save, and what does it actually cost? Most businesses skip this step and go straight to "AI can probably help here." That's how automation budgets get wasted on the wrong processes.
The math people usually get wrong
The typical calculation is: hours saved per week × hourly cost × 52. That number is almost always too optimistic, because it assumes the process runs perfectly, every time, with zero exceptions. Real processes have exceptions, and exceptions need a human — which means the real time saved is lower than the theoretical maximum.
Four numbers to actually collect first
- Volume — how many times this process actually runs per week, not per year averaged out
- Current cost per instance — real fully-loaded time, not just the 'quick part' someone remembers
- Exception rate — what % of cases need a human to step in, and how long that takes
- One-time build cost + ongoing monitoring cost — automation isn't free to maintain
The break-even question that actually matters
Instead of asking "how much time will this save," ask: "at what volume does this pay for itself, and are we actually at that volume?" A process that runs 5 times a week almost never justifies a custom build. A process that runs 500 times a week almost always does — even with a fairly high exception rate.
If you can't say what volume makes this worth it, you're not ready to automate it yet — you're ready to automate a guess.
Run your own numbers
We built a free ROI calculator that walks through exactly this — volume, current cost, and a realistic (not inflated) automation estimate. No email required. If the numbers come back close, that's usually a sign the process is worth a proper look; if you want that look, Business Process Automation is where we'd start.