Selecting grants management software is one of the most consequential operational decisions a foundation makes. The right system streamlines administration, improves grantee experience, and provides the data foundations need to understand their impact. The wrong system creates friction at every stage of the grant lifecycle — and switching later is expensive and disruptive.
This guide provides a practical framework for foundations evaluating grants management software: what features matter, how to structure a comparison, and how to avoid the mistakes organisations commonly make in software selection.
The grants management software market has matured significantly over the past decade. There are now dozens of systems ranging from spreadsheet-based tools to sophisticated cloud platforms. The options available in New Zealand and globally include purpose-built grants management platforms, CRM systems with grants modules, and government-sector grant portals.
The difficulty is that different systems serve different contexts well:
- A large government grants agency with high application volumes and complex compliance requirements needs different features than a small family foundation with 20 annual grants
- A foundation that makes large research grants needs different workflow to one making community grants
- A grantmaker focused on equity-centred grantmaking needs flexibility that standardised systems may not provide
There's no universal right answer — only the right answer for your context.
The most common mistake in software selection is starting with a vendor demonstration rather than a requirements analysis. Every vendor shows their system at its best; without knowing what you need, you can't tell whether the demo reflects your reality.
Start with:
Current process mapping: Document your current grant lifecycle — how does an application come in, how is it assessed, how is the grant made, how are reports received and reviewed? Understanding your current process identifies what the software needs to support.
Pain points: What's most frustrating about your current system (whether it's a spreadsheet, an old system, or a manual process)? These pain points are the problems the new system must solve.
Volume and complexity: How many applications do you receive annually? How many active grants do you manage? How many team members use the system? Higher volume and complexity justify more sophisticated (and usually more expensive) systems.
Grantee experience requirements: What do you want the applicant and grantee experience to be? Some platforms offer sophisticated applicant portals; others are primarily administrative tools.
Reporting requirements: What reports do you need from the system — to your board, to donors, to government? Systems vary significantly in reporting flexibility.
Integration requirements: What other systems does grants management need to integrate with — accounting systems, CRM, email, document management?
Application management: Online application intake, configurable application forms, document upload, eligibility screening, application tracking. Evaluate: how flexible is form design? Can you create different forms for different grant types? Is the applicant experience intuitive?
Assessment and review: Reviewer assignment, scoring rubrics, review workflows, panel management, deliberation documentation. Evaluate: can multiple reviewers assess independently? Can you weight criteria? Is the review interface clean for assessors?
Grant management: Grant award processing, payment scheduling, milestone tracking, grant condition management, amendment handling. Evaluate: how easily can you track and manage the full lifecycle of an active grant?
Reporting and compliance: Grantee progress and financial reports, report review workflows, acquittal processing. Evaluate: can grantees submit reports directly in the system? Is there automated reminders for late reports?
Communication: Email communication with applicants and grantees, communication history tracking, template management. Evaluate: is all communication tracked? Can you personalise communications from within the system?
Analytics and reporting: Dashboard analytics, portfolio reporting, custom report generation, data export. Evaluate: can you get the data you need in formats that work for your reporting?
User management and permissions: Staff roles and permissions, assessor access management, grantee portal access. Evaluate: is the permission system flexible enough for your team structure?
Implementation: How long does implementation take? What does it involve? Who is responsible for data migration? What training is included?
Support: What are the support channels (email, phone, live chat)? What are the response time commitments? What does after-hours support look like?
Configurability: How much can we configure the system without technical skills? What requires vendor involvement to change?
Data ownership: Who owns the data? Can we export all our data at any time? What happens to our data if we cancel the subscription?
New Zealand specific: Does the system support NZD? Does it integrate with New Zealand charities register? Does it accommodate GST in grant accounting? Is there New Zealand support coverage?
Security: Where is data stored? What are the security certifications? How are backups managed?
Roadmap: What's coming in the next 12 months? How are feature requests handled? How often are major updates released?
References: Can we speak to three current customers with similar profiles to ours?
Over-specifying requirements: Requiring every feature of the current system (including workarounds that exist only because of system limitations) rather than identifying what the new system needs to achieve.
Insufficient grantee perspective: Evaluating systems primarily from the funder's perspective without adequately testing the applicant and grantee experience.
Ignoring total cost of ownership: Focusing on the subscription price without considering implementation costs, training time, ongoing maintenance, and the cost of switching if it doesn't work out.
Rushing the demo: Showing the vendor demo to the CEO for 30 minutes without involving the programme and grants staff who will use the system daily.
Not testing with real data: Theoretical evaluations miss the problems that emerge when you try to enter your actual grants, your actual processes, and your actual reporting requirements.
Confusing price with value: The cheapest system is rarely the best value if it doesn't support your processes well and requires significant workarounds.
Most foundation boards want to understand the value of a software investment before approving it:
Tahua is purpose-built grants management software for community foundations and philanthropic organisations — designed for the New Zealand and Australasian context, with intuitive grantee portals, configurable assessment workflows, and the analytics that help foundations understand their portfolio impact.