Every team has a spreadsheet of subscriptions and no idea which ones earn their keep. This SaaS ROI calculator compares what a tool costs — per seat, per month, plus onboarding — against the hours it saves and any revenue it can be credited with, and returns a year-one figure and a payback period.
"It saves time" is not a business case
Time saved only becomes money when one of three things happens: the hours turn into work you would otherwise have paid someone for, the same team ships more without new hires, or the tool removes a cost outright. If the saved hours just become a slightly calmer Tuesday, the subscription is a convenience purchase, not an investment.
That is why the calculator asks for a blended hourly cost. Take a salary, add 25–35% for benefits, taxes and overheads, divide by actual working hours. A $60,000 role works out around $38 an hour loaded; a $120,000 engineer closer to $75. Using a salary divided by 2,080 hours understates the real cost and makes every tool look good.
What goes in each field
- Price per seat per month. The number on the pricing page, at the tier you actually need. Annual plans usually discount 15–20%, so divide the yearly figure by twelve.
- Seats. Count the people who will genuinely use it, then add 10%. Unused seats are the single most common way these budgets leak.
- Setup and training. Migration, onboarding, integrations, and the week where nobody is as fast as they were before.
- Hours saved per seat per month. Be conservative. A tool that saves an hour a day is saving 20 hours a month — almost always an exaggeration. Start at 3–5 hours and see if the answer still works.
- Extra revenue. Only count revenue you could defend in a meeting. "Better reporting might win us deals" is not a number.
A worked example
Eight seats at $45 a month is $3,600 a year, plus $600 of onboarding: $4,200. If each seat saves 4 hours a month at a $50 blended rate, that is $1,600 a month of value, or $19,200 a year. Year one net gain is $15,000 and the setup pays for itself in well under two months.
Now change one input. Suppose the team only saves one hour a month per seat. Monthly value falls to $400, the tool costs $360 a month, and the whole case collapses — a $40 a month saving is not worth a migration project. The difference between a great tool and a bad one is often just the number of hours people actually use it.
The costs people leave out
| Cost | Why it is easy to miss |
|---|---|
| Integration work | Someone has to connect it to your data, usually a developer, usually for a week |
| Admin and renewal | Permissions, offboarding, invoices, someone chasing the renewal date |
| Seat sprawl | Seats get bought for a project and never removed |
| Switching cost | Leaving later means exporting, retraining, migrating again |
| Tool overlap | The thing often duplicates a feature you already pay for elsewhere |
A practical rule: if the year-one ROI is under 50% after including setup, the case is too thin to survive a busy quarter. Under 0%, you either cut seats or cut the tool.
When a subscription clearly earns its keep
Tools that earn their place tend to share a shape: they replace work someone was already being paid to do, they are used daily by the whole team, and the alternative is hiring. Analytics, billing, support desks and CI minutes usually qualify. Design tools with three active seats out of twelve usually do not.
Buy versus build is the other comparison worth doing. A $45 a month tool costs $540 a year. Building the same thing internally costs a few weeks of engineering time, which at $75 an hour is $6,000 or more, plus maintenance forever. In almost every case, buying wins unless the tool is core to how you differentiate.
Run the numbers with your real seat count and a deliberately pessimistic hours-saved estimate. If it still clears, you have an answer you can defend at the next budget review.