Key Takeaways — Chapter 2: Thinking Like a Funder
-
Funders have missions, not spare cash. They fund to advance a specific mission, and their published priorities are a literal description of what will persuade them. Decode that language phrase by phrase; if you cannot honestly satisfy it, it may be the wrong funder.
-
Your true audience is the individual reviewer — tired, expert, overloaded — not the organization. Writing for that human (early clarity, visible structure, no buried points) is the difference between a proposal that is complete and one that is persuasive. It is not "simplifying"; it is lowering reading cost while keeping full rigor.
-
Decisions are made in different rooms. NIH study section (2–3 assigned reviewers carry your fate to a panel scoring Significance/Investigators/Innovation/Approach/Environment as one holistic impression); NSF panel (Intellectual Merit and Broader Impacts both count); foundation board (relationship- and program-officer-driven); government office (rubric/compliance); corporate committee (business benefit). Write for the room you're in.
-
Reviewer fatigue is real and designable-for. Front-load what matters, make structure skimmable, never make the reviewer hunt for the point, and answer the "but what about X?" where it arises. Pass the skim test before you submit.
-
Reviewers ask questions in order: fit → significance → approach → capacity → budget. A "no" on fit ends it. Spend your best writing on fit and significance, where the score is actually decided — not on the budget, which mostly confirms or undermines.
-
Two fears drive every score: championing a flawed proposal, and missing a great one. Win by being both defensible (rigorous, honest about limits) and exciting (vivid significance, clear innovation).
-
The program officer is your most important relationship. A pre-application conversation can confirm fit, correct your mechanism, reveal what reviewers value, and save you from a hopeless application — and it serves the funder too. Relationships matter as much as the document.
-
Translate, don't shoehorn. Re-frame the true features of your project to lead with the funder's problem and its significance, placing your idea as the vehicle. Inventing fit is dishonest and self-defeating; if only misrepresentation works, find a better funder.
Common Mistakes
- Writing to the organization's logo instead of the human reviewer.
- Saving your best point for the end.
- Over-investing in budget/methods while under-investing in fit and significance.
- Avoiding program officers for fear of "bothering" them.
Decision Framework — Ready to write?
You should be able to answer: (1) Whose mission does this advance, in their words? (2) Who is the reviewer, in what room? (3) Can I state fit + significance in three page-one sentences? (4) Have I talked to a program officer (or tried)? If not, you're ready to research — Chapter 3 — not to write.
Your Project
You should now have a sharpened, funder-centered opening paragraph (four moves: funder's problem → significance → your project as vehicle → payoff) and a plan/email for contacting a program officer.