Chapter 2: Thinking Like a Funder — What Reviewers and Program Officers Actually Want

It is Saturday morning, and a professor you will never meet is sitting at her kitchen table with a cup of coffee going cold and a stack of forty grant proposals she agreed, months ago and now regrets, to review. She is doing this for free. She has her own grants to write, her own lab to run, and a daughter's soccer game at noon. She is on proposal number twenty-three. She has been reading since six. And your proposal is next.

This person — not the agency, not the foundation, not the logo at the top of the funding announcement — is who you are actually writing for. Everything in this chapter follows from taking her seriously: her mission, her constraints, her fatigue, and the handful of questions running through her mind as she picks up your proposal and gives it, if you are lucky, twenty minutes of divided attention.

Chapter 1 gave you the map of the funding world and one big idea: a grant is a mission transaction. This chapter makes that idea operational by introducing you to the people on the other side of the table. By the end you will understand how funding decisions are really made, what reviewers want and in what order they want it, and why a fifteen-minute phone call to a program officer before you write a single word may be the highest-return activity in all of grant writing. This is, by the reckoning of many veteran grant writers, the most important chapter in any book on the subject. Master it, and the rest of the book is technique applied in service of a reader you understand. Miss it, and the technique has nothing to attach to — you will write polished proposals aimed at no one in particular, and lose to plainer ones aimed squarely at the person holding the pen.

2.1 Funders Have Missions, Not Spare Cash

The first and most expensive misconception a beginner holds is that funders have money and are looking for good things to spend it on. They are not. Funders have missions, and they are looking for the most effective ways to advance them. The money is not the point; the money is the tool. This distinction sounds subtle and is in fact everything.

Every funder exists to accomplish something specific. The National Institutes of Health exists to seek fundamental knowledge about the nature of living systems and to apply that knowledge to improve health — and Congress holds it accountable for doing so. A family foundation exists to carry out the philanthropic intentions of the family that endowed it, intentions that may be as broad as "improve education" or as narrow as "support music programs in three named counties." A corporate giving program exists to advance the company's strategic interests — workforce, brand, community goodwill — through philanthropy. None of them wakes up wanting to give money away. Each wakes up wanting to advance a mission, and giving money away is simply how they do it.

This is why funding priorities exist. A priority is a funder's statement of where, right now, it believes it can best advance its mission. The NIH issues priorities through specific funding announcements and institute strategic plans. A foundation announces priorities through its program areas and, increasingly, through multi-year strategies. These priorities are not bureaucratic noise to be skimmed past on the way to the application form. They are the funder telling you, in writing, exactly what they are trying to accomplish — which is to say, exactly what you must show your project will do for them.

Where do you read a funder's mind? In the documents they publish, and there are more of them than beginners realize. For federal agencies: the strategic plan, the specific funding announcement (the FOA/NOFO), and institute or program "concept" pages. For foundations: the mission and program-area pages on their website, their annual report, and — revealingly — their tax filing (the Form 990-PF), which lists every grant they actually made last year. That last source is worth its weight in gold, because what a funder says it cares about and what it funds can differ, and the list of real grants tells you the truth. We will turn all of these into a systematic research method in Chapter 3. For now, absorb the habit: before you write for a funder, read everything they have published about what they want, and read their list of past grants to confirm it.

💡 Key Insight: Read every word a funder publishes about its mission and priorities as if it were a description of the person you are trying to persuade — because it is. When a foundation says it prioritizes "community-led solutions to food insecurity," it is not describing a category; it is describing the argument that will win, and the framing that will lose. A brilliant food-security project that is not community-led is, for this funder, a worse fit than a modest one that is. Priorities are not boxes to check. They are the funder's own statement of what will persuade them.

Learning to decode a priority statement is a skill in itself, because funders rarely say everything they mean. Take a real-sounding example: a foundation states it funds "evidence-based, community-led programs that improve educational outcomes for students furthest from opportunity." Read it the way a funder-thinker reads it, word by word. "Evidence-based" means they will expect you to cite research or data, not just passion — a proposal built on conviction alone will fail here. "Community-led" means the community must be in the driver's seat, not the recipient of an expert's plan — a top-down program, however good, is a poor fit. "Students furthest from opportunity" means they are prioritizing the most marginalized, so a program serving a broad or already-advantaged population is off-target. "Improve educational outcomes" means they will want to see measurable outcomes, which foreshadows the evaluation plan they will expect (Chapter 10). Four phrases, four strong signals about what will win and what will lose — all sitting in plain sight in a single sentence that a hurried applicant skims past on the way to the application form.

