How to Approach a Foundation for a Grant: A Practical Sequence

The development director who emails a foundation a 12-page proposal as a first contact is making the same mistake as a salesperson who sends a contract before the first call. The work is sequenced, and skipping steps does not accelerate the outcome — it forecloses it.

This guide walks through the actual sequence that produces foundation funding: research, first contact, conversation, LOI, proposal, decision, stewardship. Each step is short on its own. Combined, they take months. Done well, they produce funded relationships that compound over years.

Step 1: Research Before You Reach Out

Approaching a foundation without reading their 990-PF is like applying for a job without reading the posting. The 990-PF tells you whether you should approach at all.

What to extract from the 990-PF:

• Stated priorities (Part XV line 2). What the foundation says it funds.
• Actual grants (Part XV line 3). What they’ve actually funded recently. Cross-reference against priorities — sometimes they diverge.
• Geographic patterns. Where recent grants went. If 90% of recent grants are in Massachusetts and you are in Florida, this is unlikely to be a fit.
• Grant size range. Typical, smallest, and largest recent grants. Match your ask to the typical range.
• Application instructions (Part XV line 2). Whether unsolicited proposals are accepted, what the application process is, deadlines.
• Officers and trustees (Part VIII). Names, titles, addresses. Identify the program officer or executive director.

Plus the foundation’s website if they have one. Many smaller family foundations have no website; the 990-PF is the only documentation.

If the foundation explicitly does not accept unsolicited proposals, do not send anything. Move on or find an introduction through your network. For more on 990-PF reading and prospect research, see foundation directory online guide and private foundation grants guide.

Step 2: First Contact (Email)

The first email is short, specific, and addressed to the right person. Aim for 4–6 sentences.

A working template:

Subject: [Your nonprofit name] — alignment with [Foundation]‘s [specific priority area]

Dear [Name],

[Foundation]‘s recent support of [specific grantee or priority — drawn from 990-PF or website] led me to your attention. [Your nonprofit] runs [one-sentence program description], serving [specific population] in [specific geography]. We’re exploring a [size range] investment to [specific outcome]. I’d appreciate a 20-minute conversation to understand whether this aligns with your current priorities. Are you open to a call in the next few weeks?

[Your name and title]

What this does:

• Demonstrates you read the 990-PF or website (specific grantee referenced).
• Names the population, geography, and outcome — not just “great work.”
• Names a request size range early so the foundation can self-select.
• Asks for a conversation, not a check.
• Closes with a clear next step.

What to avoid:

• “We’d love to partner with [Foundation].” Vague.
• Multiple paragraphs of organizational history. Save for the call.
• Attached PDFs of an annual report or proposal. Premature.
• Generic mass-merge salutations. Spot the program officer’s name.

Expect roughly 30–50% reply rates from well-targeted first emails to foundations that accept outreach. Lower rates indicate the email is too long, too generic, or sent to foundations that don’t engage with unfamiliar applicants.

Step 3: The Program Officer Conversation

If a program officer agrees to a call, the conversation has one purpose: learn what the foundation will fund. You are not pitching — you are listening.

Run a 20-minute call this way:

• Minute 0–2: Brief introduction. Two sentences on the organization. State the topic (“We wanted to learn whether our work might align with your current priorities.”)
• Minute 2–10: Ask. Listen.
• Minute 10–15: Brief description of your specific program when invited. Two minutes maximum.
• Minute 15–18: Discuss next steps the program officer suggests.
• Minute 18–20: Confirm follow-up. Thank.

Questions that produce information:

• What’s currently driving the foundation’s priorities within [your alignment area]?
• What kind of organizations have you been funding recently?
• What size grants make sense in this priority area?
• What’s the typical decision timeline?
• Do you accept LOIs first, full proposals, or have an online portal?
• Is there anything in our work I should describe that might help you assess fit?

What you’re listening for:

• “We’re focused on [narrower scope than the public materials suggest].”
• “We’re looking for [specific organizational characteristic — community-led, evidence-based, BIPOC-led, etc.].”
• “We’ve recently funded [signal of what they like].”
• “We’re not currently funding [signal of what to avoid].”
• “Our cycle for [type of grant] opens [specific date].”

This information is unobtainable from any database. The conversation is the source. Capture it in your CRM immediately after the call.

Common conversation mistakes:

• Pitching the whole organization in the first three minutes.
• Asking nothing — turning the call into a monologue.
• Treating the conversation as a sales call rather than a discovery call.
• Not asking about size, timeline, or process.
• Following up immediately with a 12-page proposal regardless of what was said.

Step 4: The Letter of Inquiry (LOI)

When a program officer says “send us an LOI,” they are signaling provisional interest. Treat the LOI as carefully as a full proposal — most rejections happen here.

LOI components (1–3 pages):

• Paragraph 1. Organization snapshot. One paragraph: name, mission, scale, geography, key programs.
• Paragraph 2. Statement of need. Two to three sentences establishing the problem with quantitative grounding.
• Paragraph 3. Proposed work. The program model, target population, key activities, timeline.
• Paragraph 4. Outcomes. Two or three measurable outcomes with specific targets.
• Paragraph 5. Organizational capacity. Brief — why you can deliver.
• Paragraph 6. Request. Amount, purpose, period, total project budget context.
• Closing. Express interest in a full proposal if invited.

