Prompt Library

ChatGPT Prompts for Grant Writing

30 copy-paste prompts

30 tested prompts to draft letters of inquiry, needs statements, project narratives, measurable objectives, budgets, and funder-tailored proposals that win funding.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly — no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup · Founder, Techpresso

Last updated May 15, 2026·Hand-curated & tested by the AI Academy team

Letters of Inquiry & Concept Notes

5 prompts

Draft a Letter of Inquiry

1/30

<context> Organization: [ORGANIZATION] Mission: [ONE-SENTENCE MISSION] Funder: [FUNDER] Project: [PROJECT] Amount requested: [$AMOUNT] Funder priorities (from their site/guidelines): [PASTE FUNDER PRIORITIES] </context> <task> Write a one-page letter of inquiry (LOI) under 450 words. Structure it as: 1. Opening hook tying [ORGANIZATION]'s work to [FUNDER]'s stated priorities. 2. The problem [PROJECT] addresses, with one striking data point. 3. Our proposed solution and why we are credible to deliver it. 4. The specific amount requested and what it funds. 5. A closing that invites a full proposal. Use a confident, concise tone. Avoid jargon. Flag any place I should insert a local statistic in [BRACKETS]. </task>

Produces a tight, funder-aligned one-page letter of inquiry ready to personalize.

💡

Pro tip: Paste the funder's actual guidelines into the context block so the mirror language is exact, not generic.

Write a Concept Note

2/30

<context> Organization: [ORGANIZATION] Project: [PROJECT] Target population: [WHO YOU SERVE] Requested amount: [$AMOUNT] Project duration: [MONTHS/YEARS] </context> <task> Draft a 2-page concept note with these sections: Background, Problem Statement, Goal & Objectives, Approach/Activities, Expected Outcomes, and Budget Summary. Keep each section to 2-4 sentences. Make objectives measurable. End with a single sentence on organizational capacity. Output with clear section headers. </task>

Generates a structured concept note covering all standard funder-requested sections.

💡

Pro tip: Reuse the concept note as the skeleton for a full proposal once a funder expresses interest.

Tailor an LOI to Multiple Funders

3/30

<context> Master LOI: [PASTE YOUR BASE LOI] Funder A priorities: [PASTE] Funder B priorities: [PASTE] Funder C priorities: [PASTE] </context> <task> Produce three versions of the LOI, one per funder. For each, keep the core project facts identical but: 1. Rewrite the opening to echo that funder's specific language and focus areas. 2. Reorder the proof points so the most relevant one to that funder leads. 3. Adjust the closing ask to match their typical grant range if I provided it. Label each version clearly and note in one line what you changed and why. </task>

Spins one base letter into three funder-specific versions without losing factual consistency.

💡

Pro tip: Ask ChatGPT to keep a shared "facts" block so numbers never drift between versions.

Craft an Opening Hook

4/30

<context> Project: [PROJECT] Problem: [THE PROBLEM] Funder: [FUNDER] Most compelling statistic or story I have: [PASTE] </context> <task> Write five distinct opening paragraphs (3-4 sentences each) for a grant inquiry. Use a different technique for each: (1) a startling statistic, (2) a single beneficiary story, (3) a provocative question, (4) a shared-values statement aligned to [FUNDER], (5) a moment-in-time urgency frame. After each, add a one-line note on when this opening works best. </task>

Gives five ready-to-test opening hooks using different persuasion techniques.

💡

Pro tip: Test the statistic hook on data-driven foundations and the story hook on community funders.

Summarize Funder Guidelines Into a Checklist

5/30

<context> Funder: [FUNDER] Guidelines text: [PASTE FULL RFP / GUIDELINES] </context> <task> Read the guidelines and produce: 1. A submission checklist (every required document, attachment, and form). 2. Hard eligibility criteria as yes/no questions I can self-assess against. 3. All stated word/page/budget limits. 4. The exact evaluation criteria and their weights if listed. 5. The deadline and submission method. Flag anything ambiguous that I should confirm with the program officer. </task>

