Custom GPT: Build a Grant Writing Assistant That Knows Your Organization

What This Builds

A purpose-configured Claude Project that functions as a dedicated grant writing assistant for your organization — one that already knows your mission, programs, voice, past winning proposals, and funder relationships. Every conversation starts from full organizational context. New staff can use it on day one. Freelance colleagues can use it without a briefing. And you stop re-explaining your organization to AI in every new chat session.

Prerequisites

• Claude Pro subscription ($20/month — see Level 3 guide for Claude for Nonprofits discount)
• Completed the basic Claude Projects setup (Level 3 guide: "Build Your Organizational Knowledge Base in Claude")
• 1–3 of your best past winning proposals in digital format
• Your current boilerplate library (or key organizational documents)
• Time to build: 1.5–2 hours for the full setup; ongoing refinement
• Cost: $20/month (Claude Pro)

The Concept

Think of this as training a new junior grant writer who's extremely fast at writing but knows nothing about your organization. You spend one afternoon teaching them everything — your mission, your programs, your outcomes data, your voice, your funder relationships, your past proposals. After that, they can produce accurate, on-voice first drafts for any section of any proposal, without you having to explain context every time.

The Claude Project is that junior writer. The Project Instructions are your orientation handbook. The uploaded documents are your organizational library. Once set up, every conversation in the Project starts from full context.

Build It Step by Step

Part 1: Deepen Your Project Instructions

If you've completed the Level 3 Claude setup, you already have a basic Project with instructions. Now you're going to significantly expand those instructions to add:

• Detailed program descriptions
• Your current funder relationships
• Voice and style rules that go beyond a single sentence
• Common pitfalls to avoid
• A library of standard formats you use

Open your existing Claude Project. Click the pencil icon on the Project Instructions. Expand them to include:

# [Organization Name] Grant Writing Assistant

## Who You Are
You are the grant writing assistant for [Organization Name], a [type] nonprofit founded in [year] and based in [city, state].

## Organization Overview
**Mission:** [paste full mission statement]
**Vision:** [paste vision if you have one]
**Tax status:** 501(c)(3)
**Annual budget:** approximately $[X]
**Staff:** [X] full-time, [X] part-time
**Geographic service area:** [specific counties/cities/state]

## Programs (current)
For each program, include:
- Program name:
- Brief description (2-3 sentences):
- Population served:
- Annual participants:
- Key outcomes from most recent data:
- Funding sources currently:
- Budget for this program: $[X]

[Repeat for each program]

## Voice and Style Rules
ALWAYS:
- Write in an accessible, warm tone — avoid academic jargon
- Use person-first language ("people experiencing homelessness," not "the homeless")
- Lead with community strengths before describing challenges
- Back claims with specific data when available
- Be specific — exact numbers, locations, program names

NEVER:
- Use the word "vulnerable" to describe our participants
- Write passive voice throughout (occasional passive is fine)
- Invent statistics — flag when you need data that hasn't been provided
- Use phrases like "cutting-edge," "innovative," or "unique" without specifics
- Write more than the requested word count

## Common Funder Relationships
[For each active funder, note:]
- [Funder name]: [their priorities, our relationship history, any style preferences we've learned]

## Formatting Standards
- Logic models: table format with 5 columns (Inputs | Activities | Outputs | Short-Term Outcomes | Long-Term Outcomes)
- Objectives: SMART format — "By [date], [X]% of participants will [measurable change]"
- Budget narrative: justify each line item with 2-4 sentences connecting cost to program activity
- Progress reports: open with summary sentence, report on each objective in order, close with next-period projection

## What to Do When You Don't Have Information
If I ask you to draft a section and you don't have a key piece of information in the uploaded documents, do not invent it. Instead, include a [NEED: describe what's missing] placeholder in the text and flag it after the draft: "I've flagged [X] items where I needed information not in the uploaded documents."

Save the instructions.

Part 2: Upload Your Best Winning Proposals

Return to the Project's document section. Upload your 3 best past winning proposals — ideally from different funder types (community foundation, corporate, government). These teach Claude your proven language patterns.

As you upload each, add a note in a separate uploaded text file that says which proposals are the strongest models:

# Proposal Models

Best community foundation proposal: [name of file]
Best government proposal: [name of file]
Best corporate proposal: [name of file]

These proposals have been funded and represent our strongest work. Use them as style models.

