Grant writers work at the intersection of two knowledge demands: they must know their organization's programs, outcomes, and capacity in enough depth to represent them accurately and compellingly, and they must know each funder's priorities, history, and culture well enough to make their organization's work genuinely relevant to each funder's goals.
Neither of these knowledge bases is static. Funders change their priorities, their leadership, and their strategic direction. Organizations evolve their programs, develop new outcomes data, and expand or contract their capacity. The grant writer who relies on last year's knowledge for this year's proposals is working with outdated intelligence on both sides of the equation.
Four information problems define what a grant writer's knowledge system needs to solve:
Problem 1: Funder intelligence — Who are these funders? What do they actually care about? What makes their funded organizations different from the ones they decline?
Problem 2: Organizational knowledge — What does this organization actually do? What outcomes have been achieved? What can be accurately claimed in proposals?
Problem 3: Opportunity pipeline management — What opportunities are in the pipeline? What deadlines are approaching? What's the status of each application?
Problem 4: Professional expertise — What has been learned about grant writing craft? What makes proposals win? What approaches have been successful or unsuccessful?
Problem 1: Funder Intelligence — The Foundation of Compelling Proposals
Funder intelligence is the knowledge that converts generic grant proposals into targeted ones. The proposal that could have been written for any funder rarely wins; the one that demonstrates genuine understanding of what this specific funder is trying to accomplish competes differently.
FUNDER INTELLIGENCE SYSTEM
Per funder:
STRATEGIC PROFILE:
Mission: [What this funder is trying to accomplish — in their own words]
Strategic priorities: [Current focus areas — from recent 990s, website, RFPs, announcements]
Geographic focus: [Where they fund]
Organization type preferences: [What kinds of organizations they fund]
Grant size range: [Typical grant amounts; maximums; multi-year availability]
WHAT THEY ACTUALLY FUND:
Recent grantees: [Who they've funded recently — what kinds of work]
What the funded work has in common: [Pattern across grantees — what actually gets funded]
What they say vs. what they fund: [If these differ — sometimes they do]
Where our work aligns: [Specifically — which of their priorities does our work serve?]
Where our work doesn't fit: [What we shouldn't try to make fit]
RELATIONSHIP INTELLIGENCE:
Key contacts: [Program officers; their areas; their backgrounds]
Our relationship history: [Prior contact; prior proposals; prior funded grants]
What I've learned about their preferences: [From conversations, declines, funded grants]
How they prefer to communicate: [Email? Phone? Meetings? Conferences?]
APPLICATION INTELLIGENCE:
Application requirements: [LOI? Full proposal? Online portal? Deadlines?]
What they ask for: [Evaluation criteria; required sections; budget format]
What matters most in their review: [From program officers, funded grantees, feedback]
What we've been told about our prior proposals: [Feedback received]
WHAT I KNOW ABOUT WHAT WINS WITH THIS FUNDER:
What their funded proposals have in common: [From research on grantees]
What they respond to positively: [From conversations with program officer]
What they don't fund even if it meets criteria: [What I've learned from declines]
What to avoid: [Content, framing, language that doesn't work for this funder]
"What they say vs. what they fund — if these differ" is the funder intelligence field that distinguishes experienced grant writers from new ones. Funders don't always fund exactly what their guidelines describe. Some funders say they fund "innovative approaches" but consistently fund well-established organizations doing conventional work. Others say they fund "systems change" but their grantee list shows primarily direct service organizations. Understanding what a funder actually funds — not just what they say they fund — is the intelligence that makes proposal targeting accurate.
Problem 2: Organizational Knowledge — Accurate and Specific Proposals
Organizational knowledge is what makes proposals accurate and specific rather than generic and vague. The proposal that says "we serve thousands of people annually" is weaker than the one that says "we served 847 clients last year, 73% of whom were below 200% of the federal poverty level." Both require the grant writer to know the organization deeply.
ORGANIZATIONAL KNOWLEDGE SYSTEM
Programs and services:
PER PROGRAM:
What it does: [Specific description — not the mission statement, the actual activities]
Who it serves: [Demographics; eligibility; reach]
What it costs to deliver: [Per participant; total annual; program budget]
Outcomes achieved: [Specific data — not "participants improve their lives"]
Evidence of effectiveness: [Studies; evaluations; comparison data]
What makes it different: [Distinctive approach; why it works when other approaches don't]
Staff delivering it: [Qualifications; experience; capacity]
WHAT'S NOT WORKING:
Program challenges: [Honest — what's hard; where outcomes are weaker]
Capacity constraints: [What limits the program's reach or quality]
What would improve outcomes: [If we had more resources; what specifically we'd do]
Organizational capacity:
FINANCIAL HEALTH:
Annual budget: [Total; current year]
Revenue sources: [By type; diversity; trends]
Reserves: [Months of operating expenses]
Audit status: [Clean? Concerns?]
LEADERSHIP AND GOVERNANCE:
Executive director: [Tenure; background; relevant expertise]
Board composition: [Size; relevant expertise; active vs. passive]
Key staff: [Who delivers programs; their qualifications]
TRACK RECORD WITH GRANTS:
Prior grant history: [What funders we've had; outcomes we've reported; relationships maintained]
What we've reported back to funders: [Outcomes delivered on prior grants]
Where we've fallen short of grant goals: [Honest — and what we learned]
WHAT WE CAN ACCURATELY CLAIM:
Outcomes data we have: [Real data; date range; measurement methodology]
Outcomes data we don't have but should: [What we should be collecting]
What I've been told we can and can't say: [From program staff; executive director]
"What we can accurately claim" is the professional discipline field for organizational knowledge. Grant writers are sometimes pressured to inflate outcomes data, broaden program descriptions, or claim capacity the organization doesn't have. The grant writer who knows what the organization can accurately claim — and maintains that standard — protects the organization's credibility and relationships with funders. A funded grant that the organization can't deliver on damages relationships that took years to build.
Problem 3: Opportunity Pipeline Management
Opportunity pipeline management is what ensures that no deadline is missed, every proposal is submitted on time, and the organization's grant portfolio is strategically coherent.
OPPORTUNITY PIPELINE MANAGEMENT SYSTEM
Per opportunity:
PROSPECT STATUS:
Funder: [Name and contact]
Opportunity type: [Annual cycle / LOI / Invited / New prospect]
Status: [Researching / Planning / LOI submitted / Proposal in progress / Submitted / Decision pending / Funded / Declined]
DEADLINES:
LOI deadline: [If applicable]
Application deadline: [Hard deadline]
Decision expected: [When we'll hear]
Grant start date: [If funded, when the grant period begins]
PROPOSAL DETAILS:
Amount requested: [What we're asking for]
Program being funded: [Which organizational program]
What the grant would fund: [Specific activities; staff; materials]
TIMELINE:
Working deadline for internal completion: [2 weeks before submission deadline]
Review and approval needed: [Who reviews; their timeline]
Budget sign-off: [From finance; timeline]
Executive director signature: [If required; lead time]
WHAT'S BEEN SUBMITTED:
Date submitted: [When]
What was submitted: [Final version; any LOI; supporting materials]
Reference number: [Portal reference or tracking]
Portfolio view:
REVENUE TRACKING:
Funded grants by funder: [Amount; period; what funds]
Pending (submitted, awaiting decision): [Amount; probability]
In development: [Amount; deadline]
Revenue by program: [Which programs are funded vs. unfunded]
STRATEGIC COHERENCE:
Funder diversification: [Too concentrated in one funder?]
Program coverage: [Which programs are well-funded vs. underfunded]
Multi-year stability: [Which funders provide multi-year support?]
Problem 4: Professional Expertise — Grant Writing Craft
Professional expertise is what makes proposals excellent rather than just complete — the knowledge of what works in grant writing, how to make arguments compelling, what proposal reviewers actually respond to.
PROFESSIONAL EXPERTISE KNOWLEDGE BASE
What works in proposals:
WHAT MAKES PROPOSALS WIN:
What I've observed in our successful proposals: [Specific — what they had in common]
What I've heard from program officers: [About what they look for]
What I've learned from proposal feedback: [From funders who've given feedback]
What I've observed in proposals from peer organizations: [From publicly available funded proposals]
WHAT DOESN'T WORK:
Common mistakes I've made and learned from: [Specific]
What program officers have told me doesn't work: [From conversations]
What I've cut from proposals that made them better: [What I used to include that wasn't helping]
PROPOSAL CRAFT:
How I approach the needs statement: [My current approach; what I've learned works]
How I handle budget narratives: [What funders actually want to see]
How I write evaluation sections: [What makes evaluation sections compelling vs. perfunctory]
How I handle sustainability: [Addressing this challenge; what works]
WHAT I KNOW ABOUT RELATIONSHIP CULTIVATION:
What makes conversations with program officers productive: [What I've learned]
What I've learned about timing: [When to reach out; when not to]
How I follow up on declines: [What produces useful feedback vs. nothing]
Key Takeaways
-
"What they say vs. what they fund — if these differ." Actual funding patterns are the intelligence, not just guidelines.
-
"What we can accurately claim." Credibility with funders is protected by honest representation.
-
Pipeline management that works backward from submission deadlines. Deadlines missed can't be recovered.
-
"What I've learned from proposal feedback." Funder feedback is the most valuable professional development available.
-
Relationship intelligence per funder. Program officer knowledge compounds over years.
Conclusion
Grant writer software stack addresses four information problems: funder intelligence ("what they say vs. what they fund — if these differ" as the field that distinguishes experienced grant writers; strategic profile with mission, priorities, geographic focus, grant size range; what they actually fund — recent grantees, pattern across grantees, where our work aligns and where it doesn't; relationship intelligence — key contacts, our history, their preferences, how they communicate; application intelligence — what they ask for, what matters most in review, prior feedback); organizational knowledge ("what we can accurately claim" as the professional discipline field; per program — specific activities, who served with demographics, outcomes with real data, evidence of effectiveness, what makes it different; what's not working — honest about challenges and capacity constraints; financial health with revenue diversity; track record with grants including where we've fallen short; "outcomes data we don't have but should collect"); opportunity pipeline management (per opportunity — prospect status, deadlines with hard submission and decision expected, proposal details with amount and what funded, timeline working backward from deadline, review and approval needed, what's been submitted; portfolio view — revenue tracking by funder and type, funder diversification, program coverage, multi-year stability); and professional expertise (what makes proposals win — observations from successful proposals, program officer conversations, proposal feedback, peer organization funded proposals; what doesn't work — specific mistakes; proposal craft for needs statement, budget narrative, evaluation sections, sustainability; relationship cultivation — productive program officer conversations, timing, follow-up on declines). The grant writer who maintains deep knowledge of both funders and the organization builds the targeting advantage that distinguishes competitive proposals from generic ones.
Related reading: The Ultimate Guide to Web Clipping.