TL;DR: Most development teams under-ask their highest-capacity donors. The culprit is not skill or capacity. It is bias. Comfort bias, status bias, and recency bias steer outreach toward the easy donors and away from the ones who could fund the strategic plan. Audit the pattern. Then build the system that interrupts it.
Every development team has a pattern, even when they swear they do not. You can see it in the call logs. The same donors get the warm Friday afternoon outreach. The same donors get the personal thank-you call. And the major donor who gave $25,000 eighteen months ago, the one whose foundation just closed a fresh capacity grant, is still sitting in the "I will get to it next week" column.
That pattern is fundraiser bias. It is not a skill gap. It is not a capacity gap. It is the predictable way human attention drifts toward the easy ask and away from the consequential one.
If your team is missing major gift targets while smaller donations decline, the answer is rarely "ask more people." It is usually "ask the right people, and stop avoiding the ones who matter most."
What is fundraiser bias?
Fundraiser bias is the set of cognitive shortcuts that shape who a development team asks and who they leave alone. Researchers in social psychology call the underlying problem ask aversion. Cornell researcher Vanessa Bohns, whose work has been profiled by NPR's Hidden Brain, has shown that volunteer fundraisers overestimate the number of people they need to ask by roughly double, because they fixate on their own anxiety rather than the donor's likely response.
In practice, the result is a prospect list that looks rational on paper but operates on instinct. The donors who are easy to reach get reached. The donors who feel intimidating, distant, or socially complicated get postponed.
Here is the catch. Those postponed donors are usually the ones who would have given the most.
Why does this matter right now?
The macro picture has shifted. According to the Fundraising Effectiveness Project's 2025 reports, total dollars raised are up roughly 2.9% year over year, but donor counts have fallen for five consecutive years. The increase is being driven almost entirely by larger gifts from fewer households.
Translation: the sector is more dependent on major donors than at any point in the last decade. The mid-level and major pipeline is where revenue lives. Which means a bias that skips your highest-capacity prospects is no longer a soft inefficiency. It is a strategic vulnerability for growing nonprofits.
The four biases distorting your prospect list
There are dozens of cognitive biases in the academic literature. Four of them show up in nearly every development team conversation.
Comfort bias. You reach out to the donors who feel easy. They reply quickly. They thank you for the call. The conversation is light. You leave feeling productive. The problem is that ease and impact are usually inverse. The donor who makes you a little nervous is often the donor who would make the biggest gift if asked properly.
Recency bias. Whoever donated last week is the loudest signal in your CRM. They show up in dashboards. They show up in pipeline reports. They show up in your inbox. Meanwhile a donor who gave once eighteen months ago, and is now between gifts, gets quietly filed away. Recency does not equal capacity.
Status bias. Some fundraisers find it socially complicated to ask people who hold positions of authority, public profile, or significantly more wealth. Fundraising consultant Tori Tishman made this exact point on a recent episode of The Focused Fundraiser: "People don't necessarily want to be asked from someone that they see as air quotes inferior to them. They want to be asked from someone they trust, someone they see as their own level."
Egocentric bias. You are far more focused on how the ask feels for you than on how it feels for the donor. The donor, in most cases, is already favorably disposed toward your mission. You are running an internal movie about rejection while the donor is wondering when you will finally invite them deeper into the work.
How do these biases compound?
The biases stack. Comfort bias narrows your call list. Recency bias re-weights the list toward whoever just gave. Status bias removes the highest-capacity prospects. Egocentric bias makes you under-ask everyone who is left.
The compounding effect explains a pattern that frustrates almost every executive director. A development team is genuinely working hard, hitting their activity goals, and still missing the major gift number at the end of the year. The team's activity is real. The activity is just pointed at the wrong donors.
How can a development team audit who they are not asking?
The audit is simpler than it sounds. Pull two lists from your CRM.
List one: every donor your team contacted in the last 30 days. List two: every donor capable of a five-figure gift this year who has not been contacted in the last 90 days. If list two is longer than list one, that is your bias gap.
The next step is to interrogate it. For each donor on list two, ask three questions. Why have you not reached out? Who on the team is best positioned to reach out? What would the ask be if you did?
If you cannot answer the first question, you have probably found a comfort or status bias case.
Why willpower is the wrong fix
Willpower is not the answer. Bias is structural. The fix is structural too.
This is where the right CRM stops being a nice-to-have. A development team running on memory, sticky notes, and dashboards-by-vibes will recreate the same comfort patterns every quarter. A development team running on a system that surfaces the right donors, regardless of who is comfortable to call, will outperform every time.
That is why DonorDock built Smart Nudges into the daily workflow. The Smart Nudges feature surfaces donors at risk of being missed, the ones whose recency or status puts them in the bias gap, and routes them to the Action Board as the next task. Your team sees who they have been avoiding before they get the chance to avoid them again.
Used well, a CRM does more than record relationships. It interrupts the patterns that cause you to lose them.
A 20-minute exercise for your next development meeting
Bring the two bias audit lists from the section above into your next development meeting. For each donor on list two, assign one of three colors.
- Green for "we have not asked because the timing is genuinely wrong."
- Yellow for "we have not asked because we have not decided what to ask for."
- Red for "we have not asked because someone is uncomfortable making the move."
Red is your gold. Red is where the next major gifts are hiding.
Pick three reds. Assign each one to a teammate best positioned to take the next step. Set a 14-day deadline for an initial outreach attempt. Document the result in the CRM, win or no-win, so the team can see whether interrupting the bias actually changes the numbers.
Run the exercise quarterly. Within two cycles, the team will start surfacing reds on their own.
Where this gets harder during stretched seasons
Bias gets worse under load. When a development team is racing to close a year-end campaign or recover from a staffing change, the path of least resistance dominates. Comfort bias becomes the operating default. The hardest prospects fall off the list first.
This is exactly when the audit pays the highest dividend. If the same three reds keep getting deferred quarter after quarter, that is a signal worth elevating to the executive director, the development committee, or the board chair. The pattern, made visible, becomes a leadership conversation rather than a personal failure.
If your team is operating beyond capacity, see our piece on using automation to reduce the mental load on your fundraisers. Reducing cognitive load is one of the most reliable ways to reduce the bias gap.
The shift that follows the audit
When a development team gets honest about who they have been avoiding, two things tend to happen.
The first is uncomfortable. The team realizes the prospect list has been shaped by comfort, not capacity, for longer than they want to admit.
The second is liberating. Once the bias becomes visible, it stops controlling the calendar. The hard asks get scheduled. The major donors get the attention they were always supposed to have. And the development team stops measuring its quality of work by activity and starts measuring it by impact.
The work that matters most is rarely the work that feels easiest. The discipline of choosing impact over comfort, supported by a CRM that surfaces the right donors at the right time, is the through-line of a development team that consistently meets its number.
You will not eliminate fundraiser bias. You can interrupt it. That alone is worth the audit.
If you want to see how a CRM builds the structural cues that interrupt comfort bias automatically, that is the conversation we would love to have with your team.
