How to Build a Nonprofit Development Team: Roles, Sequence, and Scaling

Building a nonprofit development team is a sequencing problem more than a staffing problem. The wrong first hire — and the wrong hiring sequence after it — can set a fundraising operation back two years even when each individual hire is well-intentioned.

This guide covers how to think about development team structure at a mid-sized nonprofit, which roles to hire in what order, how the team scales by budget size, and the operational decisions that determine whether the team compounds value or churns in place.

What a Development Team Is For

A development team executes the organization’s fundraising strategy across all revenue channels. The work is broader than most non-development staff understand:

• Strategic planning — annual fundraising plan, multi-year revenue projection, diversification strategy
• Major gift cultivation, solicitation, and stewardship
• Annual fund and direct mail campaigns
• Monthly giving program development and management
• Institutional grants — prospecting, writing, compliance, reporting, renewal
• Events and special campaigns
• Donor database management and segmentation
• Acknowledgment and stewardship workflows
• Board fundraising support and engagement
• Coordination with finance on revenue forecasting, restricted fund tracking, and audit support

A team is staffed when these functions have clear owners and dedicated capacity. A function without an owner gets done badly or not at all.

The First Hire: Development Director

For nonprofits below roughly $1.5M in budget, the first dedicated development hire should be a development director (or a director-level generalist) who can lead all of fundraising. The reasoning is operational: the work that requires strategic ownership — major donor relationships, grant strategy, board engagement, fundraising planning — does not happen at an operational level. A development associate or coordinator hired first leaves the strategic work distributed (badly) between the executive director and the board.

The development director job description guide covers the role in detail. The first development director at a small nonprofit is a hands-on operator: writing grants directly, managing the major donor portfolio personally, running the annual fund, and overseeing whatever operational support exists.

Compensation at this stage typically runs $65,000–$90,000 depending on region. The compensation question is not “what can we afford?” but “what is the market for the scope we are building?” Underpaying for the role leads to short tenure and recurring transitions.

The first development director hire takes 6–12 months to fully ramp. The first 18 months are heavy in infrastructure work — building or rebuilding the donor database, establishing the grant pipeline, creating reporting workflows, normalizing acknowledgment processes. Fundraising results compound after the infrastructure is in place, not before it.

The Second Hire: Operational Capacity

Once the development director is in place and the operational load is clear, the second hire is typically a development manager, development coordinator, or grants manager — depending on where the bottleneck is.

Development manager or coordinator when the bottleneck is operational volume: the director cannot personally run the database, manage acknowledgments, coordinate events, and execute the annual fund alongside the strategic work. This is the right second hire when the revenue mix is heavy on individual giving and events.

Grants manager when the bottleneck is the grant portfolio: the director is spending more than 40% of their time on grant operations, the active grant volume has crossed 12–15 awards, or federal grants have entered the portfolio. The grants manager job description guide covers when this hire is right.

The decision between the two is not generic — it is specific to your revenue mix and current operational pain. A nonprofit with a $2.5M budget that is 60% individual giving and 30% grants needs the development manager second; the same-size nonprofit at 30% individual giving and 60% grants needs the grants manager second.

Scaling by Budget Size

The typical development team composition by budget size at U.S. mid-sized nonprofits:

$500K–$1.5M: Development director (or director-level generalist), supported by part-time or volunteer help on operational tasks. Total dedicated FTE: 1.0–1.2.

$1.5M–$3M: Development director plus one — typically a development associate, coordinator, or part-time grants writer. The director still does most strategic work; the associate handles database, acknowledgments, and operational support. Total FTE: 1.5–2.0.

$3M–$6M: Small team of three — development director, grants manager, and a development manager or coordinator. The director focuses on strategy and major donors; the grants manager owns the grant portfolio; the development manager runs annual fund, events, and operations. Total FTE: 2.5–3.5.

$6M–$10M: Established team of four to five — development director, grants manager, development manager, donor relations or major gifts officer, and operational/database support. The director’s role becomes more strategic and external-facing; specialized roles emerge. Total FTE: 4.0–5.5.

These ranges are typical, not prescriptive. A nonprofit with a $4M budget that depends on a single foundation for 60% of revenue has different staffing needs than a $4M nonprofit with 5,000 individual donors. Revenue mix drives staffing, not budget alone.

The Operational Infrastructure That Multiplies Team Capacity

A development team’s effective capacity depends heavily on the operational infrastructure they work with. The same three-person team is twice as productive on a unified system as on a fragmented stack of donor database, separate grant tracking, separate event tools, separate restricted fund tracking.

The development operations infrastructure guide covers the operational layer in detail. The high-leverage infrastructure investments:

• Unified donor and grant management system. One source of truth for donor records, gift history, grant pipeline, restricted fund tracking, and compliance calendars. Eliminates the daily reconciliation work between fragmented systems.
• Documented workflows. Acknowledgment, stewardship, gift entry, grant submission, reporting — each documented as a process, not held in one staff member’s head.
• Compliance calendar visibility. Every active grant’s reporting requirements, deadlines, and dependencies visible across the team.
• Reporting infrastructure. Standard reports for the ED, board, and finance produced from the system, not rebuilt each time.

A development team without this infrastructure spends 30–50% of capacity on reconstruction work. The same team with mature infrastructure can shift that capacity to fundraising activity.

Common Staffing Mistakes

The mistakes that set development teams back:

