How to Prompt AI to Write in Your Nonprofit's Voice
To prompt AI to write in your nonprofit's voice, do not describe the voice with adjectives. Show it. This prompt analyzes writing samples you paste in from your own organization and produces a short voice and style guide. You then paste that guide at the top of later grant writing prompts so drafts start closer to how you actually sound.
The prompt
You are helping me document my nonprofit's existing writing voice so I can reuse it when drafting grant proposals. Analyze only the writing samples below. Do not infer facts, programs, audiences, outcomes or claims that are not supported by the samples. Identify the recurring patterns in: 1. How we frame our mission and impact 2. Tone and personality 3. Who we seem to be writing for and how we relate to them 4. Vocabulary and preferred terms, including how we refer to the people we serve 5. Sentence length and paragraph structure 6. How we use evidence, stories and calls to action 7. Words, tones or habits we avoid Then write a reusable voice and style guide of 200 to 300 words. Write it as practical instructions that begin with verbs such as "Lead with," "Use," "Prefer" and "Avoid." Quote a short phrase from the samples to illustrate each instruction. Add a five-item checklist I can use to review future grant drafts against this voice. If the samples conflict with each other or are too limited to support a conclusion, say so instead of guessing. Writing samples (each labeled with its purpose and audience): [PASTE WRITING SAMPLES]
Works in ChatGPT, Claude, Gemini and other AI chat tools. Replace each bracketed placeholder with your own details before you send it.
What to fill in
- [PASTE WRITING SAMPLES]
- Several pieces of writing your organization has already approved and published: website copy, annual report narrative, program descriptions, newsletter text. Label each one with its purpose and audience, for example "Annual report, for donors." Remove names, contact details and anything confidential first.
Why this prompt works
Asking an AI to "sound warm and professional" produces the same generic voice for everyone, because adjectives mean different things to different writers. Examples are far more precise.
- Examples before instructions. Giving the AI real samples lets it work from observable choices (word length, how you name the people you serve, how often you use numbers) instead of interpreting vague labels.
- Named categories. The seven areas direct the analysis to the features that matter in grant writing, so you get more than "the tone is friendly."
- Analysis first, then a guide. The prompt asks the AI to identify patterns before it writes instructions. Separating the two steps tends to give a guide that is tied to the evidence.
- Quoted illustrations. Requiring a phrase from the samples for each instruction lets you check that the guide describes your writing and not nonprofits in general.
- A length limit. At 200 to 300 words the guide is short enough to paste into every later prompt.
- Source grounding. The samples are evidence of how you write. The prompt tells the AI not to treat them as a source of facts to reuse.
Why it is appropriate to use
This is a setup task you do once, before drafting begins. It belongs in the readiness phase because a shared voice guide helps everyone who touches a proposal, whether staff, consultants or an AI tool, start from the same place.
It is an appropriate use of AI because the input is writing your organization has already made public, and the output describes your own style. Nothing in it is a claim to a funder.
A voice guide does not replace grant strategy, program design or compliance review. Do not use it to imitate another organization, to dress up weak evidence or to make AI-written text pass as written entirely by a person. Some funders restrict or require disclosure of AI use, so check each funder's policy before using AI-assisted text in an application. A consistent voice does not make an inaccurate statement accurate.
Do not paste confidential proposals, client stories that identify individuals or unpublished financial information as samples.
How to check and revise the output
- Compare the guide with the samples. Each instruction should have a quoted phrase behind it. Remove any that read like general writing advice.
- Have the right person approve it. Ask whoever owns communications, or your executive director, to confirm the guide sounds like the organization on a good day.
- Check the language about people. Make sure the guide reflects the respectful terms your organization and community actually use.
- Test it. Paste the guide into a new chat with one low-stakes paragraph of real program facts and ask for a rewrite. If the result is off, fix the guide, not the paragraph.
- Keep facts separate. Store the guide apart from current statistics and program details so old examples never become new claims.
Frequently asked questions
- What should you include in a prompt so AI can write in your nonprofit's voice?
- Include several representative writing samples and ask the AI to analyze them for tone, vocabulary, sentence style, structure, audience and formality. Tell it to work only from those samples and turn its findings into a short, reusable voice guide, flagging anything it is unsure about.
- How many writing samples does the AI need?
- Use several pieces rather than one, so a single unusual document does not define the guide. Choose samples from the kinds of writing you want the guide to cover, and label each with its audience.
- Will a voice guide stop my proposal from sounding AI-written?
- It helps drafts start closer to your own style, but it is not a guarantee and it should not be used to hide AI use from a funder that asks about it. A person who knows the program still needs to revise every draft and verify every fact.