Reflections from host Sarah Olivieri ...

Why Your Nonprofit Can't Afford to Outsource Its Own Capacity

There is a moment that arrives in almost every mission-driven organization. You build something that works. A program, a platform, a process. It depends on one person, one vendor, one funder, one system that only one set of hands understands. And for a while, that works just fine.

Then that one thing disappears. The developer leaves. The funder pulls out. The grant ends. The person who knew how everything fit together walks out the door. And suddenly the thing you built is not just struggling. It is locked. You cannot get in. You cannot fix it. You cannot move.

This is not a story about bad luck. When an organization's capacity lives entirely outside its own walls, a single disruption becomes an existential threat. That is a question of nonprofit technology capacity, and it is structural. When the systems your mission depends on are owned by someone else, you are not running an organization. You are renting one.

The Source of This Thinking

I've been thinking a lot about this lately. I recently had a conversation about exactly this with Chris Conlee, and it sharpened how I think about what actually creates staying power in nonprofits. Not because the ideas were new, but because they explained why certain approaches hold up over time.

Outsourced Capacity Is a Structural Vulnerability

Here is the pattern I keep seeing. A heart-first leader has a real idea. They do not have the technical skill to build it, so they hire it out. They find a vendor, sign a contract, and hand over the keys. The thing gets built. It even works.

What they have actually done is create a dependency they cannot see. The code, the logins, the design files, the institutional knowledge of how it all connects, all of it lives somewhere else. As long as the relationship holds, nobody notices the risk. The risk is invisible right up until the moment it is the only thing that matters.

This framing adds risk because it hides the cost. You feel like you saved money by not building in-house. What you actually did was move the most fragile part of your organization outside your own control and hope nothing ever happened to it.

When the disruption comes, and it always comes eventually, the bill arrives all at once. You are locked out of your own work. You have already spent more than you raised. And you are facing a choice between starting over and shutting down.

Heart-First Is Not the Problem

Let me say something clearly, because heart-first leaders carry too much shame about this already. The nonprofit sector is full of people who led with their hearts and figured out the systems later. Very few of them woke up one day and decided to become a nonprofit CEO and then went to school for it. They saw a need. They moved toward it. The leadership skills and the systems came second.

There is nothing wrong with that order. The mission should come first. The trouble is what happens when the heart builds something real and then never circles back to build the foundation underneath it.

You cannot run a complex business model on heart alone forever. At some point the moving parts multiply, the dependencies stack up, and the gap between what you care about and what you can actually control becomes the thing that breaks you. The answer is not to care less. It is to build the plumbing first, so the thing you care about has something solid to stand on.

The Single Point of Failure Is Always a Design Choice

When you rely on one developer, one platform, one funder, you have made a design choice, whether you meant to or not. You have decided that the survival of your organization rests on something you do not control.

Most leaders never decide this consciously. It happens by default. You build the fastest way you can with the resources you have, and the fastest way almost always means leaning hard on a single source. Speed feels like progress. The hidden cost is concentration. The same logic shows up in budgets, which is why I think of underfunding as a design choice rather than an accident.

The work of leadership is to look around the corner before the corner arrives. Where is your organization dangerously concentrated right now? One major donor who covers half your budget. One staff member who is the only one who knows how payroll runs. One vendor who holds the keys to the system your whole program depends on. These are the questions that separate organizations that last from organizations that get one bad season and disappear.

The Mechanism, Named Plainly

One line from that conversation has stayed with me:

"It's not that you need to use AI to stay ahead, because it's now sort of expected. If you're not using AI, you're just by default behind."

What I appreciate about this framing is that it explains the mechanism. The ground has shifted. The tools that used to require a hired specialist and a five-figure budget are now within reach of a determined leader with the right guardrails. The barrier that justified outsourcing your capacity is mostly gone. When you keep outsourcing anyway, you are paying the old price for a problem that no longer requires it.

Owning Your Capacity Changes What You Can Survive

When Chris rebuilt his organization's app himself, the thing that changed was not the app. It was the relationship between the organization and its own infrastructure. A user reports a bug. He opens the logs. He fixes it in minutes, in-house, without waiting on anyone twelve time zones away.

That is what owning your capacity buys you. Not perfection. Things still break. Owning your capacity means that when something breaks, you can fix it. The difference between an organization that survives disruption and one that does not is rarely the size of the disruption. It is whether the organization can respond without being locked out of its own work.

This is true far beyond app development. The same logic applies to your donor data, your financial systems, your program delivery, your knowledge of how the whole thing runs. Wherever a single external dependency holds your mission hostage, you have found the place that will break you first.

What This Makes Possible

When a leader sees this clearly, the relationship to technology stops being a source of dread. The fear of the system breaking, of the vendor disappearing, of being locked out, that fear comes from not owning the thing your mission depends on. Build the capacity inside the organization and that weight lifts.

What you are left with is an organization that can absorb a bad season without collapsing.

One that fixes its own problems instead of waiting on someone else to find the time. One that can take the expertise it already holds and put it in front of the people who need it, at a scale that actually moves the needle. That is what staying power looks like. It is built, not hoped for.

Closing

This isn't about doing more.

It's about owning what your mission depends on.

Nonprofits can control their own systems. They can fix their own problems. They can scale the expertise they already have.

Not by hiring it all out and hoping it holds, but by building the capacity to stand on their own.

About the Guest

Chris Conlee is my guest for this episode.

Chris is an Army veteran and a long-time Hollywood film editor who traded the red carpet for the server room to build something that matters. After a series of "perfect storm" disasters—including a total industry shutdown and losing our lead developer—I spent six months teaching myself to code with AI to rebuild PIFster from the ground up.

My wife Shashana and I now run this community of micro-donors, where we prove every day that a bunch of people giving just $1 a month can collectively change the life of an "underdog" charity. When I'm not in the code, I'm likely at our home in East LA, which we've turned into a bit of a sanctuary for local street rescues.

Connect with Chris:

• Website: ChrisConlee.com (Personal)

• Website: imdb.com (Other)

• LinkedIn: linkedin.com/in/chris-conlee-editor

Be sure to subscribe to Inspired Nonprofit Leadership so that you don't miss a single episode, and while you're at it, won't you take a moment to write a short review and rate our show? It would be greatly appreciated!

Let us know the topics or questions you would like to hear about in a future episode. You can do that and follow us on LinkedIn.