The grant writer who has been in the field for a decade has knowledge that can't be quickly replicated: they know which funders consistently fund organizations like theirs and which merely seem to, which program officers respond best to which approaches, which organizational narratives have resonated across multiple funders, and which proposal structures consistently lose with certain funder types.
This accumulated knowledge only improves proposals if it's accessible — not locked in the grant writer's memory where it's retrievable only when they happen to remember it. Four domains build the grant writer's knowledge base: funder intelligence (the deep knowledge of each funder relationship and preference), organizational knowledge (the accurate and current understanding of programs and outcomes), proposal craft knowledge (what the grant writer has learned about writing winning proposals), and sector and field knowledge (the contextual knowledge that makes proposals credible).
Domain 1: Funder Intelligence — The Targeting Advantage
Funder intelligence is the most immediately valuable domain — the knowledge that allows a grant writer to target proposals precisely rather than generically.
FUNDER INTELLIGENCE KNOWLEDGE BASE
Per funder in active prospect or current portfolio:
STRATEGIC UNDERSTANDING:
What this funder is trying to accomplish: [In their own words and in my interpretation]
How their priorities have evolved: [What they funded 3 years ago vs. now]
What direction they're moving: [What I observe vs. what they say]
Where there's tension in their priorities: [What they say vs. what they fund]
WHAT ACTUALLY GETS FUNDED:
Pattern across recent grantees: [What do funded organizations have in common?]
What's been funded in our program area: [Specifically — not generally]
Grant sizes and types: [Typical amounts; multi-year vs. single-year; general operating vs. project]
Who they fund and who they don't: [Unstated preferences I've observed]
OUR RELATIONSHIP WITH THIS FUNDER:
Application history: [What we've submitted; results; dates]
Relationship history: [Conversations; meetings; site visits]
What I've learned about them from direct contact: [Specific — not generic]
What they've said about us or our work: [Verbatim if important]
Where our relationship is: [New / Emerging / Established / Long-term partner]
WHAT WORKS WITH THIS FUNDER:
Framing that has worked: [How we've described our work that resonated]
Framing that hasn't worked: [What we've tried that didn't land]
What they've told us directly about our proposals: [Feedback received]
What I've inferred from outcome patterns: [What distinguishes our funded vs. declined proposals]
APPLICATION KNOWLEDGE:
Their process: [LOI? Full proposal? Portal? Timeline?]
What they emphasize in their guidelines: [What they say matters; what seems to matter more]
Reviewer perspective: [If I know anything about their review process]
Technical requirements: [Page limits; formatting; required sections]
Cross-funder patterns:
WHAT I'VE OBSERVED ACROSS FUNDERS:
What funder types consistently support our work: [Community foundations vs. private foundations vs. corporate]
What our most funded programs have in common: [Why some programs are more fundable]
What our hardest-to-fund programs have in common: [Why some programs face more resistance]
What proposal elements correlate with funding success: [Across our portfolio of proposals]
"What I've inferred from outcome patterns — what distinguishes our funded vs. declined proposals" is the most valuable field in funder intelligence. Most grant writers know why individual proposals succeeded or failed when feedback is available. Few systematically compare across their funded and declined proposals to identify patterns. The grant writer who has done this analysis — "our funded proposals average 2.3 specific outcome metrics per program; our declined proposals average 0.8" or "our funded proposals consistently frame the problem with local data; our declined ones use national statistics" — has actionable intelligence that improves future proposals.
Domain 2: Organizational Knowledge — Accuracy Under Pressure
Organizational knowledge is what protects the grant writer from the most dangerous failure mode in grant writing: inaccurate representation of the organization, its programs, and its outcomes.
ORGANIZATIONAL KNOWLEDGE BASE
Program knowledge:
PER FUNDED PROGRAM:
What it does: [Plain-language description — what actually happens, not the mission statement]
Evidence of effectiveness: [With citation; date; methodology]
Current capacity: [How many people we can serve; current utilization]
Staff delivering it: [Key roles; qualifications; tenure]
What makes it distinctive: [Why this works when others don't; specific approach]
What it doesn't do: [Honest — what's outside scope; what would require expansion]
CLAIMS WE CAN MAKE:
Outcome claims: [Specific; with data period and source]
Impact claims: [What we can say about broader impact vs. what requires qualification]
Comparison claims: [What we can say about ourselves relative to others — verified]
Capacity claims: [What we can accurately say about our ability to deliver]
CLAIMS WE CANNOT MAKE:
What would be exaggeration: [What sounds good but isn't accurate]
What's aspirational: [What we hope to achieve vs. what we've achieved]
What's unverified: [What we believe but haven't measured]
Organizational history and track record:
GRANT HISTORY:
Funders we've had: [Name; years; amounts; what funded; relationship status]
What we reported: [Outcomes delivered on prior grants — must match future proposals]
Where we fell short: [Honest — and what we learned and changed]
Funder relationships maintained: [Who remains a relationship; who we've lost and why]
WHAT WE'VE LEARNED ABOUT OUR FUNDABILITY:
Our most fundable programs: [What makes them compelling]
Our hardest-to-fund areas: [Why; what would improve fundability]
The organizational stories that resonate: [What funders respond to]
What we've been told about why we're funded: [From program officers and feedback]
"Claims we cannot make" is the organizational integrity field. The grant writer who knows explicitly what cannot be claimed — and maintains that standard under pressure from internal stakeholders who want stronger language — protects the organization's funder relationships. The funded grant on exaggerated claims creates a compliance nightmare when reporting time arrives. The declined proposal on accurate claims maintains credibility for future applications.
Domain 3: Proposal Craft Knowledge — What Wins
Proposal craft knowledge is the grant writer's professional intelligence about what makes proposals win — the accumulated learning about narrative structure, argument construction, funder communication, and proposal strategy.
PROPOSAL CRAFT KNOWLEDGE BASE
What makes proposals win:
NARRATIVE STRUCTURE:
How I approach the problem/needs statement: [Current approach; based on what]
How I structure program descriptions: [What works; what I've stopped doing]
How I handle evaluation sections: [What funders actually want to see here]
How I write budget narratives: [What makes them compelling vs. perfunctory]
How I address sustainability: [What works; what sounds hollow]
WHAT WORKS BY FUNDER TYPE:
Community foundations: [What this funder type typically values]
Private/family foundations: [How they differ; what they respond to]
Government grants: [The requirements; what reviewers look for]
Corporate foundations: [What distinguishes their priorities]
WHAT I'VE LEARNED FROM FEEDBACK:
What funders have specifically told me about our proposals: [Organized by theme]
What I've inferred from decline patterns: [What I observe but haven't been told]
What successful re-applications have required changing: [What we changed and it worked]
COMMON MISTAKES I MAKE AND HAVE MADE:
Specific mistakes with specific examples: [What I've learned to avoid]
What I used to think worked that doesn't: [How my practice has evolved]
What early drafts consistently need: [What review always catches]
Writing techniques:
WHAT PRODUCES COMPELLING PROPOSALS:
Opening sentences that work: [Examples; patterns]
How to introduce the organization: [What to include; what's unnecessary]
How to make local data compelling: [Not just quoting statistics]
How to describe impact credibly: [Not overclaiming; not underclaiming]
PROPOSAL PHRASES AND LANGUAGE:
Language that resonates with funders: [What produces positive response]
Language to avoid: [Jargon; clichés; phrases funders have seen too often]
How different funder types use language: [What resonates with whom]
Domain 4: Sector and Field Knowledge — Contextual Credibility
Sector and field knowledge is the contextual awareness that makes proposals credible — understanding the issue areas the organization works in well enough to write about them with authority.
SECTOR AND FIELD KNOWLEDGE BASE
By issue area (for each program area we seek funding in):
WHAT I KNOW ABOUT THIS ISSUE AREA:
Scope and scale: [How large this problem is; evidence base]
What the evidence says about effective approaches: [What works; what doesn't]
What's changed recently: [New research; policy changes; demographic shifts]
How our approach fits in the landscape: [Where we are in the evidence hierarchy]
WHAT FUNDERS BELIEVE ABOUT THIS ISSUE AREA:
How this issue area is framed in philanthropy: [What funders emphasize]
What the major funders in this space are focused on: [Where the sector is going]
What language funders use for this issue: [Versus the language practitioners use]
What's controversial or contested: [What to navigate carefully]
CURRENT CONTEXT:
Recent research or data: [What's changed the context for this issue]
Policy environment: [What policy has done or is doing in this area]
What other organizations are doing: [The landscape of approaches]
HOW I STAY CURRENT:
Sources I monitor: [Specific; not vague "I follow the field"]
How often: [Realistic schedule]
What I do with what I learn: [How it enters proposals]
Key Takeaways
-
"What distinguishes funded vs. declined proposals — from outcome patterns." The self-analysis that produces actionable craft intelligence.
-
"Claims we cannot make" is maintained under pressure. Organizational credibility is protected by consistent accuracy.
-
"What funders have told me about our proposals" organized by theme. Accumulated feedback is the most valuable craft intelligence.
-
Sector knowledge organized by what funders believe, not just what's true. Funder framing matters for proposal language.
-
Relationship history per funder with what I've learned from direct contact. Explicit relationship intelligence compounds over years.
Conclusion
Grant writer knowledge base across four domains: funder intelligence ("what I've inferred from outcome patterns — what distinguishes funded vs. declined proposals" as the most actionable field; strategic understanding — what they're trying to accomplish, how priorities have evolved, where there's tension between what they say and what they fund; what actually gets funded — pattern across recent grantees, grant sizes and types, unstated preferences observed; our relationship — application history, what I've learned from direct contact, where the relationship is; what works with this funder — framing that has and hasn't worked, feedback received; cross-funder patterns with what funder types consistently support our work and what proposal elements correlate with success); organizational knowledge ("claims we cannot make" as the organizational integrity field; per program — plain-language description, evidence with citation and date, current capacity, staff qualifications, what makes it distinctive, what it doesn't do; claims we can make — outcome with data period and source, impact with qualification, capacity claims accurate; grant history — what we reported and where we fell short honestly, relationship status; "what we've been told about why we're funded" from program officers); proposal craft knowledge (narrative structure — how I approach each section based on what works; what works by funder type; "what funders have specifically told me about our proposals — organized by theme" as accumulated feedback intelligence; common mistakes I make and have made — specific examples; proposal language — what resonates and what to avoid by funder type); and sector and field knowledge (by issue area — scope and evidence base, what evidence says about effective approaches, what funders believe vs. what practitioners know, current context and policy environment; organized by what funders believe not just what's true because funder framing matters for proposal language). The grant writer whose knowledge base includes the outcome pattern analysis and accumulated funder feedback builds the targeting and craft advantage that improves funded rates over time.
Related reading: The Personal Knowledge Management Guide.