Grant writers research constantly: they research funders to understand their priorities, research organizational programs to describe them accurately, research sector context to make proposals credible, and research prior successful proposals to improve current ones. The challenge is converting all of this research into the outputs that produce funding: compelling proposals, thorough grant reports, strategic prospect analyses, and organizational narratives that travel across proposals.
Research that doesn't convert into output doesn't fund programs. Four outputs define the research-to-output work in grant writing: grant proposals (the primary funding vehicle), grant reports (the accountability demonstration), funder prospect analyses (the cultivation roadmap), and organizational narratives (the reusable content asset).
Output 1: Grant Proposals — Translating Research into Funded Arguments
Grant proposals are the primary output — translating the grant writer's research about the funder, the organization, and the issue area into a compelling argument for why this funder should invest in this work.
PROPOSAL SYNTHESIS WORKFLOW
Pre-writing synthesis — before drafting begins:
WHAT I KNOW ABOUT THIS FUNDER (from knowledge base):
Their stated priorities: [What the guidelines say]
What they actually fund: [Pattern from grantee list; my research]
What I know from prior contact: [What the program officer has said]
What has worked with them before: [If prior relationship]
What hasn't worked: [Framing, language, arguments that have missed]
WHAT I KNOW ABOUT THE ORGANIZATION (from knowledge base):
Program to be funded: [What it does, specifically]
Outcomes achieved: [Verified data; period; source]
What makes it distinctive: [Why this approach; what evidence]
What it costs: [Budget; per-participant cost]
Who delivers it: [Staff; qualifications]
THE CONNECTION:
How does this program serve this funder's priorities? [Specifically — not generically]
What evidence do I have that matches their interest in evidence?
What's the strongest argument for why this funder should fund this program?
What's my most honest assessment of fit? [1-10; what would improve it]
Proposal structure decisions — based on synthesis:
LEADING ARGUMENT:
What argument am I leading with? [Not what's in the guidelines — what's most compelling]
Why this argument for this funder? [What I know about what they respond to]
PROBLEM FRAMING:
How am I framing the problem this funder cares about? [In their language; from their perspective]
What data am I using? [Local vs. national; why this data for this funder]
What's the connection to their geographic or population focus?
PROGRAM DESCRIPTION:
What aspects of our program am I emphasizing? [Based on funder priorities]
What's the distinctive element that makes us different from other applicants?
What outcomes am I claiming? [Only verified; with source]
EVALUATION:
What are my measurable targets? [Specific; realistic; tied to program activities]
How will I measure? [Method; who; timeline]
What will I report back to this funder? [Setting up the report]
BUDGET:
What am I requesting and why? [Specific justification per line item]
What does this cover? [What percentage of program cost; what's unfunded]
What else funds this program? [Funder diversification; matching]
WHAT MAKES EACH SECTION COMPELLING:
Needs statement: Not just statistics — why this problem matters to THIS FUNDER in THIS COMMUNITY
Program description: Not what we do — what we've learned that makes us effective
Evaluation: Not how we'll measure — what we expect to find and why that matters
Budget: Not a list of expenses — evidence that we know what it costs to deliver this
Sustainability: Not how we'll raise money — how this becomes durable because it works
"What's the strongest argument for why this funder should fund this program?" is the synthesis question that produces the most compelling proposals. Many grant writers draft proposals that describe the program and hope the relevance is apparent. The ones who articulate the strongest argument before drafting — and structure the proposal around making that argument — write proposals that feel compelling rather than comprehensive.
Output 2: Grant Reports — Demonstrating Accountability and Building Relationships
Grant reports are the output that determines whether a funded relationship becomes a long-term partnership. The grant report that is late, vague, or reveals that the organization couldn't deliver what it promised damages the relationship more than almost anything else.
GRANT REPORT SYNTHESIS WORKFLOW
Pre-report synthesis — before drafting begins:
WHAT WAS PROMISED:
Grant proposal outcomes: [What we said we'd achieve]
Grant agreement requirements: [What the grant contract specifies]
Prior conversations with program officer: [Any informal commitments made]
WHAT WAS ACHIEVED:
Actual outcomes: [What happened; measured how; compared to targets]
Where we met or exceeded targets: [Specifically; with data]
Where we fell short: [Specifically; with data; with explanation]
Why there was any variance: [Honest; not defensive]
WHAT WE LEARNED:
What worked better than expected: [What this tells us about the program]
What worked less well: [What we're changing as a result]
What we'd do differently with this grant: [Honest program learning]
Report structure decisions — based on synthesis:
HOW TO ADDRESS SHORTFALLS:
If we didn't meet targets: [Acknowledge directly; explain honestly; describe changes made]
If we used funds differently than proposed: [Was this authorized? How to explain]
If program was discontinued: [How to handle this relationship]
HOW TO DEMONSTRATE VALUE:
Participant stories: [Specific; with permission; tied to outcomes]
Community impact: [What changed because of this program]
What wouldn't have happened without this grant: [Attribution; honest]
NEXT RELATIONSHIP STEP:
What does this report position us for? [Re-application? Next conversation?]
What should I be sure to include for relationship purposes? [What this funder cares about]
What should I follow up on in conversation? [Beyond the written report]
WHAT MAKES GRANT REPORTS EXCELLENT:
Honesty about shortfalls: Funders know programs don't always hit every target
The grant writer who explains honestly builds more trust than the one who hides
Specificity: Participant counts; outcome percentages; named changes made
Learning: What we know now that we didn't when we applied
Narrative alongside data: The story that makes the numbers matter
Funder acknowledgment: If appropriate; how the grant enabled this work
What's next: Where the program goes from here; whether grant continued or not
"What we'd do differently with this grant — honest program learning" is the relationship-building field in grant reports. Funders who receive grant reports that honestly describe what worked, what didn't, and what the organization has learned are receiving evidence of organizational learning capacity — which is one of the things most funders are investing in when they make grants. The grant report that presents perfect execution is less credible and less relationship-building than the one that presents honest reflection.
Output 3: Funder Prospect Analyses — The Cultivation Roadmap
Funder prospect analyses are the output that guides cultivation strategy — translating research on potential funders into specific plans for relationship development and proposal timing.
FUNDER PROSPECT ANALYSIS WORKFLOW
Per prospect analysis:
WHAT I RESEARCHED:
Funder basics: [Mission; priorities; grant sizes; geography; grantee types]
Recent grantees: [Who they've funded; pattern; what it tells me]
Our potential fit: [Specifically where our work aligns]
Application process: [How to apply; deadlines; whether LOI required]
MY ASSESSMENT OF FIT:
Overall fit rating: [1-5 or percentage]
Strongest alignment: [Specifically where we fit best]
Weakest alignment: [Where we'd be stretching]
What would improve fit: [If we developed a specific program element; if they shifted priorities]
RELATIONSHIP STATUS:
Do we have any connection? [Board? Peer organization? Staff?]
What would be the first step to establish connection? [Specific]
Who should make that connection? [Executive director? Program staff? Grant writer?]
RECOMMENDED STRATEGY:
Apply this cycle? [Yes / No / Soft research first]
If yes: What program; what amount; what approach
If not yet: What to do to position for future application [Timeline; steps]
WHAT CONCERNS ME:
Risk factors in this prospect: [Why they might decline despite apparent fit]
What we'd need to address in the proposal: [Specific challenges]
Whether it's worth the investment: [Time to develop this prospect vs. expected return]
Output 4: Organizational Narratives — The Reusable Content Asset
Organizational narratives are the reusable content that travels across proposals — descriptions of programs, organizational history, impact statements, and needs framings that can be adapted for multiple funders rather than rewritten from scratch.
ORGANIZATIONAL NARRATIVE SYNTHESIS WORKFLOW
What to develop as reusable narrative:
ORGANIZATIONAL BOILERPLATE:
Organization founding and history: [Brief; most relevant facts]
Mission statement: [Official; used consistently]
Program overview: [What the organization does at the level above individual programs]
Organizational credentials: [Why we're the right organization to do this work]
PER PROGRAM NARRATIVE BLOCKS:
Program description: [Adaptable; core content stable; language and emphasis adjustable]
Outcomes narrative: [What we achieve; with data; adaptable to funder interest]
Distinctive approach: [What makes our approach different; why it works]
NEEDS NARRATIVE BY ISSUE AREA:
The problem we're addressing: [Adaptable to local vs. national; different data for different funders]
Who is affected: [Demographic framing; adaptable to funder focus population]
Why this problem persists: [What the evidence says; adaptable to funder theory of change]
WHAT MAKES NARRATIVES REUSABLE BUT NOT GENERIC:
Core content that stays stable:
Factual information: [Numbers; dates; program descriptions — shouldn't change funder to funder]
Organizational positioning: [Who we are; why we do this — consistent]
Outcome claims: [Only what we can verify — same data across proposals]
Framing and emphasis that adapts:
Which outcomes to emphasize: [Match to funder priority]
Which program elements to highlight: [Match to funder interest]
Problem framing language: [Match to how this funder talks about this issue]
Geographic framing: [More local vs. more state/national based on funder focus]
WHAT MAKES A NARRATIVE BLOCK VALUABLE:
It's accurate and verified: [Can be used without fact-checking each use]
It has multiple versions: [200 words; 100 words; 500 words — for different applications]
It's dated: [When outcomes were measured; when description was current]
It's tagged by program and funder type: [Easy to find the right block]
The Research-to-Output Connection
WHAT EACH OUTPUT REQUIRES
Grant proposals:
Funder knowledge: Priorities + what actually gets funded + relationship intelligence
Organizational knowledge: Program specifics + verified outcomes + distinctive approach
Sector knowledge: Issue framing + evidence base + what funders believe
Craft knowledge: What arguments work + how to structure sections
Synthesis: The specific argument for why this funder should fund this program
Grant reports:
Grant file: What was promised + grant agreement + prior conversations
Program data: Actual outcomes + variance from targets + explanations
Program learning: What worked + what didn't + what changed
Relationship knowledge: What this funder cares about + next relationship step
Funder prospect analyses:
Funder research: Mission + grantees + priorities + process
Organizational fit assessment: Where we align + where we stretch
Relationship intelligence: Connections + cultivation path
Strategic judgment: Worth pursuing + timeline + recommended approach
Organizational narratives:
Accurate program knowledge: Current and verified
Outcome data: With sources and dates
Multiple versions: Different lengths + different emphasis
Maintenance discipline: Updated when programs change or data updates
Key Takeaways
-
"What's the strongest argument for why this funder should fund this program?" The synthesis question before every proposal draft.
-
"What we'd do differently — honest program learning." The grant report field that builds long-term funder relationships.
-
Organizational narratives maintained in multiple lengths with dates. Reusable content that's accurate and accessible.
-
Prospect analysis before prospect cultivation. Strategic assessment guides whether to invest in a relationship.
-
Problem framing adapts by funder; facts stay constant. The reuse discipline that maintains accuracy while improving targeting.
Conclusion
Grant writer research-to-output across four output types: grant proposals ("what's the strongest argument for why this funder should fund this program?" as the synthesis question; pre-writing synthesis — what I know about this funder from knowledge base, what I know about the organization, the connection with honest fit assessment; proposal structure decisions based on synthesis — leading argument, problem framing, program description, evaluation with measurable targets, budget with specific justification; what makes each section compelling: needs statement connects statistics to this funder in this community; program description shows what we've learned that makes us effective; evaluation shows what we expect to find; budget demonstrates we know what delivery costs; sustainability shows durability because it works); grant reports ("what we'd do differently — honest program learning" as the relationship-building field; pre-report synthesis — what was promised, what was achieved, where we fell short with honest explanation; how to address shortfalls — acknowledge directly, explain honestly, describe changes; how to demonstrate value — participant stories, community impact, what wouldn't have happened without this grant; what makes reports excellent: honesty about shortfalls builds more trust than hiding; specificity over vague description; learning; narrative alongside data); funder prospect analyses (what I researched; fit assessment with rating and strongest/weakest alignment; relationship status with who should make connection; recommended strategy — apply this cycle or position for future; what concerns me — risk factors and whether worth the investment); and organizational narratives (reusable content in multiple lengths with dates; core content that stays stable — facts, positioning, outcome claims; framing that adapts — which outcomes to emphasize, program elements to highlight, problem language, geographic framing; "what makes a narrative block valuable" — accurate and verified, multiple versions in different lengths, dated, tagged by program and funder type). Research-to-output connection: each output draws on different knowledge combinations with craft synthesis connecting them.
To go deeper, check out Clip Articles for Later Reading.