The most common mistake in grantseeking is treating a foundation like a vending machine: insert proposal, receive money. In reality, grants are relationships. The organizations that win — and keep winning — build genuine, human connections with the people behind the money: program officers. A program officer is your guide, your advocate inside the foundation, and the person who can tell you in five minutes whether your idea is worth a 20-hour proposal.
This page walks the full relationship arc: how to approach a program officer, how to run the initial inquiry call or email, what to do at a site visit, how to steward a funder between grant cycles, and — the part everyone needs but few prepare for — how to read a rejection, request reviewer feedback, and decide whether to re-apply. There is a sample outreach email you can adapt below.
Practices vary by funder; community foundations, family foundations, and large national funders all behave differently. Treat what follows as defaults to confirm against each funder's stated process — verify, as of 2026.
Why grants are relationships, not transactions
Behind almost every foundation grant is a person — the program officer — who reviews proposals, recommends them to a board, and manages the funder's relationship with grantees. The Council on Foundations and Candid Learning both describe the program officer role as relational and advisory, not just gatekeeping. That person can tell you whether your project fits before you write a word, flag a deadline you'd have missed, and advocate for you in the room where decisions get made.
This matters because the economics of grantseeking are brutal without a relationship. Most foundations fund a minority of the proposals they receive, and a cold proposal into a funder you've never spoken to is a long shot. A single qualifying conversation can save you from writing a proposal that was never going to fit — and warm relationships are how a one-time grant becomes a renewable, multi-year partnership.
The relationship mindset
- Your goal in early contact is mutual qualification, not pitching — is this a fit for both sides?
- The program officer is a person doing a job, often overloaded; be brief, prepared, and easy to help.
- Every interaction is part of one long relationship — the report you file this year shapes next year's grant.
- Funders fund organizations they trust, and trust is built over time, not in a single application.
None of this replaces the basics. Relationships open doors; a strong, fundable program walks through them. If your fundamentals aren't in place yet, start with how to get grant-ready before investing in outreach.
How to approach a program officer
Before you contact anyone, do the homework. Funder relations starts with prospect research: confirm the foundation funds your cause, your geography, and your size of organization, and that they've recently funded work like yours. Read their guidelines closely — many foundations explicitly state whether they welcome pre-proposal contact or accept proposals by invitation only. Respect what they say. Contacting a funder who asks for no contact is a fast way to start on the wrong foot.
When the guidelines allow contact, your first job is to earn a short conversation. Lead with evidence that you've done your research: reference a specific grant they made or an initiative they launched. Be specific about who you are and what you do, and make a small, clear ask — usually a brief call to check fit.
| Do | Don't |
|---|---|
| Read and follow the funder's stated contact rules | Cold-call a funder who says "no unsolicited contact" |
| Reference their actual grantmaking specifically | Send a generic, copy-paste email |
| Ask a focused question about fit and process | Pitch your whole project in the first message |
| Keep the first ask small (a short call) | Attach a 12-page proposal nobody invited |
| Be warm, concise, and easy to say yes to | Be vague about who you are or what you want |
One reframe that helps: you are not asking for money in the first contact — you're asking whether it makes sense to invest each other's time. That posture is honest, lowers the stakes, and tends to get a response.
The initial inquiry call and email
The inquiry — sometimes a short email, sometimes a brief call — is where fit gets tested. Keep the written version tight. A widely used rule of thumb is roughly 150–250 words, short paragraphs, plain language, so a busy officer grasps your core message in under a minute (as of 2026 — verify against the funder's own format). Open with your research-based hook, state who you are and the problem you address, name the rough amount and purpose, and close with a low-pressure request for a short conversation.
If you get a call, prepare like it's an interview, because it is. Have a short list of questions ready so you use the time well. The most valuable questions probe fit and process:
- Fit: "Based on what I've described, is this the kind of work you're looking to fund?"
- Process & timing: "What's your typical review timeline, and when's the best window to apply?"
- Format: "Do you prefer a full proposal or a letter of inquiry first?"
- Budget: "What grant size is realistic for a first-time grantee?"
- Strengthening the ask: "What would make a proposal like this competitive for your board?"
Then listen more than you talk. If the officer signals it isn't a fit, thank them and ask if they can suggest a better-suited funder — many will, and that referral is gold. If it is a fit, confirm the next step and the timeline in writing afterward.
Inquiry-call etiquette
- Confirm how much time they have and respect it
- Be honest about challenges, not just wins — it builds credibility
- Take notes; you'll need the details for the proposal
- Send a short thank-you within a day, summarizing next steps
Worked example: a program-officer outreach email
Here is a sample initial inquiry email you can adapt. Note the structure: a research-based opening line, a one-sentence identity, the problem and your approach, a specific amount and purpose, and a small ask. It runs about 190 words — within the 150–250 range many practitioners recommend (as of 2026 — verify).
| Element | Sample text |
|---|---|
| Subject | Inquiry: youth literacy program — fit for the Riverside Foundation? |
| Opening hook | "Dear Ms. Alvarez, I read that the Riverside Foundation recently funded the Eastside Reading Corps, and your focus on early literacy in under-resourced schools closely mirrors our work." |
| Who we are | "I'm the executive director of Maple Street Learning Center, a 501(c)(3) serving 240 K–3 students in the Maple Street corridor." |
| Problem & approach | "Two-thirds of the children we serve read below grade level. Our tutoring program pairs each child with a trained volunteer twice a week, and last year 78% of participants advanced at least one reading level." |
| Amount & purpose | "We're seeking roughly $25,000 to extend the program to a second school next year." |
| The ask | "Before I prepare anything formal, would you be open to a brief 15-minute call to see whether this is a fit for your current priorities? I'm grateful for your time either way." |
| Close | "With appreciation, [Name, title, phone, email]" |
Numbers and names here are illustrative. Replace every figure with your own verified data, and check the foundation's guidelines before sending — some accept inquiries only through an online portal.
Before you hit send
- Addressed to a real person by name, spelled correctly
- References something specific and true about the funder
- States who you are and your 501(c)(3) status plainly
- Includes one concrete outcome number you can back up
- Names a rough amount and clear purpose
- Makes one small, easy-to-grant ask
- Under ~250 words, no uninvited attachments
- Follows the funder's stated contact rules
The site visit: when a funder comes to see you
For larger or later-stage grants, a program officer may request a site visit — a chance to see your work in person before deciding. This is good news; it means you're being seriously considered. Practitioner guidance from sources like Candid Learning consistently frames the visit as a relationship-builder, not an interrogation.
Before the visit, ask logistics: who's coming, how many, how long, and whether there's anyone specific they'd like to meet. If you have questions for them, send them a few days ahead. Brief your team and, if you can, arrange for one or two board members to attend alongside the executive director — board presence signals organizational commitment. Confirm the appointment the day before.
During the visit, open with a short overview of why the work matters, then show the program in action — seeing the work beats any paper application. Be candid about challenges as well as successes; funders trust organizations that are honest about what's hard. Be welcoming and personable; you're hosting a guest in your house.
After the visit, send a prompt thank-you, answer any open questions, and provide anything you promised. The visit is a milestone in a relationship you hope grows year over year.
What funders are quietly assessing
- Capacity — can your team actually deliver what you propose?
- Clarity — are your goals and outcomes well defined?
- Sustainability — what happens to the work after this grant ends?
- Impact — is there real, measurable change for the people you serve?
That sustainability question is the one most nonprofits fumble. Funders want to back programs that aren't fully dependent on the next grant. Being able to point to durable, diversified income — and how you measure outcomes — turns a good visit into a confident yes.
Stewardship between grant cycles
The biggest missed opportunity in grantseeking is going silent after the check clears and only resurfacing when you want more money. The strongest funder relationships are tended between cycles, when nothing is being asked for. Stewardship of an institutional funder borrows directly from donor stewardship: report well, acknowledge generously, and keep the relationship warm.
- Report on time, every time. Nothing builds funder trust faster than a clean, punctual report. See grant management & reporting for the mechanics.
- Share good news unprompted. A two-line email when a milestone is hit — "thought you'd want to see this" — keeps you top of mind without asking for anything.
- Be honest when things go sideways. If a program hits trouble, tell the funder early. Funders renew grantees who surface problems, not those who hide them.
- Acknowledge properly. Thank the funder the way their agreement specifies, and recognize them where appropriate.
- Invite them in. A program event, an annual update, or an offer to visit keeps the relationship human.
Treat stewardship as a year-round system, not a scramble. A simple grants calendar and pipeline that tracks report dates, check-in touches, and re-application windows keeps every funder relationship moving forward — and makes the next ask far easier. For deeper work on this, see building funder relationships as an ongoing discipline.
After a no: reading rejection, getting feedback, re-applying
You will be rejected. Even excellent organizations are turned down far more often than funded — most funders have far more good applicants than dollars. A no is rarely a verdict on your worth; it's often about fit, timing, or a crowded field. What separates organizations that eventually win is how they handle it.
First, read the letter carefully — but don't over-read it. Rejection letters are often vague ("highly competitive cycle," "not a fit at this time") and may not reveal the real reason. Don't assume the stated language is the whole story, and don't spiral over boilerplate.
Second, ask for feedback — graciously. A brief, professional follow-up requesting comments or scoring is one of the highest-value moves in grantseeking: it gathers information and keeps the relationship open. Some funders share detailed feedback; many won't, and that's their prerogative. Whatever you receive, accept it without arguing. Say thank you, ask clarifying questions, and never debate the decision — arguing won't reverse this grant and will poison the next one.
A clean feedback request
- Thank them sincerely for considering your proposal
- Ask if they'd be willing to share what would make a future application stronger
- Ask whether re-applying in a future cycle would be welcome
- Keep it short, warm, and free of any defensiveness
- Whatever they say, reply with gratitude — not a rebuttal
Third, decide whether to re-apply. Use a simple test: is this still a genuine fit, and can you meaningfully improve the proposal? If the rejection points to fixable problems — a weak narrative, a shaky budget, missing alignment with funder priorities — re-applying with a stronger package is often a smart investment. If the funder simply doesn't fund your kind of work, your energy is better spent finding funders who do; revisit how to find grants.
| Signal in the no | Likely move |
|---|---|
| "Strong proposal, very competitive cycle" | Re-apply next cycle; stay in touch meanwhile |
| Specific, fixable critique (budget, outcomes, clarity) | Fix it, get an outside review, re-apply stronger |
| "Outside our funding priorities / geography" | Move on; find better-fit funders |
| No reason given, no feedback offered | Send a gracious note, keep the door open, reassess fit |
Before resubmitting, have someone outside your organization read the revised proposal — a peer, advisor, or grant writer often spots what you can't. The most resilient organizations don't pin their hopes on any single funder; they keep a healthy pipeline of prospects at different stages, so one rejection is a setback, not a crisis.
Build an income base that doesn't depend on the next grant
Funders fund organizations that can answer the sustainability question. With Good Circles, supporters pick your cause once, then a share of their everyday local spending funds you automatically — about $72 per active supporter per year, roughly $36,000 a year from 500 supporters. It's recurring, unrestricted, and free to join. An estimate, not a guarantee — but exactly the kind of durable base that makes a site visit go well.
Claim a Founding Nonprofit spot →Sources & tools
Free first
- Candid Learning — Free and low-cost trainings, webinars, and a knowledge base on fundraising, proposal writing, and funder relations — including sample letters of inquiry and proposals.
- Council on Foundations (cof.org) — The membership body for grantmakers; its resources help you understand how foundations and program officers actually work, which sharpens how you build relationships with them.
- National Council of Nonprofits — Practical, free guidance on fundraising, grants, and nonprofit operations, plus links to state associations that often run local funder-relations training.
Paid — optional labor-savers
- A grants consultant — An experienced grants consultant or grant writer who can advise on funder strategy, sharpen proposals, and in some cases open doors through existing relationships with program officers. Worth it when Worth it when you're trying to break into new institutional funders, have a strong program but limited internal grant-writing capacity, or keep getting rejections you can't diagnose. Check references and confirm they know your cause area and region before hiring.
Last verified 2026-06-16. Figures and rules change — verify at the source before you act.
FAQ
Should I contact a program officer before applying?
Usually yes — if the funder's guidelines allow it. Many foundations welcome a brief inquiry call or email to check fit before you write a full proposal, and a single qualifying conversation can save you from a proposal that was never going to be funded. But always follow the funder's stated contact rules: some explicitly say no unsolicited contact or accept proposals by invitation only, and you should respect that. Verify each funder's process, as of 2026.
How long should an initial inquiry email be?
Keep it short. A common rule of thumb is roughly 150 to 250 words, with short paragraphs and plain language so a busy program officer can grasp your core message in under a minute (as of 2026 — verify against the funder's own format). Open with a specific, research-based reference to their grantmaking, say who you are, name the problem and a rough amount and purpose, and close with a small ask — usually a brief call to check fit. Don't attach an uninvited full proposal.
What should I do if my grant proposal is rejected?
First, read the letter without over-reading it — rejection language is often vague and may not reveal the real reason. Then send a brief, gracious follow-up asking whether they'd share feedback and whether re-applying in a future cycle would be welcome. Accept whatever you hear without arguing. Finally, decide whether to re-apply using a simple test: is this still a genuine fit, and can you meaningfully improve the proposal? Fixable problems are worth fixing and resubmitting; a true mismatch in funder priorities means your energy is better spent elsewhere.
What do funders look for during a site visit?
Site visits let a funder see your work in person before deciding. They're quietly assessing your capacity to deliver, the clarity of your goals and outcomes, the sustainability of the work after the grant ends, and the real impact on the people you serve. Be welcoming, show the program in action, be honest about challenges as well as successes, and if you can, have a board member attend alongside your executive director to signal commitment. Send a prompt thank-you afterward.