Claude Prompts for Grant Writing

You are a veteran grant writer for a nonprofit. Write a compelling statement of need that makes a funder feel the problem is urgent and solvable. <context>Organization: [org]. Community served: [population + geography]. The problem: [problem]. Supporting data: [stats/sources I'll paste]. Gap in current services: [gap]. Why now: [urgency].</context> <task>Write a statement of need that establishes the problem with evidence, shows the human stakes, and positions our program as the answer.</task> <constraints>Ground every claim in the data I provide, do not invent statistics. Balance hard numbers with the lived human impact. Avoid blaming the community, frame them as capable people facing systemic barriers. Keep it tight, funders skim. Under 500 words. End by connecting the need directly to what we're proposing.</constraints> <format>Three to four short paragraphs: the scope of the problem (with cited data), who is affected and how, the gap current services leave, and a bridge sentence to our solution. Flag any [citation needed] gaps for me to fill.</format>

You are a grant writer building funder confidence. Write an organizational background section that proves we can deliver. <context>Organization: [name, founded, mission]. Track record: [past programs + outcomes]. Relevant experience: [why us for this project]. Team/partners: [key capacity]. Recognition: [awards, accreditations].</context> <task>Write a capacity statement that convinces a funder our organization is a low-risk, high-competence choice for this grant.</task> <constraints>Show, don't boast, back every capability claim with a specific past result or credential. Emphasize experience directly relevant to this project, not everything we've ever done. Reassure the funder we can manage the funds responsibly. Under 400 words. Professional and confident.</constraints> <format>Structure: a mission line, a proof-of-track-record paragraph (with concrete outcomes), a relevant-experience paragraph tied to this project, and a capacity/team paragraph. Keep it scannable with strong topic sentences.</format>

You are a program strategist and grant writer. Turn a surface problem into a root-cause narrative funders respect. <context>Surface problem: [symptom]. Who's affected: [population]. What I know about causes: [notes]. Systemic factors: [barriers]. Data available: [sources].</context> <task>Write a problem-framing section that traces the symptom to its underlying root causes, showing we understand the issue deeply enough to solve it.</task> <constraints>Distinguish symptoms from causes explicitly. Avoid oversimplifying or savior framing. Use a cause-and-effect logic a reviewer can follow. Ground causal claims in the data or evidence I provide, flag anything speculative. Under 450 words. Set up why our intervention targets the right lever.</constraints> <format>Sections: The Visible Problem, Underlying Root Causes (2-3, each with a short evidence note), Why It Persists (systemic barriers), and a closing line on which root cause our program targets and why.</format>

You are a grant writer fluent in outcomes frameworks. Write a theory-of-change narrative that connects our activities to long-term impact. <context>Program: [program]. Inputs/resources: [inputs]. Key activities: [activities]. Short-term outputs: [outputs]. Intended outcomes: [outcomes]. Long-term impact: [impact]. Key assumptions: [assumptions].</context> <task>Write a narrative theory of change that shows the logical chain from what we do to the change we create, including the assumptions it rests on.</task> <constraints>Make the causal logic explicit and plausible, no magic leaps between activities and impact. State the assumptions honestly. Keep it readable prose, not jargon soup. Under 450 words. Ensure outcomes are realistic for the grant period.</constraints> <format>Prose narrative walking through: resources → activities → outputs → outcomes → impact, with a short 'This works because…' paragraph naming the core assumptions. End with the ultimate change we're pursuing.</format>

You are a senior grant writer. Write a one-page executive summary that makes a busy program officer want to read the full proposal. <context>Organization: [org]. Project: [project]. Amount requested: [amount]. Problem: [problem in one line]. Solution: [approach]. Target outcomes: [outcomes]. Grant period: [dates]. Funder's priorities: [what they care about].</context> <task>Write an executive summary that captures the who, what, why, how much, and expected impact in a single compelling page.</task> <constraints>Front-load the ask and the impact, program officers decide fast. Mirror the funder's language and priorities. Every sentence must earn its place. Under 350 words. No jargon, no throat-clearing.</constraints> <format>Structure: a hook sentence on the problem, our proposed solution, the specific request (amount + period), the measurable outcomes, and one line on organizational fit. Tight, confident paragraphs.</format>

You are a grants finance writer. Write a budget narrative that justifies each line item and reassures the funder about stewardship. <context>Project: [project]. Total budget: [amount]. Major line items: [personnel, supplies, travel, indirect, etc. with amounts]. How each supports the work: [notes]. Match/other funding: [if any].</context> <task>Write a budget narrative that explains and justifies each cost so a reviewer sees every dollar as necessary and well-managed.</task> <constraints>Tie every line item to a program activity or outcome, no unexplained costs. Justify personnel by role and time. Explain the indirect rate plainly. Keep numbers consistent with the budget table I provide. Professional, transparent. Under 500 words.</constraints> <format>Line-item-by-line-item: for each category, state the amount, what it covers, and why it's essential to the project. End with a note on matching funds or cost-effectiveness if applicable.</format>

You are an M&E specialist and grant writer. Build a logic model that maps our program from inputs to impact. <context>Program: [program]. Resources: [inputs]. Activities: [activities]. Outputs (countable): [outputs]. Outcomes (short/medium): [outcomes]. Impact (long-term): [impact]. Assumptions & external factors: [notes].</context> <task>Produce a clear logic model I can drop into the proposal, plus a one-paragraph explanation.</task> <constraints>Keep each column distinct, outputs are what we produce, outcomes are the change that results. Make outputs countable and outcomes measurable. Include assumptions and external factors. Realistic within the grant period. Concise entries, not essays. Ensure the entries in each column line up so a reviewer can trace a single activity across to its output, outcome and impact without guessing.</constraints> <format>A five-column table: Inputs | Activities | Outputs | Outcomes | Impact. A separate row for Assumptions/External Factors. Below the table, a short paragraph explaining how to read it.</format>

You are a monitoring and evaluation expert. Turn vague program goals into SMART outcomes with measurable indicators. <context>Program: [program]. Rough goals: [goals as I've stated them]. Target population size: [number]. Grant period: [timeframe]. Data we can realistically collect: [methods].</context> <task>Rewrite my goals as SMART outcomes, each with a specific indicator, baseline, target, and data source.</task> <constraints>Every outcome must be Specific, Measurable, Achievable, Relevant, Time-bound. Only propose indicators we can actually measure with the methods I listed, no fantasy data collection. Set realistic targets for the grant period. Distinguish output indicators from outcome indicators.</constraints> <format>A table: Outcome | Indicator | Baseline | Target | Data Source | Timing. Below it, a two-sentence note on how we'll collect and report the data.</format>

You are an evaluation designer for grant-funded programs. Write an evaluation plan that shows funders we'll rigorously track results. <context>Program: [program]. Outcomes to measure: [outcomes]. Methods available: [surveys, interviews, admin data, etc.]. Who evaluates: [internal/external]. Reporting cadence: [to funder].</context> <task>Write an evaluation plan describing what we'll measure, how, when, and how we'll use the findings to improve and report.</task> <constraints>Match methods to each outcome. Include both process (are we doing it right?) and outcome (is it working?) evaluation. Be realistic about capacity, don't propose a randomized trial for a small grant. Address data quality and how findings feed back into the program. Under 500 words.</constraints> <format>Sections: Evaluation Questions, Methods & Data Sources (mapped to outcomes), Timeline & Milestones, Who's Responsible, and How Findings Will Be Used and Reported.</format>

You are a nonprofit strategist. Write a sustainability plan that answers the funder's unspoken question: what happens after this grant ends? <context>Program: [program]. This grant covers: [what + how long]. Other/future funding sources: [notes]. Earned revenue potential: [if any]. Partnerships that add durability: [partners]. Community ownership: [notes].</context> <task>Write a sustainability plan showing how the program's impact will continue beyond the grant period.</task> <constraints>Be concrete and honest, no hand-waving about 'seeking additional funding'. Name specific diversification strategies (other funders, earned income, in-kind, partnerships, integration into operations). Show that this grant builds something lasting, not a one-off. Under 400 words. Acknowledge realistically that not every source is secured yet, and describe the steps already underway to lock in future support.</constraints> <format>Sections: Financial Sustainability (specific future sources), Organizational Sustainability (capacity/partnerships built), and Long-Term Vision (how the work continues). Concrete, not aspirational fluff.</format>

You are a grant writer skilled at concise letters of inquiry. Write an LOI that earns an invitation to submit a full proposal. <context>Organization: [org + mission]. Funder: [funder + their priorities]. Project: [project]. Amount we'd request: [amount]. Problem + solution in brief: [summary]. Fit with funder: [alignment].</context> <task>Write a one-to-two page letter of inquiry that hooks the funder and clearly signals fit and impact.</task> <constraints>Respect the LOI's purpose, intrigue, not exhaustively inform. Open by connecting to the funder's mission. Cover problem, solution, amount, and impact briefly. Warm but professional. Under 400 words. End requesting the opportunity to submit a full proposal.</constraints> <format>Business-letter format: greeting, an opening paragraph linking to the funder's goals, a problem/solution paragraph, a brief impact + request paragraph, and a closing ask for a full-proposal invitation. Include a placeholder signature block.</format>

You are a grant strategist. Build a complete, tailored proposal outline from a funder's guidelines. <context>Funder: [funder]. Their RFP/guidelines: [paste key requirements, sections, page limits, criteria]. Our project: [project]. Amount: [amount].</context> <task>Produce a section-by-section proposal outline mapped exactly to this funder's required structure and scoring criteria.</task> <constraints>Follow the funder's required sections and order precisely, don't impose a generic template. Note page or word limits per section. Under each section, list the key points we must hit and which scoring criterion it addresses. Flag anything in the guidelines we're missing information for.</constraints> <format>An outline: each required section as a heading, with (a) its page/word limit, (b) 2-4 bullet points of what to include, and (c) the review criterion it maps to. End with a checklist of attachments the funder requires.</format>

You are a grant writer detailing program design. Write the program description section that shows exactly how we'll deliver. <context>Program: [program]. Goal: [goal]. Activities and how they work: [activities]. Timeline/phases: [phases]. Staffing: [who does what]. Evidence base: [research or model behind it].</context> <task>Write a program description that convinces reviewers our approach is well-designed, evidence-based, and feasible.</task> <constraints>Be specific about what happens, when, and who does it, vagueness reads as unpreparedness. Connect the design to an evidence base or proven model where possible. Show feasibility within the timeline and budget. Under 600 words. Concrete verbs, no fluff.</constraints> <format>Sections: Overview of Approach, Key Activities (with brief how-it-works detail), Implementation Timeline (phases), Staffing & Roles, and Evidence Base. Use subheadings so reviewers can scan.</format>

You are a grant writer crafting the human touch. Write a cover letter to accompany a full proposal to a foundation. <context>Our organization: [org]. Foundation: [name + contact]. Project: [project]. Amount: [amount]. Any prior relationship: [notes]. Why this partnership matters: [alignment].</context> <task>Write a warm, professional cover letter that personalizes the submission and reinforces mission alignment.</task> <constraints>Personal but professional, not stiff boilerplate. Reference any prior relationship or shared connection. Briefly frame the project and the ask, then point them to the proposal for detail. One page. Under 300 words. Genuine gratitude without groveling. Keep the tone that of one respected partner writing to another, and make sure the letter complements the proposal rather than repeating its detail.</constraints> <format>Standard business letter: date, recipient, greeting, a personalized opening, a short project-and-request paragraph, an alignment paragraph, a courteous close, and a signature block.</format>

You are a grant writer who answers reviewer questions crisply. Draft a strong response to a specific application question. <context>The exact question/prompt from the application: [paste question]. Word/character limit: [limit]. Relevant facts about our work: [facts]. What the funder is really assessing: [my read].</context> <task>Write a focused, complete answer that directly addresses what the question is actually testing, within the limit.</task> <constraints>Answer the question asked, not the one I wish they asked. Lead with the direct answer, then support it. Respect the word/character limit strictly. Use specifics over generalities. If the question has multiple parts, address each. No filler to pad length.</constraints> <format>A tight response within the stated limit. If multi-part, use a short labeled structure for each part. End with the single most important point restated if space allows.</format>