Turns dense funder guidelines into an actionable compliance checklist.

💡

Pro tip: Run this first on any new RFP so you never get disqualified on a technicality.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Needs & Problem Statements

5 prompts

Write a Needs Statement

6/30

<context> Organization: [ORGANIZATION] Community served: [GEOGRAPHY / POPULATION] Problem: [THE PROBLEM] Data I have: [PASTE STATISTICS, SOURCES] Project: [PROJECT] </context> <task> Draft a needs statement of 300-400 words that: 1. Defines the problem with cited data, scaling from national to the local population we serve. 2. Explains the consequences of the problem going unaddressed. 3. Identifies the gap in current services (without disparaging other organizations). 4. Positions [PROJECT] as the logical response. Keep it evidence-led, not emotional. Mark every place that needs a citation with [SOURCE]. </task>

Produces an evidence-driven needs statement that funnels from broad context to local need.

💡

Pro tip: Always replace every [SOURCE] tag with a real, dated citation before submitting.

Strengthen a Weak Problem Statement

7/30

<context> Current problem statement: [PASTE] What reviewers said (if any): [PASTE FEEDBACK] </context> <task> Critique my problem statement against these criteria: specificity, data support, local relevance, logical flow, and absence of solution-bias. For each criterion, give a score out of 5 and one concrete fix. Then rewrite the statement applying every fix. Keep my real facts; do not invent statistics, but mark where stronger data would help with [ADD DATA]. </task>

Audits and rewrites a problem statement against the criteria reviewers actually score on.

💡

Pro tip: Never let ChatGPT fabricate figures, so the [ADD DATA] flag forces you to source real numbers.

Translate Data Into a Compelling Narrative

8/30

<context> Raw data: [PASTE STATISTICS / SURVEY RESULTS] Audience: [FUNDER / REVIEW PANEL] </context> <task> Turn this raw data into 2-3 narrative paragraphs that make the scale of the problem felt, not just stated. For each key number: 1. Translate it into a human-scale comparison. 2. Connect it to a real consequence for [ORGANIZATION]'s population. 3. Keep every figure exactly as I provided it; do not round or alter. End with one sentence that frames why action is urgent now. </task>

Converts dry statistics into a vivid but accurate problem narrative.

💡

Pro tip: Ask for "human-scale comparisons" so a big number lands emotionally without exaggeration.

Build a Root-Cause Analysis

9/30

<context> Problem: [THE PROBLEM] Population: [WHO] What I know about causes: [PASTE NOTES] </context> <task> Develop a root-cause analysis I can use in the needs section. Provide: 1. The presenting problem (what people see). 2. 3-5 underlying root causes, each with a one-line rationale. 3. Which root cause(s) [PROJECT] directly targets. 4. A short paragraph explaining why addressing the root cause beats treating the symptom. Note any cause that I should validate with local data before claiming it. </task>

Maps presenting problems to root causes so the proposal targets causes, not symptoms.

💡

Pro tip: Funders favor projects that hit root causes, so explicitly name which one your project targets.

Localize a National Problem

10/30

<context> National/global problem: [PROBLEM] National statistics: [PASTE] Our service area: [GEOGRAPHY / POPULATION] Local data I have: [PASTE OR "none yet"] </context> <task> Write a passage that bridges the national problem to our specific community. Structure it as: national framing, then the funnel to local relevance. Where I lack local data, suggest exactly which local sources to pull from (e.g., census tract data, school district reports, county health rankings) and what metric to look for. Do not invent local numbers. </task>

Connects a national problem to your local service area and points to real local data sources.

💡

Pro tip: County health rankings and census tract data are credible, free sources reviewers trust.

Project Narrative & Methodology

5 prompts

Draft the Project Narrative

11/30

