Buy, configure or build grant management software
Most grant software decisions are framed as a choice between products. The bigger choice comes first: do you buy a specialist product, configure a platform you already run, or build from code? Each is a different bet about who makes the design decisions and who carries the work after go-live. This deep dive sets out the costs, timelines and trade-offs, with a worked three-year comparison. For the tool-by-tool comparison and the 2-minute decision tool, see our grant management software buyer’s guide.
Three bets, not three price points
Buy a specialist product when your process looks like most funders’: open call, review, award, report. You get years of other foundations’ lessons built in, a vendor responsible for security and upgrades, and a peer community. You also adopt the product’s model. If your funding moves in stages tied to outcomes, or one programme is co-funded by four companies with different reporting years, you will spend the contract working around the product.
Configure a platform (Zoho Creator, Zoho CRM, Salesforce) when your workflow is distinctive, when grants must connect to programme data and accounting you already run, or when local compliance isn’t covered by US-built products. You get a system shaped around your decisions and data you control. Someone has to make those decisions, and the system is only as good as the scoping.
Build from code only when you have an in-house engineering team, a long horizon and needs no platform meets. The market has voted: TAG found custom systems fell to 3% of foundations in its 2024 survey. We write custom code ourselves when nothing else fits, but for grants it is rarely the first answer.
What each path costs
Total cost has three parts: licences, implementation, and your own team’s time. The third is the one budgets forget.
| Path | Year-one licence (USD) | Implementation | Ongoing |
|---|---|---|---|
| Specialist product, small funder | ~$5,000–$35,000 on Tech Impact's 2024 estimates | From $0 (self-serve) to $10,000–$50,000+ for guided onboarding | Annual subscription; add-ons as you grow |
| Specialist product, mid-size or large funder | ~$17,000 to $300,000+ | Often a fixed onboarding package plus extra hours | Subscription usually scales with annual giving |
| Grant-seeking tool for nonprofits | $3,588–$11,988 (Instrumentl, annual billing) | Self-serve | Subscription |
| Configured platform (e.g. Zoho Creator) | Example: 10 internal users on Professional = $2,400 (Zoho Creator pricing), plus portal users for external applicants or grantees; nonprofit pricing may apply via Zoho for Nonprofits | Partner-led scoping and staged build | Licences, a support plan, and an internal owner |
| Custom code | Hosting only | Highest of the four; you are funding a product team | Maintenance, security and upgrades are yours |
A configured platform’s licence line looks small, and it is, but design decisions and admin effort move onto your side of the table. A specialist product’s licence looks large, and part of that price is the decisions the vendor has already made for you.
Worked example: a small foundation, three years
Take a foundation making about 60 grants a year with 10 staff users. Licence figures come from the sources above; implementation and staff time are placeholders the buyer fills in.
| Line | Specialist product (Foundant Standard, listed) | Configured Zoho Creator (10 users, Professional) |
|---|---|---|
| Licence, year 1–3 | $9,900 × 3 = $29,700 (Capterra) | $2,400 × 3 = $7,200, plus portal users |
| Implementation | Separate vendor fee [quote] | Partner build [quote] |
| Internal admin time | Low: vendor-defined workflow | Higher: an internal owner for rules and changes |
| Change requests | Wait for the product roadmap or work around | Configure yourself or with a partner |
| Exit | Export terms per contract | You own the data model |
The licence gap is real, about $22,500 over three years in this example. Whether it survives implementation and staff time depends on how distinctive your process is. If it is standard, the product’s lower admin burden often wins. If it isn’t, the workarounds cost more than the licence gap.
How long each path takes
| Path | Typical time to first use | What drives it |
|---|---|---|
| Specialist product, standard setup | 4–6 weeks (Fluxx Quick Start) to 2–4 months (Bonterra's marketed range, per Plinth, a competing vendor) | Form and workflow setup, data migration, reviewer training |
| Configured system with EdZola | Most launch in 3–4 months: 1–2 week diagnosis, 6–16 weeks of staged build with screens every 2–4 weeks, then 30–60 days of support after go-live | Scope clarity, accounting integration, migration of past grants |
| Custom code | Longer than either, and never finished | Team capacity, testing, ongoing change |
The migration trap
The step that slips in every path is migration. Past grants carry years of inconsistent field use. On a scholarship programme we supported, field-level standardisation for the migration ran over three months of back-and-forth before the history could be trusted. Decide early how many years of history you need, and which fields must come across clean. Our scholarship disbursement and renewal workflow shows why renewal history is usually the part worth migrating carefully.
When EdZola is not the right choice
If you are a US or UK foundation with a standard grant cycle, a small team and no appetite for owning configuration, buy a product. Foundant’s support scores and Fluxx’s Quick Start exist for that buyer. If you are a nonprofit with four grants a year, a well-kept spreadsheet, a shared calendar and your accounting system’s cost centres will do the job. Come back when the spreadsheet starts lying to you.
If you do configure, scope grants as part of your wider programme data system, not as a standalone app. Our guide to a nonprofit MIS explains how the pieces fit. Funders should also write the portal requirements before choosing a path; see what a grantee portal should include.
Bring us one grant
Bring one grant that shows what’s wrong with the current setup. In a free 30-minute walkthrough we’ll trace it through your process and tell you plainly whether to buy, configure or wait, and, if a product fits better, which kind.