Should Your Nonprofit Use AI? An Honest, Practical Guide

Short answer: maybe — and "not yet" is a perfectly good answer that almost nobody will give you honestly.

If you run a nonprofit in Northern New Mexico, the pressure to "adopt AI" is coming from every direction at once — a board member who read an article, a funder who added a line about "innovation," a vendor who found your email, a peer organization that just announced something. Almost all of that pressure pushes one way: toward action, toward a tool, toward spending money you may not need to spend.

This guide pushes the other way — not against AI, but toward a real decision. Below is how we'd think it through with you: where AI actually earns its place in a small nonprofit, where it's premature, and the questions to answer before you commit staff time or budget to any of it.

First, the Honest Framing

AI is not one thing, and "should we use AI" is not one question. For a small nonprofit, it usually breaks into three very different situations:

• A specific, repetitive task is eating staff hours (drafting first passes of donor thank-yous, summarizing meeting notes, reformatting the same report for three funders).
• A capability you lack would genuinely change what you can do (a two-person shop that can't afford a grant writer, a program with no capacity to analyze its own outcome data).
• A vague sense that you should be "doing something with AI" because everyone else seems to be.

The first two are worth examining seriously. The third is not a reason to adopt anything — it's a reason to slow down. Fear of falling behind is the single most expensive motivation in technology, because it makes you buy the answer before you've written down the question.

When AI Genuinely Helps a Small Nonprofit

There are real, unglamorous wins available right now for organizations that are ready for them. The pattern they share: a repetitive, language-heavy task where a human still reviews the output before it goes anywhere.

• Drafting, not deciding. First drafts of donor communications, program descriptions, or social posts — with a person editing every one. AI is a competent intern, not a communications director.
• Summarizing and reformatting. Turning a long meeting transcript into notes, or reshaping one narrative report into the three formats three funders demand. Tedious work, low stakes, easy to check.
• Getting unstuck. Outlining a grant narrative, brainstorming program names, drafting a survey. The value is beating the blank page, not producing the final product.
• Making sense of your own data. Spotting patterns in donor history or program outcomes you don't have the staff hours to analyze by hand — as a prompt for human judgment, never a replacement for it.

Notice what these have in common: a human stays in the loop, the stakes of a mistake are low, and you'd have done the task anyway. That's the safe zone.

When It's Premature (or Just the Wrong Move)

Just as important — and far less often said out loud — are the situations where the honest answer is wait, or don't.

• Your data is a mess. If the spreadsheet underneath a process is inconsistent, out of date, or scattered across five people's inboxes, automating on top of it just produces faster errors. Fix the foundation first. This is the most common "not yet" we see.
• The task carries real trust or privacy weight. Anything involving sensitive donor records, client data, or protected information demands a clear answer to "where does this data go and who can see it" before a tool touches it — not after.
• No one will own it. A tool nobody is responsible for maintaining, checking, and training staff on will be quietly abandoned in a few months. If you don't have the capacity to own it, you don't have the capacity to adopt it.
• You're doing it to look modern. Adopting AI to impress a funder or a board is a cost dressed as a strategy. Funders fund outcomes, not tools.

None of these are permanent verdicts. They're conditions. Change the condition and the answer can change with it.

The Questions to Answer Before You Spend Anything

Before any tool, any subscription, any pilot, work through these with your team. If you can't answer them, that's your signal that the honest next step is clarity, not software.

1. What specific problem are we solving? Name the task and the hours or dollars it currently costs. "Be more efficient" is not an answer.
2. Whose job does this touch, and are they in the room? The person doing the work knows where the real friction is. Deciding for them usually gets it wrong.
3. What data would the tool see, and is that okay? If it involves donor or client information, you need a straight, specific answer on storage, access, and whether it trains someone's model.
4. Who checks the output, and how would we know if it's wrong? If the answer is "no one," stop.
5. What does 'not doing this' actually cost us? Sometimes the cost of inaction is real. Often, honestly, it's zero — and naming that saves you money.
6. Who owns this after the excitement wears off? If there's no owner, there's no adoption.

A nonprofit that can answer these six questions is ready to make a good decision — with or without AI. A nonprofit that can't isn't ready to buy anything, no matter how good the demo looked.

Why You Can Trust a "No"

Most people who will advise you on this get paid more when you say yes — through commissions, reseller margins, or the sale of the tool itself. That's the quiet reason "you should adopt AI" is so easy to hear and so hard to trust.

We built Breakwater Operations to remove that conflict on purpose. We don't resell software, take commissions, or earn anything based on which tool you choose — so when the honest answer is "wait" or "do nothing yet," we can say it plainly. For a small nonprofit, that's the difference between money spent on a shelved platform and money kept in your programs. (More on why that independence matters, and how our engagements work, in our overview of AI consulting in Northern New Mexico.)

We also work this way because the two of us don't agree by default. Barry brings fifty years of operating judgment and a well-earned skepticism of technologies sold as revolutions; Griffin's research is on where AI systems fail and how to make them auditable. A recommendation only reaches you after it survives both. That's the same structured caution we'd want your board to apply.

So — Should Your Nonprofit Use AI?

Here's the honest version:

• If you have a specific, low-stakes, language-heavy task, clean-enough data, and someone to own it — yes, probably, and start small. A narrow pilot with a human checking the output beats a sweeping "AI strategy" every time.
• If your data is messy, the task is sensitive, or no one can own it — not yet. Fix the foundation first. That's not falling behind; it's not wasting money.
• If the only reason is that everyone else seems to be doing it — that's not a reason. Get a clear diagnosis before you spend a thing.

The goal was never to use AI. The goal is to serve your mission with the limited time and money you have. Sometimes AI helps with that. Sometimes the most valuable thing an honest advisor can tell you is that it doesn't — yet.

Where We Come In

If you want a grounded, independent read on your specific situation, that's exactly what our Operational & AI Audit is for: a full review of your workflows, data, and readiness, translated into a clear recommendation — do now, do next, pilot, defer, or avoid — with a plan you can take to your board. Fixed scope, measured in weeks, no product waiting at the end of it.

If you'd rather start smaller, an AI Literacy Workshop gets your whole team and board speaking the same language first — often the best first step of all.

Either way, the goal of a first conversation is the same: you leave with a clearer picture of what's worth doing, what isn't, and what it would take — whether or not you ever hire us.

We work with nonprofits across Northern New Mexico. See our nonprofit page or start a conversation.