Grant Writing for Small Nonprofits: A Practical Guide for 2026

2026-03-30 · Jerry Wang

You don't need a grant writer to win grants

Let's get this out of the way first: you don't need to hire a professional grant writer to get funded. Plenty of small nonprofits win grants with proposals written by their executive director, a board member, or a program manager who's never written a grant before.

What you do need is a clear understanding of what funders are looking for and a straightforward way to give it to them.

What funders actually want to see

Every grant application is different, but most funders are trying to answer the same five questions:

  1. What's the problem? Not a vague, global problem. A specific, local, measurable problem that your community faces right now.
  1. What are you going to do about it? Your proposed activities, spelled out clearly enough that someone who knows nothing about your work can follow along.
  1. Why are you the right organization to do it? Your track record, your team, your connection to the community you serve.
  1. How will you know it worked? Measurable outcomes. Not "we will help people" but "we will serve 200 families and 80% will report improved food security at 6 months."
  1. How much will it cost? A realistic, line-item budget that ties directly to the activities you described.

That's it. Everything else in a grant application is some variation of these five questions.

Writing the narrative: section by section

The executive summary

Write this last, even though it goes first. It should be one paragraph that covers the problem, your solution, who benefits, and how much you're asking for. Keep it under 200 words.

Bad example: "Our organization seeks to address the multifaceted challenges facing underserved populations through an innovative, trauma-informed approach."

Better example: "Oak Street Community Center requests $50,000 to expand our after-school tutoring program from 3 to 5 days per week, serving 150 elementary students in East Austin who are currently below grade level in reading."

See the difference? The second one tells you exactly what's happening, for whom, and how much it costs. No jargon. No buzzwords.

The needs statement

This is where you make the case that the problem is real, urgent, and worth solving. Use local data whenever possible. Census data, school district reports, county health statistics, and your own program data are all fair game.

The biggest mistake people make here is going too broad. Don't write about national hunger statistics when you're running a food bank in El Paso. Write about hunger in El Paso. Use data from the El Paso Food Bank, from the local school district's free lunch qualification rates, from the Texas Health and Human Services data for your county.

Funders want to know you understand your specific community, not that you can google national statistics.

The project description

Spell out exactly what you're going to do, when, and for whom. Use a timeline if possible. Be specific about activities, not just goals.

Instead of: "We will provide mentoring services to at-risk youth."

Try: "We will recruit and train 20 volunteer mentors who will each be paired with one student from Jefferson Middle School. Pairs will meet weekly for 90 minutes at our facility from September through May. Our program coordinator will conduct monthly check-ins with each pair and facilitate group activities once per quarter."

The reader should be able to picture your program running. If they can't, you haven't been specific enough.

The budget

Your budget should tell the same story as your narrative. If you described hiring two part-time tutors in the project description, those tutors should show up as line items in the budget. If you mentioned renting space for workshops, the rent should be in there.

Common line items for program grants:

  • Personnel: Staff salaries and benefits (list each position with hours and hourly rate)
  • Supplies: Materials, curriculum, food for participants
  • Equipment: Anything over $500 that lasts more than a year
  • Travel: Mileage, parking, conference attendance
  • Contractual: Outside trainers, evaluators, consultants
  • Indirect costs: Your organization's overhead rate (typically 10-15% for small nonprofits)

Don't pad the budget. Don't lowball it either. Funders review hundreds of budgets and they know what things cost. A realistic budget builds trust.

Outcomes and evaluation

This is where most small nonprofits struggle, and it's also where you can stand out. You don't need a PhD in program evaluation. You need to answer two questions:

  1. What will be different because of this project?
  2. How will you measure that difference?

Use the SMART framework: Specific, Measurable, Achievable, Relevant, Time-bound.

Instead of: "Youth will show improved academic performance."

Try: "By June 2027, 75% of program participants will improve their reading level by at least one grade level, as measured by the STAR Reading Assessment administered at program entry and exit."

Mistakes that get applications rejected

After looking at thousands of grant applications across our platform, here are the patterns we see in rejected proposals:

  • Mismatched scope and budget. Asking for $10,000 to "transform youth education in Texas." That's either too little money or too big a promise.
  • No specifics. Everything is described in vague, aspirational language with no concrete activities or numbers.
  • Copy-paste from a different application. Funders can tell. Especially when you forget to change the other funder's name.
  • Ignoring the guidelines. If they ask for a 5-page narrative, don't submit 12 pages. If they want Times New Roman 12pt, don't use Arial 10pt.
  • Missing the deadline. Obvious, but it happens constantly. Many small nonprofits track deadlines on sticky notes or in someone's memory.

Tools that actually help

You don't need expensive software to write grants, but a few things make the process much less painful:

  • A template library. Save every grant you write. Next time a similar opportunity comes up, you're not starting from scratch.
  • A boilerplate document. Keep an updated file with your mission statement, organizational history, board list, staff bios, and key program statistics. You'll use these in almost every application.
  • Deadline tracking. A shared calendar, a spreadsheet, anything that means you don't find out about deadlines the day before.
  • AI drafting tools. Tools like GrantDrop can generate a first draft of your proposal using your organization's real data. You still need to edit and personalize it, but starting with a structured draft instead of a blank page saves hours.

One more thing

Grant writing is a skill, and like any skill, it gets easier with practice. Your first application will take the longest. Your tenth will take half the time. Keep at it, learn from rejections (most funders will tell you why if you ask), and remember that every funded grant started as someone sitting down and writing the first sentence.

You're closer than you think.