AI Prompts for Grant Writers

Draft a one-page letter of inquiry (LOI) to introduce our nonprofit and project to a prospective funder.

Organization: [name, mission in one line]
Track record: [year founded, one credibility marker]
Project name: [name]
Problem we address: [1-2 sentences]
Population served: [who, how many]
Amount requested: $[amount]
Total project cost: $[amount]
Funder: [foundation name]
Why this funder: [their stated priority or funding area this project matches]
Contact: [name, title]

Requirements:
- Length: one page, roughly 350-400 words
- Structure: (1) an opening that connects our mission to the funder's stated interest, (2) the problem and who it affects, (3) our proposed project and expected outcomes, (4) the requested amount and total project cost, (5) a close that invites a full proposal
- Tone: professional, warm, and confident, never desperate
- Use only the facts I provided; do not invent statistics, dates, or outcomes
- Where a specific figure or name is needed but not given, leave a [bracketed placeholder] so I can fill it in
- Cut filler; every sentence should earn its place

Write a statement of need (needs statement) for a grant proposal.

Organization: [name]
Project: [name]
Community/population affected: [who]
The problem: [describe the specific problem]
Verified data I have: [paste statistics with source, or write "none yet"]
Root causes: [what drives the problem]
Consequences of inaction: [what happens if it is not addressed]
Geographic scope: [city/region]

Requirements:
- Length: 300-450 words
- Open with the human impact, then support it with the data I provided
- Establish the gap between current conditions and the desired conditions
- Connect the need to our organization's ability to respond, but save the full solution for the project narrative
- Use only the statistics I supplied. If a claim needs a number I did not give, insert [add verified figure + source] rather than inventing one
- Cite sources inline as [Source, year] using the citations I provided
- Tone: urgent but factual, never exaggerated or manipulative

Write a project narrative section for a grant proposal.

Project name: [name]
Goal: [the change this project creates]
Target population: [who, how many]
Key activities: [list 3-6 main activities]
Timeline: [duration and major phases]
Staffing: [who delivers the work]
Partners: [collaborating organizations, if any]
Expected outcomes: [what will change]
How we measure success: [metrics/evaluation approach]

Requirements:
- Length: 600-900 words
- Use clear subheadings: Approach, Activities & Timeline, Staffing & Partners, Expected Outcomes, Evaluation
- Show a logical chain from activities to outcomes (why these activities produce this change)
- Be concrete about the activities, their cadence, and who is responsible; avoid vague aspirations
- Do not fabricate outcome numbers or completion dates; use [bracketed placeholders] where I still need to add specifics
- Tone: confident and evidence-based, written for a program officer who reads dozens of these
- Avoid buzzwords like leverage, synergy, or empower unless they name a defined program

Turn our project goals into SMART objectives for a grant proposal.

Project: [name]
Overall goal(s): [1-3 broad goals]
Target population: [who]
Baseline data: [current numbers, or "to be established"]
Project duration: [e.g., 12 months]
Realistic capacity: [staff, reach, scale we can actually deliver]

For each goal, write 2-3 objectives that are Specific, Measurable, Achievable, Relevant, and Time-bound.

Requirements:
- Format as: the Goal, then its SMART objectives indented beneath it
- Each objective must name the metric, the target number, the population, and the deadline
- Keep targets realistic for the capacity I described; flag any target that looks over-ambitious with a short note
- Where I did not provide a baseline or target, insert [add baseline] or [add target] instead of inventing a number
- After each objective, add a one-line note on the data source we would use to measure it
- Use plain, measurable language; no vague verbs like "improve" without a number attached

Build a logic model for a grant proposal from the details below.

Project: [name]
Problem/need: [1-2 sentences]
Resources/inputs we have: [staff, funding, partners, facilities]
Main activities: [list]
Who we reach: [population, numbers]
Short-term changes expected (0-12 months): [knowledge, skills, attitudes]
Longer-term changes expected (1-3 years): [behavior, conditions]

Produce the logic model in two formats:
1. A table with columns: Inputs | Activities | Outputs | Short-Term Outcomes | Long-Term Outcomes | Impact
2. A 3-4 sentence "if...then" narrative summary of the theory of change

Requirements:
- Outputs must be countable (e.g., "# of workshops delivered," "# of participants served")
- Outcomes must describe change, not activity
- Keep each cell to a concise phrase, not a paragraph
- Use only what I provided; mark any gap as [add detail]
- Do not invent participant numbers or outcome targets

Write a budget justification (budget narrative) for a grant proposal.

Project: [name]
Grant amount requested: $[amount]
Project period: [duration]
Budget line items (paste amounts I have already calculated):
- Personnel: [roles, % FTE, $]
- Fringe benefits: [$ or %]
- Travel: [$]
- Equipment/supplies: [$]
- Contractual/consultants: [$]
- Other direct costs: [$]
- Indirect/overhead: [rate, $]
Other funding sources: [matching funds, in-kind, if any]

Requirements:
- Write a short justification for each line item explaining what it covers and why it is necessary to the project
- Tie each cost back to a specific project activity or objective
- Use only the dollar figures I provided; do not calculate, alter, or invent amounts. Where a number is missing, insert [add amount]
- Note any cost-share or in-kind contribution where I listed it
- Tone: precise and reasonable, so a reviewer sees every dollar as justified
- End with one sentence on why the budget is cost-effective relative to the outcomes
- Do not attempt the math or reconcile totals; if figures look inconsistent, flag with [verify total]