<context> Project: [PROJECT] Goal: [PROJECT GOAL] Key activities: [PASTE LIST] Timeline: [DURATION] Staffing: [WHO DELIVERS IT] </context> <task> Write a project narrative of 600-800 words covering: project overview, who it serves, the core activities in logical sequence, the implementation timeline, the team responsible, and how activities lead to outcomes. Use confident present/future tense ("we will"), tie each activity to an objective, and keep paragraphs short. Add subheadings. </task>

Generates a complete, well-structured project narrative tied to your objectives.

💡

Pro tip: Match the narrative's word count to the funder's stated page limit before you start editing.

Describe Your Methodology

12/30

<context> Project: [PROJECT] Approach/model: [EVIDENCE-BASED MODEL OR APPROACH] Why this approach: [RATIONALE] </context> <task> Write a methodology section that explains HOW we will deliver [PROJECT]. Include: 1. The model or framework we use and the evidence behind it. 2. The step-by-step delivery process. 3. Why this approach fits our population better than alternatives. 4. How we will adapt if early results lag. Cite the evidence base generically and mark exact citations needed with [SOURCE]. </task>

Explains your delivery methodology and grounds it in an evidence base.

💡

Pro tip: Reviewers reward evidence-based models, so name the specific framework rather than "best practices."

Build an Implementation Timeline

13/30

<context> Project: [PROJECT] Duration: [TOTAL MONTHS] Key activities: [PASTE LIST] </context> <task> Create an implementation timeline as a table with columns: Phase, Months, Key Activities, Responsible Party, Milestone/Deliverable. Break the project into 3-4 logical phases. Make sure every activity I listed appears, and add a launch and a close-out phase. Keep milestones concrete and verifiable. </task>

Outputs a phased implementation timeline table with milestones and owners.

💡

Pro tip: Concrete milestones double as your progress-report checkpoints later, so make them measurable.

Write a Logic Model

14/30

<context> Project: [PROJECT] Resources available: [STAFF, FUNDING, PARTNERS] Activities: [PASTE] Intended change: [WHAT SHOULD IMPROVE] </context> <task> Produce a logic model as a table with these columns: Inputs, Activities, Outputs, Short-Term Outcomes, Long-Term Outcomes/Impact. Keep outputs countable (numbers served, sessions delivered) and outcomes about change (knowledge, behavior, condition). Below the table, add a 3-sentence "theory of change" narrative connecting them. </task>

Builds a complete logic model with a short theory-of-change narrative.

💡

Pro tip: Keep outputs (counts) and outcomes (change) strictly separate, which is where many drafts blur.

Demonstrate Organizational Capacity

15/30

<context> Organization: [ORGANIZATION] Years operating: [N] Relevant past results: [PASTE METRICS / OUTCOMES] Key staff and qualifications: [PASTE] Partnerships: [PASTE] </context> <task> Write a capacity statement (250-350 words) proving [ORGANIZATION] can deliver [PROJECT]. Cover: track record with quantified past results, relevant staff expertise, infrastructure/systems, and strategic partnerships. Lead with the strongest proof. Be specific and confident without overclaiming. Mark any metric I should verify with [CONFIRM]. </task>

Drafts a capacity statement that proves your organization can deliver the project.

💡

Pro tip: Lead with a quantified past result; "served 1,200 youth, 87% completed" beats adjectives.

Goals, Objectives & Evaluation

5 prompts

Write SMART Objectives

16/30

<context> Project goal: [GOAL] Project: [PROJECT] Population: [WHO] Timeframe: [DURATION] </context> <task> Write 3-5 SMART objectives for [PROJECT]. Each objective must be Specific, Measurable, Achievable, Relevant, and Time-bound, and follow the format: "By [date], [target number/%] of [population] will [measurable change], as measured by [data source]." After each objective, add a one-line note confirming which SMART criterion is strongest and which I should double-check for realism. </task>

Produces measurable SMART objectives in a reviewer-friendly, data-source-anchored format.

💡

Pro tip: If you cannot name the measurement source after "as measured by," the objective is not yet measurable.

