TLDR
A working grant writing function at a mid-sized nonprofit needs three roles - a writer, a reviewer, and a project lead who supplies program detail - and a tiered pipeline that matches effort to opportunity size. Most teams under-resource the program-detail role, which is where proposals fail, not the writing role.
Definition
A grant writing team structure is the assignment of roles, responsibilities, and pipeline ownership across the people who research, write, review, submit, and report on grant proposals. At a mid-sized US nonprofit, the structure typically spans development (the writer and the development director), program (subject-matter staff who supply detail), and finance (the CFO who certifies the budget). It is the operational backbone behind every successful grant - and the most under-designed part of most fundraising programs.
This guide covers how to structure that team for a $500K to $10M nonprofit: how many people you need, what each role does, how the pipeline tiers, and the tradeoffs between in-house, freelance, and consultant models. The structures described here are calibrated for organizations that submit between 10 and 60 proposals per year. Above and below that range, the math changes.
The three core roles
Every grant proposal - federal, foundation, corporate, government - needs three roles filled. They can be three different people or one person wearing three hats, but every role must be performed.
The writer
The writer owns the narrative draft, the budget narrative, the structure of the proposal package, and the timeline from research to submission. Strong writers have three skills: they read funder guidelines word by word and deliver exactly what is asked; they translate program staff’s technical detail into clear prose without losing the technical accuracy; and they hit deadlines. The writer is not the source of program substance - that comes from program staff - but the writer is responsible for the quality of every word that lands at the funder.
A senior in-house grant writer at a mid-sized nonprofit typically commands a salary of $65K to $95K depending on geography and federal grant experience. Freelance grant writers typically charge $50 to $125 per hour, with some specialized federal writers at $150+ per hour. Project-based pricing for a foundation proposal runs $1,500 to $5,000; for a federal proposal, $4,000 to $15,000. See the grant proposal writing guide for what is in scope.
The reviewer
The reviewer reads every proposal before it goes out and catches errors the writer missed. At a minimum, the review chain includes: a peer review for narrative quality, a finance review for budget accuracy, and an executive director review for strategic fit and signature. Larger organizations add a board review for major federal proposals. The review chain is sequential - peer first, finance second, ED last - and each stage produces written comments the writer addresses before moving on.
Reviewers find three categories of error: budget-narrative mismatches (numbers in the spreadsheet do not match numbers in the prose), funder-guideline violations (missing required attachment, wrong page count, wrong font), and program-claim overreach (the proposal promises outcomes the program cannot actually deliver). Each category has a different fix, and each requires a specific reviewer with the right expertise to catch it.
The project lead (program-detail owner)
The project lead is the program staff member who knows the substance: how the program actually works, what the population numbers actually are, what the intervention actually entails, how outcomes are actually measured. Without the project lead, the writer is inventing. With the project lead, the writer is translating.
Most failed proposals fail at the program-detail layer, not the writing layer. The funder reads a generic-sounding intervention description and concludes the program is not as developed as the writing implies. Or the funder catches a population number that does not match the program’s most recent annual report. The fix is to put the project lead on every proposal early - as a 5-hour input role for routine proposals, a 20-hour input role for complex federal proposals - and to budget that time formally rather than treating it as overhead.
Pipeline tiers
Not every proposal deserves the same investment. A defensible tiering structure assigns effort to opportunity size and risk:
Tier 1 - Strategic federal and large foundation proposals. $250K+ awards, new funders, multi-year. The writer spends 60 to 120 hours. The senior reviewer reads twice. The CFO reviews the budget formally. The ED meets with the program officer before submission if possible. Tier 1 represents 20% of proposals and 60% of revenue at most mid-sized nonprofits.
Tier 2 - Foundation renewals and mid-size new proposals. $50K to $250K, often returning funders. The writer follows a template that pulls from the boilerplate library and customizes the narrative and budget to the specific opportunity. 20 to 40 hours of effort. Junior reviewer. Standard finance check. Tier 2 represents the bulk of pipeline volume - 50% to 60% of proposals.
Tier 3 - Small foundation grants. Under $25K, often local foundations or family foundations. Fixed time budget of 6 to 12 hours per proposal, completed by a junior writer using heavy boilerplate. No senior review unless the funder is strategically important. Tier 3 represents 20% to 30% of proposals and a small share of revenue but a meaningful share of relationship-building.
Without tiers, the senior writer applies Tier 1 effort to every proposal. The pipeline becomes a queue, deadlines slip, and the volume drops. With tiers, the right level of attention reaches each opportunity, and the program scales linearly with capacity rather than collapsing under volume.
Capacity math
A reasonable working ratio for a $5M nonprofit’s grant writing operation:
- One full-time senior writer (1.0 FTE): produces 25 to 40 proposals per year across all tiers
- Program staff input (0.2 FTE equivalent across multiple program leads): supplies detail
- Reviewer time (0.1 FTE equivalent): peer + CFO + ED
- Optional: 0.25 FTE junior writer or contracted freelancer for Tier 3 overflow
A two-writer team (1 senior, 1 junior or 0.5 contracted) can comfortably submit 40 to 60 proposals per year and handle a federal portfolio. A three-writer team becomes a department and starts to need a manager role separate from the writing role.
The threshold for hiring a second writer is typically 25 to 30 proposals per year sustained. Below that, a senior writer plus contracted overflow is more efficient. Above 50 to 60 proposals per year, the bottleneck is no longer writing capacity but reviewer capacity and program-detail capacity - at which point the right hire is not another writer but a grants manager or a development operations role.
In-house vs freelance vs consultant
In-house is the right model when grant revenue is above $400K annually, the work is steady year-round, and the organization values continuity and institutional knowledge. The writer becomes deeply familiar with the programs, the funders, and the organizational voice.
Freelance is the right model when volume is lumpy, the team is in transition, or the organization needs specialized expertise (federal grants, healthcare research, scientific peer-review proposals). Freelancers can be retained on a monthly minimum or a per-proposal basis. Strong freelancers build relationships with multiple nonprofits and bring cross-pollination of approaches.
Consultant is the right model for setup, training, and one-time strategic projects: launching a federal grants program, pursuing a major capital campaign proposal, or auditing an existing program. Consultants charge $200 to $400 per hour or project-based fees of $20K to $80K. They are not cost-effective for routine writing.
A common hybrid: 0.5 FTE in-house writer + a freelance federal specialist on retainer for the 2 to 4 federal proposals per year + a one-time consultant engagement to set up the boilerplate library and the pipeline tracker. This pattern fits well for $3M to $7M nonprofits transitioning from a fully outsourced model to a structured in-house function.
Pipeline tracking
The pipeline must be visible to everyone who touches it. At minimum, a working tracker shows for each opportunity: funder name, deadline, requested amount, status (researching, drafting, internal review, submitted, awarded, declined), assigned writer, assigned reviewer, and project lead. Status moves through the stages as the proposal advances; the most useful weekly metric is “proposals at deadline this week” and the most useful monthly metric is “proposals by stage.”
Spreadsheets work for the first 20 to 30 active opportunities. Beyond that, a structured tracker prevents missed deadlines and lost program-detail dependencies. GrantPipe was built specifically for this need at mid-sized nonprofits - see the grant management best practices guide for what mature pipeline tracking looks like in practice.
Common structural failures
Three patterns cause structural failure even when individual people are strong:
-
The single point of failure - one writer carries every proposal, every funder relationship, and every program-detail conversation. When that writer leaves, takes parental leave, or burns out, the program collapses for 6 to 12 months.
-
The unowned project lead - proposals require program detail, but no program staff member is formally assigned. The writer scrambles for input the week before deadline, and the proposal goes out with thin substance.
-
The bypassed reviewer - under deadline pressure, the writer skips finance review or executive director sign-off. Proposals go out with budget errors or strategic mismatches that compound over years as the funder relationship matures.
The fix for all three is structural, not motivational: assign roles formally, document them, and build slack into the calendar so the structure holds when one person is unavailable.
Frequently asked questions
How many grant writers does a $5M nonprofit need?
Most $5M nonprofits run with one full-time grant writer or a 0.5 FTE writer plus contracted overflow. The right number depends on grant volume - a writer can produce 25 to 40 well-researched proposals per year if program staff supply the technical detail and the reviewer turnaround is fast. Below 15 proposals per year, a contracted writer is more cost-effective. Above 40, you need a second writer or a structured tiering system.
Should we hire a grant writer or use a freelancer?
Hire when grant revenue is above $400K annually and the work is steady year-round. Use a freelancer when volume is lumpy, when you need specialized expertise (federal proposals, healthcare grants), or when you are testing whether a grant writing function is worth a permanent role. Hybrid models are common: a 0.5 FTE in-house writer for foundation work plus a federal grant specialist on retainer.
What is the role of program staff in grant writing?
Program staff supply the technical detail that the writer cannot invent - population numbers, intervention specifics, evaluation methodology, prior outcomes, partnership descriptions, and budget assumptions tied to actual program operations. The writer translates and structures, but the substance comes from the program. Proposals fail at the program-detail layer more often than the writing layer; under-resourcing program input is the most common structural mistake.
How do you tier proposals by effort?
Tier 1 (federal, $250K+, new funders) gets full senior writer attention and 60 to 120 hours of effort. Tier 2 (foundation renewals, $50K to $250K) follows a template and runs 20 to 40 hours. Tier 3 (small grants under $25K) follows a fixed time budget of 6 to 12 hours and uses heavy boilerplate. Without tiering, every proposal consumes the same effort and the senior writer becomes the bottleneck.
Who reviews grant proposals before submission?
Three reviewers in sequence: a peer writer or development director for narrative, the CFO or finance manager for budget accuracy, and the executive director for strategic fit and signature. Each review produces written comments, the writer revises, and the cycle ends when all three sign off. Skipping the finance review is the single most common cause of post-submission errors and budget-narrative mismatches.
Where to go next
For day-to-day pipeline practice, see grant management best practices. For the writing craft itself, see the grant proposal writing guide. For the broader program structure, see the grant lifecycle guide.
Free resource
Get the Nonprofit Grant Compliance Checklist
A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.
Frequently asked