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.

Learn More + Register

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.

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.

I estimate the true cost of a single fundraiser departure at $377,500.

That figure isn’t built from recruitment fees alone. It accounts for six compounding components: recruitment and search costs, onboarding and transition productivity loss, lost donor relationships, institutional knowledge loss, staff morale drag across the team, and — critically — the elevated probability of a second search, because organizations that lose one fundraiser in 18 months are rarely fixed before the next hire starts the clock again.

$377,500. Per departure.

For most nonprofits, that number doesn’t appear anywhere on the balance sheet. It’s absorbed invisibly — in stalled campaigns, in donor relationships that quietly cool, in the exhaustion of a leadership team running a search while also trying to close the fiscal year.

The cost is real. It’s just distributed in ways that are easy to overlook until the pattern is impossible to ignore.

Here is what that cost looks like in practice.

The Story Behind the Number

She was exactly what the job description asked for.

Proven major gifts experience. Strong donor relationships at her previous organization. Enthusiastic about the mission. In the final interview, she talked about the long game — building a pipeline, deepening board engagement, creating the kind of donor culture that compounds over time.

The board was relieved. The ED was hopeful. The development committee approved the hire unanimously.

Fourteen months later, she was gone.

Not because she wasn’t talented. Not because the mission stopped mattering. But because the organization she joined wasn’t designed to support what she was hired to do.

The goals had been set before she arrived — reverse-engineered from a budget gap, not built from actual donor capacity. The program team operated on a separate calendar, rarely looping development in until the last minute. There was no CRM discipline, no portfolio framework, no institutional knowledge about which donors needed what kind of attention and when. She was expected to build relationships and manage a system and report to the board and cover the annual fund and steward the major donors — all at once, all urgently.

She did it. For fourteen months, she held it together through sheer personal commitment.

And then she left for an organization with a better-functioning system.

This story is a composite. But if you’ve led a nonprofit for more than five years, you’ve probably lived some version of it. And now you have a number for what it cost.

The Diagnosis Most Leaders Miss

When an ED loses a fundraiser, the instinct is to examine the hire. Was the fit wrong? Was the compensation off-market? Was the manager relationship difficult?

Sometimes those factors matter. But in the organizations I’ve worked with, the more consistent answer is structural.

The fundraiser didn’t fail the organization. The organization’s operating system failed the fundraiser.

Most nonprofits are running their fundraising on what I call a legacy operating system — a set of inherited assumptions, informal practices, and cultural norms that quietly determine how revenue work actually happens. Goals get set the way they’ve always been set. Teams communicate the way they’ve always communicated. Capacity gets managed the way it’s always been managed.

That system may have worked when the organization was smaller, or when one exceptional person held it all together. But as missions grow and demands increase, the legacy system accumulates debt.

Fundraising System Debt is the compounding cost of structural shortcuts — the revenue goals disconnected from real capacity, the silos between development and programs, the donor relationships held entirely in one person’s head, the culture that normalizes crisis as a permanent operating mode.

The debt doesn’t announce itself. It shows up gradually, as instability, as turnover, as revenue that feels perpetually fragile no matter how hard the team works.

And here’s what makes it so difficult to address: the same heroic effort that masks the debt also delays the diagnosis. As long as someone is compensating for the broken system, leadership rarely has to confront the system itself.

Until they leave.

What Changes When You Fix the System

The Fundraising Operating System (fOS)™ is built around a single premise: that sustainable fundraising is an organizational design problem, not a talent problem. When its five layers — Clarity, Culture, Collaboration, Capacity, and Feedback — are aligned, the job stops requiring a superhero.

• Goals stop being aspirational and start being architectural — because the fOS builds them from actual donor engagement data and real staff bandwidth, not from what the budget requires. The development team stops inheriting numbers they don’t believe in and starts co-authoring targets they can defend.