Hiring a grant writer before a grants manager. A grant writer writes proposals. A grants manager owns the portfolio. Hiring only a grant writer leaves compliance and renewal work distributed across staff who do not own the function, which is where most grant compliance failures originate.

Hiring a development associate as the first development hire. The associate-level role exists to support a director-level role. Hiring an associate first makes them functionally a coordinator without the strategic ownership the work requires, and the strategic work fails to get done.

Splitting major donor work between the ED and the development director. Either the ED or the development director needs to be the primary lead on each major donor relationship. Shared ownership without clear primary accountability results in donors who feel under-stewarded by both parties.

Building events capacity before grants or major gifts capacity. Events are necessary but operationally expensive. A nonprofit that staffs an event coordinator before staffing major gifts or grants is investing in a function with relatively flat ROI before functions with compounding returns.

Hiring slowly and behind need. Development hires take 90+ days to fill and 6+ months to ramp. A nonprofit that waits until the development director is overwhelmed before posting the second role is structurally always behind. Hire ahead of need, with the next role on a clear timeline before the current team is at capacity.

Underpaying relative to market. Saving 15% on development director compensation costs an average of 9 months of vacancy after the first underpaid director leaves at month 18. Compensation is a retention investment, not an expense to minimize.

Reporting Structure and Authority

The development team should report to the executive director through the development director. Direct reporting lines:

• Development director → executive director
• Grants manager → development director
• Development manager → development director
• Development coordinator/associate → development manager (when the role exists) or development director directly

Avoid:

• Routing the development director through a chief operating officer who lacks fundraising expertise
• Splitting reporting authority such that the grants manager reports to finance instead of development
• Matrix reporting that makes the team accountable to multiple supervisors without clear primary accountability

Authority matters as much as reporting structure. The development director should have explicit decision rights — what they decide independently, what requires ED sign-off, what requires board approval. Without explicit authority, the role spends time perpetually negotiating its own scope.

Cross-Functional Coordination

The development team works closely with three other functions:

Finance. Revenue forecasting, restricted fund tracking (see restricted fund accounting basics), pledge accounting under FASB ASC 958 (see FASB ASC 958 nonprofit reporting), audit support, and donor acknowledgment compliance. A weekly or biweekly development-finance meeting normalizes the coordination.

Program staff. Grant proposals require technical narrative from program leads. Funder reports require outcome data from program staff. Site visits and donor cultivation events require program staff presence. The relationship is structural — not “ask program when you need something” but “program is part of the development workflow.”

Executive director. The ED is involved in major donors, leadership-level institutional funders, and board fundraising engagement. The development director coordinates the ED’s fundraising time so it lands on the highest-leverage activity rather than getting diluted across all donor cultivation.

The Board’s Role in Development Team Structure

The board’s responsibility on development team structure is governance, not management. The board should:

• Approve the fundraising plan and the staffing investment to execute it
• Receive regular reporting on fundraising results and team performance
• Engage the development committee (when there is one) on strategic fundraising decisions
• Support the executive director in making the staffing investments the plan requires

The board should not:

• Direct day-to-day staffing decisions or specific hires
• Override the ED on compensation or reporting structure
• Require fundraising results disproportionate to the staffing investment authorized

The development committee nonprofit guide covers what the board’s development committee should and should not do.

Volunteer and Contractor Capacity

Some development work can be done by volunteers or contractors:

• Event volunteers — common, useful, and clearly bounded
• Grant writing contractors — can work for routine renewals or specific proposals, but full portfolio ownership requires staff
• Development consultants — useful for specific strategy projects (capital campaign feasibility, planned giving program design, donor research) but should not substitute for permanent staff capacity
• Database volunteers — risky; donor data integrity is operationally consequential and amateur volunteer support can degrade data faster than it adds value

The unifying principle: volunteer and contractor capacity supplements staff capacity but does not replace it. A nonprofit relying primarily on volunteers and contractors for development work has chosen instability and limited compounding returns.

Tenure and Continuity

Development director tenure at mid-sized nonprofits averages 2.5–4 years. Grants manager tenure runs 3–5 years. Each transition costs 6–12 months of fundraising momentum and significant institutional knowledge.

Tenure-extending practices:

• Realistic targets that scale with team size and tenure
• Clear authority and decision rights
• Investment in professional development — AFP, CASE, GPA conferences and credentials
• Compensation that tracks the market, with regular benchmarking
• Strong systems infrastructure that compounds the team’s work
• A culture that values fundraising as a discipline, not as a perpetually unfinished project

The donor stewardship plan guide covers donor retention; the same logic applies to staff retention. Continuity is a multiplier on every other operational investment.

The System Difference

Building a development team is partly about hiring and partly about the systems infrastructure the team works with. A team on fragmented systems spends 30–50% of capacity on reconstruction work — pulling data from multiple places, reconciling records, rebuilding reports. The same team on unified systems spends that capacity on fundraising activity.

GrantPipe is built for mid-sized nonprofit development teams: unified donor and grant management, integrated restricted fund tracking, shared compliance calendars, and reporting infrastructure that produces the standard reports the team needs without rebuilding. The grant compliance checklist lead magnet covers the compliance scope; the system is what makes the compliance work routine instead of effortful.

The team you build is the team you can keep, support, and equip. The hiring sequence, the compensation, the reporting structure, and the systems infrastructure are all part of whether the build-out compounds value or churns through staff every 18 months.