SmartyGrants is the incumbent in Australasian grants management for good reason. It has been solving real operational problems for NZ and Australian funders for two decades. Its form builder is mature. The sector knows it. Applicants have logins. Assessors are trained on it. That is a meaningful foundation that deserves a fair accounting in any comparison.
This article provides one. It is written for the grants manager or operations lead who is mid-evaluation — who has either been on SmartyGrants and is questioning fit, or who is evaluating it for the first time alongside other options. If you are earlier in the process and want a broader framework for evaluating any platform, the article on what to look for when you've outgrown your current system covers that ground. This article is specifically the head-to-head.
The conclusion of this comparison is not that one platform is universally better. It is that the choice turns on which phase of the grants lifecycle matters most to your organisation — and being honest about what each platform actually handles.
This comparison is useful if:
It is not particularly useful if:
Any honest comparison starts here.
SmartyGrants' form builder is one of the best in the sector. It supports conditional logic, multi-page forms, file uploads, eligibility screening, and a wide variety of question types. It handles high-volume intake well, and its applicant interface is familiar to a large portion of the NZ and Australian grantseeker community. That familiarity reduces applicant friction and decreases the amount of onboarding support organisations need to provide.
Assessment tools are solid. SmartyGrants supports multi-assessor review, scoring rubrics, and assessor panels. Assessors can access their assigned applications without seeing others' scores, and the interface is intuitive. For organisations whose primary complexity is managing the intake and assessment phase, it works.
Reporting on the pre-award phase — application volumes, round activity, assessor workload, recommendation summaries — is well developed. The platform has been refined over many cycles of real-world use, and the pre-award reporting reflects that.
Support and sector knowledge are also genuine advantages. SmartyGrants has a large customer base across the sector, extensive documentation, and support staff who understand the grants context. For an organisation with limited internal technical capacity, that is meaningful.
The gap in SmartyGrants' coverage appears at the point of approval. Once a funding decision is made, the post-award lifecycle — contracts, milestones, payment management, accountability reporting — moves outside the platform's native capability.
Many SmartyGrants customers manage this through integrations, workarounds, or parallel systems. The most common pattern: applications and assessment live in SmartyGrants; contracts are managed in a document system or email; milestone tracking happens in a spreadsheet; payments are processed by the finance team based on that spreadsheet; accountability reporting is produced manually from a combination of sources.
That is not a failure of individual organisations. It is a structural gap in the platform's design. SmartyGrants was built as an intake and assessment tool, and it is excellent at that. It was not built as an end-to-end grants management system, and it does not behave like one.
The practical consequences:
For organisations whose post-award complexity is low, this gap is manageable. For organisations managing 50+ active grants with multiple tranches, it is the source of most of their administrative overhead.
Tahua was designed as an end-to-end grants management system. The lifecycle it is built to support runs from application intake through eligibility screening, assessment, decision, contract, milestone management, payment release, and final accountability reporting. Each phase is native to the platform, not bolted on.
The structural differences are most visible in the post-award phase.
Milestone management is a first-class feature. Grantees submit evidence through the same portal they used to apply. Programme staff review evidence within the platform and record their findings against specific milestone conditions. Approval is documented against a named reviewer with a timestamp. The milestone status is visible in real time across all active grants.
Payment triggers are connected to milestone approval. When a milestone is approved, a Xero bill is created automatically: grantee details mapped, payment amount populated, grant reference attached. Finance reviews and approves in Xero. No CSV export. No data re-entry. No manual handoff between the grants team and finance.
The audit trail runs end-to-end. Every field-level action on every application — from the initial submission through to the final payment confirmation — is logged against a named user with a timestamp. The log is immutable. That audit architecture is what makes Tahua appropriate for Crown entities and organisations with accountability reporting obligations.
Multi-programme management is native. If your organisation runs multiple grant programmes concurrently, you can see across all of them: open milestones, pending payments, upcoming round deadlines, and total funds under management. That view doesn't require switching between systems or combining spreadsheets.
For NZ government agencies and Crown entities, the comparison has additional dimensions beyond the operational ones.
Data residency is a procurement requirement. Tahua's data is hosted on AWS ap-southeast-2 in Sydney and does not transit through offshore infrastructure. The security architecture aligns with NZISM requirements and uses AES-256 encryption. That is verifiable in writing.
Conflict-of-interest management in Tahua operates at the data access level: when an assessor declares a conflict with a specific application, they are automatically blocked from accessing that application's scoring data and assessment history. The recusal is logged in the audit trail. This is different from a COI policy or a declaration form — it is enforcement at the system level.
Ministerial and parliamentary reporting obligations require that programme activity can be reported accurately and consistently, drawn from a single authoritative source. When the grants lifecycle is managed across multiple systems, that reporting requires manual reconstruction. When it is native to the platform, it is a report run.
Te Māngai Pāho, which administers a $60M+ annual programme, has doubled both the number of funding rounds and the number of contracts under management with the same team size since implementing Tahua. NZ On Air, which has statutory parliamentary reporting obligations, manages its accountability reporting through the platform. Taupō District Council uses the public register feature to meet community accountability obligations.
The government-specific requirements — immutable audit trails, COI enforcement, data residency, OIA readiness — are covered in more detail in the government agency comparison.
Pricing for both platforms is customised based on organisation size, programme structure, and volume. Neither SmartyGrants nor Tahua publishes a standard price list that makes direct comparison straightforward without a conversation.
What can be said about the comparison:
SmartyGrants has a large customer base and a well-established pricing model. Their support infrastructure is substantial, reflecting the scale of their operation.
Tahua's implementation model is train-the-trainer: a typical implementation runs 6 to 8 weeks, with configuration, data migration, and training included. The intent is that your team can manage the platform independently after implementation, not that you become dependent on ongoing professional services.
The total cost of ownership question — which is the right framing for this comparison — requires accounting for the cost of the spreadsheets and workarounds alongside the platform subscription. If post-award management currently requires 60% of your admin time on manual processes (as was the case at Acorn Foundation before they moved to Tahua), that time is part of the cost of the current system even if it doesn't appear on the invoice.
The most useful question is not "which platform has more features?" Both have extensive feature lists. The useful question is: which phase of the grants lifecycle is the source of most of your team's pain right now?
If the answer is intake and assessment — volume management, form complexity, assessor coordination — SmartyGrants is a well-validated solution and switching to Tahua is unlikely to deliver a step change.
If the answer is post-award — tracking milestone status across active grants, connecting approval to payment, managing accountability reporting without manual extraction, producing a clean audit trail for a programme under scrutiny — then SmartyGrants' gap is structural, not a configuration problem.
If the answer is both, or if you are planning programme growth that will push post-award complexity into new territory, then the evaluation question is whether you want to build the post-award layer in addition to the intake and assessment layer, or choose a platform that handles both natively.
Tahua's differentiation is end-to-end. That is most valuable to organisations that have already outgrown intake-only coverage. It is also most valuable to organisations with accountability obligations that run across the full grants lifecycle, not just the pre-award phase.
The 5.0/5.0 rating on Capterra reflects what that end-to-end approach means in practice for teams that have moved to it. But the rating is a data point, not a decision. The decision is the lifecycle question above.
To see the post-award workflow specifically — milestone submission, evidence review, Xero payment creation — book a 30-minute comparison walkthrough. We'll show you the phases that the standard SmartyGrants demonstration doesn't cover.