How to calculate the ROI of admin work.
Automation ROI starts with the work people repeat every week. Count the hours, the delays, the revenue leaks, and the software workarounds before deciding what to build.
Start with weekly hours
Pick one workflow and estimate how many people touch it, how often it happens, and how long each step takes. The number does not need to be perfect. It needs to be honest enough to compare options.
If a task takes 20 minutes and happens 30 times a week, that is 10 hours before you count mistakes, delays, or context switching.
Add revenue and delay cost
Some workflows matter because they save time. Others matter because they protect revenue: missed calls, slow lead follow-up, late quotes, delayed collections, and customer status gaps.
A good first build has a visible business reason, not just a prettier process.
Compare against the first build
A fixed-scope build should be judged against one narrow workflow. If the first system saves hours, protects revenue, or replaces a tool workaround, the payback becomes easier to understand.
If the workflow is low-frequency or impossible to measure, it should usually wait.