35 ChatGPT Prompts for Grant Writers (Claude, ChatGPT & DeepSeek)

The RFP deadline is in 11 days. You're leading three simultaneous proposals: a federal continuation grant at $2.1M, a local community foundation letter of inquiry due the same week, and a corporate funder proposal your executive director promised last quarter. The federal proposal alone requires a project narrative, logic model, evaluation plan, budget with 42 line-item justifications, and a data management plan. The project team hasn't finalized the budget numbers. And your organization's audited financials from last year still haven't been filed.

Grant writing is fundamentally a translation profession. Your program staff understand the work. Your finance team knows the numbers. Your executive director knows the funders. Your job is to translate all of that into coherent, compelling, compliant prose that tells the funder exactly why this organization should receive this money to do this work at this moment.

The Association of Fundraising Professionals (AFP) 2024 Fundraising Effectiveness Report found that professional grant writers spend an average of 40% of their time on writing and editing tasks — not program development, not funder research, not relationship management. Writing. For organizations relying on grant funding for 30% or more of their revenue, the grant writing capacity constraint is a direct ceiling on mission impact.

These 35 prompts cover seven grant writing workflows: letters of inquiry, proposal narratives, budget justification, evaluation frameworks, progress and final reports, funder relationship communication, and internal coordination. They work with Claude, ChatGPT, and DeepSeek.

Critical note: Grant proposals, reports, and funder correspondence must reflect accurate organizational data, actual program design, and truthful representation of your work. AI-generated drafts are starting frameworks — they require verification against actual program data, organizational financials, and funder requirements. Misrepresentation in grant applications can result in award termination, repayment obligations, and legal liability.

---

Why Grant Writers Write More Than They Should Have To

Three structural pressures drive the grant writing burden.

First, proposal complexity has increased while organizational capacity has not. Federal grant applications routinely require 15 to 25 distinct narrative sections, multiple attachments, system registrations in SAM.gov and grants.gov, and compliance certifications. Foundation proposals vary widely in format requirements — some require 500-word narratives, others want 15-page detailed program plans. A grant writer managing a diverse portfolio navigates different format requirements for every proposal, rebuilding structure from scratch rather than adapting content.

Second, the reporting burden compounds with every award received. Each grant has its own reporting schedule, reporting format, and data requirements. An organization with 12 active grants may have 20 to 30 reporting events per year — quarterly reports, semi-annual reports, annual reports, and final reports — each requiring data collection, narrative writing, and financial reconciliation. The reporting burden grows with grant portfolio size, creating a capacity constraint that limits how many grants an organization can responsibly pursue.

Third, funder relationship maintenance requires consistent, personalized communication that most grant writers don't have time to execute well. Acknowledgment letters, interim updates, meeting preparation, stewardship communication after award decisions — these touchpoints build the relationship that creates renewal probability, but they fall to the bottom of the priority list when proposals are due.

These 35 prompts handle the writing structure. Your program knowledge, funder relationships, and strategic judgment remain essential.

---

Category 1: Letters of Inquiry (LOIs)

---

Prompt 1 — Foundation LOI

Write a letter of inquiry for a foundation grant.

Organization: [NAME + TYPE — e.g., "community health nonprofit serving urban communities"]
Funder: [FOUNDATION TYPE — e.g., "community foundation", "family foundation", "corporate foundation"]
Funder priorities: [THEIR STATED INTERESTS — from their website/guidelines]
Program name: [NAME OF PROGRAM OR PROJECT]
Problem statement: [1-2 SENTENCES — what problem this program addresses, with 1 data point]
Proposed solution: [BRIEF — what you do and how]
Target population: [WHO + NUMBERS SERVED]
Request amount: [$AMOUNT]
Grant period: [LENGTH]
Key outcome: [1 MEASURABLE OUTCOME — what change will occur as a result]
Organization credibility: [1 SENTENCE — why your org is positioned to do this work]

Foundation LOI. Most foundations want LOIs that are 1-2 pages. Lead with the problem statement using a compelling statistic or specific local data point — not with organization history. The funder reads hundreds of these; make the problem undeniable in the first paragraph. Be specific about what you will do, who will benefit, and what you're asking for. Under 400 words.

---

Prompt 2 — Government Grant LOI / Pre-Application

Write a government grant letter of intent or pre-application summary.

