Your Technology Isn’t the Problem. Your Decisions Are.

On By admin

What Nonprofits Get Wrong About Tech — and How to Fix It (Especially When You’re Small and Stretched)

Most nonprofits think they have a technology problem.

They don’t. They have a decision problem.

I’ve spent more than three decades in this sector. I started in organizations that tracked donors on 3×5 cards — literal boxes of them, alphabetized, updated by hand. I’ve been pitched by nearly every platform in the market since, including several that no longer exist. The tools have changed. The cycle hasn’t.

The first piece in this series named the systemic failure: vendors who exploit, and nonprofits who participate in their own disadvantage. A third piece takes that argument directly to the vendors. This one belongs to you — and specifically, to the decision problem that no platform upgrade will fix.

A system is purchased with optimism. The demo was strong. The promise was compelling. Then reality arrives: implementation drags, data is messy, staff adoption is uneven, and the system that was supposed to create capacity quietly consumes it. That gap between expectation and readiness is where things break — and for smaller nonprofits, where there is no bench and no margin for wasted effort, the stakes are higher.

If you believe the issue is the tool, you will keep searching for a better one. You will keep getting the same result.

1. Start With the Work, Not the Tool

Small nonprofits do not have the luxury of abstraction.

“We need a CRM” is not a strategy. It’s a shopping list.

Technology will not clarify your work for you. It will expose where your work is unclear. If you cannot answer who owns donor follow-up, how often donors are contacted, or what qualifies as a meaningful interaction — then a CRM will not fix your problem. It will document your confusion more efficiently.

What to do instead:

Before you look at a single platform, write down:

  • The 3 most important fundraising actions you need to do consistently
  • Who is responsible for each
  • What “done well” actually looks like

If you cannot define the work, do not buy the tool.

2. Design for Your Actual Capacity (Not Your Aspirations)

This is where smaller organizations get into trouble. You buy for the organization you want to be — not the one you actually are.

The platform assumes clean data, consistent usage, dedicated ownership, and time for setup and maintenance. You have one person doing development (and three other jobs), limited time, and inconsistent processes. That gap doesn’t close on its own.

What to do instead:

Choose the system your current team can realistically sustain — not the one that looks most impressive. Ask:

  • Can we maintain this weekly with the staff we have?
  • Can we train everyone who needs to use it?
  • Will this reduce work within 90 days — or add to it?

If the answer isn’t clear, it’s not the right fit.

3. Treat Training Like Oxygen, Not Dessert

Small nonprofits skip training because they have to. And then they pay for it anyway.

Without training: one person becomes the “system translator,” everyone else avoids it, data degrades, and reporting becomes unreliable. Training receives roughly 1 percent of nonprofit technology budgets sector-wide. The consequences are entirely predictable.

What to do instead:

Keep it simple and realistic:

  • Schedule two focused training blocks (not one long session)
  • Assign one internal owner who learns it deeply
  • Create 3–5 “this is how we use this” rules

You do not need sophistication. You need consistency.

4. Build the Smallest Possible System That Works

You do not need a fully optimized system. You need a usable one.

Smaller nonprofits win when they track fewer things but track them well, run fewer reports but actually use them, and automate less but follow through more. Complexity does not make you more sophisticated. It makes you more fragile.

What to do instead:

Start with:

  • Clean donor records
  • A simple follow-up cadence
  • One reliable report you actually review monthly

That alone will outperform most underused “advanced” systems.

5. If You’re Stuck With a Bad Vendor, Don’t Panic — Get Strategic

Sometimes you’re already in it. You signed the contract. The system isn’t working. The vendor is unresponsive. And you don’t have the capacity to rip everything out and start over.

Good. Don’t.

Leaving too quickly is often as expensive as choosing poorly in the first place. Instead, stabilize.

Step 1: Narrow the scope

Stop trying to use everything. Identify the 2–3 functions you actually need and focus only on those. You don’t need the system to be great. You need it to be useful.

Step 2: Document the friction

Where is time being lost? What is confusing? What breaks repeatedly? Not emotionally — operationally. This becomes leverage.

Step 3: Re-engage the vendor with specificity

General frustration gets ignored. Specific issues get addressed.

Instead of: “This isn’t working”

Try: “We are unable to generate a reliable monthly donor report without manual correction. We need a resolution within X timeframe.”

Step 4: Decide — optimize or exit

  • If it can be stabilized → optimize what works
  • If it cannot → plan your exit deliberately, not reactively

A bad system is survivable. A reactive organization is not.

6. Stop Confusing Movement With Progress

Buying a new system feels like action. It is not the same as improvement.

You can spend six months implementing a platform and still be doing the same work — with slightly better reporting on why it isn’t improving. Reality is slower, less exciting, and far more dependent on discipline than tools.

The Throughline That Actually Matters

Technology will not save you. It will not fix your strategy. It will not create time. It will not replace ownership.

What it will do is amplify whatever is already there. If your systems are clear, it will strengthen them. If your processes are weak, it will expose them. And if your organization is unwilling to invest the time and effort to make it work, no platform will compensate for that.

What This Looks Like in Practice

For a small nonprofit, getting this right is not about sophistication. It is about clarity and consistency.

Define the work before you buy anything. Choose tools your actual team can sustain, not the ones that look most impressive in a demo. Train your people as though adoption matters — because it does. Simplify the system until it gets used. Stabilize before you replace. And use your leverage with vendors, because you have more of it than you think.

Not easy. Entirely within your control.

You do not need better technology. You need better decisions about technology.

And the organizations that make them — deliberately, consistently, and without illusion — are the ones that stop chasing solutions and start building systems that actually work.