• Information starts flowing between development and programs — because the fOS treats cross-functional integration as a structural requirement, not a cultural aspiration. Fundraisers can tell a coherent story about impact because they were part of building it.

• Donor relationships become institutional rather than personal — because the fOS builds portfolio infrastructure that holds relationship history, giving patterns, and cultivation notes at the organizational level. When someone leaves, the relationship doesn’t leave with them.

• And the job stops requiring a superhero — because the fOS redesigns roles for humans, with workloads calibrated to what a skilled professional can actually sustain. That’s when tenure extends. That’s when donor relationships deepen. That’s when revenue stops feeling fragile.

Not because the organization found a better fundraiser. Because it finally built a system worth staying for.

The Question Worth Sitting With

If you’ve cycled through more than one fundraiser in the last five years, the search process isn’t the problem. The search process is the symptom.

The question underneath it — the one most leaders haven’t had a clear way to answer — is this: Is our organization actually designed to produce sustainable fundraising results?

That’s what the fOS Self-Assessment was built to surface. Five structural layers. Less than ten minutes. A clear read on where your system is functioning and where the debt is compounding.

Not a report. Not a diagnosis someone else hands you. A mirror — so you can see what you’re actually working with.

You just put a number on what the broken system costs. The assessment takes less than ten minutes. That’s a reasonable investment to find out whether you’re building toward the next departure — or finally building a system worth staying for.

Take the fOS Self-Assessment

Share this with an ED who has said “we just need the right person” more than once. The problem probably isn’t the person.

One Development Director said what dozens were thinking: "I know what you're describing. I just didn't have a name for it."

Having a name is useful. But a name doesn’t tell you where the debt lives in your specific organization, which layer is under the most strain, or where to focus first.

That’s what the new fOS Self-Assessment is built to do.

Before I introduce the tool, I want to walk through what it’s actually measuring — because the five layers aren’t obvious, and the debt in each one looks different.

Why Debt Looks Different in Each Layer

Most organizations have System Debt in multiple places simultaneously. But it rarely distributes evenly. One layer tends to be the load-bearing weak point — the place where the most compensating effort is concentrated, and where a failure would do the most damage.

Knowing which layer that is changes everything about where you focus.

Goal Debt — The Clarity Layer

Goal Debt accumulates when revenue targets are set from the top down, based on what the budget requires rather than what the donor pipeline can actually support.

It produces a specific dysfunction: the development team learns to perform optimism. Pipeline reports look healthier than they are. Bad news gets absorbed privately and surfaced late — not because people are hiding things, but because past experience has taught them that surfacing problems gets them more problems, not more support.

The tell: when a development director’s pipeline update and her private assessment of the pipeline are two different conversations.

Relationship Debt — The Capacity Layer

Relationship Debt accumulates when donor relationships are held by individuals rather than the institution. It’s the most invisible form of debt because it only becomes visible when someone leaves.

When a major gifts officer carries twelve relationships through personal loyalty and then departs, those relationships don’t transfer automatically. The institution discovers it never actually owned them. What looked like institutional strength was individual heroics with no backup.

The tell: when the answer to “who manages this donor relationship?” is a person’s name rather than a portfolio structure.

Information Debt — The Collaboration Layer

Information Debt accumulates when development and programs operate as separate functions. Fundraisers describe programs in general terms because that’s all they have access to. Program staff develop new work without development input on what donors need to hear.

The result is a donor experience built on misalignment. The story donors hear in cultivation doesn’t match the story at the gala, which doesn’t match the annual report. The inconsistency erodes trust slowly — invisibly, until the damage is already done.

The tell: when your most experienced major gifts officer can’t answer a specific donor question about program outcomes without checking with someone else first.

Culture Debt — The Culture Layer

Culture Debt is the most consequential and the least discussed. It accumulates when organizations normalize the suppression of bad news — when surfacing a risk feels more dangerous than absorbing it.

It produces a distinctive pattern: problems get managed privately and escalated late.