Quality bar:

• Specific numbers, not adjectives.
• Outcomes that can be measured.
• A request size that matches what the program officer signaled.
• Language and framing aligned to the conversation.
• Cleanly formatted, properly proofread, sent on time.

For broader proposal-writing principles, see grant proposal writing guide.

Step 5: The Full Proposal (When Invited)

If the LOI clears, the foundation invites a full proposal. The full proposal expands on the LOI, follows any prescribed format, and includes required attachments.

Standard components:

• Cover letter (1 page).
• Proposal narrative (5–10 pages depending on foundation).
• Detailed budget and budget narrative.
• Evaluation plan.
• Organizational capacity section.
• Sustainability section.
• Required attachments (501(c)(3) determination, audited financials, 990, board list, organizational budget).

The proposal documents what the LOI promised. New material should be development of detail (specific outcome targets, evaluation methodology, budget line items) rather than new programs or new requests.

For annotated examples, see grant proposal examples annotated. For the full lifecycle from prospect through closeout, see grant lifecycle guide.

Step 6: Waiting and Following Up

After submission, decision timing varies — typically 60–120 days for a full proposal review.

During the wait:

• Do not nudge unless the published timeline has passed.
• Send relevant updates if material — a major new partnership, an award, a relevant outcome — but only if genuinely relevant.
• Keep the rest of your pipeline moving. Don’t treat any one application as decisive.

On decision:

• Award: Acknowledge within 24 hours. Send a formal thank-you. Outline a reporting plan (even before required). Update your CRM.
• Decline: Acknowledge respectfully. Ask whether feedback is available. Some foundations share, some do not. Add a follow-up note to the calendar in 6–9 months — a declined application this year may be a funded application next year if the work evolves.

Step 7: Stewardship and the Path to Renewal

The first grant is the start of the relationship, not the destination. Most foundations grant repeatedly to organizations they trust. Building that trust is the post-award work.

Stewardship cadence:

• Within 24 hours of award: Acknowledgment.
• Within 30 days: Formal thank-you letter signed by the executive director. Sometimes a board member as well.
• Mid-grant (typically month 6 of a 12-month grant): Optional update to program officer, even if not required.
• End of grant period: Formal narrative and financial report.
• Post-grant: Update at 6 and 12 months on what the grant enabled.

For broader donor-side stewardship principles that apply to foundation relationships, see donor stewardship plan.

Common Approach Mistakes

1. Going to the foundation before going to peer 990s. Reading peer organization 990s reveals which foundations have funded similar work — a much better starting list than keyword searches.

2. Sending a full proposal as first contact. Almost universally fails. Foundations have processes for a reason.

3. Treating all foundations the same. Family foundations, community foundations, mega-foundations, corporate foundations operate differently. See private foundation grants guide, community foundation grants guide, and corporate grants foundation vs. matching.

4. Approaching during a closed cycle. Some foundations only review once a year. Cold-emailing in month 8 of a 12-month cycle wastes time on both sides.

5. Generic conversation prep. Going into a program officer call without having read the 990-PF and recent annual report is professionally embarrassing.

6. Overpromising in the LOI or proposal. Promises become commitments at award. A program promise that the organization cannot deliver becomes a compliance problem.

7. Disappearing after a decline. Many funded grants come from a relationship rebuilt over a year or two from an initial decline. Stewardship of declined applications is real strategy.

A Realistic Timeline

For a single foundation cultivation:

• Week 1: Research (990-PF read, peer 990s, foundation website).
• Week 2: First email outreach.
• Weeks 3–6: Schedule and conduct program officer call.
• Weeks 7–10: Draft and submit LOI.
• Weeks 11–18: LOI review.
• Weeks 19–22: Full proposal drafted (if invited).
• Weeks 23–34: Full proposal review.
• Week 35: Decision.

Roughly 8 months from start to decision. Treat foundation cultivation as a long-cycle investment, not a quick funding response.

Frequently Asked Questions

What if the foundation has no listed program officer? Address the executive director or board chair. For very small family foundations, sometimes the listed contact is a family member or fund administrator.

Should I name-drop existing funders? Selectively, yes. If you have funding from a peer foundation the program officer would respect, mentioning it briefly signals quality. Listing 30 funders does the opposite.

Is it appropriate to ask the program officer to introduce me to other foundations? Sometimes. Once you have a funded relationship, asking for introductions to peer funders is common practice. Asking before any relationship exists is premature.

Can I send the same proposal to multiple foundations? Usually no. Each foundation has different priorities, formats, and emphases. Sending the same boilerplate signals unseriousness. Tailor each.

What if a foundation says “we’ve decided not to fund this year, but reapply next year”? That’s a soft yes for next cycle. Mark it in your CRM, follow up in 9–10 months with material updates, and treat the next application as a continuation of the current relationship rather than a new cold approach.