📋 Template — Decode the priority statement: Copy a target funder's mission or priority sentence into your notes. Underline every substantive word or phrase. Beside each, write what it implies about (a) what your proposal must demonstrate, and (b) what kind of project would be a poor fit. If you cannot honestly satisfy a phrase, you have learned something valuable before writing a word: this may be the wrong funder. Do this for every funder you seriously consider.

There is a humbling consequence here. Your project's worth, in the abstract, is almost irrelevant to a given funder. What matters is your project's worth to that funder's mission, right now, relative to the other proposals competing for the same dollars. A genuinely excellent project can be a poor fit, and a more modest project can be an excellent fit. The skill of "thinking like a funder" begins with internalizing this and never again asking "is my project good?" without immediately asking "good for whom, toward what mission?"

🔄 Check Your Understanding: A funder's website states its mission is "to expand access to the arts for rural communities." Two applicants apply: (A) a world-renowned urban orchestra seeking support for a prestigious downtown concert series, and (B) a small touring ensemble that performs in rural school gymnasiums. Whose project is "better," and whose is a better fit? Why might the fit matter more?

Answer

By prestige and artistic stature, (A) may well be "better." But (B) is the far better fit — it directly advances the funder's mission of arts access for rural communities, while (A) does not. Fit matters more because the funder gives money only to advance its mission; it cannot justify funding excellent work that does not serve its stated purpose. This is the mission-transaction principle from Chapter 1 made concrete.

2.2 Your Real Audience Is the Reviewer

Here is the move that separates people who write proposals from people who win them.

🚪 Threshold Concept: Your true audience is not the funding organization. It is the individual, specific, tired, human being who will read your proposal among dozens of others and form an opinion that decides your fate. You are not writing to "the NIH" or "the Hartwell Foundation." You are writing to Professor Whoever at her kitchen table on Saturday morning, or to a program officer with thirty letters of inquiry to get through before a board meeting. Write for that person — their attention, their fatigue, their need to be convinced and to be able to defend their choice to others — and everything about how you write will change.

Why does this reframing matter so much? Because organizations do not read proposals; people do. An organization has a mission, but a person has the mission plus a limited attention span, a stack of competitors, a fear of championing something that turns out to be flawed, and a strong preference for proposals that make their job easy. When you write to the abstract organization, you produce a proposal that is technically complete and humanly unpersuasive — accurate, thorough, and somehow inert. When you write to the actual human reviewer, you produce a proposal that anticipates their fatigue, answers their questions in the order they ask them, and hands them the argument they will need to advocate for you in the room.

Notice that this does not mean dumbing anything down or being unprofessional. The tired professor is brilliant and expert; she is simply also human and overloaded. Writing for her means respecting her intelligence and her constraints at the same time: rigorous content, delivered with a structure and clarity that does not make her work to find your point.

A small illustration of the difference. Writing to the organization, an applicant produces a sentence like: "It is anticipated that the proposed intervention will be implemented across multiple sites in order to assess its efficacy in diverse populations." It is grammatical, professional, and lifeless — passive, abstract, and slow. Writing to the person, the same applicant produces: "We will test the program in four clinics — urban and rural, large and small — to find out whether it works for everyone or only for some." Same meaning, but the second version moves, it is concrete, and a tired reader grasps it at a glance. The organization would accept either. The human reviewer, at proposal twenty-three, silently thanks you for the second and quietly resents the first. Across a whole proposal, that accumulated gratitude or resentment becomes a score.

🔄 Check Your Understanding: Why is "writing for the reviewer" not the same as "simplifying" or "being less rigorous"?

Answer

The reviewer is an expert and expects rigor; what they lack is time and patience, not intelligence. Writing for them means keeping the full rigor of the content while removing every needless obstacle to understanding it — passive constructions, buried points, abstraction, jargon used for its own sake. You are lowering the reading cost, not the intellectual level.

🗣️ From the Review Panel: I have reviewed proposals for federal agencies and foundations both, and I can tell you the exact moment a proposal wins or loses me, and it is early — usually within the first page. It is the moment I can either say to myself "ah, I see what they're doing and why it matters to us," or I cannot. If I can, I read the rest generously, looking for reasons to support it. If I cannot, I read the rest skeptically, looking for reasons to set it aside — and on proposal twenty-three of forty, I am not short of reasons. The single most important thing your proposal does is create that early moment of clarity. Everything in Part II of this book is, in one way or another, about engineering it.