Part 3: Build a Prompt Template Library

Create a Google Doc called "Grant Assistant Prompt Templates" and add it to the Project. Include copy-paste prompt templates for your most common tasks:

# Standard Prompts for [Org Name] Grant Assistant

## Needs Statement
"Draft a [X]-word needs statement for a [program name] proposal to a [funder type].
Funder priority: [their focus]. Use our real community data and current program stats."

## Program Description
"Write a [X]-word program description for [program name] for a [funder type] grant.
Include: model description, evidence base, staff qualifications, and outcomes.
Special emphasis for this funder: [anything specific to this application]."

## LOI
"Write a 2-page Letter of Inquiry to a [funder type] for [program name].
Request amount: $[X]. Funder priorities: [their focus areas]. Use our strongest outcomes data."

## Progress Report
"Write a [X]-word progress report for [funder name] on [program name].
Reporting period: [dates]. Original goal: [paste]. Outcomes: [paste data]."

## Evaluation Plan
"Write an evaluation plan for [program name] grant. Objectives: [paste].
Grant period: [X months]. Reporting schedule: [quarterly/annual/interim+final]."

Part 4: Test with a Real Proposal Challenge

Give the assistant a challenging task that requires drawing on your organizational context:

"We're applying to the [Foundation] for the first time. Their priorities are [X and Y]. We want to fund our [program name]. Write a 500-word program description that positions our work in terms of their priorities while accurately representing our actual program model. Use our real outcome data."

Read the output carefully:

• Does it use your actual program name and statistics? (good)
• Does it match your organizational voice? (check against your past proposals)
• Does it accurately represent your program model? (critical)
• Does it position for the funder's priorities while staying authentic? (the hard part)

If it invents statistics or gets the program model wrong, check which documents are uploaded and add the missing information.

Real Example: Full Workflow in Action

Setup: Your Claude Project has:

• Project Instructions with full org context, voice rules, and program descriptions
• 3 past winning proposals uploaded
• Current outcome data document uploaded
• Annual report uploaded
• Prompt template library uploaded

Input: "We've been invited to submit a full proposal to the Roberts Family Foundation for our senior isolation program. Their priorities are aging-in-place and social connection. Request: $30,000. Required sections: needs statement (400 words), program description (600 words), evaluation plan (300 words), org capacity (300 words). Deadline: 3 weeks."

Output: Claude produces all four sections drawing from your uploaded documents — your actual senior program data, your org's real history, the voice from your past proposals, and positioning that reflects the funder's stated priorities. You spend 45 minutes reviewing and personalizing rather than 8 hours drafting from scratch.

Time saved: 6–7 hours on this proposal alone. Across a grant season with 20+ proposals, this represents weeks of recaptured time.

What to Do When It Breaks

• Claude doesn't use uploaded documents: In your prompt, explicitly say "Use our program data from the uploaded outcome report." Claude sometimes needs to be directed to specific documents.
• Output doesn't match our voice: Add more voice examples to the Project Instructions — paste 3-4 of your best written sentences as explicit style examples.
• Claude invents statistics: Reinforce in instructions: "NEVER invent statistics. Use [NEED: ] placeholders when data is missing." Then provide the missing data by uploading it.
• Claude exceeds word limits: Add to instructions: "Strictly respect all word limits. If I say 300 words, do not exceed 310 words."

Variations

• Simpler version: Don't create a full Project — just start every new Claude conversation by pasting your context document (2–3 paragraphs about your org). Less powerful but zero setup time.
• Team version: Share the Project with co-writers or a freelance grant writer so they can produce on-voice content without being briefed on your organization.
• Multi-funder version: Create separate Claude Projects for your 3–4 major funders, each with that funder's past RFPs and application guidelines uploaded alongside your org documents. Each Project then "knows" both your org and that specific funder's preferences.

What to Do Next

• This week: Expand your Project Instructions to the full template above and upload your best 3 proposals
• This month: Run 5 real proposal sections through the assistant and refine instructions based on what's accurate vs. what needs correction
• Advanced: Create a "funder relationship" section in your Project Instructions documenting what you've learned about each major funder's preferences, program officer quirks, and past feedback on your applications — the institutional knowledge that's currently only in your head

Advanced guide for nonprofit grant writer professionals. Claude Pro features and Projects interface are updated regularly — check claude.ai/changelog for current feature availability.