Foundation Grant Proposals

Foundation grants operate by a different logic from federal research grants. Foundations have specific theories of change. They fund what advances those theories. The proposal that wins is one that demonstrates alignment with the foundation's mission and shows that funding your work is the most efficient path to the foundation's goals.

## Key Points

- **The mission statement.** What does this foundation exist to do?
- **The strategy or theory of change.** How does the foundation think change happens? What is its model?
- **The grant guidelines.** What kinds of organizations and projects does it fund? What are the dollar ranges? What are the geographic and topical scopes?
- **Recent grants.** What has the foundation funded in the last 2–3 years? What does that say about its current priorities?
- **The annual report.** What does the foundation say about its work? What outcomes does it celebrate?
1. **Opening paragraph.** What you're asking for, in one sentence. Amount, duration, project name. The foundation officer wants to know in 15 seconds whether to keep reading.
2. **Problem and mission alignment.** The problem you address. How it aligns with the foundation's mission. Use the foundation's language where appropriate; signal you've read their strategy.
3. **Project overview.** What you'll do. Who you'll serve. How you'll know it worked.
4. **Organizational capacity.** Why your organization is positioned to succeed. Track record briefly. Key partnerships if relevant.
5. **Budget and ask.** The total project budget; the amount you're requesting; what other funders are or might be involved.
6. **Closing.** A specific next step if there's interest.
- This is new work; we're seeking initial seed funding.

Foundation grants operate by a different logic from federal research grants. Foundations have specific theories of change. They fund what advances those theories. The proposal that wins is one that demonstrates alignment with the foundation's mission and shows that funding your work is the most efficient path to the foundation's goals.

This shifts the proposal's center of gravity. Federal grants center on technical merit and feasibility; foundation grants center on impact and fit. Both matter for both, but the emphasis differs.

Know the Foundation

Before writing a single sentence, study the foundation. Read:

• The mission statement. What does this foundation exist to do?
• The strategy or theory of change. How does the foundation think change happens? What is its model?
• The grant guidelines. What kinds of organizations and projects does it fund? What are the dollar ranges? What are the geographic and topical scopes?
• Recent grants. What has the foundation funded in the last 2–3 years? What does that say about its current priorities?
• The annual report. What does the foundation say about its work? What outcomes does it celebrate?

A proposal that shows you've done this homework — by alignment with the foundation's specific framing of the problem — has a head start. A proposal that sounds like it could go to any funder loses immediately.

Letter of Inquiry (LOI)

Most foundations require a Letter of Inquiry before a full proposal. Treat the LOI as the most important 1–2 pages you'll write to that foundation.

LOI structure:

1. Opening paragraph. What you're asking for, in one sentence. Amount, duration, project name. The foundation officer wants to know in 15 seconds whether to keep reading.
2. Problem and mission alignment. The problem you address. How it aligns with the foundation's mission. Use the foundation's language where appropriate; signal you've read their strategy.
3. Project overview. What you'll do. Who you'll serve. How you'll know it worked.
4. Organizational capacity. Why your organization is positioned to succeed. Track record briefly. Key partnerships if relevant.
5. Budget and ask. The total project budget; the amount you're requesting; what other funders are or might be involved.
6. Closing. A specific next step if there's interest.

Foundations receive far more LOIs than they accept. Yours has to stand out for clarity, alignment, and concreteness. If you survive the LOI, you'll be invited to submit a full proposal.

The Full Proposal

When invited to a full proposal, build it around what the LOI promised. The foundation officer is your advocate at this point; make their job easier.

Sections:

Statement of Need

The problem and why it matters. Specific. Quantified where possible. Local context where relevant.

The Need section should make the reader feel the problem. Not just statistics; a description that brings the problem into focus. A specific community. A specific struggle. A specific gap.

Don't manufacture urgency. Foundation officers can tell. Make the case calmly with the facts.

Project Description

What you'll do. The activities, the timeline, the participants, the outputs.

Foundation officers want concreteness. Not "we will work to address" but "we will deliver 12 workshops to 240 participants over 18 months, producing X." Specific verbs, specific numbers.

Theory of change should be visible: if you do A, then B, then C will happen. The reader should be able to follow the chain.