2.3 How Review Actually Works: Three Rooms

To write for the reviewer, you need to know what room they are sitting in. Decisions get made differently across the funding world, and the differences shape how you should write. Here are the three most important settings. We will return to each in depth in Part III; this is the orientation.

The NIH Study Section

For most NIH grants, applications are evaluated by a study section — a panel of roughly twenty to thirty scientists, organized by topic, that meets (in person or virtually) to review a batch of applications. Each application is assigned to a small number of reviewers — typically a primary reviewer and one or two others — who read it in depth and write critiques. The rest of the panel reads the assigned reviewers' summaries, not the full application.

This structure has enormous implications. Your application's fate rests heavily on two or three assigned reviewers who actually read it, and on whether those reviewers can persuade the rest of a tired panel in a few minutes of discussion. The panel discusses only the applications that score well enough in the preliminary round; the rest are triaged, as you learned in Chapter 1. When an application is discussed, the assigned reviewers state their preliminary scores, briefly debate, and then the whole panel votes a score. The discussion is often short — sometimes only a few minutes per application.

What this means for you: you are writing for the primary reviewer who must understand your work deeply and be equipped to defend it concisely to colleagues who have not read it. You must make your significance and your approach so clear that your advocate can summarize them in two sentences and your skeptics cannot easily attack them.

It also helps to know, even now, that NIH reviewers score against five named criteria — Significance, Investigators, Innovation, Approach, and Environment — and assign an overall impact score that is not a simple average of them. (Chapter 16 dissects all of this.) Two features of that system matter for how you think like a funder. First, Significance and Approach tend to dominate the overall impression — a project can have strong investigators and environment and still score poorly if reviewers doubt its importance or its plan. Second, because the overall score is holistic, a single serious weakness can drag the whole score down regardless of strengths elsewhere; reviewers remember the thing that worried them. This is why preempting weaknesses (Chapter 9) and nailing significance (Chapter 8) matter so much: you are managing not five independent grades but a single, fragile, overall impression formed by a tired human.

The NSF Panel

The National Science Foundation also uses panels, but with its own culture. Reviewers evaluate proposals against two explicit criteria — Intellectual Merit (the quality and importance of the research) and Broader Impacts (the benefit to society) — and these two criteria carry real, formal weight. A proposal that is scientifically excellent but treats Broader Impacts as an afterthought can be sunk by it, a fact that surprises and frustrates many researchers (we devote much of Chapter 17 to this). NSF program officers also have more individual discretion than their NIH counterparts in shaping funding decisions, which makes the program-officer relationship even more consequential.

The Foundation Board (and Program Officer)

Foundations are the most varied of the three. A large foundation may have professional program officers who review proposals, conduct site visits, and make recommendations to a board that meets quarterly. A small family foundation may be a single part-time staffer, or just the family, reading letters of inquiry around a conference table. There may be formal scoring criteria or none. The process may be transparent or opaque. What unites them is that foundation decisions are typically more relationship-driven and less formulaic than federal ones. A program officer who has met you, understands your work, and believes in it can champion your proposal to the board in a way that no document alone can. This is why, in the foundation world, cultivation of the relationship often matters as much as the proposal itself — a theme we develop fully in Chapter 18.

The Government Program Office and the Corporate Giving Committee

Two more rooms deserve a mention, because between them they account for an enormous share of funding. State and local government programs (and many non-NIH/NSF federal programs) are usually reviewed by agency staff or contracted panels against a published scoring rubric, often with points assigned to each section. The defining feature is compliance: these reviewers frequently work from a checklist, and a proposal that omits a required element or violates a formatting rule can lose points mechanically, before merit is even weighed. Writing for this room means treating the rubric as a literal scoring key — giving each criterion its own clearly labeled section, in the order and proportion the rubric specifies. We return to this in Chapter 19.

