All Insights

Claude AI’s New Nonprofit Fundraising Toolkit: How to Get Started, Benefits, and Risks

By Ryan Clement · Published

Preparing a grant application often starts with a familiar search: the latest program description, the approved budget, the funder’s requirements, and the results your organization can document.

That preparation is part of the work. It also creates a useful place to test AI.

Anthropic released its Claude for Nonprofits plugin on October 26, 2026, bringing reusable workflows for fundraising and nonprofit operations into Claude. For development officers, grant writers, and nonprofit leaders, it offers a starting point for work they already need to complete. See Anthropic’s announcement.

The practical question is whether it can help your team produce work that is easier to prepare, verify, and use. Here is how I would approach it.

What the toolkit includes

The official product is the Claude for Nonprofits plugin. “Fundraising toolkit” describes its practical purpose.

A plugin brings several capabilities together inside Claude. A skill supplies reusable instructions for a task. A connector gives Claude access to an external service, subject to authorization and permissions. That distinction matters when you move from asking questions to working with organizational information. Read how Claude plugins work.

The nonprofit plugin supports work such as:

  • Grant preparation: Break down eligibility and application requirements, then develop a first draft from your organization’s materials.
  • Grant reporting: Prepare a draft that connects results and spending to supporting records.
  • Donor and funder communication: Build meeting briefs, follow-up messages, and stewardship drafts.
  • Leadership support: Develop board orientation materials and help plan a board meeting presentation.

These are capabilities described in Anthropic’s product announcement. Their usefulness will depend on your materials and the review that follows.

The potential benefit is a more consistent starting process. A grant writer could spend less time rebuilding the same requirements checklist. A development officer could use a repeatable brief format. A small team could document a process that another colleague can follow.

How to get started

1. Confirm your organization’s access

Start with the Claude for Nonprofits program page.

The nonprofit program uses discounted Team and Enterprise plans. Team applicants verify their nonprofit status through Goodstack; Enterprise inquiries go through Anthropic’s sales team. Check eligibility and current pricing before signing up. Some organization types, including higher education institutions, are excluded from the nonprofit discount. Review the onboarding guide.

If your organization already has an account, use its approved workspace and check with the person responsible for managing it.

2. Find the nonprofit plugin

The plugin is normally preinstalled on nonprofit plans. If it is missing, ask your workspace administrator to check its availability. Claude’s nonprofit tutorial explains this starting point.

On Claude’s website or desktop app:

1. Open Customize in the left sidebar.
2. Select Plugins and check your installed plugins.
3. If you need to add a plugin, open Discover.
4. If the nonprofit plugin is available to your account, select it and choose Add.

Your organization’s settings may affect what you can install. The current menu path is documented in Claude’s plugin guide.

3. Give Claude useful organizational context

I would prepare a small set of approved materials: a current program summary, a verified budget, and examples of writing your organization is comfortable sharing with the tool.

The nonprofit plugin includes two useful setup skills:

  • /where-things-live maps where your organization keeps records.
  • /org-voice-guide helps establish a writing guide from your organization’s materials.

The map records locations; it does not import your records or grant access to those systems. Memory must be enabled to retain the map across chats. You can also attach approved files for an individual task. See the nonprofit setup tutorial.

Be specific about which documents are current. If an old proposal contains last year’s participation numbers, identify it as a writing example rather than a source for this year’s results.

4. Run one task you can check

Start a chat, type /, and select /funder-and-grant-research for the example below. This skill can assess your fit for a grant using the opportunity and your organizational materials. Claude also provides a + menu for accessing skills. See the plugin controls and nonprofit skill guide.

For a first test, I would use a public grant opportunity and an approved program summary. That gives you a manageable task with sources you can open and compare.

A first prompt you can adapt

After selecting the relevant grant skill and attaching your materials, try:

Review this grant opportunity against our approved program summary. Use the funder’s instructions for application requirements and our materials for facts about our organization.

Create a table showing each eligibility rule, deadline, required attachment, and reporting obligation. For each item, identify the source, whether our materials establish that we meet it, and what information is still missing.

Keep confirmed facts separate from assumptions. If a deadline, figure, or requirement cannot be verified, mark it as unconfirmed.

Finish with the questions our team needs to resolve before deciding whether to apply. Do not invent program outcomes, funding commitments, or supporting documents.

Then check the result against the original sources.

For example, imagine a grant that requires a 20% cash match. Your program summary describes volunteer support but says nothing about available matching funds. A useful output would flag that gap and ask for a finance decision. Treating volunteer time as an eligible cash match would create a problem, even if the rest of the draft reads well.

This is the kind of test that tells you something about the workflow. You can see whether it identifies a decision your team actually needs to make.

The risks worth understanding

Accuracy still needs a person

Claude can produce incorrect or unsupported information. Asking for sources and allowing it to say that information is missing can help, but those instructions do not guarantee accuracy. Anthropic’s guidance on reducing hallucinations recommends grounding answers in source material and checking claims.

For grant work, verify deadlines, eligibility, budget calculations, and statements about program results. Open the cited source and confirm it supports the claim. A link beside a sentence is only useful when the source actually says what the draft says it does. Before submitting, check the funder’s instructions for any rules about AI-assisted writing or disclosure.

Privacy involves more than model training

Anthropic says inputs and outputs from its commercial products, including Team and Enterprise, are not used for model training by default. However, submitting feedback through thumbs-up or thumbs-down, or otherwise opting in, can create an exception. Organization owners can disable the feedback setting. Read the commercial data policy.

That training policy does not remove the need to decide what staff may upload, retain, or share. Your donor confidentiality rules and restrictions on client information still apply. Before using confidential material, review your organization’s sharing, retention, and feedback settings. Anthropic’s nonprofit data-handling guide explains these controls.

For the first test, leave sensitive donor and client information out.

Connectors can take actions

When you are ready to connect another service, go to Customize → Connectors and review what it can do. Some connectors can read information; others can also edit files, change records, or send messages. Installing a plugin does not automatically authorize access to every system.

Owners on Team and Enterprise plans can restrict connector actions, including requiring approval or blocking writes. Connected providers also operate under their own terms. Review both the access requested and any account or subscription requirements. Read Claude’s connector documentation.

For an initial rollout, I would keep access limited to the task and retain human approval for consequential actions.

A polished draft can hide an unresolved decision

Some of the most important questions are organizational.

Does the program team agree with the proposed outcome? Has finance approved the budget? Does the development officer want to make that commitment to a donor?

A draft can make those questions look settled before the right person has answered them. Give each output a reviewer who understands the work and has responsibility for what happens next.

How to make it part of your workplace

Once the first test is useful, choose one recurring task and document the process.

Record which materials the team should use, who maintains them, which skill or instructions to run, and who reviews the result. Give the person managing the workflow time to improve it and teach colleagues how to use it.

Before expanding, compare several completed examples with your existing process:

  • How much preparation and review time did the task require?
  • What errors or missing information did someone have to catch?
  • Could another colleague follow the same process?
  • Did the finished work make the next decision or action clearer?

A quick draft that requires extensive correction may offer little benefit. A repeatable process that produces usable work and makes gaps visible is a stronger reason to continue.

Start with work your team understands

Claude’s new nonprofit fundraising toolkit offers a practical place to begin, particularly for teams that want existing workflows to build on.

I would start with one grant opportunity or one recurring communication, use approved information, and involve the person who knows the work well enough to question the output.

Then improve the process based on what the test shows. That is how a new AI tool can earn a useful place in your organization.