Separate Goals From Objectives

17/30

<context> My current goals/objectives draft: [PASTE] </context> <task> Review my draft and: 1. Identify which statements are true goals (broad, aspirational, the big change) versus objectives (specific, measurable steps). 2. Rewrite into a clean hierarchy: one or two goals, each with 2-3 supporting measurable objectives. 3. Flag any objective that is actually an activity in disguise and rewrite it as an outcome. </task>

Untangles goals, objectives, and activities into a clean, correctly-leveled hierarchy.

💡

Pro tip: Activities ("hold 12 workshops") are not objectives; the objective is the change those workshops produce.

Design an Evaluation Plan

18/30

<context> Project: [PROJECT] Objectives: [PASTE YOUR OBJECTIVES] Data capacity: [WHAT YOU CAN REALISTICALLY COLLECT] </context> <task> Design an evaluation plan as a table mapping each objective to: Indicator, Data Source, Collection Method, Frequency, and Responsible Party. Distinguish process measures (was it delivered) from outcome measures (did it work). Recommend one simple, low-cost method per indicator given my stated data capacity. Add a 2-sentence note on how findings feed back into the program. </task>

Creates an objective-to-indicator evaluation matrix scaled to your real data capacity.

💡

Pro tip: Pick collection methods you can actually sustain; an over-promised eval plan undercuts credibility.

Define Outcomes and Indicators

19/30

<context> Project: [PROJECT] Intended change: [WHAT IMPROVES] Population: [WHO] </context> <task> For [PROJECT], propose: 1. 2-3 outcome statements (the change we expect in the population). 2. For each outcome, 1-2 quantitative and 1 qualitative indicator. 3. A realistic baseline-and-target approach for each indicator. Keep indicators measurable and tied to the outcome, not the activity. Note which indicators a funder is most likely to want reported. </task>

Defines outcomes with paired quantitative and qualitative indicators and target logic.

💡

Pro tip: Pair every quantitative indicator with one qualitative one; stories make the numbers persuasive.

Plan for Sustainability

20/30

<context> Organization: [ORGANIZATION] Project: [PROJECT] Grant period: [DURATION] Current/potential revenue sources: [PASTE] </context> <task> Write a sustainability section (200-300 words) explaining how [PROJECT] continues after the grant ends. Address: diversified funding strategy, earned revenue or partnerships if relevant, capacity built that outlasts the grant, and any plan to institutionalize the work. Be realistic; do not promise permanent funding you cannot show a path to. Flag claims I must back up with [EVIDENCE]. </task>

Drafts a credible sustainability plan showing the project survives past the grant.

💡

Pro tip: Funders fear being a one-time crutch, so emphasize diversification and capacity that outlasts the grant.

Budgets & Budget Justifications

5 prompts

Build a Line-Item Budget

21/30

<context> Project: [PROJECT] Total request: [$AMOUNT] Duration: [MONTHS/YEARS] Known costs: [PASTE STAFF, MATERIALS, TRAVEL, ETC.] Funder restrictions: [PASTE ANY, e.g. no indirect over 10%] </context> <task> Build a line-item budget as a table with columns: Category, Line Item, Calculation, Amount, Funding Source (this grant vs. other). Group into Personnel, Fringe, Supplies, Travel, Other Direct Costs, and Indirect. Show the math in the Calculation column. Total it and confirm it equals [$AMOUNT]. Respect every funder restriction I listed and flag anything that exceeds a stated cap. </task>

Generates a fully calculated line-item budget that respects funder cost restrictions.

💡

Pro tip: Show the math in a calculation column; reviewers distrust round numbers with no formula behind them.

Write a Budget Justification

22/30

<context> Budget: [PASTE LINE-ITEM BUDGET] Project: [PROJECT] </context> <task> Write a budget narrative/justification that explains WHY each line item is necessary for [PROJECT]. For every category: 1. State what it funds and how it connects to a specific project activity or objective. 2. Show the calculation basis (rate x quantity x time). 3. Justify any item a reviewer might question. Keep each justification to 2-3 sentences. Use the same category order as the budget. </task>

