Fundraising and development: size matters
As organizations grow, the distinction between fundraising and development becomes more pronounced
Knowing the difference between fundraising and development is one thing. Knowing how that difference plays out in your specific organization is another.
Size matters here—not because the concepts change, but because the way they’re carried out changes considerably depending on how many people you have and what they’re responsible for.
In a small organization, the lines between fundraising and development tend to blur out of necessity.
If you’re an executive director with a lean team, you’re probably doing most of it yourself: writing grants, cultivating donors, managing sponsors, handling membership, coordinating in-kind donations, and somewhere in between all of that, trying to keep your donor database reasonably current and your messaging reasonably consistent.
The fundraising is visible because it has to be—there are immediate revenue needs and limited hands to meet them. The development work, when it happens at all, tends to be informal. Relationship management happens through personal emails and phone calls. Record-keeping lives in spreadsheets. Stewardship is reactive rather than planned.
This isn’t a failure. It’s a reality. But it’s worth naming, because the risk in small organizations is that development never quite gets the attention it deserves.
When every day is spent executing fundraising activities, it’s hard to step back and ask: are we building the systems that will make this easier next year? Are we nurturing the relationships that will make our next campaign more effective? Those questions don’t get answered when you’re in permanent execution mode, and over time, that takes a toll.
As organizations grow and bring on additional staff, something important happens: the separation between fundraising and development starts to become visible.
Mid-size organizations often have staff dedicated to specific revenue channels—someone focused on major gifts, someone managing grants, someone running membership or earned-income programs—while others are focused on the systems that support all of those efforts.
That’s the moment when development starts functioning as its own distinct thing. Donor data is managed more deliberately. Stewardship is planned rather than improvised. Messaging is consistent across channels. Revenue streams are coordinated rather than running in parallel without talking to each other.
This is also when development becomes a coordination function. It’s not just about managing individual relationships; it’s about making sure that everything the organization does to generate resources is aligned, coherent, and sustainable. At this stage, leadership can shift some attention from executing every fundraising task to thinking strategically about which activities to prioritize, which relationships to deepen, and how to build for the long term.
In larger organizations, development is typically its own department, with staff organized around specific functions—major gifts, corporate partnerships, planned giving, membership, events, grants, and so on—all operating within a shared strategic framework.
At this scale, development manages complexity. It maintains organizational memory. It ensures that no revenue stream operates in isolation and that the full picture of how the organization generates resources is always in view. Leadership alignment—between the executive director, the development team, and the board—becomes essential to sustaining that framework over time.
The takeaway isn’t that small organizations are doing it wrong or that large ones have it figured out. It’s that size shapes what’s possible, and being honest about your organization’s capacity helps you make better decisions about where to focus.
At every stage, the goal is the same: to build enough development infrastructure to make your fundraising more effective, more consistent, and more sustainable—even if what that looks like in practice is very different depending on who you have and what you’re working with.