When you ask for budget for a new tool, the question you will get is whether it is worth the money. For most business software the honest answer depends on one thing: how much time it saves, and what that time is worth.
The basic formula
Annual value is hours saved per week, times the value of an hour, times 52 weeks, times the number of people using it. Subtract the annual cost to get net value. Divide net value by the cost to get ROI.
Value of time saved
5 h × $50 × 52 wk × 1 userequals$13,000
Net value
$13,000 − $2,400equals$10,600
ROI
$10,600 ÷ $2,400equals442%
At that rate the tool pays for itself in a little over two months.
Small savings across a team add up
A tool that saves each person only an hour a week can still be an easy decision once a whole team uses it. Here is a $6,000/year tool used by 8 people whose time is valued at $60 an hour:
Value of time saved
1 h × $60 × 52 wk × 8 usersequals$24,960
Net value
$24,960 − $6,000equals$18,960
ROI
$18,960 ÷ $6,000equals316%
Putting a value on an hour
Salary divided by hours worked is a start, but it understates the real cost of an employee's time. Benefits, payroll taxes, equipment and office costs are commonly estimated to add 20 to 30% on top of salary. That fuller figure is called a loaded rate.
Keeping the estimate honest
ROI estimates are only as good as the hours-saved figure, and that is the number most likely to be optimistic.
- Time one real task before and after, rather than guessing.
- Assume not everyone will use the tool fully, especially in the first few months.
- Count the setup and training time as a cost.
- Run a pessimistic version too. If the tool still pays for itself at half the savings you expect, it is a safe decision.
Saved time only has value if it goes into other useful work. It is worth saying what the team will do with the hours, because that is usually what makes the case convincing.
A worked example
A team of 20 is considering a tool that costs $50 per user a month, $12,000 a year. Trials suggest it saves each person about 2 hours a week. Over 48 working weeks that is 2 × 48 × 20 = 1,920 hours a year. At a loaded cost of $50 an hour (salary plus taxes and overheads), the time is worth $96,000. ROI = ($96,000 − $12,000) ÷ $12,000 = 700%.
That figure looks spectacular, which is exactly why it needs testing. If people really save only half an hour a week, and half of that time is lost to other interruptions rather than turned into useful work, the value falls to $12,000 and the ROI to zero. The difference between a great investment and a wasted one is entirely in the assumptions.
Costs that are easy to leave out
- Setup and migration time: moving data, configuring the tool, connecting integrations.
- Training: every person's first few weeks at lower productivity.
- Admin: someone has to manage users, permissions and renewals.
- Tools it does not replace: if the old tool has to stay for a while, count both.
- Price increases at renewal, especially after an introductory discount.
Payback period is often the better question
ROI answers "is it worth it?" Payback period answers "how soon do we get our money back?", which is often what a small business really needs to know. Divide the total first-year cost by the monthly benefit. A tool costing $12,000 a year that creates $3,000 of value a month pays back in four months. If payback is longer than the contract, treat the decision with extra caution.
Measure after you buy
Write down the expected saving before you buy, then check it after three months: time spent on the task, errors, turnaround times, or whatever the tool was meant to improve. If the benefit has not appeared, find out why before renewal. This habit also makes future ROI estimates more realistic.
Tip: Per-seat pricing grows with your team. Check what the tool will cost at next year's headcount, not just today's.
Questions people ask
- What ROI does a $2,400 tool saving 5 hours a week give?
- In our calculator, at $50 an hour, about 442% with payback in about 2.2 months. At 1 hour a week, it falls to about 8%.
- Should I use salary or loaded cost for time savings?
- Loaded cost, which includes taxes, benefits and overheads, but only count time that genuinely turns into useful work.
- How long should software take to pay back?
- Ideally well within the contract length. If payback is longer than the commitment, be cautious.
- How do I calculate software ROI?
- Hours saved per week × value of an hour × 52 × number of users gives annual value. Subtract the annual cost for net value, then divide net value by the cost.
- What hourly value should I use for staff time?
- A loaded rate: salary per hour plus the 20% to 30% that benefits, payroll taxes, equipment and office costs commonly add.
- How do I keep an ROI estimate realistic?
- Time a real task before and after, assume partial adoption, count setup and training time, and check that the tool still pays off at half the expected savings.
- What is a software payback period?
- Total cost ÷ monthly benefit. A $12,000-a-year tool creating $3,000 of value a month pays back in four months.