The tell: The development director knows in March that a $200,000 gift is at risk. She works the relationship harder. She doesn’t flag it because past experience has taught her that flagging problems means owning them alone. By October, it registers as a surprise.

Culture Debt is what makes all the other debt worse. It’s what prevents structural problems from being named — and fixed.

Culture Debt is also what makes the other four types of debt self-perpetuating.

• Goal Debt can’t be corrected if the team can’t safely challenge the number.

• Relationship Debt can’t be addressed if people can’t name the portfolio risk.

• Information Debt can’t be cleared if teams won’t admit they’re operating in silos.

Fix culture last and you fix nothing. Fix it first and everything else becomes possible.

Learning Debt — The Feedback Layer

Learning Debt accumulates when organizations process fundraising performance annually rather than continuously. The year-end post-mortem is near-universal. It’s also nearly useless as a learning mechanism.

By the time the post-mortem happens, the team has partially turned over. The decisions that shaped outcomes are months in the past. The organization generates insights it doesn’t act on — because the moment for action has already passed.

The tell: when every year-end review produces the same three recommendations, and next year’s review notes they weren’t implemented.

How Debt Compounds Across Layers

The reason System Debt is so damaging isn’t that any single layer is catastrophic on its own. It’s that debt in one layer generates pressure that flows into others.

Goal Debt puts the development director under pressure she can’t surface safely — because Culture Debt makes honesty feel risky. That pressure gets absorbed through heroic individual effort — building Capacity Debt. The team is too strained to invest in cross-functional relationships — deepening Information Debt.

And because no one is tracking signals in real time, the compounding damage stays invisible — until it isn’t.

This is why organizations that try to fix one layer in isolation — new software, a new hire, a new campaign strategy — rarely see lasting change. They’re addressing a symptom while the underlying debt continues to compound.

Clearing debt requires knowing where it lives across all five layers simultaneously. That’s what the assessment is designed to show you.

Introducing the fOS Self-Assessment

Today I’m releasing the fOS Self-Assessment — a free diagnostic tool built around the five layers of the Fundraising Operating System.

It takes about eight minutes. It asks you to evaluate your organization’s current state across Clarity, Culture, Collaboration, Capacity, and Feedback. No jargon. No trick questions. Just an honest look at how each layer is actually functioning.

The fOS Self-Assessment: A free 8-minute diagnostic across all five fOS layers

→ Take the assessment

The assessment is designed for executive directors and senior leaders who are close enough to the work to answer honestly. The only requirement: answer the way things actually work, not the way they look on paper.

When you finish, you’ll see a pattern — which layers of your system are solid and which ones have accumulated debt. There’s no score. No grade. No percentile ranking against other organizations.

What you get is a mirror.

Most leaders who complete it recognize the pattern immediately. Some have been circling it for years without having language for it. The assessment doesn’t tell you anything you don’t already know — it just makes it harder to look away.

If what surfaces feels significant, that’s the signal worth following.

You can’t fix what you can’t name. And you can’t name what you haven’t looked at directly.

Picture it concretely: a development director answering donor emails at 10pm, covering for a system that was never designed to function without her. A major gifts officer holding relationships together through sheer personal loyalty because no institutional infrastructure exists to support them. A team pushing harder into the fourth quarter because the goals were set in January without anyone asking whether they were actually achievable.

That’s the invisible subsidy. And when it runs out — when the people can no longer compensate for the system — what’s left is the system itself. Fractured. Fragile. Exposed.

The result: burnout, turnover, and revenue that feels perpetually unstable.

Welcome to Fundraising, Reconstructed — a space for leaders and fundraisers committed to building the organizational conditions where missions actually thrive.

Recently, I wrote about standing in the Rubens Gallery in Antwerp — about the modello, the precise structural blueprint that made Rubens’ studio possible at scale. I ended that piece with a question: Are you painting the background, the animals, and the figures all by yourself? Or are you ready to lead a studio?

