Anthropic just published a practical playbook for nonprofits ready to graduate from copy-pasting prompts into a chat window. According to Anthropic, most nonprofit teams still treat Claude like a smarter Google, missing the features that turn it into an actual operational tool. The guide walks through how to move from one-off conversations to repeatable workflows that save staff hours every week.
What stands out here is the framing. Anthropic isn’t pitching new tech. It’s showing teams how to use what already exists in ways most users skip past. Below is a step-by-step adaptation of the workflow shifts the guide recommends.
Quick Start
You’ll learn how to move nonprofit workflows out of single chat sessions and into structured, reusable systems inside Claude. You need a Claude account (free or paid), some recurring tasks you do manually, and roughly an hour to set up your first Project.
- Audit Your Repetitive Tasks: Before opening Claude, list the writing and research tasks your team does every week. Grant reports, donor emails, board updates, social posts, volunteer onboarding. This matters because chat is fine for one-time questions, but anything you do twice should live in a Project. Without this audit, you’ll keep rebuilding context from scratch.
- Set Up Projects for Each Recurring Workflow: Anthropic recommends creating a separate Project for each major workstream. Inside each Project, upload your style guide, past examples, donor personas, mission statement, and any reference docs. Claude pulls from this context every time, so you stop pasting the same background into every prompt. One nonprofit cited in the guide cut grant draft time roughly in half after loading two years of funded proposals as Project knowledge.
- Build Reusable Prompts as Custom Instructions: Inside each Project, write custom instructions that define tone, format, and constraints. Example: “Write in second person. Keep paragraphs under three sentences. Always end with a specific ask.” This is the highest-leverage step in the guide. Custom instructions turn Claude from a generalist into your organization’s voice.
- Use Artifacts for Anything You’ll Edit: When you need a document, email, spreadsheet, or webpage, ask Claude to produce it as an Artifact. Artifacts open in a side panel you can edit directly, version, and export. Anthropic notes this is where teams underuse the platform most. Drafting a fundraising one-pager in an Artifact beats wrestling with chat output you have to copy into Google Docs.
- Connect Your Tools: The guide highlights integrations as the real workflow shift. Connect Google Drive so Claude can read your existing materials. Connect Gmail or Outlook for drafting replies in your voice. For technical teams, Claude Code can pull from your CRM or database. The point: stop manually feeding Claude information it could fetch itself.
- Delegate Multi-Step Work to Agents: For research-heavy tasks like prospect research on potential funders, use Claude’s agent capabilities. You give one instruction (“research these 20 foundations and summarize their giving priorities”), and Claude works through it autonomously. This is the biggest time saver for development teams, who often spend full days on this manually.
- Train Your Team on the System, Not the Tool: Anthropic’s closing point lands hard. Tools change. Workflows persist. Document which Project handles which task, who owns each one, and the prompt patterns that work. New hires inherit a system, not a Slack thread of tribal knowledge.
Why This Matters
Nonprofits run lean. Every hour reclaimed from administrative work goes back into mission delivery. The teams pulling ahead aren’t the ones with the biggest AI budgets. They’re the ones treating Claude as infrastructure, not a search bar.
Next Steps
Pick one workflow from your Step 1 audit. Build the Project this week. Measure how much time it saves over two weeks. Then build the next one. Full details are available in Anthropic’s original guide.