The corporate giving committee is the most informal and the most strategically self-interested room. It may be a single community-relations manager, or a committee that meets a few times a year, asking less "is this rigorous?" and more "what does this do for us — our employees, our brand, our community standing?" Writing for this room means making the benefit to the company visible and concrete (employee engagement, local goodwill, alignment with the company's stated values), without pretending the relationship is purely philanthropic.

🗣️ From the Review Panel: The mistake I see most often is a proposal that was clearly written for one room and submitted to another. A dense, jargon-heavy research narrative lands on a foundation program officer who wanted a human story and a clear outcome. A warm, mission-driven narrative with no rigor lands on a study section that wanted methods and controls. A proposal that ignores half the scoring rubric lands on a government reviewer who is, quite literally, adding up points. The content of your project may be perfect; if it is dressed for the wrong room, it still loses. Know the room before you write, not after you are rejected.

📊 From the Field: The same project, submitted to these three rooms, must be written three different ways. To the NIH study section: lead with significance and rigor, and arm your primary reviewer with a defensible case. To the NSF panel: give Intellectual Merit and Broader Impacts each their genuine due. To the foundation board: lead with mission fit and a compelling, human story backed by evidence, and remember that a program officer you have spoken with may be reading it with a friendly eye. Writing one generic proposal for all three is the single most common way sophisticated applicants waste excellent work.

🔄 Check Your Understanding: In an NIH study section, why is it a mistake to assume that the entire panel has read your full application in depth?

Answer

Because typically only the two or three assigned reviewers read the full application; the rest of the panel relies on those reviewers' written critiques and the brief discussion. So you must write so that your assigned reviewers can both understand the work deeply and summarize and defend it concisely to colleagues who have not read it. Your clarity becomes your advocate's ammunition.

2.4 The Tired Reviewer: Reading Your Thirtieth Proposal

Let us return to that kitchen table, because reviewer psychology is not a footnote — it is the single most actionable thing in this chapter.

Reviewers are almost always volunteers or overloaded staff. They are experts, but they are reading your proposal at the end of a long queue, often outside their core specialty, frequently when tired. This produces a predictable psychology that you can and must design for. Call it reviewer fatigue: as the stack wears on, reviewers read faster, skim more, and become less willing to work to extract your meaning. A point that is buried on page eleven might as well not exist. A sentence that requires rereading is a small tax that, levied often enough, turns appreciation into irritation.

The implications are concrete and they shape every later chapter:

• Front-load everything that matters. The reviewer forms an impression early and spends the rest of the proposal confirming or revising it. Your most important point — what you will do and why this funder should care — belongs on the first page, not as a payoff at the end. (This is why the specific aims page and the executive summary, Chapters 6 and 7, are the highest-leverage pages in any proposal.)
• Make the structure visible. A reviewer skimming should be able to navigate by headings and topic sentences alone and still grasp your argument. White space, clear section headers, and informative first sentences are not decoration; they are mercy, and mercy is rewarded.
• Never make them work to find the point. Every paragraph should declare its purpose in its first sentence. If a reviewer has to read a paragraph twice to learn why it is there, you have spent goodwill you cannot afford.
• Anticipate the question and answer it where it arises. A reviewer reading your approach is silently asking "but what about X?" The proposal that raises X and addresses it before the reviewer can write it in the margin earns trust; the one that ignores X invites the critique.

To make front-loading concrete, compare two openings of the same paragraph. Buried: "Childhood asthma has many environmental triggers. Dust mites, mold, and tobacco smoke have all been studied. Housing quality is a factor that has received attention. In low-income housing, these factors often co-occur. Our project addresses this." A reviewer must read five sentences to learn what the project even is. Front-loaded: "We will reduce childhood asthma attacks in low-income housing by remediating the three environmental triggers — mold, dust mites, and tobacco smoke — that co-occur there. Here is why each matters." The point is in the first sentence; everything after it is support. Same facts, same rigor — but the second version respects a tired reader and rewards a skim. Multiply that difference across forty pages and forty proposals, and you see why structure is not cosmetic.

⚠️ Common Pitfall: The "save the best for last" instinct, trained into us by school essays, is poison in grant writing. A reviewer is not a patient reader building toward your grand conclusion; they are a tired triager deciding, early and fast, whether to invest further attention. Putting your strongest material at the end means most reviewers never reach it at full attention. Lead with your best. Then support it. Then, if there is room, build on it. Never make the reviewer earn your thesis.

📋 Template — The skim test: Before you submit any proposal, run this test on yourself. Read only the title, the first sentence of each paragraph, the section headings, and any bolded text or figure captions — nothing else, at speed, the way a tired reviewer will. Then ask: from that skim alone, can you state (1) what the project will do, (2) why it matters to this funder, and (3) why this team can pull it off? If yes, your structure is doing its job and the skimming reviewer will arrive at the right impression. If no, your argument is hidden in the body text where fatigue will bury it — and you need to lift your key points into the first sentences and headings. Most reviewers will skim; the skim test makes sure they skim their way to a "yes."

🪞 Learning Check-In: Think about how you read something long and obligatory — terms of service, a dense report, the twenty-third proposal. You skim. You look for signposts. You give up on paragraphs that do not quickly reward you. Now ask: does your own writing assume a reader as generous and rested as you wish they were, or one as hurried and divided as you actually are when the roles are reversed? Designing for the second reader is the whole game.

2.5 What Reviewers Look For — and in What Order

Reviewers do not weigh all parts of your proposal equally, and they do not consider them in the order you wrote them. They run, consciously or not, a rough triage of questions, and they tend to ask them in a particular sequence. Knowing the sequence lets you put your answers where the reviewer is already looking.

The order looks roughly like this:

1. Fit: "Is this even ours to fund?" Does the project match our mission, our priorities, our program, our eligibility rules? A "no" here ends it immediately, regardless of quality. This is why alignment (Chapter 3) precedes everything.
2. Significance / Need: "If they succeed, does it matter?" For research, is the question important? For a program, is the need real and urgent? A project that is feasible but unimportant scores poorly; reviewers are looking for impact.
3. Approach / Feasibility: "Can they actually do it?" Is the plan sound, rigorous, and realistic? Strong significance with a weak approach is a classic, fundable-looking, ultimately-rejected proposal — exciting but not credible.
4. Capacity: "Are these the right people, in the right place, to pull it off?" Track record, expertise, resources, environment.
5. Budget and the rest: "Is the ask reasonable and the package complete?" By now the reviewer has largely decided; the budget mostly confirms or undermines credibility rather than driving the decision (though an unreasonable budget can sink an otherwise strong proposal).

💡 Key Insight: Reviewers decide significance early and budget late, but beginners often invert their effort, lavishing attention on a detailed budget and methods while underinvesting in the significance and fit that actually drive the score. Spend your best writing where the decision is actually made: on fit and significance, up front. We will operationalize each of these questions in Part II — Chapter 6 and 7 for the up-front fit-and-significance pitch, Chapter 8 for need, Chapter 9 for approach, Chapter 13 for capacity, Chapters 11–12 for budget.

🔍 Why Does This Work?: Why do reviewers ask "does it matter?" before "can they do it?" Because their job is to allocate scarce dollars to maximum mission impact. A perfectly executed project on a trivial question advances the mission little; an important question pursued with a sound (even if not flawless) plan advances it greatly. Significance is the multiplier. So the reviewer protects against the most expensive mistake — funding the feasible-but-pointless — by screening for importance first. Write to that logic: establish that your work matters before you prove you can do it.

The Two Fears That Shape Every Score

Underneath the questions, reviewers carry two quiet fears, and understanding them explains a great deal of otherwise-puzzling reviewer behavior. The first fear is championing a flawed proposal — staking their credibility on a project that later turns out to be unfeasible, naïve, or already done by someone else. The second fear is missing a great one — being the reviewer who triaged what became a landmark study. These two fears pull in opposite directions, and a good proposal soothes both.

You soothe the first fear by being rigorous, specific, and honest about limitations: you show you have thought about what could go wrong (the "pitfalls and alternatives" strategy of Chapter 9), you do not overclaim, and you give your advocate ammunition to defend you against skeptics. You soothe the second fear by making your significance vivid and your innovation clear: you make the reviewer feel the cost of not funding you. The proposals that win tend to do both at once — exciting enough that a reviewer fears missing them, solid enough that a reviewer does not fear championing them. The proposals that lose usually trip one fear: thrilling but flimsy (triggers the first fear), or solid but forgettable (triggers the second).

🔍 Why Does This Work?: Why frame reviewer behavior in terms of fear rather than preference? Because a volunteer reviewer's reputation is on the line in the room. When they advocate for your proposal, colleagues will judge their judgment. People protect their credibility, so they gravitate toward proposals they can defend without embarrassment. If you write so that supporting you is safe as well as exciting, you have aligned your proposal with the reviewer's deepest incentive — and that, far more than flattery or polish, is what moves a score.

2.6 The Program Officer: Your Most Important Relationship

Now the single most underused tactic in grant writing, and the one most likely to feel uncomfortable to a beginner: talk to the funder before you write.

Most funders employ program officers (called program managers, program directors, or simply "the staff" at some foundations) whose job is to steward a portfolio of grants in a particular area. Crucially, part of their job is to talk to prospective applicants. They are not gatekeepers to be evaded; they are guides who can tell you, in a fifteen-minute conversation, things you could not learn from any amount of website-reading: whether your project fits their current priorities, which mechanism or program is the right one, whether they have funded similar work, what their reviewers tend to value, and — sometimes most valuably — whether you should bother applying at all.

This last point is worth dwelling on. A program officer who tells you "honestly, this isn't a fit for us" has just saved you weeks of unpaid work and a near-certain rejection. That is not a setback; it is a gift. The applicants who lose the most time in grant writing are the ones who never ask, who write entire proposals to funders who would have told them, had they asked, not to.

✅ Best Practice: Before investing serious time in a proposal, attempt to make contact with the relevant program officer. For federal agencies, the funding announcement usually names a contact. For foundations, look for a program officer in your area; for small foundations, a brief, respectful email may reach the decision-maker directly. Come prepared with a crisp one-paragraph description of your project (your mission-transaction framing from Chapter 1) and a few specific questions. Respect their time, listen more than you talk, and take notes. Then use what you learn to shape the proposal — or to decide not to write it.

What do you actually ask? A short, high-value list:

• "Is this project a fit for your current priorities?" (alignment)
• "Which program or mechanism would be the right home for it?" (so you apply to the right thing)
• "Have you funded work like this before?" (calibrates your odds and your framing)
• "What do your reviewers tend to find most compelling — or most often criticize — in this area?" (gold, if they answer)
• "Is there anything about our approach you'd encourage us to strengthen or reconsider before we apply?"

If a phone call feels too forward, or the funder prefers written contact, a short email opens the same door. Keep it under 150 words: who you are, your one-paragraph project framing, a specific fit question, and a low-pressure ask.

📋 Template — First-contact email: Subject: Fit question — [your topic] for [program name] "Dear [Name], I lead [organization/role]. We are developing [one sentence: the project, framed around the funder's mission], and we are considering applying to [program]. Before investing in a full proposal, I wanted to ask: is this a fit for your current priorities, and if so, is [mechanism/program] the right home for it? I have attached a one-paragraph summary. I'm grateful for any guidance, and equally grateful for a candid 'not a fit.' Thank you for your time. — [Name, contact]"

The line "equally grateful for a candid 'not a fit'" does real work: it signals that you respect their time and will not argue, which makes an honest answer easier to give — and an honest "no" now is worth a dozen wasted weeks later.

⚠️ Common Pitfall: Beginners avoid contacting program officers out of a fear of "bothering them" or "looking unprepared." This gets it backwards. Program officers want well-matched applications and fewer hopeless ones in their pile; a good pre-application conversation serves them too. What looks unprepared is not asking and then submitting a misaligned proposal. The only way to bother a program officer is to come with questions their website plainly answers, or with no specific project to discuss. Come prepared and specific, and you are doing them — and yourself — a favor.

Here is what a good first contact actually sounds like — a composite, condensed, but true to form. Notice how much the applicant learns in a few exchanges, and how the program officer's tone shifts from gatekeeper to guide once the applicant proves they have done their homework.

📊 From the Field — a program-officer call (composite): Applicant: "Thank you for taking a few minutes. I lead a community health center, and we run a diabetes-prevention class. We have early data suggesting it lowers participants' blood sugar, and we're considering applying to your [program] to test it more rigorously. Before we invest in a full proposal, I wanted to check whether this is a fit for your current priorities." Program officer: "It could be. We did move our emphasis last year toward interventions that are scalable — things other clinics could adopt cheaply. Is yours?" Applicant: "It is — it's built on free text messaging and existing staff, so the marginal cost per patient is low. I can speak to scalability directly." Program officer: "Good, lead with that; our reviewers care about it. One caution: we've funded two adherence projects recently, so reviewers may ask what's new here. And honestly, the [specific mechanism] you mentioned is the wrong one — it's for larger trials. You'd want [different mechanism] for a project this size." Applicant: "That's exactly what I needed. May I send a one-page concept before we apply?" Program officer: "Sure. Keep it to a page."

In five minutes the applicant has learned the current priority (scalability), a likely reviewer objection to preempt (what's new), a corrected mechanism (saving a fatal misfire), and an open door (the concept paper). No website could have delivered that. This is why the call comes before the writing.

There are limits and etiquette, which differ by funder and which we detail in Part III. Some agencies have rules about contact during certain windows; some foundations prefer a letter of inquiry to a call. But the underlying truth holds across the funding world: relationships with funders matter as much as the written proposal, and the relationship usually begins with a conversation you initiate before you write. This is recurring theme number six of this book, and you will see it again and again.

📜 How We Got Here: Why do funders employ people whose job includes talking applicants out of applying? Because review is expensive. Every misaligned proposal costs the funder reviewer time, staff time, and goodwill. A program officer who steers a poorly matched applicant elsewhere, and helps a well-matched one apply strongly, makes the whole system more efficient. Understanding this dissolves the fear: you and the program officer have a shared interest in your applying only if it fits. The conversation is not an imposition on the system; it is the system working as designed.

🔄 Check Your Understanding: A colleague says, "I never contact program officers — I don't want to annoy them or seem like I'm angling for special treatment." Give two reasons, from this section, that this reasoning costs them, and name one thing a program officer can tell you that no website can.

Answer

It costs them because (1) program officers want well-matched applications and fewer hopeless ones, so a prepared, specific inquiry helps them too — it is not an annoyance; and (2) skipping the call risks submitting a misaligned proposal or using the wrong mechanism, wasting far more time than the call would. Things only a program officer can tell you: whether your project fits current priorities, which mechanism/program is right, whether they have recently funded similar work, and what their reviewers tend to value or criticize.

2.7 Reading the Funder's Mind: Translating Your Project

Put it all together and you arrive at a practical skill you will use in every proposal: taking the same true project and re-expressing it in the funder's language, aimed at the reviewer, organized around the questions they ask in the order they ask them.

Consider Dr. Hernandez from Chapter 1, with her text-message intervention for Type 2 diabetes. Watch the translation.

Applicant-centered (what beginners write): "We have developed an innovative text-message platform that delivers tailored medication reminders and glucose feedback. Our pilot data are promising. We request funding to conduct a randomized trial."

This is accurate and inert. It leads with the applicant's cleverness, not the funder's mission. It asks the reviewer to supply the significance themselves.

Funder-centered (what wins): "Half of adults with Type 2 diabetes do not take their medications as prescribed, a failure that drives avoidable complications, hospitalizations, and cost — a problem squarely within [this institute's] mission to reduce the burden of diabetes. We propose to test whether a low-cost, scalable text-message intervention improves adherence and glycemic control in a randomized trial, building on pilot data showing [specific result]. If it works, it offers the institute a cheap, deployable tool against one of diabetes care's most stubborn problems."

Same project. But now it opens with the funder's mission and a significant problem, frames the work as a way to advance that mission, and tells the reviewer exactly why to care — before describing the cleverness. It answers "is it ours to fund?" and "does it matter?" in the first three sentences, where the reviewer is already asking them.

📋 Template — The funder-centered opening: Draft your project's opening as four moves, in this order: (1) the funder's problem — name a problem that is squarely within the funder's mission; (2) its significance — show it matters (who is affected, what it costs); (3) your project as the vehicle — "we propose to [do X] in order to [advance the mission]"; (4) the payoff to the funder — what they get if you succeed. Notice that your idea appears only at move three, framed as a means to their end. Keep applicant-centered cleverness out of the first two moves entirely.

The same translation works at every scale. RYCC's coding program, applicant-centered, says "we run a great coding club and want to expand." Funder-centered, aimed at a youth-opportunity foundation, it says "the digital-skills gap is widening for kids in our neighborhood, foreclosing futures the foundation exists to open; our proven program can reach three times as many of them for [amount], turning the foundation's dollars directly into youth opportunity." Same expansion, transformed from a request for support into an offer to advance the funder's mission.

A caution before you run too far with this. Translating your project into the funder's language is alignment, not dishonesty — and there is a line. Honest translation re-frames true features of your project to foreground the ones this funder values. Dishonest translation invents or distorts features to fit, claiming a community-led process you do not have or a population you do not serve. The first wins funding and keeps your integrity; the second wins funding you cannot deliver on, which ends in failed reports, a damaged reputation, and a funder who will not take your next call. If you find that the only way to fit a funder is to misrepresent your project, you have not found a framing problem — you have found the wrong funder, and Chapter 3 will help you find a better one. Alignment is about telling the true story that this funder most needs to hear, not a false one.

🔍 Why Does This Work?: Why does leading with the funder's problem outperform leading with your solution, even when your solution is genuinely clever? Because the reviewer must care about the problem before they can care about the solution. A clever answer to a question the reviewer has not yet been made to care about reads as a solution in search of a problem. By establishing the problem and its stakes first — their problem, in their mission's terms — you create the need that your project then satisfies. You make the reviewer want the thing before you reveal that you have it.

📐 Project Checkpoint — Write your funder-centered opening: Using the four-move template above, draft a short opening paragraph for your project, aimed at the kind of funder you expect to approach. You drafted a rough mission-transaction paragraph in Chapter 1; sharpen it now with the four moves, leading with the funder's problem and its significance, and placing your own idea only at move three. Save it in your "My Proposal" document. You will refine it again in Chapter 3 once you have identified a specific funder, and it will become the seed of your specific aims or executive summary in Chapters 6–7.

Spaced Review

Retrieval strengthens memory, so before moving on, answer these from Chapter 1 without looking back.

1. (From Chapter 1) What is the "mission transaction" reframe, and how does this chapter's idea — that your true audience is the individual reviewer — build on it?
2. (From Chapter 1) Name three of the six common reasons proposals fail. Which of them does "thinking like a funder" most directly prevent?
3. (From Chapter 1) What does it mean for an application to be triaged, and how does Section 2.4's account of reviewer fatigue explain why triage exists?

Answers

1. The mission transaction is the idea that a funder buys progress toward its own mission, not your project per se. This chapter sharpens it: the mission is held by an individual reviewer, so you write to advance the mission as that tired human experiences it — early clarity, answered questions, a defensible case. 2. Any three of: misalignment, unclear ask, weak structure, insufficient evidence, late start, noncompliance. Thinking like a funder most directly prevents misalignment (and, via front-loading, the unclear ask). 3. Triage is setting aside the lower-ranked half without full discussion. Reviewer fatigue explains why: panels cannot deeply debate every proposal, so they protect their limited attention by discussing only the top tier — making early clarity and fit decisive for survival.

Chapter Summary

Key Takeaways

• Funders have missions, not spare cash. They fund to advance their mission, and their published priorities tell you exactly what will persuade them. Your project's abstract worth matters far less than its worth to this funder's mission, now, against the competition.
• Your true audience is the individual reviewer — tired, expert, overloaded — not the organization. Write for that human's attention, fatigue, and need to defend their choice.
• Decisions are made in different rooms: the NIH study section (a few assigned reviewers carry your fate to a panel), the NSF panel (Intellectual Merit and Broader Impacts both count), and the foundation board (relationship-driven, program-officer-mediated). The same project must be written differently for each.
• Reviewer fatigue is real and designable-for: front-load what matters, make structure visible, never make them hunt for the point, and answer their questions where they arise.
• Reviewers ask questions in order: fit → significance → approach → capacity → budget. Spend your best writing on fit and significance, where the decision is actually made.
• The program officer is your most important relationship. A pre-application conversation can confirm fit, point you to the right mechanism, reveal what reviewers value, and sometimes save you from a hopeless application. Relationships matter as much as the document.

Action Items

• Read your likely funders' mission and priority statements as descriptions of the person you must persuade.
• Draft your project's funder-centered opening using the four-move template (Project Checkpoint).
• Identify a program officer or contact for at least one likely funder, and plan the questions you would ask.

Common Mistakes to Avoid

• Writing to the organization instead of the human reviewer.
• Saving your strongest point for the end (reviewer fatigue means it is never reached at full attention).
• Lavishing effort on the budget and methods while underinvesting in fit and significance.
• Avoiding program officers out of a fear of "bothering" them.

Decision Framework: Are You Ready to Write?

Before drafting a full proposal, you should be able to answer: (1) Whose mission does this advance, in their words? (2) Who is the reviewer, and in what room will they sit? (3) Can I state my fit and significance in three sentences a tired reviewer would grasp on page one? (4) Have I talked to a program officer, or at least tried? If you cannot answer these, you are not yet ready to write — you are ready to research, which is Chapter 3.

Looking Ahead

You now understand the people you are writing for and what moves them. The obvious next question is: which funder, exactly? Of the thousands of possible funders, which ones share your mission closely enough to be worth your time — and how do you find them without drowning? Chapter 3: Finding the Right Funder turns funder research from a desperate Google search into a disciplined strategy. You will learn the databases the professionals use, how to read a funding announcement for what it really means, how to score alignment honestly, and how to build a funder pipeline so that you spend your limited time only on the funders most likely to fund you. The thinking-like-a-funder mindset you built here is the lens; Chapter 3 is the disciplined search that turns the lens on the real world and hands you a short list of funders worth pursuing.

Continue to the Exercises, the Quiz, and the two Case Studies (1, 2). The Key Takeaways card is your quick-review anchor.

Next: Chapter 3 — Finding the Right Funder: Research, Alignment, and the Art of Not Wasting Your Time.