How to Write a Grant Proposal for a Small Nonprofit (Step-by-Step)

You found a foundation that funds work like yours. The deadline is three weeks away. You have a day job, no grants team, and a blinking cursor. This is the walkthrough I wish someone had handed me the first time.

It assumes you're a small 501(c)(3) (annual budget under ~$2M), applying to a private foundation or corporate giving program. The same steps work for small federal grants, but federal applications add compliance layers we'll flag along the way.

Step 1: Read the RFP twice before you write anything

The RFP (Request for Proposals) is the rubric. Reviewers grade against it line by line. Before you open a blank doc:

• Highlight every required section, page limit, and attachment.
• Note the funder's stated priorities — the exact words they use.
• Find the eligibility checklist. If you're not eligible, stop now and find a different funder.
• Look at past grantees (usually on the funder's website). Do they look like you in size, geography, and focus area? If not, your odds are low — apply anyway only if you have a strong angle.

Step 2: Build a one-page proposal outline

Before drafting any prose, sketch the proposal in bullet points. Most foundation proposals follow this structure:

1. Cover letter or executive summary (½–1 page)
2. Statement of need (1–2 pages)
3. Program description (2–3 pages)
4. Goals, objectives, and outcomes (1 page)
5. Evaluation plan (½–1 page)
6. Organizational capacity (1 page)
7. Sustainability (½ page)
8. Budget and budget narrative (1–2 pages)

If the RFP gives a different structure, use theirs. Never reorganize a funder's sections to suit your narrative.

Step 3: Draft the statement of need first

The need section is the hardest and the most important. Lead with the population you serve and a local, current statistic. Show the gap — what's already being done, why it's not enough. End with a single sentence that makes your program feel inevitable. We have a full needs-statement guide with examples.

Step 4: Describe the program in concrete terms

Reviewers skim. They want to know: who does what, to whom, where, how often, and starting when. A weak program section says "We will provide educational programming to underserved youth." A strong one says: "Two part-time tutors will deliver 90-minute literacy sessions to 24 second-graders at Lincoln Elementary, Tuesdays and Thursdays after school, September 2026 through May 2027."

Include the activities, the staff who run them, the schedule, the location, the number of people served, and the start and end dates. If you have partners, name them and attach letters of support.

Step 5: Write goals, objectives, and outcomes — and know the difference

• Goal: the big-picture change ("Improve third-grade reading proficiency in the Lincoln Elementary attendance zone").
• Objective: the specific, measurable, time-bound milestone ("By May 2027, 75% of participating second-graders will read at or above grade level on the DIBELS assessment").
• Outcome: the change in the participant ("Participants gain an average of 1.5 grade levels in reading fluency").

One or two goals, three to five objectives, and clear outcomes is plenty. Funders distrust proposals with twelve objectives — it reads as unfocused.

Step 6: Lay out an evaluation plan

Name the tool (pre/post survey, DIBELS, attendance log, third-party assessment), the cadence (quarterly, annually), who collects the data, and who reviews it. "We will track outcomes and report to the funder" is not an evaluation plan. See our post on common grant writing mistakes for what reviewers actually want here.

Step 7: Make the case for your capacity

Funders are betting on your organization, not just your program. Briefly cover: your mission and year founded, the staff or volunteers who will run the project (with one-line bios), your annual budget, and one or two recent accomplishments with numbers. If you've never managed a grant of this size, address it directly and name your fiscal controls.

Step 8: Address sustainability honestly

"How will this continue after our grant ends?" is a near-universal funder question, and the worst answer is "We will seek additional grants." Better: name the other revenue streams (earned revenue, individual donors, in-kind support, government contracts), the diversification target, and the realistic outcome — sometimes a program is funded by foundations for its full lifespan, and that's okay if you can defend why.

Step 9: Build the budget and budget narrative

The budget is a table. The budget narrative is a paragraph or two explaining each line item: what it pays for, how you calculated it, and why it's necessary to the program. We cover this in detail in how to write a budget narrative funders actually approve.

Step 10: Cut, then submit

First drafts are always too long. Read each section and ask: does this sentence help a reviewer decide to fund this? If not, delete it. Then check every page limit, every required attachment (board list, 501(c)(3) letter, audited financials, organizational budget, project budget, letters of support, key staff résumés), and submit at least 24 hours before the deadline. Portals crash on deadline day.

How GrantDraft can help

This is a lot of work to do from a blank page. GrantDraft takes your nonprofit's basics and the funder's RFP and generates a full first draft — one section at a time, each editable, each measured against a reviewer rubric. When the model doesn't know a specific fact about your nonprofit, it inserts a "[INSERT: …]" placeholder instead of inventing one. You fill in the real numbers, sources, and partner names.

Try GrantDraft free — your first grant draft is on us.