July 5, 2026 · 9 min read

How to Write a Grant Proposal: A Step-by-Step Guide for Small Nonprofits

If you run a small nonprofit, you already know the frustrating math of grant writing: professional grant writers charge $50–$150 per hour, a single proposal takes 15–40 hours to produce, and most small organizations submit applications with a two-person team squeezing the work between programs, fundraising events, and everything else. This guide walks you through the entire process, step by step, so you can write a competitive proposal without a professional on staff.

Before you write a single word

Step 1: Read the funder's guidelines twice

More proposals die here than anywhere else. Every funder publishes priorities, eligibility rules, deadlines, word limits, and required attachments. Read them once to understand the opportunity, then a second time with a highlighter, marking every requirement. If the funder says they support "youth education in rural counties" and you run an urban senior program, stop — no amount of good writing fixes a bad fit. Applying to well-matched funders is the single highest-leverage decision in grant writing.

Step 2: Collect your raw material

Strong proposals are built from specifics, and hunting for specifics mid-draft is what makes writing take weeks. Before drafting, gather: your mission statement, program descriptions, the number of people you serve, outcomes and results from past work, your annual budget, staff and volunteer counts, and any data about the problem you address. Keep this in one document — you will reuse it for every proposal you ever write.

Step 3: Define the project, not just the need

Funders don't fund needs; they fund plans. "Children in our district are behind in reading" is a need. "A 12-week after-school tutoring program serving 60 children, staffed by 2 teachers and 10 trained volunteers, costing $25,000" is a fundable plan. Be able to answer: what exactly will you do, for whom, over what period, at what cost, and how will you know it worked?

The standard proposal structure

Most grant proposals follow a six-section structure. Some funders use their own application forms with different questions, but the same content applies — you'll just rearrange it.

1. Executive summary (200–300 words)

Written last, read first. Summarize the problem, your organization, the proposed project, the amount requested, and the expected impact — in that order. A program officer skimming fifty applications decides in this half-page whether yours deserves a careful read. Every sentence must earn its place.

2. Statement of need (300–500 words)

Describe the specific problem your project addresses. Use local data where you can: "42% of third-graders in our county read below grade level" beats "literacy is a national crisis." Explain why the problem matters now and why your organization is positioned to address it. Avoid melodrama — funders read emotional appeals all day; concrete evidence stands out.

3. Goals and objectives (250–400 words)

Goals are broad outcomes ("improve reading proficiency among elementary students"). Objectives are specific and measurable ("60 students will improve reading scores by one grade level within 12 weeks, measured by pre/post assessment"). Write 1–2 goals and 3–5 objectives beneath them. If an objective doesn't contain a number and a timeframe, tighten it until it does.

4. Methods and activities (300–500 words)

This is your "how." Walk through what will actually happen: who does what, when, and where. Connect every activity back to an objective. A simple timeline (month 1: recruit and train volunteers; months 2–4: run sessions; month 5: assessment and reporting) shows the funder you've thought it through operationally, not just aspirationally.

5. Budget narrative (250–400 words)

Alongside your line-item budget (usually a separate attachment), the narrative explains the numbers in prose: what the money buys and why each cost is reasonable. Personnel, program materials, administration — walk through the major categories. Never pad the budget; experienced program officers spot inflation instantly, and it damages trust in the entire application.

6. Evaluation plan (250–350 words)

How will you know the project worked? Name the indicators you'll track, how you'll collect the data (attendance logs, pre/post tests, surveys), and how you'll report results to the funder. Small nonprofits often fear this section, but funders don't expect academic research — they expect you to have a credible way of measuring what you promised.

Writing tips that separate funded proposals

Mirror the funder's language. If their guidelines say "food insecurity," don't write "hunger relief." Program officers scan for alignment with their published priorities.

Be specific everywhere. Numbers, names, places, timeframes. Specificity is credibility. Vague proposals read like wishful thinking; specific ones read like plans.

Never invent data. If you don't have a statistic, write around it honestly. One fabricated number discovered by a funder ends the relationship permanently.

Respect word limits ruthlessly. Going over limits signals you can't follow instructions — a red flag for how you'll handle reporting requirements if funded.

Get one outside reader. Someone who knows nothing about your program should understand exactly what you plan to do after one read. If they can't explain it back to you, revise.

How long should this take?

Done manually from scratch, a first proposal typically takes 20–40 hours. With your organizational material collected in one place (step 2 above) and a clear structure, experienced teams get this down to 8–15 hours. AI-assisted tools like GrantEasy compress the drafting stage further — generating a structured first draft from your organization's profile in minutes, so your time goes into refining and tailoring rather than staring at a blank page. The thinking is still yours; the blank page problem disappears.

The mindset that wins grants

Rejection is normal — even excellent proposals face funding rates of 10–30%. The organizations that win consistently treat grant writing as a pipeline, not a lottery ticket: they apply to multiple well-matched funders, reuse and adapt their core content, track deadlines systematically, and improve each proposal based on feedback. Write one genuinely strong proposal, and you've written the raw material for the next ten.