Grant Writing Basics: Your First Foundation Application

Every grant proposal answers the same underlying question a funder is asking, whether they say it directly or not: "Why should I invest in this organization over the many others competing for these limited funds?"

Answering that well requires being specific, compelling, and honest. Generic proposals that could describe any organization working in your issue area get rejected, because they give the funder no reason to pick you specifically. Proposals tailored to the funder's stated priorities and grounded in real organizational specificity — actual numbers, actual names, actual outcomes — are what get funded.

Why this framing matters: thinking of a grant application as "asking for help" leads to vague, hopeful writing. Thinking of it as "making a case for investment" leads to writing that gives the funder exactly what they need to say yes — evidence, a plan, and accountability.

The single highest-leverage thing you can do before writing anything is to understand your funder thoroughly:

• ›What are their stated priorities? Read their website, annual report, and grant guidelines closely — not skimmed.
• ›What did they fund last year? Most foundations publish grantee lists. Look for organizations similar to yours in size, issue area, and stage.
• ›What size grants do they typically make? Apply within their normal range — asking for far more or far less than their typical grant signals you haven't done your homework.
• ›Can you get a pre-application call? A conversation with a program officer before submitting is one of the most effective things you can do — it lets you tailor your proposal to their real interests and signals that you're a serious, prepared applicant, not someone mass-applying.

Only apply if your work genuinely fits their priorities. Off-target proposals waste your limited writing time and can burn a relationship for future cycles — program officers remember applicants who clearly didn't read the guidelines.

Every funder has their own format, but most applications ask for some version of these components — understanding why each one exists helps you write it well, not just fill in the blank.

1. Executive summary (1 paragraph–1 page). Often the only section some reviewers read before deciding whether to keep going. Cover who you are, what you do, who you serve, what outcomes you achieve, how much you're requesting, and what the funds will accomplish. Why it matters: it's your one shot to earn the reviewer's full attention for the rest of the application.

2. Organizational background (1–2 pages). Your history, mission, programs, and key accomplishments. If you're new, lean on your leadership team's relevant experience. Why: funders are assessing execution risk — can this team actually deliver what they're promising?

3. Statement of need (1–2 pages). Why this problem matters and why your community specifically needs this work. Use local data — it's far more compelling than national statistics because it proves you understand the specific gap you're filling, not just the general cause. Describe your beneficiaries' need for services, not your organization's need for funding — those are different arguments, and funders can tell which one you're making.

4. Program description (2–3 pages). What you'll actually do with the funds: specific activities and delivery methods, who delivers them (credentials matter), a timeline, expected participant numbers, and how participants are recruited and selected. Why specificity matters here above all: "vague" is the single most common reason funders cite for rejection.

5. Evaluation plan (1 page). How you'll know the program worked — specific outcome metrics, how you'll collect the data, who's responsible, and how you'll report back. See the companion lesson on Impact Measurement for how to build this properly.

6. Budget (1–2 pages). A line-item budget for the grant period: personnel (position, % time on this grant, salary, benefits), non-personnel direct costs, and indirect/overhead. Most funders allow an indirect cost rate in the 10–20% range for overhead — the federal "de minimis" indirect rate that agencies must accept without further justification is currently 15% of modified total direct costs. Always include an indirect rate. Under-budgeting overhead doesn't make you look lean; it quietly starves your organization of the money it needs to actually run the program well.

7. Organizational budget. Your full annual budget, usually requested separately, showing all revenue and expenses — this lets the funder see your grant in the context of your whole operation.

If funded: send a thank-you, meet every reporting deadline, and keep building the relationship — foundations preferentially renew grants to organizations they already trust and who make their job easy.

If rejected: ask for feedback. Many program officers will explain why an application wasn't selected, and that input is some of the highest-quality free consulting you'll ever get. Apply again next cycle if your work still fits their priorities — a "no" this year is often just "not this round."

Set your expectations correctly: most community foundation grant pools are oversubscribed 3-to-1 or more, so even excellent, well-aligned proposals get rejected regularly. A roughly 30% acceptance rate on genuinely strong proposals is considered good in this field. Treat rejection as data about how to improve the next application, not as a verdict on your organization.