The two chapters before this one described the federal giants — the NIH (Chapter 16) and the NSF (Chapter 17) — vast, formalized systems with mechanisms, scoring scales, and rulebooks. Now we cross into a different world. Foundations — the private...
Prerequisites
- 2
- 3
- 7
- 17
Learning Objectives
- Distinguish the major types of foundations and how each makes decisions
- Explain how foundations decide, including the role of boards, program officers, and trust
- Apply the principle that the proposal is an instrument of a relationship, not a substitute for one
- Navigate the letter-of-inquiry-to-invited-proposal process and follow each funder's guidelines exactly
- Write a foundation proposal that wins trust through story, outcomes, and credibility
- Steward a funded grant into a renewable, lasting funder relationship
In This Chapter
Chapter 18: Foundation Grants — Where the Relationship Is the System
The two chapters before this one described the federal giants — the NIH (Chapter 16) and the NSF (Chapter 17) — vast, formalized systems with mechanisms, scoring scales, and rulebooks. Now we cross into a different world. Foundations — the private philanthropic institutions that give away tens of billions of dollars a year in the United States alone — operate on a fundamentally different logic. There is rarely a 1–9 score or a payline. There is often no standardized form. The asks are usually smaller, frequently local, and the decisions are made not by a study section of distant experts but by a handful of people — a program officer, a board, sometimes a single family — who are deciding whether they trust you and your organization to do something they care about. For the small nonprofit, the community organization, and the mission-driven group, foundations are often the most important funder of all, and learning to work with them is a distinct skill.
That skill has a single organizing idea, and it is the threshold concept of this chapter: with foundations, the proposal is an instrument of a relationship, not a substitute for one. At the NIH you can, in principle, succeed as a stranger — write a brilliant application, never speak to a soul, and get funded on the merits. At most foundations, that is not how it works. You are funded by people who have come to trust you, your organization, and your capacity to deliver on a mission you share with them. The proposal matters enormously — but it is one move in a relationship, not a transaction you complete by uploading a document. The grant writers who succeed with foundations are those who understand that they are not submitting into a formula; they are being trusted by people.
In this chapter we map the foundation landscape and its types, examine how foundations actually decide, develop the relationship-as-system mindset, walk through the letter-of-inquiry-to-invited-proposal process that governs much foundation fundraising, learn to write a foundation proposal that wins trust, and cover the stewardship that turns one grant into a lasting partnership. Our anchor throughout is the Riverside Youth Coding Collective (RYCC) — a small nonprofit, roughly \$400,000 in annual budget, run by Executive Director **Denise Okafor**, seeking its first \$50,000 grant from the Hartwell Family Foundation to expand its free after-school coding program from one school to three (90 students across three sites, a 30-week program). RYCC is exactly the kind of organization for which foundations are the lifeblood, and Denise's first foundation campaign will show the relationship-as-system principle in action. (As always, foundation practices vary enormously; treat these as durable patterns, and follow each foundation's own stated process.)
18.1 The Foundation Landscape
"Foundation" is an umbrella term for several quite different kinds of funders, and knowing which kind you're approaching changes how you approach it.
A private (independent) foundation is the classic grantmaking foundation — an endowed institution, often created from a fortune (think of the large named foundations), that gives grants from the returns on its endowment. Private foundations are legally required to pay out a minimum share of their assets each year (commonly discussed as roughly 5% of assets annually — the payout requirement), which is why they must give money away: it's not optional generosity but a legal obligation, a fact that quietly works in your favor. They typically have defined program areas, professional program officers, published guidelines, and a board that approves grants.
A family foundation is a private foundation governed by a family, often smaller and more personal, where the donors' values and the family's interests drive the giving. Decisions can be warmer, more relational, and less bureaucratic — but also more idiosyncratic, turning on a family's particular passions. (Hartwell, RYCC's target, is a family foundation.)
A community foundation pools donations from many donors in a specific geographic area and makes grants to benefit that community. Community foundations are deeply local, often welcoming to grassroots organizations, and frequently a small nonprofit's best first institutional funder — they exist precisely to support the local nonprofit ecosystem. (A community foundation might be a strong funder for Lighthouse Community Services, the reentry workforce program we've met elsewhere.)
A corporate foundation or corporate giving program is philanthropy connected to a company, funding causes aligned with the company's values, markets, or employees' interests. Corporate giving often seeks visible community benefit and brand alignment, and may come with expectations about recognition or employee engagement.
An operating foundation primarily runs its own programs rather than making grants to others — useful to recognize so you don't waste effort asking an operating foundation for a grant it doesn't give.
🎓 Going Deeper — the giving spectrum and donor-advised funds: The five types above are the classic categories, but the philanthropic landscape has more texture worth knowing. Corporate giving ranges from a formal corporate foundation (with its own staff and guidelines) to an informal giving program run out of marketing or community relations, to sponsorships and in-kind gifts — and the right contact and ask differ at each. A growing share of individual philanthropy now flows through donor-advised funds (DAFs) — accounts, often housed at community foundations or financial firms, from which donors recommend grants; these are harder to prospect because the donor is less visible, which is one more reason cultivation and being known in your community matters. Community foundations themselves often do more than grantmaking — they convene, they advise donors, and they can introduce a credible local nonprofit to individual donors and DAF holders, making a relationship with your community foundation unusually high-leverage. The practical lesson: don't picture "foundations" as a single monolith of formal grant programs. Picture a spectrum from highly formal national private foundations to a local family's personal giving, and meet each where it actually sits — the more personal and local the giving, the more the relationship, rather than the document, drives the decision.
🧩 Productive Struggle: Before reading on, consider: a small nonprofit like RYCC has limited staff time and can seriously pursue only a handful of funders. Given the five types above, which should Denise prioritize for a first \$50,000 expansion grant, and why? Jot your reasoning. As you'll see, the answer — family and community foundations with a local, youth-opportunity focus — flows from matching the type of foundation to RYCC's size, locality, and mission, exactly the alignment thinking of Chapter 3 applied to the specific texture of foundations. The biggest national private foundations, however prestigious, are often a poor first target for a small local nonprofit.
📜 How We Got Here: Private foundations exist in their modern form partly because of tax law. In exchange for favorable tax treatment, foundations are required to devote their resources to charitable purposes and to pay out a minimum each year, rather than simply accumulating wealth. Understanding this explains a great deal about foundation behavior: they are obligated to give money away, they must give it to charitable purposes, and they answer to boards and to regulators for doing so responsibly. The payout requirement is why there is, every year, a large pool of foundation money that must find worthy recipients — and why a well-matched, trustworthy organization with a compelling mission is not a supplicant but a solution to the foundation's own need to deploy its funds well. This reframing — you help the foundation fulfill its purpose — is the healthy posture for the whole relationship.
18.2 How Foundations Decide
Federal agencies decide through formalized peer review (Chapters 16–17). Foundations decide through a blend of mission alignment, trust, and human judgment, and the mechanics are looser and more variable.
Most foundations of any size have program officers — staff who manage a portfolio of grants in a program area, scout for promising organizations, guide applicants, recommend grants to the board, and steward relationships. The foundation program officer is, like their federal counterpart (Chapter 2), your single most important contact — but the relationship is often even more central, because there is no impersonal scoring system standing between the program officer's judgment and the funding decision. A program officer who believes in you and your work becomes your champion inside the foundation, advocating for your grant to the board. Cultivating that championing relationship is the heart of foundation fundraising.
The board of trustees typically makes the final grant decisions, often at periodic meetings. This means foundation timelines are set by board cycles, that decisions can involve trustees' personal priorities and politics, and that your program officer's job is partly to package your proposal persuasively for people who will never meet you. It also means a "no" is frequently about fit, timing, or the board's competing priorities — not about the quality of your work.
🔍 Why Does This Work?: Why does cultivating the program officer matter so much when the board makes the decision? Because in the board meeting where your grant is decided, you are not in the room — but your program officer is. The board relies heavily on staff to vet, recommend, and explain requests; a program officer who knows and believes in your work becomes your advocate, framing your proposal persuasively, answering trustees' questions, and vouching for your organization's reliability. A proposal with no internal champion arrives as a cold document among many; a proposal a program officer actively supports arrives with a trusted insider's endorsement. This is the structural reason the relationship is the system: the decision is made by people you'll never meet, through a person you can build a genuine relationship with. Invest in that relationship, and you place an advocate in a room you cannot enter.
Foundations publish (or imply) giving priorities — the causes, populations, geographies, and strategies they fund. As Chapter 3 taught, these priorities, plus the foundation's actual past grants, are the heart of the alignment question. And the single best public source for what a foundation actually funds — as opposed to what it says — is its tax filing. For private foundations this is the Form 990-PF, which lists the grants it actually made, to whom, and for how much. Reading the 990-PF (Chapter 3) tells you the real grant sizes, the real recipients, and whether an organization like yours has a genuine chance.
💡 Key Insight: The most important question about any foundation is not "do they fund my topic?" but "do they fund organizations like mine, at the size I need, in the place I work?" A foundation whose 990-PF shows it funds only large, established institutions with six-figure grants is a poor fit for a small nonprofit seeking \$50,000, even if the topic matches perfectly. Denise at RYCC learned this in Chapter 3: she confirmed via Hartwell's 990 that \$50,000 sits within its typical range and that it has funded several neighborhood-led youth programs. That evidence — that Hartwell funds organizations like RYCC, at the size RYCC needs, in RYCC's region — is what makes Hartwell a real prospect rather than a hopeful guess. Topic alignment is necessary but never sufficient; fit of size, type, and place is what separates a prospect from a long shot.
🔄 Check Your Understanding: Why is a foundation's Form 990-PF often more useful than its website for deciding whether to apply?
Answer
Because the website states intentions and priorities (which can be aspirational, vague, or out of date), while the 990-PF documents what the foundation actually did — the real grants it made, to whom, in what amounts. The 990-PF reveals true grant sizes, the types of organizations actually funded, and geographic patterns, letting you judge whether an organization like yours, at the size you need, in your area, has a genuine chance. Use the website for priorities and process; use the 990-PF to verify real-world fit.
18.3 The Relationship Is the System
Now the threshold concept, stated plainly and then put to work. At a foundation, you are not primarily submitting a document into an evaluation machine; you are building and drawing on a relationship with people who decide whether to trust you. The proposal is an instrument of that relationship — a crucial one — but it does not replace the relationship, and a strong proposal from a stranger usually loses to a comparable proposal from an organization the program officer knows and trusts.
🚪 Threshold Concept: With foundations, the proposal is an instrument of a relationship, not a substitute for one. This reframes everything. It means the work starts long before the proposal: with research (Chapter 3), with cultivation (Chapter 2), with a first conversation, with showing up in the community the foundation serves. It means the proposal's job is partly to confirm and deepen a relationship the program officer already has reason to believe in. And it means stewardship after the grant — reporting well, delivering on promises, keeping the funder genuinely informed — is not an afterthought but the foundation of the next grant. Cross this threshold and you stop thinking "how do I write a winning proposal?" and start thinking "how do I build a relationship in which my proposal can win?"
What does building the relationship actually look like? It looks like the cultivation Chapter 2 introduced: researching the foundation thoroughly; making a brief, well-prepared first contact (often a short email or call to the program officer asking whether your work fits and how they prefer to be approached); listening more than pitching; attending events the foundation hosts or supports; and demonstrating, over time, that your organization is credible, mission-aligned, and trustworthy. It looks like being known before you ask — or, when that's not possible, making your first ask the beginning of a relationship rather than a one-shot transaction.
Watch Denise do this with Hartwell. Having confirmed fit in Chapter 3, she doesn't simply mail a proposal. She emails Hartwell's program officer with a short, well-prepared note: she introduces RYCC in two sentences, mentions specifically that she's seen Hartwell's support for neighborhood-led youth programs, and asks two genuine questions — whether RYCC's planned expansion fits Hartwell's current interests, and how the program officer prefers to be approached. The reply tells her Hartwell likes a brief LOI first and that a site visit is welcome. Denise invites the program officer to see the program in action; the officer comes, watches the kids code, and meets Denise's board chair. By the time RYCC's LOI arrives, the program officer is not reading about an unknown nonprofit — she's reading about an organization she has seen, run by a director she has met, doing work she has watched land with real children. None of this is manipulation; it's Denise doing the honest, patient work of being known before she asks. That work is what converts a cold proposal into a championed one.
📊 From the Field: Foundation program officers will often tell you, candidly, that they fund organizations and leaders they trust as much as they fund proposals. A program officer who has visited your program, met your director, and watched you deliver on a small grant will advocate for your next, larger request in a way no cold proposal can match. This is why experienced nonprofit leaders treat foundation relationships as long-term assets: the first grant is frequently smaller than you'd like, because it's partly the foundation testing the relationship — and delivering well on that first grant, and stewarding it attentively, is what unlocks the larger, multi-year support later. The relationship is the system, and the system runs on demonstrated trust accumulated over time.
🪞 Learning Check-In: If you come from a research or technical background, the relationship-centered nature of foundation fundraising can feel uncomfortable — even improper, as though funding should be decided purely on written merit. Notice that reaction. Foundations are not federal agencies; they are mission-driven institutions whose stewards are supposed to use judgment about whom to trust with their charitable dollars. Building a genuine relationship is not gaming the system; it is the system, and it's a legitimate, even admirable one — philanthropy directing private wealth toward public good through human relationships of trust. You don't have to abandon your integrity to work this way; you have to bring your authentic mission and your reliability into a relationship. The discomfort fades once you see cultivation as honest relationship-building rather than manipulation.
18.4 The Foundation Proposal Process
Because foundations vary so much, there is no single foundation proposal format — and that variability is itself the first rule: follow each foundation's stated guidelines exactly (Chapter 15's lesson, in a setting where the rules are less standardized and therefore easier to get wrong). That said, a common process and a common set of components recur.
The most frequent process is the letter of inquiry (LOI) — sometimes called a letter of intent — followed by an invited full proposal. Rather than accept full proposals from everyone, many foundations ask first for a short letter (often one to three pages) describing your organization, the need, your proposed project, the outcomes, and the amount requested. The foundation screens these and invites full proposals only from the organizations it wants to consider further. The LOI is thus a gatekeeper and a relationship opener — closely related to the executive summary and LOI you learned to write in Chapter 7. A strong LOI gets you invited; a weak or ill-fitting one ends the process before it begins.
📋 Template — Common foundation proposal components (always verify against the specific funder's guidelines): A cover letter; the LOI or proposal narrative (need, project, outcomes, organizational background, sustainability); a project or organizational budget; the amount requested and its purpose; organizational information (mission, history, leadership, board list); proof of tax-exempt status (the IRS 501(c)(3) determination letter); recent financial statements or an audit; sometimes a logic model, evaluation plan, or letters of support. Foundation proposals are typically shorter than federal ones — often a few pages of narrative, not dozens — so concision and clarity matter even more. Send exactly what they ask for, in the format they specify, and nothing they didn't ask for.
⚠️ Common Pitfall: Sending a generic, one-size-fits-all proposal to many foundations. Because foundation proposals are shorter and the process feels less formal than a federal application, applicants are tempted to write one "foundation proposal" and mass-mail it. Program officers spot a generic proposal instantly — it fails to reference their priorities, their community, their language — and it signals exactly the wrong thing: that you haven't done the relationship work. The fix is to tailor every proposal to the specific foundation's stated priorities and your specific relationship with them, even when the core project is the same. A foundation wants to feel that you are asking them, for reasons specific to them — not blasting the same letter to fifty funders.
Denise's process with Hartwell follows this shape. Having confirmed fit in Chapter 3, she makes contact with Hartwell's program officer, learns that Hartwell prefers a brief LOI first, and prepares one tailored to Hartwell's stated interest in neighborhood-led youth opportunity. We'll follow her LOI and proposal next — including the realistic possibility, true to foundation fundraising, that a first attempt may not succeed immediately.
To make the LOI concrete, here is the shape of Denise's letter to Hartwell (condensed and paraphrased; a real LOI is a page or two of warm, specific prose):
Opening — the connection and the ask. Dear [program officer], Riverside Youth Coding Collective respectfully requests \$50,000 to expand our free after-school coding program from one school to three, serving 90 middle-schoolers across our neighborhood. We're approaching Hartwell because of your long commitment to neighborhood-led youth opportunity — the families in the three schools we hope to reach are the families Hartwell has championed for years.
The need — as story and evidence. In our neighborhood, middle-schoolers have almost no access to computer science... [a brief, human picture of the gap, with a local statistic].
The project and outcomes. Over a 30-week program at three sites, 90 students will build computational skills and confidence, taught by two instructors and a coordinator. We will measure [specific skill gains and engagement outcomes]...
Trustworthiness. RYCC has run this program successfully at our first school for [time], reaching [number] students; we operate on a \$400,000 annual budget with an engaged board, and families at the next two schools have asked us to come.
The close — an invitation to relationship. We would welcome the chance to show you the program in person and discuss whether a full proposal would be useful to you. Thank you for considering this request.
Notice the features: it asks Hartwell specifically and says why; it tells the need as a human story backed by a little evidence; it promises concrete outcomes, not just activities; it establishes that RYCC can be trusted to deliver; it keeps to the size Hartwell actually funds; and it closes by inviting a relationship (a visit, a conversation), not merely a check. That is an LOI built to get RYCC invited — and to deepen the relationship whether or not this particular cycle ends in a grant.
18.5 Writing the Foundation Proposal
When you do write — whether an LOI or an invited full proposal — the foundation proposal has a different center of gravity from a federal application. Federal reviewers want rigor, methodology, and technical merit. Foundation decision-makers want, above all, to trust that your organization will use their money to make a real difference in something they care about. That shifts the emphasis toward three things: a compelling story, credible outcomes, and demonstrated trustworthiness.
Story. Foundations, especially family and community foundations, are moved by a clear, human, mission-centered narrative: who you serve, what they face, what you do, and why it matters. This is not manipulation; it's communicating the human reality behind the numbers. The needs-and-significance craft of Chapter 8 applies, but the register is often warmer and more narrative than a federal significance section — you are speaking to people who give because they care, not only because the data compels them.
Outcomes. Foundations increasingly want to know what changes as a result of their grant — the outcomes-not-activities lesson of Chapter 10, in foundation form. What will be different for the people you serve? How will you know? A foundation funding RYCC wants to hear not "we will run coding classes" but "90 middle-schoolers in an under-resourced neighborhood will gain computational skills and confidence, measured by [specific outcomes]." Outcomes make the grant feel like an investment in change rather than a donation to an activity.
Trustworthiness. Because the decision is fundamentally about trust, the proposal must establish that your organization can deliver: your track record, your leadership, your board, your financial health, your capacity (the organizational-capacity case of Chapter 13, scaled to a small nonprofit). A foundation taking a chance on a small organization needs reassurance that the money will be well managed and the work actually done.
✅ Best Practice: Where the foundation allows it, don't be afraid to ask for general operating support rather than narrow project support. Many small nonprofits, conditioned by restrictive funders, ask only for tightly scoped project money — but unrestricted operating support (which covers the salaries, rent, and infrastructure that make all the programs possible) is the most valuable money a nonprofit can receive, and a growing number of foundations, recognizing this, prefer to give it to organizations they trust. The relationship is what unlocks it: a funder rarely gives flexible, trust-based operating support to a stranger, but often will to an organization it has come to believe in. So read the foundation's guidelines for whether operating support is welcome, and when it is and the relationship supports it, make the case for the funding your organization actually needs rather than artificially packaging everything as a discrete project. This is also why the first grant matters beyond its dollars: a well-stewarded first project grant is the path to the flexible, sustaining support that genuinely strengthens an organization (Chapter 14's sustainability theme, in foundation form).
🗣️ From the Review Panel: (A family-foundation trustee reflects.) When our board reviews requests, we're not scoring methodology — we're asking, "Do we believe in these people, and will this money do what they say?" The proposals that win us over tell us clearly who they help and what will change, show us they've thought about how they'll know it worked, and give us confidence the organization can handle the money and the work. What sinks a request is vagueness about outcomes, or a sense that the organization is stretched too thin to deliver, or — honestly — a letter that could have been sent to any foundation and clearly wasn't written for us. We give to organizations we trust to advance the things our family cares about. Make us trust you, show us the change, and speak to us specifically, and you're most of the way there.
Consider RYCC's case concretely. Denise's \$50,000 request to Hartwell tells a clear story (free coding for middle-schoolers in an under-resourced neighborhood, expanding from one school to three where families have asked for it), promises credible outcomes (90 students served across three sites over a 30-week program, with specific skill and engagement measures), and establishes trustworthiness (RYCC's track record at its first school, Denise's leadership, a real budget, a functioning board). It is tailored to Hartwell's stated interest in neighborhood-led youth opportunity, and it asks for an amount Hartwell actually gives. This is a strong, well-fitted request — and even strong, well-fitted requests sometimes need more than one cycle, because the relationship is still forming.
📊 From the Field: Here is a truth that beginners find discouraging and veterans find normal: a first foundation approach, even a well-matched one, is often declined — and that decline is frequently the beginning of the relationship, not the end of it. RYCC's first LOI to Hartwell may well come back as a "not this cycle," because Hartwell's board is still getting to know RYCC, its funds for the cycle are committed, or the timing is wrong. The organizations that ultimately win foundation support are the ones that treat that first "no" the way Hernandez treated her NIH summary statement (Chapter 16): not as a verdict, but as a stage in a process. Denise's right response is to thank the program officer, ask what would make a future request stronger, invite them to visit the program, stay in touch with updates, and return the next cycle as a known organization rather than a stranger. We follow exactly this declined-then-funded arc in detail in Chapter 22 (The Resubmission), where RYCC's first foundation LOI is declined and then, the following cycle, invited and funded — the foundation-world counterpart to the federal A1. The lesson to carry now: persistence and relationship-building, not a single perfect letter, are what win foundation funding.
📐 Project Checkpoint — Build your foundation prospect list and draft an LOI: For your project, (1) using the Chapter 3 method, build a short list of well-matched foundations — the right type (family/community/private/corporate), size, geography, and priorities — verifying real-world fit via each one's 990-PF or published grants. (2) For your top prospect, note your relationship status (warm/cold) and a concrete cultivation step (a first email to the program officer, an event to attend, a question to ask). (3) Draft a one-to-two-page LOI tailored to that specific foundation: organization, need (as story + evidence), project, outcomes, amount requested, and why this foundation. Save it in your "My Proposal" document. If you're a researcher whose primary funders are federal, do this anyway for a foundation that funds work like yours — most research careers eventually touch foundation money, and the relationship skill transfers.
18.6 Stewardship: Turning a Grant into a Partnership
The federal chapters ended with the resubmission. The foundation chapter ends with stewardship, because in foundation fundraising the period after the grant is where the next grant is won. Stewardship means using the money as promised, reporting honestly and on time, keeping the funder genuinely informed (including about challenges, not only successes), acknowledging the foundation appropriately, and treating the program officer as a partner in the work. A foundation that has a good experience funding you — clear reporting, delivered outcomes, honest communication, no surprises — is a foundation predisposed to fund you again, often at a higher level and over multiple years.
This is why the relationship-as-system frame extends past the grant decision. The first \$50,000 grant, stewarded well, becomes the basis for a renewal, then perhaps multi-year general operating support, then a deepening partnership in which the foundation becomes an advocate and connector for your organization. The grant writers and nonprofit leaders who understand this treat every funded grant as the beginning of a relationship to be nurtured, not a transaction completed — and over years, that compounding trust becomes the most reliable funding an organization has.
🔍 Why Does This Work?: Why does attentive stewardship reliably unlock future funding? Because it directly reduces the foundation's central risk. A foundation's program officer is accountable to a board for deploying charitable dollars well, and their biggest fear is a grant that disappoints — money spent with little to show, or an organization that goes quiet and surprises them with bad news. An organization that reports clearly, delivers what it promised, and communicates honestly through difficulties removes that fear: it makes the program officer's job easy and makes them look good to their board for having backed you. The next grant is, in part, a reward for being low-risk and high-trust — and stewardship is how you demonstrate exactly that. Good stewardship isn't just gratitude; it's the evidence on which the renewal decision rests.
🔄 Check Your Understanding: A nonprofit receives a \$50,000 grant, does good work with it, but never sends the agreed report, goes quiet for a year, and then applies again for a larger amount. Why is the second request likely to struggle, even though the funded work went well?
Answer
Because stewardship failure breaks trust regardless of program success. From the funder's side, an organization that went silent and skipped its report looks risky and unaccountable — the program officer cannot easily show the board what the first grant accomplished, and the silence signals that a larger grant might bring the same uncertainty. The decision is about trust, and the nonprofit undermined exactly that by neglecting the relationship after the check cleared. Good work plus poor stewardship still reads as a poor partnership. The renewal rests not only on whether the work succeeded but on whether the organization was a communicative, accountable, low-risk partner — which is demonstrated through reporting and contact, not just results.
18.7 Strategy: A Portfolio of Relationships
Pull the threads together into foundation strategy. Succeeding with foundations means: identify well-matched foundations by type, size, geography, and priorities, verified against real grants (Chapter 3); start with the funders where you have, or can build, a relationship — often local family and community foundations for a small nonprofit; cultivate the program officer as a potential champion (Chapter 2); follow each foundation's process and guidelines exactly, usually an LOI before an invited proposal; write proposals centered on story, outcomes, and trustworthiness, tailored to each specific funder; and steward every grant into a lasting partnership. Above all, hold the threshold concept: the proposal is an instrument of a relationship, not a substitute for one.
Because most organizations need many funders, foundation strategy is portfolio strategy — but a portfolio of relationships, not just applications. A healthy small nonprofit cultivates a stable of foundation relationships at different stages: funders it's currently funded by (to be stewarded toward renewal), funders in active conversation (to be moved toward a first grant), and prospects being researched and approached (to enter the pipeline). This is the funder pipeline of Chapter 3, deepened by the recognition that each entry is a human relationship to be tended over time.
It helps to set the foundation world beside the federal one we've just left:
| Dimension | Federal (NIH/NSF, Ch 16–17) | Foundations (Ch 18) |
|---|---|---|
| Decision basis | Formalized peer review; merit scores | Mission alignment + trust + human judgment |
| Who decides | Study section / panel → institute / program officer | Program officer → board of trustees |
| Form & process | Standardized forms, strict rules | Varies by funder; often LOI → invited proposal |
| Typical size | Often large; multi-year | Often smaller; frequently local; sometimes multi-year |
| Relationship's role | Helpful (program officer) but merit can carry a stranger | Central — the relationship often is the system |
| Proposal emphasis | Rigor, methodology, technical merit | Story, outcomes, organizational trustworthiness |
| After the decision | Resubmission (A1) if declined | Stewardship → renewal; relationship compounds |
The deepest lesson of Part III holds here too: the universal craft is your engine, and each funder is a different chassis. The foundation chassis is built from relationships and trust. Master the relationship — the cultivation, the tailored ask, the attentive stewardship — and you've learned to work with the funders that sustain much of the nonprofit world. And because relationships, unlike single applications, compound over time, the foundation skill rewards patience more than any other: the organization that has spent five years building genuine relationships with a dozen well-matched funders has something far more durable than any one grant — a community of supporters who know it, trust it, and want it to succeed.
🔄 Check Your Understanding: RYCC's project, budget, and outcomes are identical whether Denise approaches a federal agency or the Hartwell Family Foundation. Name two things she must do differently to succeed with Hartwell that she would not do (or not emphasize) for a federal application.
Answer
Several are defensible. Two clear ones: (1) Cultivate the relationship and the program officer first — research Hartwell, make personal contact, often submit a brief LOI before any full proposal, and tailor everything to Hartwell specifically, because the relationship and trust are central in a way they are not for a stranger-friendly federal review. (2) Shift the proposal's emphasis toward story, outcomes, and organizational trustworthiness (in a warmer, more narrative register), rather than the technical rigor and methodology a federal reviewer prioritizes — and plan to steward the grant attentively afterward to earn the renewal. (Also acceptable: follow Hartwell's specific, non-standardized guidelines exactly; keep it short.)
Spaced Review
Retrieve these from earlier chapters without looking back.
- (From Chapter 17) How does the NSF's decision process differ from a foundation board's, and what does each difference imply about how much the relationship can carry you?
- (From Chapter 3) What is a Form 990-PF, and how does it let you judge real fit with a foundation before you invest in applying?
- (From Chapter 7) How is a foundation LOI related to the executive summary, and why must both let a busy reader grasp and want to fund the project quickly?
Answers
1. The NSF uses external peer review with a program officer recommending funding under merit criteria; a foundation board makes judgment-based decisions about whom to trust, guided by a program officer who champions you. The relationship can carry you much further at a foundation, where trust is central and there is no impersonal score, than at the NSF, where a stranger can still win on merit (though the program-officer relationship helps there too). 2. The 990-PF is a private foundation's public tax filing listing the grants it actually made, to whom, and for how much — letting you verify real grant sizes, recipient types, and geography, and thus whether an organization like yours has a genuine chance, before spending effort on an application. 3. A foundation LOI is a close cousin of the executive summary / LOI of Chapter 7 — a short, self-contained pitch (organization, need, project, outcomes, ask) whose job is to make a busy program officer quickly understand the project and want to invite a full proposal; like the executive summary, if it doesn't land on its own, the rest never gets read.
Chapter Summary
Key Takeaways
- Foundations give tens of billions annually and are often the most important funder for small, local, and mission-driven organizations. Types — private (independent), family, community, corporate, operating — differ in scale, formality, and how they decide; match the type to your size, locality, and mission.
- Foundations decide through mission alignment + trust + human judgment: program officers champion grants to a board of trustees. The 990-PF reveals what a foundation actually funds (Chapter 3).
- Threshold concept: the proposal is an instrument of a relationship, not a substitute for one. You are funded by people who trust you to advance a shared mission, not by a form submitted into a formula.
- Most foundation fundraising runs LOI → invited full proposal; processes and formats vary by funder, so follow each one's guidelines exactly. Foundation proposals are usually shorter than federal ones.
- Foundation proposals win on story, outcomes, and trustworthiness, tailored to the specific funder — not generic mass-mailed letters.
- Stewardship (honest reporting, delivered outcomes, genuine communication) turns one grant into a renewable, compounding partnership — the period after the grant is where the next grant is won.
Action Items
- Build a short list of well-matched foundations by type, size, geography, and priorities; verify real fit via the 990-PF or published grants.
- For each top prospect, note relationship status and a concrete cultivation step (contact the program officer; attend an event; ask how they prefer to be approached).
- Learn each foundation's process (LOI? invited proposal? deadlines tied to board cycles?) and follow it exactly.
- Draft a tailored LOI centered on story, outcomes, and trustworthiness — written for that foundation.
- Plan stewardship from the start: how you'll report, communicate, and steward the relationship toward renewal.
Common Mistakes
- Treating the proposal as the whole game and skipping the relationship (cultivation, the program officer, stewardship).
- Mass-mailing a generic proposal instead of tailoring to each foundation's priorities and your relationship with them.
- Chasing big national foundations that don't fund organizations of your size or type, instead of well-matched local funders.
- Ignoring the 990-PF and applying on topic alignment alone, without checking size/type/geography fit.
- Going quiet after the grant — neglecting stewardship and forfeiting the renewal the relationship could have produced.
Decision Framework — "Is this foundation worth pursuing, and how?"
- Is the type right for me (family/community/corporate/private) given my size, locality, and mission? → Operating foundations don't give grants; skip them.
- Does the 990-PF show real fit — organizations like mine, at my size, in my area? → If not, reject confidently (Chapter 3).
- What's my relationship status, and what's the next cultivation step? → Warm beats cold; start building if needed.
- What's their process — LOI first? deadlines? guidelines? → Follow it exactly; send only what's asked.
- Can I make the case on story, outcomes, and trust, tailored to them? → If it's generic, rewrite it for this funder.
- How will I steward the grant toward a renewal? → Plan it before you're funded.
🔁 Carry this forward: You've now seen three funder worlds — the NIH's mechanisms (Chapter 16), the NSF's two criteria (Chapter 17), and the foundation's relationships (this chapter). Next, government grants beyond NIH and NSF (Chapter 19) return to the formal, compliance-heavy end of the spectrum — state and federal program grants, with their RFPs, strict eligibility, and reporting. Watch how the same universal proposal keeps getting refitted to each funder's machinery, and how the relationship skills you built here still matter even where the forms are rigid.