Write an executive summary for a grant proposal, based on the finished proposal details below.

Organization: [name, one-line mission]
Amount requested: $[amount]
Project name: [name]
Problem: [1 sentence]
Solution/approach: [1-2 sentences]
Target population: [who, how many]
Key outcomes: [top 2-3 measurable results]
Project duration: [timeframe]
Why us: [one credibility marker]

Requirements:
- Length: 200-300 words, one or two paragraphs
- Cover, in order: who we are, the need, the project, the outcomes, the amount requested, and the fit with this funder
- Lead with the most compelling point, not boilerplate about our founding
- Use only the facts and numbers I provided; insert [placeholder] for anything missing
- It must stand alone: a reviewer who reads only this should understand the entire ask
- Tone: crisp and confident, with no filler openings like "In today's world"

Create a funder research brief to help me decide whether to apply to this foundation. Organize and analyze the information I paste; do not invent any facts about the funder.

Our organization: [name, mission, focus area, geography, budget size]
Our project seeking funding: [name, amount needed]
Funder information I am pasting: [paste their mission, funding priorities, past grantees, typical grant size, deadlines, eligibility, from their site or 990]

Produce a brief with these sections:
1. Fit assessment: how well our mission and project align with their stated priorities (High / Medium / Low, with reasoning)
2. Funding pattern: typical grant size, geography, and grantee profile based on what I pasted
3. Alignment hooks: 3-4 specific talking points connecting our work to their language and priorities
4. Red flags / eligibility gaps: anything that may disqualify us or weaken the fit
5. Recommended next step: send an LOI, submit a full application, cultivate a relationship first, or skip
6. Open questions to research before applying

Requirements:
- Base every statement on the information I pasted; if something is unknown, list it under Open Questions rather than guessing
- Do not fabricate grant amounts, deadlines, or program officer names
- Keep it scannable with bullet points

Write an impact statement describing the outcomes our project will achieve (or has achieved), for a grant proposal or report.

Project: [name]
Population served: [who, how many]
Results/outcomes: [paste real data: numbers served, outcomes measured, % change, or write "projected"]
Timeframe: [period the results cover]
How outcomes were measured: [survey, pre/post, administrative data]
Representative example: [one anonymized story or case, if available]

Requirements:
- Length: 200-350 words
- Lead with the single most significant measurable outcome
- Pair the numbers with one human example to make the impact concrete
- Clearly label projected results as "projected" and achieved results as "achieved"; never present a projection as a completed result
- Use only the figures I provided; insert [add verified figure] where a number is missing
- Do not exaggerate, round up favorably, or imply causation the data does not support
- Tone: credible and specific, since funders trust measured claims over superlatives

Write a thank-you letter to a funder who awarded us a grant.

Funder: [foundation name]
Contact/program officer: [name, title]
Grant amount: $[amount]
Project funded: [name]
What the funding enables: [1-2 concrete things]
Our organization: [name]
Signatory: [name, title]
Reporting commitment: [next report date, if known]

Requirements:
- Length: 200-250 words
- Express specific, genuine gratitude by naming what their support makes possible, not generic thanks
- Reinforce the shared mission and the difference the grant will make
- Briefly note our commitment to stewardship and reporting
- Tone: warm, sincere, and professional, not effusive or over the top
- Use only the details I provided; insert [placeholder] for anything missing
- Close with an invitation to stay connected, such as a site visit or updates

Write a grant report narrative for a funder on our funded project.

Report type: [interim / final]
Funder: [name]
Grant: [project name, amount, period covered]
Objectives we set: [paste the original objectives]
Actual results against each objective: [paste real data for each]
What worked: [successes]
Challenges: [obstacles and how we responded]
Budget status: [on track / variance, with explanation if I provide one]
Next steps: [what comes next, or sustainability plan]

Requirements:
- Structure: Summary, Progress Against Objectives (address each one), Successes, Challenges & Adaptations, Financial Update, Looking Ahead
- Report honestly against each stated objective, including any we fell short on, with context
- Use only the results and figures I provided; never inflate numbers or hide shortfalls. Insert [add actual figure] where data is missing
- Tone: transparent, professional, and accountable, since funders value honesty over spin
- Length: 500-800 words
- Do not fabricate outcomes, spending figures, or explanations for variances

Read the grant RFP/guidelines I paste below and produce a compliance checklist so our proposal meets every requirement.

RFP / funder guidelines: [paste the full solicitation, eligibility, and submission instructions]
Our organization: [name, type, location] (to check eligibility)

Produce:
1. Eligibility check: list each eligibility criterion and whether we appear to meet it, or [need to confirm]
2. Required documents: every attachment and form the RFP asks for, as a checkbox list
3. Narrative requirements: each required section, its page or word limit, and any formatting rules (font, margins, spacing)
4. Budget requirements: allowable and unallowable costs, match/cost-share, indirect rate cap
5. Key dates: LOI deadline, full proposal deadline, submission method or portal
6. Scoring criteria: how reviewers score, with point weights if given, so we prioritize accordingly
7. Easy-to-miss requirements: anything buried that applicants commonly overlook

Requirements:
- Pull only from the text I pasted; if the RFP is silent on something, mark it [not specified - confirm with funder] rather than assuming
- Format as scannable checklists
- Do not invent deadlines, page limits, or eligibility rules