Getting budget approval for grants management software usually requires a business case. That means putting numbers on a problem that mostly shows up as friction — slow processes, duplicated effort, near-misses that didn't quite become incidents.
This guide walks through how to build an honest ROI calculation. The maths isn't complicated. Getting the inputs right is the harder part.
The biggest cost of running grants on spreadsheets isn't software licences — it's people. Specifically, it's the time your grants staff spend on tasks that software would automate or eliminate.
Estimate the following weekly time costs across your whole team:
Be honest. Most teams undercount here because these tasks are so embedded in the routine that they don't feel like overhead. A practical approach is to track one week in detail — have each team member log their spreadsheet-related admin — then annualise.
Multiply total weekly hours by your team's average hourly cost (fully loaded: salary plus leave, overhead, management time). That's your current baseline cost.
Good grants management software typically eliminates or significantly reduces:
Apply these reduction percentages to your baseline cost estimates. The result is your estimated annual time saving in dollar terms.
This is harder to quantify but often material. Consider:
Compliance risk: If your programme is subject to audit, a data integrity failure — incorrect applicant records, undocumented decisions, inconsistent assessment scores — can trigger findings that require remediation work. Even a single audit finding costs staff time to respond to and can damage funder relationships.
Funding errors: If your team has ever paid the wrong amount, paid the wrong grantee, or missed a payment because of a spreadsheet error, estimate what that cost to fix. Include staff time, any financial adjustment, and any relationship repair required.
Near-misses: Even errors that didn't result in an outcome cost time to detect and correct. If you've had spreadsheet incidents in the past 12 months, estimate what each one cost.
Spreadsheet overhead isn't linear. Adding a new programme doesn't add a proportional amount of admin — it adds more, because each new programme adds coordination complexity (more files, more data to reconcile, more stakeholders to update).
Software overhead is much flatter. A system already configured for three programmes can typically absorb a fourth with minimal additional effort.
If your programme portfolio is growing, the ROI of software improves faster than your headcount grows.
A simple ROI statement looks like this:
| Item | Annual cost |
|---|---|
| Current staff time (spreadsheet admin) | $X |
| Error and risk exposure (estimated) | $Y |
| Total current cost | $X + $Y |
| Software licence | -$A |
| Implementation and migration (one-off, amortised) | -$B |
| Training (one-off, amortised) | -$C |
| Net annual saving | $(X+Y) - (A+B+C) |
If the net annual saving is positive within 12–18 months, the business case is straightforward.
Understating current costs: Teams often estimate optimistically. Use a time-tracking exercise to get real numbers.
Ignoring migration costs: There's real work in moving data from spreadsheets to a new system. Build this into your first-year cost estimate.
Overstating vendor savings: Software vendors will give you their ROI estimates. Treat these as upper bounds, not guarantees. Use your own numbers.
Forgetting training time: Your team will need time to learn the new system. This is a short-term cost that doesn't appear in vendor projections.
The strongest business cases combine a clear financial model with one or two concrete examples — incidents or near-misses from your own programme that illustrate the risk you're carrying. Numbers make the case rational; examples make it real for decision-makers who haven't experienced the day-to-day friction.
If you're making this case to a board or governance committee, lead with the risk story and support it with the numbers. If you're making it to a finance function, reverse the order.
This article is part of the complete guide: The Hidden Cost of Managing Grants in Spreadsheets.