Outcomes and Evaluation

What success looks like. Measurable outcomes, with the methods you'll use to measure them.

Outcomes are not activities. "240 participants completed the workshops" is an output. "180 of those 240 demonstrated improved [specific skill], measured by pre-post assessment" is an outcome.

Pick outcomes that are meaningful and that you can credibly measure. Foundations are skeptical of grandiose outcome promises with weak measurement plans. Modest, well-measured outcomes outperform ambitious, hand-waved ones.

Organizational Background

Who you are. Why you can do this work. Track record on similar projects. Key staff. Board composition (for nonprofits).

Foundation officers fund track records. New organizations have a harder path; show institutional capacity through partnerships, advisory boards, or fiscal sponsors.

Budget

Detailed budget with line items and a budget narrative explaining each. Foundations want to see how their money will be spent.

Most foundations have specific rules about overhead/indirect costs. Read them. Stay within their limits.

The "leverage" view: what other funders will contribute to this work. Foundations like to see they are not the sole source.

Sustainability

What happens after the grant ends. Will the work continue? How? Funded by what?

Many foundations care about sustainability because they fund time-bounded projects but want lasting impact. A proposal that has no answer to "what happens after the grant" worries the reviewer.

The Narrative

Foundation proposals are read as narrative more than research grants are. The reviewer wants to feel the work; they want to picture the people served; they want to be moved.

The narrative voice is calibrated. Not promotional; not academic. Engaging but professional. Stories of specific beneficiaries (anonymized appropriately) help. Quotes from program participants help. Photographs (if the foundation accepts them) help.

Avoid: melodrama, manufactured urgency, manipulative storytelling. Foundation officers see through it. Honest, specific, restrained narrative wins.

The Match Question

Many foundations want to know: who else is funding this work? Why isn't the entire need being met by other funders?

Honest answers:

• This is new work; we're seeking initial seed funding.
• We have other funders, but the need is greater than current commitments.
• This foundation is the right fit for this specific component of a larger funded project.

Don't position the foundation as the savior of last resort. They aren't. They are one of many funders making allocation decisions.

Site Visits and Conversations

Many foundation grants include a site visit or a meeting with program officers. These are opportunities; treat them as such.

Preparation:

• Know who is coming and their role at the foundation.
• Have a focused agenda. The visitor's time is limited; know what you want them to see and what you want to discuss.
• Bring the program leaders, not just executives. Foundation officers want to hear from the people doing the work.
• Be honest about challenges. The foundation officer asks about what's hard because they want to know if you can handle it. Pretending things are easy makes you look naive.

Reporting

When funded, the work begins, including the reporting. Foundations require reports — usually mid-grant and end-of-grant. Read the reporting requirements before you submit.

Reports are an opportunity to:

• Demonstrate the work is on track.
• Surface challenges and how you're addressing them.
• Build the relationship for future funding.

Reports that overpromise and underreport ruin foundation relationships. Reports that are honest about what's working and what isn't build trust.

Building Relationships

Foundation funding is relational. The same officers fund repeatedly; the trust built on one grant pays off on the next.

Relationship-building:

• Meet with program officers when invited.
• Update them between grant cycles. Brief, occasional updates ("we just hit X milestone, thought you'd want to know").
• Share the work publicly in ways that credit the foundation appropriately.
• Be reliable. Submit reports on time. Spend the money on what you said you would.

The foundation that funded you once is more likely to fund you again than a foundation you've never engaged. Cultivate the relationship.

Anti-Patterns

Boilerplate proposal. Same proposal sent to multiple foundations with name swapped. Officers can tell. Customize each.

No mission alignment. The proposal sounds like it could go to any funder. Show you read the foundation's strategy; align.

Activities instead of outcomes. "We will offer workshops" — that's an activity. "Participants will demonstrate measurable improvement on X" — that's an outcome.

Manufactured urgency. Melodramatic opening; manipulative storytelling. Foundation officers see through it.

No sustainability plan. Reviewer worries the work ends when the grant does. Address it.

Inflated track record. Claiming work the organization didn't do. Foundation officers verify.

Late or vague reports. Damages the relationship. Submit on time; be specific.