Your Fundraising Goal Was Built to Fail
How the budget process sets development teams up to fall short — and what to do before it happens again.
A note: this is the first piece published under the new name of this publication — Fundraising, Reconstructed. Same work, sharper focus. If you've been here a while, thank you for staying. If you're new, this is a good place to start.
Part 1: Every nonprofit budget has one.
A number that doesn’t come from donor research. Not from pipeline analysis. Not from a conversation with the development team about what’s actually achievable.
It comes from subtraction.
The board sets the expense budget. Leadership looks at the gap between expenses and known revenue. And then — almost always in a quiet conversation, rarely in writing — development gets handed the difference.
That number is the budget gap. And somewhere along the way, it got dressed up as a fundraising goal.
If you’ve spent any part of your career trying to hit one, you already know what it costs — not just in revenue, but in the people who burn out getting there and the relationships that don’t survive the pressure.
I’ve been on the receiving end of this conversation more than once. The number is real. It’s in the budget. The board has approved it.
What usually goes unsaid is that the number has almost nothing to do with your donor base, your staff capacity, or your organization’s actual fundraising infrastructure.
It’s what’s left over after everything else was decided.
I always said some version of the same thing: this is going to be hard.
Sometimes I got sympathy. Sometimes I got silence.
Most often I got three words that have come to represent everything wrong with how nonprofits think about fundraising goals:
It is what it is.
That phrase does a lot of work.
It ends the conversation before the real one can start. It accepts the number as fixed while treating the people asked to hit it as the variable. It frames a structural problem as a motivation challenge.
And it lets everyone in the room off the hook for the decision that was just made.
Because here is what “it is what it is” actually means:
The development team will absorb the consequences of a budget process they had no part in designing.
Let me be precise about what happens next, because I’ve watched it play out enough times to know the pattern.
The development director takes the number seriously — because they’re a professional, and that’s what professionals do. They build a plan. They work the portfolio. They push into the fourth quarter harder than anyone should have to.
Sometimes they come close. Sometimes they hit it.
But close and hit come at a cost that never shows up in the budget.
It shows up in exhaustion. In the fundraiser who starts quietly updating her resume in February. In the major gifts officer who stops having creative ideas because he’s too depleted to have them. In the institutional knowledge that walks out the door when the person who held all the donor relationships decides they’ve had enough.
The team kills themselves to get there. And then some of them leave.
And the next budget cycle begins. And someone opens a spreadsheet. And the gap gets subtracted again.
The budget gap survives. The people don’t.
I want to speak directly to the EDs, CEOs, and board members reading this — because most of you didn’t arrive at this number carelessly.
Boards approve what has to balance. EDs bridge what programs need against what revenue can realistically produce. Finance committees work with the information they have. Nobody in that room is usually trying to set the development team up to fail.
But good intentions don’t change what the process produces.
When the budget gets built from the expense side first and development fills the gap last, the fundraising goal stops being a plan and becomes a wish. And wishing isn’t a strategy the development team can execute against.
The pressure you’re under is real. Boards want balanced budgets. Funders want to see growth. Programs need to be staffed. The math has to work somewhere.
But here is the question worth sitting with before the next budget cycle:
Is your fundraising goal based on what your organization is designed to produce — or on what it needs to survive?
Those are not the same question. And the difference between them is the difference between a sustainable fundraising operation and a team that quietly burns through good people every eighteen months.
The budget gap feels like a solution. It closes the spreadsheet. It gets the budget approved.
What it actually does is transfer the organization’s financial anxiety onto the development team and ask them to resolve it through individual effort.
That is not a strategy. It is a subsidy. And like all subsidies, it has a repayment schedule.
There is a different way — and it starts with the development director showing up differently. Not as the recipient of a number, but as the person who brings one.
Here is what that looks like in practice.
Step 1 — Build the evidence package before budget season starts.
Pull together four inputs: historical revenue by source, the current donor pipeline with each prospect staged and capacity-rated, a relationship readiness calendar, and an honest staff capacity assessment.
This is not a wish list. It is a picture of what the organization is currently designed to produce.
Step 2 — Translate the inputs into a range, not a single number.
The evidence produces three scenarios: a conservative goal (high-confidence asks only, current staffing), a realistic goal (pipeline at current readiness plus modest growth), and an optimistic goal (full portfolio execution, full staffing, strong board engagement).
Present all three. Let leadership choose with eyes open — and with full knowledge of what each scenario requires.
Step 3 — Bring it to the budget conversation first.
The development director presents the evidence package before the expense budget is finalized — not after. The sequence matters.
Revenue capacity informs what the organization can afford to spend. Not the other way around.
Step 4 — Name the gap explicitly.
If the evidence-based goal doesn’t cover the expense budget, that gap gets named — not absorbed.
Leadership and the board then face a real decision: reduce expenses, build reserves over time, or invest in the fundraising infrastructure that would close the gap sustainably.
Step 5 — Connect the goal to what the system needs to produce it.
Every goal has infrastructure requirements. Make them visible.
If the organization wants the goal, it funds the system that produces it — the staff hours, the donor touchpoints, the board engagement.
A fundraising goal is not just a revenue target. It is a commitment to fund the conditions that make the revenue possible.
These five steps are a starting point. In Part 2, I’ll go deeper on each one — what the evidence package actually looks like, how to build the three scenarios from real pipeline data, and how to have the budget conversation when the room isn’t ready to hear it.
The next time a budget gap lands on development’s desk and someone says “it is what it is” — that’s the moment worth pausing on.
Not because the number can’t be achieved. Sometimes it can.
But because the phrase itself is a signal. It tells you that the budget process has already decided development is a pressure valve rather than a system. It tells you that the organization’s financial planning ends where the development team’s problem begins.
That’s not a fundraising challenge.
That’s a leadership one.
And it is, in fact, something that can be changed.
Such a good outline and understanding of the budget process. Thank you for sharing.