Turns a line-item budget into a clear justification tying every cost to project activities.

💡

Pro tip: Tie each cost to an objective; an unexplained line item is the fastest way to lose budget points.

Calculate Personnel Costs and Fringe

23/30

<context> Roles on the grant: [TITLE, ANNUAL SALARY, % EFFORT for each] Fringe rate: [%] Grant duration: [MONTHS] </context> <task> For each role, calculate the charged salary (annual salary x % effort x portion of year on grant) and the fringe (charged salary x fringe rate). Present as a table: Role, Salary, % Effort, Months, Charged Salary, Fringe, Total. Sum personnel and fringe separately and combined. Show every calculation. Flag any role where % effort across all grants might exceed 100%. </task>

Computes accurate personnel and fringe figures with full, auditable calculations.

💡

Pro tip: Double-check that no staffer's combined effort across grants exceeds 100% before submitting.

Explain Indirect Costs

24/30

<context> Funder indirect policy: [PASTE, e.g. "10% de minimis" or "negotiated rate"] Our negotiated/de minimis rate: [%] Direct cost base: [$AMOUNT or "to be calculated"] </context> <task> Explain in 2-3 plain-language sentences what indirect costs cover for our organization. Then calculate the allowable indirect amount given the funder policy and our rate, showing the formula and the base it applies to. If the funder caps or disallows indirect, state how we will cover those real costs instead. Do not exceed the stated cap. </task>

Clarifies and correctly calculates indirect costs against the funder's allowed rate.

💡

Pro tip: If a funder disallows indirect, name your match or in-kind plan so the real cost is visibly covered.

Demonstrate Cost-Effectiveness

25/30

<context> Project: [PROJECT] Total cost: [$AMOUNT] People served: [NUMBER] Expected outcomes: [PASTE] Comparison/alternative cost if known: [PASTE OR "none"] </context> <task> Write a short cost-effectiveness argument. Calculate cost-per-participant and, where possible, cost-per-outcome. Frame these figures favorably and honestly. If I provided a comparison, contrast our cost against the alternative or the cost of inaction. Keep it to one tight paragraph plus the key figures. Do not invent comparison data. </task>

Builds a cost-per-participant and cost-per-outcome argument for value of investment.

💡

Pro tip: Cost-of-inaction comparisons (e.g., cost of a dropout vs. the program) are powerful when you have the data.

Go from copy-pasting to actually mastering AI.

AI Academy: 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ other tools. New tutorials added every week.

Start Your Free Trial

Funder Research & Tailoring

5 prompts

Profile a Prospective Funder

26/30

<context> Funder: [FUNDER] Info I have (990s, website, past grants): [PASTE OR SUMMARIZE] Our project: [PROJECT] </context> <task> From the information I provide, build a funder profile covering: stated priorities and focus areas, typical grant size and range, geographic scope, application process and deadlines, and recent grantees or patterns. Then assess fit with [PROJECT] on a 1-5 scale with reasoning, and list 3 questions I should answer before applying. Only use facts from what I pasted; mark gaps as [RESEARCH NEEDED]. </task>

Synthesizes funder research into a profile with a fit score and open questions.

💡

Pro tip: Feed it the funder's 990 and past-grants list; ChatGPT cannot browse, so it only knows what you paste.

Assess Funder Fit Before Applying

27/30

<context> Funder priorities: [PASTE] Funder typical grant size: [RANGE] Funder geography: [SCOPE] Our project: [PROJECT], requesting [$AMOUNT] in [GEOGRAPHY] </context> <task> Score the fit between [FUNDER] and our project across four dimensions: thematic alignment, grant-size match, geographic eligibility, and stage/type fit. Give each a 1-5 score with one sentence of reasoning. Give an overall go / no-go / clarify recommendation. If "clarify," list exactly what to confirm with the program officer first. </task>

