Your fundraising system isn’t failing. It’s learning the wrong things.
Part 3. Why organizations that fixed their fundraising goals are still stuck — and what’s missing from the loop.
Parts 1 and 2 of this series were about the fundraising goal. Where it comes from. Why most nonprofit fundraising targets are reverse-engineered from budget gaps rather than built from donor capacity. And what it takes to bring a different number to the table before the expense budget gets locked.
This part is about what happens after.
Because here’s what I keep seeing: organizations that know the plug number problem, that have started doing the work to set better goals — they’re still stuck. Not for the same reason. For the next one.
They don’t know how to read what’s happening.
You set a goal. The year starts. Now you’re measuring performance against it. The question that doesn’t get asked nearly enough: what information are you actually using to do that?
For most organizations, the answer is the pipeline.
That answer sounds reasonable. It’s not feedback.
Pipeline projections tell you what people expect to happen. Feedback tells you what’s actually happening — and why. Organizations running on projections aren’t measuring performance; they’re monitoring their own predictions. The loop closes before any real information gets in.
This is a direct consequence of the problem Parts 1 and 2 described. The plug number creates pressure. Pressure creates the need to show progress. And projections let you show progress without actually learning anything.
Early data from the Fundraising Operating System (fOS) Self-Assessment™ makes this concrete:
93% of respondents set their goals from the budget gap rather than donor capacity — which is exactly where this problem starts.
71% rely on pipeline projections rather than real-time donor signals.
Separately, 71% respond to symptoms — missed asks, late renewals, a development director who seems disengaged — rather than diagnosing causes.
Those aren’t two problems. They’re the same loop from different angles.
The pipeline shows Q3 is soft. Leadership responds: more calls, pushed timelines, a renewed push on the board. The softness persists. The pipeline updates. The response intensifies.
No one asks what the pipeline can’t tell you. Why is the donor hesitating? What shifted six months ago — before the hesitation showed up as a projection gap? What is the development director not saying in the weekly check-in?
Those questions require signals, not projections.
A projection summarizes activity — calls made, visits logged, asks pending. A signal is a current reading of the relationship: engagement patterns, time-since-last-contact, whether the donor’s language has shifted, whether they’re asking more or fewer questions.
Projections compress context into a number. When organizations run entirely on them, what remains is a number that gets more optimistic or pessimistic over time, with no structural way to understand why.
The fundraiser knows why. The nuance lives in their head. When they leave, it leaves with them.
The 71% treating symptoms rather than causes isn’t carelessness. It’s a structural consequence of what information the system is designed to receive.
If the only data flowing to leadership is pipeline projections, leadership can only respond to what the projections show. A drop looks like a fundraising problem. The response is a fundraising intervention: more outreach, a different approach, a conversation about effort.
But the drop might not be a fundraising problem. It might be a collaboration problem — program staff and development haven’t talked in three months, and donors can feel the disconnect. A culture problem — the development director is absorbing institutional anxiety that leadership hasn’t named. A clarity problem — the asks are misaligned with what the organization can actually deliver.
Pipeline projections can’t distinguish between these. So the response targets the symptom. The cause persists. The symptom returns.
A healthy Feedback layer isn’t a reporting cadence. It’s a designed capacity — the organizational architecture that allows real information to flow to the people who can act on it, before the damage compounds.
In practice, three things have to be true.
Donor signals — not just summaries — have to move through the system. Not “the donor is likely to renew” but “the donor asked twice last month whether their gift had been acknowledged by the board, and it hadn’t.” That’s the sentence that tells you something is wrong before it shows up in the pipeline.
Development and program leadership have to share information in real time, not at fiscal year reviews. A new program launches. Marketing promotes it. A donor asks the major gifts officer about it in a meeting — and she’s hearing about it for the first time. By the time that disconnect surfaces in a debrief, you’ve already lost the moment. And the donor noticed.
And there has to be a designed moment — not a fire drill — where leadership asks: what are we consistently not seeing? What would the pipeline not tell you? In most organizations, that moment arrives when an ED feels blindsided by something the development director has been saying for months. The information was there. It just wasn’t received. A standing structure doesn’t fix the relationship, but it creates the condition where the conversation has to happen before the crisis does.
This series started with a budget meeting — or rather, with what happens before one. The moment when a gap appears and development gets handed a number that was never about them. Part 1 named the design flaw. Part 2 offered a way to show up differently before that moment arrives.
This part is about what still goes wrong even when you do.
You can build a better goal. You can bring your own number to the table. And you can still spend the year responding to projections instead of learning from signals — chasing the same symptoms with better intentions but no better information.
The goal is infrastructure. So is the feedback system that runs underneath it.
Both have to be designed. Neither builds itself.
If you want to put this into practice, I'm running a free one-hour workshop on April 15 — Your Fundraising Goal Was Built to Fail, and What to Do Instead.
