Milan Bogojevic Blog

How Many Grants Should a Two-Person Team Actually Apply To?

7 min read

Grant application folders and a notebook with sticky notes on a wooden desk beside an hourglass and a clock.
Grant application folders and a notebook with sticky notes on a wooden desk beside an hourglass and a clock.

A two-person development team should apply to roughly as many grants as their realistic proposal hours divide into, not as many as they're eligible for. Count the hours each application actually takes, divide your available proposal hours by that figure, then hold back a 20 to 30 percent margin for your strongest opportunities. This is my planning rule, not a sector standard.

Why this matters for a small nonprofit team

"Apply to everything we qualify for" feels like the safer strategy, since more attempts should mean more wins. In practice, a small team has a fixed number of proposal hours per cycle, and every hour spent on a weak, rushed application is an hour not spent making a strong one stronger. Spreading the same total hours across more applications usually lowers the average quality of each one, which can lower the overall win rate even as the raw number of submissions goes up.

The nonprofit reality: a disclosed, hypothetical example

Imagine a two-person development team (a director who also runs programmes part-time, and one grants coordinator) with twelve eligible funders on their list for the quarter. Historically, they win about one in four of the applications they submit when they have real time to prepare each one properly, and closer to one in ten when they're rushing to hit a volume target.

If they apply to all twelve, spreading roughly 15 hours of actual work across each one, they're likely to win around one or two, because the rushed pace pushes their win rate toward the lower end. If they instead select the six best-timed, best-fitting opportunities and spend close to 30 hours on each, preparing a stronger budget narrative, cleaner outcome data, and a tighter case, their win rate should sit closer to the one-in-four range, putting the expected number of wins at roughly the same level, for half the total submissions and, usually, a visibly stronger application in the ones that don't win either, which matters for the relationship going into next cycle.

This is illustrative math, not a measured outcome, but it shows the mechanism: doubling the number of applications doesn't double the number of wins if it also halves the preparation time behind each one.

The Annual Proposal Budget

I treat proposal hours the same way I'd treat money: as a fixed annual budget to allocate deliberately, not a resource that stretches to fit however many opportunities show up. The calculation has four inputs, and it produces a number, not a feeling.

Step What to calculate Example input
1. Available hours Total hours per year your team can realistically spend on proposal writing, after programmes, admin, and existing reporting commitments 2 staff x 4 hours/week x 45 working weeks = 360 hours/year
2. Hours per application Honest average hours from first draft to submission, based on your own past applications, not an aspirational estimate 25 hours per application (drafting, budget, attachments, internal review)
3. Raw capacity Available hours divided by hours per application 360 / 25 = roughly 14 applications/year
4. Quality-adjusted capacity Raw capacity, reduced by a margin (my rule of thumb is 20 to 30 percent) to leave room for your strongest opportunities to get more than the average hours 14 x 0.75 = roughly 10 to 11 applications/year

The fourth step is the one most teams skip, and it's the one that actually protects win rate. Treating every application as equally deserving of the average hours means your best-fit, best-timed opportunities get the same rushed treatment as your long-shot ones. Reserving a margin lets you give two or three of your strongest opportunities extra hours, usually by pulling them from your weakest, lowest-probability ones instead of adding more total hours.

Build this on your own numbers, not an industry rule of thumb

There's no universal number of "hours per grant" or "ideal applications per year" that applies across organisations, because it depends entirely on your team's actual speed, the complexity of the funders you pursue, and how much of your reporting infrastructure is already reusable between applications. After each application this year, log the actual hours it took, separate from the time spent on the programme work itself. By next cycle, you'll have your own real average instead of a borrowed one, the same habit covered for reporting hours in Read the Reporting Burden Before You Read the Grant Amount.

My view

My rule is that a shortlist of twelve eligible funders is not a target, it's a starting point to be cut down deliberately. I'd rather a small team submit eight strong, well-timed applications than fourteen rushed ones, even though fourteen looks more productive on an activity report. The Annual Proposal Budget exists to make that trade-off visible before the cycle starts, instead of discovering it in March when every application has been under-prepared because the list was never actually narrowed.

What to do next

  • Calculate your team's available annual proposal hours, after subtracting time already committed to programmes, reporting, and admin.
  • Log the real hours your last three to five applications took, from first draft to submission, to get an honest hours-per-application figure instead of a guess.
  • Divide available hours by hours-per-application, then apply a 20 to 30 percent margin to get your quality-adjusted capacity for the year.
  • Compare that number against your current shortlist, and if the shortlist is longer, cut it using the timing and fit signals, not just by funder size.
  • Reserve part of your margin deliberately for your two or three best-timed opportunities each cycle, rather than splitting hours evenly across the whole list.

Conclusion

The instinct to apply to every eligible opportunity treats proposal writing as free, when it's actually the scarcest resource a small development team has. A capacity-based limit isn't a reason to be less ambitious, it's what protects the quality of the applications that actually have a realistic shot, instead of spreading the same fixed hours thin enough that none of them do. The number that matters isn't how many grants you're eligible for, it's how many your team can prepare well.

FAQ

What if we have more strong-fit funders than our capacity allows?

When a nonprofit has more well-matched funders than it can handle, prioritize opportunities with the strongest timing signals in the current cycle. Defer the remaining applications so each selected proposal receives enough preparation time.

Does adding a volunteer or part-time grant writer change this calculation?

Yes. Add the realistic proposal-writing hours contributed by a volunteer or part-time grant writer to the team’s available annual hours, then divide by the average hours per application and apply the quality margin. The formula stays the same; the available capacity changes.

Should every application get the same number of hours?

No. The quality-adjusted margin exists specifically so your strongest, best-timed opportunities can receive more hours than your weaker ones, pulled from the applications you choose to skip rather than added on top of your total capacity.

How is this different from just tracking a win-rate percentage?

Win rate measures the share of submitted applications that succeed; an hours-based proposal budget estimates how many applications the team can prepare well. Track both to assess workload and results. A lower win rate may warrant reviewing proposal quality and funder fit, but a small number of submissions cannot establish the cause.

Sources

About the author

Milan Bogojevic works on nonprofit grant intelligence, funding decisions and AI-assisted proposal processes for teams with limited capacity.

Last updated: 10 October 2026.

Next in Grant Intelligence