Grant program: [FEDERAL / STATE — program name and CFDA/announcement number if applicable]
Funder agency: [AGENCY NAME]
Required LOI elements from the RFP: [LIST — exactly what the funder requires. Do not add to this list]
Organization name and type: [NAME + 501(c)(3)/govt entity/etc.]
Project title: [PROPOSED TITLE]
Project period: [START + END DATE]
Total budget requested: [$AMOUNT]
Brief project description: [3-4 SENTENCES — what you will do, who it serves, key approach, primary outcome]
Key partners (if required): [LIST]
Geographic focus: [SPECIFIC]
Authorized organizational representative: [TITLE — not name]

Government LOI following RFP requirements exactly. Government LOIs are pass/fail on compliance — if the RFP requires 5 specific sections, include exactly those 5 sections in the required format and length. Do not add sections not requested. Do not exceed the page or word limit. Under 300 words (or per RFP limit).

---

Prompt 3 — Cold Outreach to Uncontacted Foundation

Write a cold outreach email to a foundation program officer.

Organization: [NAME + TYPE]
Foundation: [NAME]
Alignment: [WHY YOU'RE REACHING OUT TO THIS SPECIFIC FOUNDATION — cite their specific stated priorities, recent grants made in your area]
Program: [NAME + BRIEF DESCRIPTION — 2 sentences]
Population served: [WHO + NUMBERS]
Outcome achieved: [1 SPECIFIC RESULT — real data from your program]
Ask: [LOW-PRESSURE — "Would a brief conversation be appropriate to explore whether our work aligns with your current priorities?"]
Your contact information: [NAME + TITLE + PHONE + EMAIL]

Cold outreach email. Program officers receive dozens of unsolicited inquiries. The ones that get responses show genuine knowledge of the foundation's priorities (not just "we love your mission") and lead with a specific program result, not organizational history. Ask for a brief conversation, not a grant. Under 250 words.

---

Prompt 4 — Declining to Apply Response

Write a response to a funder declining to apply for a grant.

Situation: [FUNDER INVITED YOU TO APPLY / RFP RELEASED THAT YOU CONSIDERED]
Reason for declining: [HONEST — misalignment with current program priorities, capacity constraints, timing, geographic mismatch]
Gratitude: [GENUINE — for the relationship, for the invitation if applicable]
Future relationship: [BRIEF — keeping the door open for future alignment]
Specific future scenario if any: [e.g., "When we launch Phase 2 of [PROGRAM] in [YEAR], there may be stronger alignment"]

Declining invitation to apply. Funders who invite you and receive a thoughtful decline remember it. Funders who receive silence wonder why. A brief, honest decline that explains the reasoning and keeps the door open is a relationship investment. Under 200 words.

---

Category 2: Proposal Narratives

---

Prompt 5 — Problem Statement / Statement of Need

Write a problem statement for a grant proposal.

Program area: [TOPIC — e.g., "early childhood literacy", "housing stability for seniors", "substance use recovery"]
Geographic focus: [SPECIFIC — city, county, region]
Target population: [WHO — specific demographic or community]
Local data (use your actual data): [3-4 SPECIFIC LOCAL DATA POINTS — poverty rate, incidence rate, service gap, demographic data. Do not use national averages when local data is available]
National or state context (to support local data): [1-2 BENCHMARKS — how does your area compare]
Consequences of the problem: [SPECIFIC — what happens if this problem is not addressed]
Gap in existing services: [SPECIFIC — why what exists isn't enough for this population]
Connection to funder priorities: [HOW THIS PROBLEM CONNECTS TO THEIR STATED FOCUS AREAS]

Problem statement / statement of need. The strongest problem statements make the funder feel that NOT funding this proposal would be a mistake. Use local data first — national data is context, not the argument. Describe consequences in human terms. Make the gap specific: not "there aren't enough services" but "there are 847 individuals on the county housing waitlist with an average 18-month wait time." Under 400 words.

---

Prompt 6 — Program/Project Description Narrative

Write a program/project description narrative section.

Program name: [NAME]
Population served: [SPECIFIC — demographics, geography, qualifying criteria]
Number to be served: [SPECIFIC — with time period, e.g., "240 individuals annually"]
Theory of change: [BRIEF — if X inputs + Y activities, then Z outcomes because of A assumptions]
Program components: [LIST EACH — activity, who delivers it, how often, in what setting]
Evidence base: [WHAT RESEARCH OR MODELS INFORM THIS APPROACH — specific, not generic]
Staffing: [ROLES + QUALIFICATIONS — how many, doing what]
Partnerships: [SPECIFIC PARTNER ROLES — not just "we partner with great organizations"]
Timeline: [MAJOR MILESTONES BY QUARTER OR PHASE]
Cultural responsiveness: [SPECIFIC — how is this program designed to work for this specific population]

Program description. Funders read proposals to answer: "Will this actually work? Are these people capable of doing it?" Answer both questions with specifics. The evidence base should name the specific model or research, not just say "evidence-based approach." Under 600 words.

---

Prompt 7 — Organizational Capacity Section

Write an organizational capacity / organizational qualifications section.

Organization name: [NAME]
Organization type: [501(c)(3) + YEAR FOUNDED]
Mission: [MISSION STATEMENT — exact]
Annual budget: [$AMOUNT]
Staff size: [TOTAL FTE — breakdown if useful]
Years operating this program type: [SPECIFIC]
Track record with similar grants: [FEDERAL / FOUNDATION GRANTS — amounts, years, outcomes]
Key staff qualifications: [FOR PEOPLE LEADING THIS PROJECT — titles + credentials + relevant experience]
Financial management capacity: [AUDITS, FISCAL CONTROLS — briefly]
Relevant partnerships: [ESTABLISHED RELATIONSHIPS RELEVANT TO THIS GRANT]
Local presence/trust: [WHY YOUR ORGANIZATION IS POSITIONED TO SERVE THIS POPULATION IN THIS COMMUNITY]

Organizational capacity section. Don't write your organization's history here — write your credibility for this specific project. What prior work proves you can do this? What staff will lead it and why are they qualified? What financial infrastructure ensures responsible stewardship? Funders are assessing risk — demonstrate track record. Under 400 words.

---

Prompt 8 — Evaluation Plan Narrative

Write an evaluation plan narrative section.

Program goals: [LIST — 2-4 FROM THE PROJECT NARRATIVE]
Process measures (outputs): [WHAT YOU WILL COUNT — number served, sessions held, activities completed]
Outcome measures (outcomes): [WHAT CHANGE YOU WILL MEASURE — for each goal, what indicator, at what threshold]
Data collection methods: [FOR EACH MEASURE — surveys, assessments, database records, attendance logs, etc.]
Data collection timing: [WHEN — baseline, midpoint, exit, follow-up]
Data collection responsibility: [WHO — which staff role, what system]
Analysis plan: [HOW — describe planned analysis even if simple: pre/post comparison, percent meeting threshold]
External evaluator (if applicable): [YES/NO — if required by funder, describe]
Learning and adaptation: [HOW WILL DATA BE USED TO IMPROVE PROGRAM — not just to report to funder]

Evaluation plan. The weakest evaluation plans list outputs (number of people served) and call them outcomes. Outcomes require measurement of change: knowledge gained, behavior changed, status changed. For each outcome, name the specific tool used to measure it and the target (e.g., "80% of participants will demonstrate X, measured by Y at Z time point"). Under 500 words.

---

Prompt 9 — Sustainability Plan

Write a sustainability plan narrative section.

Current funding base: [BRIEF — diversified sources: federal, foundation, earned income, etc.]
This grant's role in the overall budget: [% OF TOTAL PROGRAM BUDGET]
Plans for funding after grant period: [SPECIFIC — not "we will pursue additional grants"]
Revenue generation potential: [IF ANY — fees for service, social enterprise, etc.]
Partnerships that contribute in-kind or reduced-cost resources: [SPECIFIC]
Track record of sustaining prior grant-funded programs: [SPECIFIC EXAMPLES IF AVAILABLE]
Policy or systems change that could make this work sustainable without recurring grants: [IF APPLICABLE]

Sustainability plan. This is one of the most commonly weak sections in grant proposals because most organizations don't have a specific sustainability plan — they have a plan to continue grant-writing. Funders know this. Address it honestly: name the specific funding sources you will pursue, the earned income strategies if applicable, and the advocacy or policy work that could make the model sustainable. Vagueness is worse than honesty. Under 350 words.

---

Category 3: Budget Justification

---

Prompt 10 — Personnel Budget Justification

Write a personnel budget justification for a grant proposal.

For each position funded by the grant:
  - Title: [POSITION TITLE]
  - FTE or % of time charged to grant: [AMOUNT + RATIONALE — why this % of time is necessary]
  - Annual salary: [$AMOUNT]
  - Grant year amount: [$AMOUNT]
  - Fringe benefits rate: [% — specify what's included: FICA, health, retirement, etc.]
  - Fringe benefit amount: [$AMOUNT]
  - Duties on this grant: [SPECIFIC — what this person will do to implement the project]

Personnel justification format for federal or foundation grant. Each position justification must connect the person's duties to the project activities. The fringe benefit rate should match the organization's actual rate or the rate documented in a negotiated indirect cost agreement. Under 300 words for a 3-person team.

---

Prompt 11 — Non-Personnel Budget Justification

Write a non-personnel budget justification.

For each line item:
  - Category: [EQUIPMENT / SUPPLIES / CONTRACTUAL / TRAVEL / OTHER — federal categories]
  - Item: [SPECIFIC DESCRIPTION]
  - Quantity: [NUMBER]
  - Unit cost: [$AMOUNT]
  - Total: [$AMOUNT]
  - Justification: [WHY THIS ITEM IS NECESSARY FOR THE PROJECT — specific connection to program activities]
  - How cost was determined: [VENDOR QUOTE / CATALOG PRICE / HISTORICAL COST — be specific]
  - If shared with other programs: [% CHARGED TO THIS GRANT AND BASIS FOR ALLOCATION]

Non-personnel budget justification. Federal grants require that every line item be allowable (permitted under the applicable cost principles), allocable (necessary for this project), and reasonable (comparable to market rates). Document how costs were determined — "estimated" is not sufficient for federal budgets. Under 400 words for a typical non-personnel section.

---

Prompt 12 — Indirect Cost Rate Justification

Write an indirect cost rate justification.

Situation: [NEGOTIATED RATE / DE MINIMIS RATE / NO INDIRECT CLAIMED — specify]
Rate: [% + BASE — e.g., "15% of modified total direct costs"]
Agreement: [COGNIZANT FEDERAL AGENCY + AGREEMENT DATE — if negotiated rate]
If using de minimis: [REFERENCE 2 CFR 200.414(f) — explain that organization has never had a negotiated rate]
What indirect costs cover: [BRIEF — general and administrative costs not directly charged]
Why this rate is reasonable: [BRIEF — if relevant]

Indirect cost rate justification. For federal grants, organizations with negotiated indirect cost rates must use them or may use a lower rate — they cannot use a different rate. Organizations that have never had a negotiated rate may use the 10% de minimis rate on MTDC under 2 CFR 200.414. Document whichever applies. Under 150 words.

---

Category 4: Progress and Final Reports

---

Prompt 13 — Quarterly Progress Report Narrative

Write a quarterly grant progress report narrative.

Grant: [FUNDER + PROGRAM NAME + GRANT PERIOD]
Reporting period: [DATES]
Progress against goals:
  For each goal/objective:
    - Goal: [RESTATE BRIEFLY]
    - Target for this period: [FROM GRANT APPLICATION — what was planned]
    - Actual: [WHAT ACTUALLY HAPPENED — specific numbers]
    - On track: [YES / BEHIND — if behind, explain why and corrective action]
Activities completed this period: [LIST — specific]
Activities planned next period: [LIST — specific]
Challenges: [HONEST — what's harder than expected and what you're doing about it]
Changes to program design: [IF ANY — always notify funder of significant changes]
Technical assistance needs: [IF ANY — what support would help]

Quarterly progress report. Funders read progress reports to assess risk. If you are behind on targets, document it clearly with an honest explanation and a specific corrective plan — funders can handle being behind; what they cannot handle is discovering a problem at the final report. Under 500 words.

---

Prompt 14 — Final Grant Report Narrative

Write a final grant report narrative.

Grant: [FUNDER + PROGRAM NAME + GRANT PERIOD]
Grant period: [START + END DATE]
Total award: [$AMOUNT]
Program overview: [BRIEF — what the grant funded]
Results achieved (for each outcome from the grant application):
  - Outcome target: [FROM APPLICATION]
  - Actual result: [WITH DATA]
  - Achievement: [MET / EXCEEDED / PARTIALLY MET — with explanation]
Unexpected outcomes: [POSITIVE OR NEGATIVE — what you learned that you didn't expect]
Success story: [ONE SPECIFIC INDIVIDUAL OR COMMUNITY OUTCOME — human interest, no identifiable info]
Lessons learned: [3 SPECIFIC — what you'd do differently, what worked better than expected]
Sustainability: [WHAT IS CONTINUING AFTER THE GRANT PERIOD — and how]
Thank you: [GENUINE — what this grant made possible]

Final grant report. The final report is both a compliance document and a relationship investment. Be honest about what you didn't fully achieve — funders who received an honest accounting of partial achievement are far more likely to fund you again than funders who received a rosy report that contradicts program data they can see. Under 600 words.

---

Prompt 15 — Grant Closeout Communication

Write a grant closeout letter to a funder.

Grant: [FUNDER + GRANT NUMBER IF APPLICABLE + AWARD AMOUNT]
Grant period: [DATES]
Final report submitted: [DATE + REFERENCE IF APPLICABLE]
Final financial report/drawdown: [STATUS — submitted, reconciled]
Any unused funds returned (if applicable): [AMOUNT + DATE]
Key accomplishments: [3 SPECIFIC — the impact this grant made possible]
Thank you: [SPECIFIC — what this partnership meant for your mission]
Future relationship: [BRIEF — hope for continued engagement, upcoming programs that may be of interest]

Grant closeout letter. The closeout is a relationship stewardship opportunity that most organizations miss. Send a brief, genuine letter when all compliance obligations are complete. Funders who received a thoughtful closeout are more likely to accept a future proposal — this is the start of the renewal conversation, not the end. Under 250 words.

---

Category 5: Funder Relationship Communication

---

Prompt 16 — Award Acknowledgment Letter

Write a grant award acknowledgment letter.

Funder: [NAME + CONTACT TITLE]
Grant: [PROGRAM NAME + AWARD AMOUNT]
What the grant will make possible: [SPECIFIC — in terms of program impact, not organizational benefit]
Key milestones in the upcoming grant period: [2-3 — when funder will hear from you, what they should expect]
Primary contact for this grant: [YOUR NAME + TITLE + DIRECT CONTACT — placeholder]
Invitation for site visit or engagement: [OFFER — if appropriate for relationship]

Award acknowledgment letter. Do more than say thank you — tell the funder what they funded and when they'll hear about results. Funders who receive a thoughtful acknowledgment with a clear engagement plan feel like partners, not ATMs. Under 250 words.

---

Prompt 17 — Declination Response

Write a response to a grant declination.

Funder: [NAME]
Grant program: [PROGRAM + AMOUNT REQUESTED]
Receipt: [ACKNOWLEDGED GRACIOUSLY]
Request for feedback: [BRIEF — if appropriate for this funder relationship]
Future interest: [SPECIFIC — if you plan to apply again, or if there's a program more aligned with their priorities]
Continued relationship: [BRIEF — staying connected without being presumptuous]

Grant declination response. Most organizations don't respond to declinations. The organizations that do — graciously, without pushback — are remembered. A brief, professional response that acknowledges the decision, invites feedback, and keeps the door open is a relationship investment that costs 15 minutes and pays dividends on the next cycle. Under 200 words.

---

Prompt 18 — Program Officer Site Visit Prep Summary

Write a site visit preparation summary for a program officer visit.

Funder: [NAME]
Visit date: [DATE]
Grant in question: [PROGRAM + AWARD]
What the program officer will see: [SCHEDULE — 30-minute overview of what's planned during the visit]
Key data points to share: [3-5 NUMBERS — most compelling outcomes to date]
Client/participant story: [ONE — brief, with consent, or composite — that illustrates the program impact]
Staff introductions: [ROLES TO BE PRESENT + WHAT EACH WILL COVER — brief]
Questions to anticipate: [3-5 LIKELY QUESTIONS + YOUR PREPARED ANSWERS]
What you want the funder to leave knowing: [1-2 KEY IMPRESSIONS]

Site visit prep summary. Site visits are won or lost in the first 10 minutes. Program officers decide quickly whether the organization runs as described in the proposal. Prepare specific data, a human story, and staff who can speak to their work without reading from a script. Under 400 words.

---

Start With These Three

• Prompt 5 — Problem statement / statement of need. The problem statement is where most grant proposals are won or lost before the program description begins. A compelling, locally-specific, data-grounded problem statement creates the urgency that makes the funder want to fund. Use this template to build a problem statement that makes NOT funding the proposal feel like a mistake.
• Prompt 8 — Evaluation plan narrative. Evaluation plans are the section grant writers dread most and funders scrutinize most carefully. Use this template to build an evaluation plan that connects each outcome to a specific measurement tool, method, timing, and target — moving from a list of outputs to a genuine outcomes measurement framework.
• Prompt 13 — Quarterly progress report. Progress reports protect the grant relationship. A specific, honest progress report that acknowledges challenges and documents corrective action builds funder trust over the grant period. Use this template to write every progress report in under 2 hours, with specific data for every target and a clear narrative of what's working and what isn't.

---

Get the Complete Grant Writer AI Toolkit

These 35 prompts cover core grant writing workflows. The complete Grant Writer AI Toolkit — available now on Gumroad — includes 80+ prompts covering federal grant applications (Section 5310, SAMHSA, HUD, DOJ), foundation proposal narrative sections, logic model development, data management plans, DUNS/SAM.gov compliance documentation, and grant database research frameworks.

👉 Get the Grant Writer AI Toolkit — Use LAUNCH30 for 30% off — limited uses remaining.

---

Works with Claude, ChatGPT, and DeepSeek. Copy-paste ready. No AI expertise required.