Every NGO we talk to is running on the same stack: spreadsheets that only one person understands, WhatsApp groups doing the work of five systems, and a reporting week before every funder deadline where the whole team stops doing the mission to reconstruct what happened to it. The software industry's answer is "buy our platform." Ours is more annoying: it depends, and the honest version of "it depends" fits in one article. This is that article.
First: what problem are you actually solving?
NGO software problems are almost always one of four:
- 01Donor memory — who gave, when, how much, were they thanked, did they get their 80G receipt, will they give again. Lose this and you lose repeat donors, which are the cheapest money in fundraising.
- 02Funder reporting — grant utilization, impact numbers, each funder in their own format. This is where reporting weeks go to die.
- 03Field coordination — volunteers, events, program delivery. Usually lives in WhatsApp; usually unrecoverable three months later.
- 04Being findable and credible — the website, the search results, what a donor sees before deciding you're real.
Name your worst one before reading on. The right answer differs per problem — that's exactly why "one platform for everything" pitches under-deliver.
When to skip software entirely.
Under roughly 200 donors and a single program? A well-structured spreadsheet — one sheet as the ledger, never copies — plus a fixed weekly hour of data hygiene beats any platform. It's ₹0, everyone already knows how to use it, and no login ever expires. The discipline is the system; software won't rescue an undisciplined ledger, it just makes the mess relational.
Skip, too, anything you can't name an owner for. Software without a named human owner dies in six months, quietly, and takes its data with it.
When to buy.
Buy when a proven tool fits 80% of your workflow out of the box. For most NGOs that's two categories: donor CRM and accounting. The 80% rule matters — customizing a bought tool past its natural shape costs more than building, and you still don't own it.
Watch two India-specific traps. First, per-seat pricing in dollars: a US-priced nonprofit CRM that's cheap for a Boston charity is a program budget line for a Bengaluru trust. Second, compliance fit: if the tool can't produce an 80G receipt or map to FCRA reporting categories without gymnastics, it wasn't built for you and won't grow toward you.
When to build custom.
Custom is justified in three situations, and only three:
- AYour program model is genuinely unusual. Off-the-shelf assumes donation-in, program-out. If your operating model doesn't fit that shape, forcing it into a generic CRM deforms either the tool or the program.
- BThe glue is the problem. Donations in one tool, volunteers in another, reports in a third — the cost isn't any tool, it's the re-entry between them. Custom glue (automation between existing tools) is the highest-ROI software most NGOs can commission, and it's usually small.
- CThe maths crosses over. When 2–3 years of SaaS subscriptions exceed the cost of building a system you own outright, and you have (or hire) the capacity to run it — build. Ownership also means your donor data never lives hostage to a price change.
One rule regardless of who builds it: you must own everything. Code, accounts, data, domain. Any builder who keeps the keys — walk away. (This is our own standing rule; it's also how you should filter us.)
The free money almost nobody claims.
Separate from all of the above: Google gives eligible nonprofits up to $10,000 per month in free search advertising through the Ad Grants program. Most Indian NGOs have never applied. If being findable is your worst problem, this — not software — is probably your highest-leverage move this quarter. We'll publish a full India-specific walkthrough here; until then, it's one of the first things we check when an NGO talks to us.
"Software won't rescue an undisciplined ledger. It just makes the mess relational."
The honest decision table.
- →<200 donors, one program → skip: structured spreadsheet + weekly hygiene hour.
- →Growing donor base, standard model → buy a donor CRM that fits 80% and does 80G/FCRA without gymnastics.
- →Tools that don't talk, reporting weeks → build the glue, keep the tools.
- →Unusual program model, or SaaS cost crossing build cost → build custom, own it all.
- →Nobody can find you → website + Ad Grants first, software second.
Who's telling you this.
OIAS is a Bengaluru studio that builds custom software for NGOs — donor systems, field tools, websites, automation. We also run our own company on the same class of systems we sell: agents do our outreach and ops, humans make the calls. That architecture is public →
Which means we make money when you build — and we still wrote the "skip" and "buy" sections above. That's the filter we'd want applied to us.
See what we build for NGOs → · Or just tell us your worst workflow →