Claude for Nonprofits: the plugin that showed up in your workspace, and what to do with it this week

On October 26, 2026, Anthropic added a Claude for Nonprofits plugin to every nonprofit organization on a Claude Team or Enterprise plan. It is installed automatically and costs nothing extra. In the same announcement, Claude Code became part of nonprofit plans at no additional cost.

A plugin is a bundle of skills (saved instructions Claude follows for a specific task, like "draft a grant report") and connectors (links that let Claude read from tools you already use). This one was built with about 30 nonprofits, so the tasks it covers are the ones those organizations said they spend the most staff time on.

If you are the person who set up Claude for your nonprofit, this lands on your desk. Most nonprofit Claude workspaces are small: Anthropic says more than 25,000 nonprofits use Claude and over 75% of them have fewer than 10 seats. So "the admin" is often also the development director or the operations manager. This guide is written for that person.

What the plugin covers

The skills are grouped into three areas.

Extend your team. Work a larger organization would hand to a dedicated staffer:

• Marketing campaign plans and content review.
• Hiring: job posts, interview guides, and a 90-day onboarding plan.
• Board support: a skills gap analysis of your current board, orientation packets for new members, and meeting decks.

Set up Claude responsibly. Two skills aimed at the admin:

• Claude maps where your organization keeps its records. The map is saved per user, and only when memory is turned on.
• Staff can ask "Can I use Claude for this?" and get an answer based on your AI use policy.

Fund your mission. The area most development teams will try first:

• Funder and grant research, with cited sources.
• Breaking down an RFP to show whether you're eligible and what it asks for.
• Drafting proposals and grant reports.
• Donor relationship support.

Do these two things before staff start using it

1. Give Claude your AI use policy

The "Can I use Claude for this?" skill answers from your policy. If you don't have one, it has nothing reliable to answer from, and staff will either guess or stop asking.

If you don't have a policy yet, start from an AI usage policy template and cut it down to one page. For a nonprofit, the questions that matter most are about donor data, client or beneficiary records, and anything covered by a funder's data agreement. Write down which of those can go into Claude and which cannot. Then read how to write a policy people actually follow before you send it round.

Anthropic is running a webinar for admins on data handling and AI use policy on November 10, and there is a new Anthropic Academy tutorial on the same topic.

2. Decide on memory before the records map gets built

The records-mapping skill saves what it learns about where your files live, per user, only when memory is on. That is useful: Claude stops asking where the board minutes are. It also means Claude is storing a description of your file layout for each person.

Decide whether memory is on for your workspace before staff run that skill, and tell them what it saves. A small team can settle this in one conversation.

Where to start: grant work

Pick one grant your team is already writing. Then run it through the plugin in this order:

1. RFP breakdown. Paste or upload the RFP and ask for eligibility, required sections, deadlines, and scoring criteria as a checklist.
2. Funder research. Ask what this funder has funded in the last few years and what they say they care about. The skill cites sources, so check two or three of them before you rely on the summary.
3. First draft. Give Claude your last successful proposal and your current program numbers. Ask for a draft that follows the RFP's section order.
4. Review. A person who knows the program reads every number and every claim about outcomes. Claude will write fluent sentences around a figure it got wrong.

Track how long the proposal took compared with the last one. That one number is the easiest way to show your board whether this is worth the time.

What Claude Code being included means for you

Claude Code is Anthropic's tool for writing and changing software. Most nonprofits don't have engineers, so the practical uses are smaller: a script that cleans a donor export, a small change to your website, or automating a report you build by hand every month. If you have a volunteer or contractor who maintains your site or database, tell them it's now included in your plan. Claude Code for your team covers how a team starts using it.

Pricing context

This announcement didn't change prices. Earlier nonprofit announcements set discounts of up to 75% for nonprofits, lowered the Team plan minimum to two people, put nonprofit plans on the same models as standard Team and Enterprise, and offered about 90% off for verified nonprofits in low- and middle-income countries, which brings a standard Team seat to $3 per user per month. If you're deciding between plans, Team vs. Enterprise lays out the difference.

Also announced

• A staff webinar on getting started, on November 12.
• Claude Corps has placed 1,000 early-career fellows in at least 400 U.S. nonprofits. Anthropic plans to extend it through a partnership with Taproot, which would match nonprofits with pro bono consultants. That part hasn't launched yet.
• Twelve consulting firms are listed as adoption partners, including Accenture, BCG, The Bridgespan Group, Deloitte, and Slalom.

A checklist for this week

1. Confirm the plugin appears in your workspace.
2. Upload or paste your AI use policy, or write a one-page version first.
3. Decide whether memory is on, and tell staff what the records map saves.
4. Run one live grant through the RFP, research, and drafting skills.
5. Register for the November 10 admin webinar, and send staff the November 12 one.

For the wider rollout after that first grant, rolling out Claude across teams covers who to bring in next and how to keep usage going after the first month.