Delivers a structured go/no-go fit assessment to protect your time on long-shot funders.

💡

Pro tip: A grant-size mismatch is a common silent rejection, so weight that dimension heavily.

Draft Outreach to a Program Officer

28/30

<context> Funder: [FUNDER] Program officer name: [NAME or "unknown"] Our project: [PROJECT] What I want to ask: [QUESTION / FIT CHECK] </context> <task> Write a brief, professional email (under 150 words) to a program officer that: introduces [ORGANIZATION] in one line, states the specific reason for reaching out, asks 1-2 focused questions, and respects their time. Tone: warm, concise, no fundraising pitch. Provide a clear subject line. Offer a short alternative version that requests a 15-minute call instead. </task>

Produces a concise, respectful program-officer outreach email plus a call-request variant.

💡

Pro tip: Ask a genuine eligibility or priority question, not for money; the relationship comes before the ask.

Mirror Funder Language

29/30

<context> Funder's own language (mission, priorities, RFP): [PASTE] My draft section: [PASTE A NARRATIVE OR LOI SECTION] </context> <task> Identify the 8-12 key terms, framings, and value-words [FUNDER] uses repeatedly. Then revise my draft to naturally adopt that vocabulary where it honestly fits, without changing any facts or overclaiming. Output: (1) the term list, (2) the revised draft, (3) a short note on any term I should NOT adopt because it would misrepresent our work. </task>

Aligns your draft with the funder's own vocabulary without distorting your facts.

💡

Pro tip: Mirroring builds resonance, but never adopt a term that overstates what you actually do.

Repurpose One Proposal for a New Funder

30/30

<context> Master proposal: [PASTE OR SUMMARIZE KEY SECTIONS] New funder: [FUNDER] with priorities: [PASTE] New funder requirements: [WORD LIMITS, REQUIRED SECTIONS, ELIGIBILITY] </context> <task> Adapt my existing proposal for [FUNDER]. Specifically: 1. Map my existing sections to this funder's required structure and flag missing sections. 2. Re-angle the framing toward this funder's priorities. 3. Trim or expand to hit their word/page limits. 4. List anything in my master proposal that should be removed because it does not fit this funder. Keep all factual data identical across versions. </task>

Reshapes an existing proposal to a new funder's structure, priorities, and limits.

💡

Pro tip: Build a reusable master proposal once; tailoring it per funder is faster and more consistent than starting fresh.

Frequently Asked Questions

ChatGPT can draft strong, well-structured sections fast, but funded proposals still depend on a real, fundable project and accurate local data. Use these prompts to produce a solid first draft, then add your verified statistics, organizational specifics, and a human edit. Reviewers fund credible organizations, not polished prose alone.

No. ChatGPT can hallucinate or misremember figures and citations, which is fatal in a grant. Every prompt here uses [SOURCE] and [ADD DATA] markers precisely so you replace placeholders with real, dated, verifiable sources. Always fact-check every number against the original source before submitting.

Keep a single "facts block" (names, numbers, dates, budget totals) and tell ChatGPT to treat it as fixed while only re-angling framing and language per funder. The tailoring prompts in this set are built to vary positioning without touching your underlying data. Spot-check that budget totals and beneficiary counts match across every version.

Most funders care about the quality, accuracy, and fundability of your proposal, not the tool used to draft it. Some federal or research funders have begun adding AI-use disclosures, so check each funder's guidelines. Either way, treat AI as a drafting assistant and ensure the final submission reflects your real work and voice.

ChatGPT excels at structure-heavy sections like logic models, timelines, budget justifications, and first drafts of narratives. Write or heavily edit the organizational story, community relationships, and any claim about results yourself, since those require lived knowledge. The strongest workflow is AI for scaffolding, you for substance and verification.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Marketers

7-day free trial. Cancel anytime.

Browse All Prompt Collections