This is my answer.

The Hidden Cost: Fundraising System Debt

Most nonprofit fundraising isn’t failing because people lack commitment.

It’s failing because the organization has accumulated Fundraising System Debt™ — small structural weaknesses that compound over time until the system itself becomes fragile.

Like technical debt in software development, Fundraising System Debt builds quietly. It accumulates through decisions that seem reasonable in the moment: setting a revenue goal based on the budget gap rather than actual donor capacity; letting development and programs operate as separate islands; allowing one exceptional fundraiser to become the sole guardian of your most important donor relationships.

Each shortcut feels manageable. Together, they create a system that only functions because extraordinary people are working extraordinarily hard to hold it together.

The debt shows up as:

• Unpredictable revenue performance

• “Sudden” turnover of your best talent

• Donor friction caused by inconsistent messaging

• A default setting of permanent crisis mode

The cost is not abstract. A single development director turnover — recruitment, transition, lost donor relationships, institutional knowledge — runs north of $377,500.1 Most organizations absorb that number and post the job again.

And yet the deeper response is almost always the same: hire a stronger fundraiser, push harder on targets, or add another campaign.

But none of those address the underlying debt. They simply ask individuals to compensate for the system.

The Rise of the Hero Fundraiser

In this environment, a particular archetype emerges: the hero fundraiser.

This person holds relationships together through personal trust. They navigate internal silos through sheer persistence. They keep revenue flowing through extraordinary effort.

From the outside, it looks like success.

Inside the system, something else is happening. The organization becomes quietly dependent on individual heroics rather than reliable structures. And hero-dependent systems are inherently unstable.

When the hero burns out, leaves, or simply runs out of capacity, the system collapses back to its underlying condition.

The problem was never the fundraiser. The problem was the system they were asked to carry.

When Passion Becomes a Subsidy

In healthy systems, effort produces results.

In fragile systems, effort becomes a substitute for structure.

Fundraisers compensate for unclear priorities. They navigate cultural friction between departments. They absorb the pressure of unrealistic expectations. Their dedication keeps the mission moving forward.

But it also masks the deeper issue.

The organization is not functioning on a designed system. It is functioning on borrowed energy.

And borrowed energy has a repayment schedule.

The Five Structural Layers of the MissionCraft fOS

The modello was Rubens’ operating system.

A shared source of truth so precise that a studio of twelve specialists couldn’t fail. Every painter knew their role. Every role served the composition. The vision held because the blueprint was built before a single stroke hit the canvas.

Most nonprofits don’t have a modello. They have a budget number and a prayer.

The MissionCraft Fundraising Operating System (fOS)™ is the modern modello — the structural blueprint that allows a team to execute without depending on one heroic individual. It isn’t about new tactics. It’s about auditing the layers that determine whether fundraising can actually function — and clearing the debt that’s accumulated in each one.

When these layers are aligned, fundraising stops relying on individual heroics and begins functioning like a well-designed system. Many organizations attempt to fix one layer while ignoring the others — new software without addressing culture, new hires without addressing capacity. Those investments are software updates running on hardware that was never designed for the job.

The debt compounds until the system fails.

The Reconstruction Ahead

The problem is not a lack of passion.

It’s that most nonprofit fundraising is operating on an outdated and fragile system — one that depends on heroic individuals to compensate for structural gaps.

And no system that relies on heroics is sustainable.

What we need now is reconstruction. Not a few new tactics. Not another campaign strategy. Not another training on donor conversations.

We need to rebuild the operating system that fundraising runs on.

The way goals are set. The way teams collaborate. The way culture supports — or undermines — the work.

This is the work ahead.

Because the future of fundraising will not be determined by who works the hardest. It will be determined by who finally decides to redesign the system.

Share this with the colleague who keeps whispering: “Something isn’t working, but I don’t know how to name it.”

You just gave it a name.