Claude Code is Anthropic’s AI assistant that church staff can use to draft emails, sermons, announcements, social posts, and meeting agendas, all in plain English with no coding required. I use it daily as Executive Pastor at New Hope Hawaii Kai and as Founder of REACHRIGHT, and I’ve built over 30 church-specific skills that turn weekly admin grind into 15-minute work. The “Code” in the name throws people off, but it’s not a developer tool. It’s a co-worker that takes plain-English instructions and gets real work done.
If you’ve heard about AI tools for ministry but felt like everything was either too generic (ChatGPT) or too technical (everything with “developer” in the name), this is for you. I’ll walk through what Claude Code actually is, why it works better than a chatbot for church work, the seven workflows my staff runs every week, the nonprofit discount most pastors don’t know about, and how to get started in 30 minutes.
I covered the broader set of AI tools for churches in my best AI tools for churches roundup. This post goes deep on one tool, the one I use more than any other.
What Claude Code Actually Is (And Why the Name Confuses Pastors)
Claude Code is Anthropic’s AI assistant that runs on your computer. You install it, sign in, and start typing instructions. It can draft documents, edit files in your folders, run scheduled tasks, and follow custom workflows you build once and reuse forever. The “Code” in the name is historical, the tool started as a coding assistant for developers, but in 2026 it works for anyone who can describe what they need.
Anthropic is the AI company behind Claude, one of the major AI assistants you’ve probably heard about alongside ChatGPT and Gemini. Claude Code is their power-user version of Claude. Think of it this way: ChatGPT.com is the web chat. Claude Code is the same intelligence with file access, custom workflows, and the ability to do real work on your computer.
Most pastors I talk to assume Claude Code is for software engineers. It’s not. The clearest sign of the shift is that Anthropic now markets Claude Code through their nonprofits program alongside grant writing, donor analysis, and program management. If they thought it was only for developers, they wouldn’t be selling it to nonprofits at 75% off.
How Claude Code Differs From the Chatbot You’ve Been Using
The single biggest difference: Claude Code can read and write files on your computer. ChatGPT in your browser handles one conversation at a time and forgets everything when you close the tab. Claude Code reads your full church documents folder, edits drafts in place, and remembers context across sessions.
The second biggest difference: Skills. A Skill is a reusable, plain-English workflow you build once. After I built my “church-email” Skill, every weekly email my communications director writes follows the same structure and voice, automatically. No retraining, no copying old prompts. The Skill remembers how we write.
The third difference: Routines. You can schedule Claude Code to run tasks on a cadence. Every Monday morning, my Skill pulls Sunday’s sermon and drafts the small group discussion questions before our group leaders even open their inboxes.
Why Claude Code Works Better Than ChatGPT for Church Workflows
ChatGPT is excellent for one-off questions and quick drafts. Claude Code is built for repeatable work, which is most of what church staff actually do.
| Capability | ChatGPT (web) | Claude Code |
|---|---|---|
| Quick Q&A | Excellent | Excellent |
| Edits files on your computer | No (manual upload) | Yes (full folder access) |
| Reusable plain-English workflows | Custom GPTs (limited) | Skills (full file access) |
| Reads your existing church files | One-by-one upload | Full folder access |
| Scheduled tasks (run weekly) | No | Yes (Routines) |
| Holds your voice across the team | Hard to enforce | Skills lock voice in |
| Cost for 501(c)(3) churches | Standard pricing | Up to 75% off via Claude for Nonprofits |
The repeatability is what matters most for ministry. A church communications director writes the same kinds of emails every week, the same kinds of announcements every Sunday, the same kinds of social posts for every sermon series. A Skill captures how your church writes once. Every output after that stays consistent without anyone retraining the AI from scratch.
7 Real Workflows My Staff Uses Every Week
This is the part most people want to skip to, so I’m not going to pad it. These are the seven workflows my team at REACHRIGHT and at New Hope Hawaii Kai run every week using Claude Code. Every one of them runs through a custom Skill I built. Every one of them saves real hours.
1. The Weekly Church Email
My communications director used to spend 60 to 90 minutes drafting the weekly email. She’d pull the announcements from the staff Slack, format them, write a warm intro, add scripture, build out events, and write a subject line.
With the church-email Skill, that process is 15 minutes including the human edit pass. She pastes in the announcements and events, the Skill drafts the full email in our voice, mobile-friendly and scannable, and she edits the human moments back in. Subject line, preview text, body, all done.
The Skill knows we don’t say “blessed and highly favored.” It knows we keep paragraphs short. It knows the CTA goes near the top, not the bottom.
2. Sunday Morning Announcement Script
Sunday announcements are a 60 to 90 second window where you either keep people’s attention or lose it. Most churches do this badly because the person reading the script wrote it five minutes before service started.
The announcement-script Skill takes the week’s events and prioritizes them, drops anything that doesn’t belong on stage, and writes a conversational 60 to 90 second script with no more than three or four items. Pastor Pat or whoever’s hosting can read it cold and it sounds natural.
3. Sermon Prep Research
The sermon-research Skill is the one I use the most personally. I feed it the scripture passage, the topic I’m preaching on, and three or four questions I’m wrestling with. It comes back with commentary insights, historical context, original language notes from the Hebrew or Greek, and thinking prompts.
It does not write the sermon. I do that. The Skill gives me what I need to think well, in 10 minutes instead of two hours of book-flipping.
Skills are the difference. Once you build a "church-email" Skill once, every weekly email after that is 10x faster and stays consistent.
4. Small Group Discussion Questions
Every Sunday’s sermon should become Monday’s small group questions. Most churches don’t do this because nobody has time to write them by Monday morning.
The small-group-questions Skill reads Sunday’s sermon notes or transcript and generates the discussion guide: an icebreaker, four to five observation and interpretation questions, two application questions, and a closing prayer prompt. Ready to hand to group leaders.
5. Midweek Devotional
Between Sundays, churches go quiet. A midweek devotional sent via email or your church app keeps people connected to the message and to each other.
The midweek-devotional Skill writes a 200 to 300 word devotional based on Sunday’s text, personal and warm, not preachy. Scripture-anchored. The whole thing takes 90 seconds.
6. Platform-Native Social Posts
Every event, sermon series launch, or important scripture deserves social posts. Generic posts get ignored. Platform-native posts (different captions for Facebook, Instagram, and Twitter) actually perform.
The church-social-post Skill takes a topic, event, or scripture and returns ready-to-paste captions optimized per platform, plus an image suggestion. My communications team posts more consistently because the friction is gone.
7. Meeting Agendas
Staff meetings. Elder board meetings. Deacon meetings. Volunteer huddles. Every one of these needs a structured agenda or it becomes a venting session.
The meeting-agenda Skill builds the agenda with time blocks, discussion questions, and action item prompts. I built it after a deacon meeting ran 45 minutes long because nobody had a clock on the discussion.
The Claude for Nonprofits Discount Most Churches Don’t Know About
This is the part of the post that should pay for the time you spent reading it.
If your church has 501(c)(3) status, this is one of the easiest wins in your tech budget for the year. Standard Claude Team pricing runs roughly $30 per seat per month. At 75% off, you’re looking at $7.50 per seat per month with Claude Code, file integrations, and the full Claude product suite included.
I won’t pretend the application is instant, you’ll need to verify your nonprofit status, but for what you get back in staff productivity, the math is obvious.
Common Mistakes Pastors Make With Claude Code
Most pastors who try Claude Code and bounce off it make one of these five mistakes. I’ve watched dozens of pastors fall into the same patterns. Here’s what to avoid.
The five patterns to avoid:
- Treating it like Google. Generic prompts get generic output. Specific context, your church’s voice, your audience, your goals, gets specific output. Build Skills, don’t just chat.
- Skipping the Skills setup. A 15-minute investment in one Skill saves five hours over the next month. The pastors who treat Claude Code as a one-shot chatbot never see the productivity curve.
- Asking for finished work instead of drafts. Claude Code writes drafts. A 30-second human edit pass is the difference between AI slop and content that sounds like you. Always plan for the human pass.
- Pasting member data without an AI policy. If you’re using Claude Code for anything involving member information, donor data, or counseling notes, you need a written AI policy first. Read my guide on church AI rules before you go further.
- Using output verbatim. Claude Code is a co-worker, not a replacement. Treat its output the way you’d treat a first draft from a junior staff member: helpful, directionally correct, and in need of your eyes before it goes out the door.
How to Get Started in 30 Minutes
You can have Claude Code installed and drafting your first email within half an hour. Here’s the path I’d take if I were starting today.
- Download Claude Code from claude.com/product/claude-code. The installer takes 2 to 3 minutes.
- Sign in with your Claude account. If your church qualifies, apply for Claude for Nonprofits before paying full price.
- Open Claude Code in your church's documents folder. This gives it the context it needs to write in your church's voice.
- Run your first prompt. Try: "Help me write Sunday's announcements based on these bullet points: [paste 3 to 4 events]." See what it produces.
- Build your first Skill. Ask Claude Code: "Help me build a Skill called 'sunday-announcements' that writes a 60 to 90 second spoken announcement script, max 4 items, conversational tone." It'll guide you through it.
- Save and run the Skill weekly. Every Sunday morning becomes 5 minutes instead of 30.
The Skill you build in step 5 is the unlock. Once you have one Skill running, you’ll start seeing other repetitive tasks and building Skills for those too. Within a month you’ll have five to seven. Within six months you’ll have what I have: a custom library that runs most of your weekly admin work.
Building Your Church’s Custom Skill Library
My library of 30+ Skills didn’t get built in a weekend. It grew organically. Every time I caught myself doing the same task twice, I’d stop and build a Skill instead of doing it a third time.
My communications director didn't believe a "developer tool" would help her, until she watched it draft a church email in our voice in 30 seconds.
If you’re starting a Skill library for your church, here are the five I’d build first, in this order:
- church-email: Weekly congregation email. Highest-frequency, highest-pain task in most churches.
- announcement-script: Sunday morning announcements. Public-facing, voice-critical.
- sermon-research: Sermon prep support. Saves the most hours per week for whoever preaches.
- small-group-questions: Weekly group guide. Closes the Sunday-to-Monday gap.
- church-social-post: Platform-native social captions. Removes the bottleneck on consistent posting.
After those five, watch your team’s weekly rhythm for two weeks. Notice what tasks keep eating time. Build a Skill for the next one. Repeat.
Some Skills I’ve built that aren’t on the starter list but you’ll probably want eventually: pastor-foundation (shared context layer that all pastor Skills inherit from), sermon-brainstorm (interactive sermon prep partner), sermon-to-blog (turn a transcript into an article), sermon-to-youtube (optimize a sermon video for YouTube), social-media-calendar (a week or month of posts mapped to dates), meeting-agenda (any meeting), midweek-devotional (between-Sunday touch), church-letter (any formal church letter), and direct-response-copy (every persuasive piece my agency writes).
Like a virtual assistant frees up administrative hours, Claude Code frees up content and communication hours. If you’ve been considering hiring a virtual assistant for church work, Claude Code does a lot of the same job at a fraction of the cost.
Frequently Asked Questions
Ready to Put AI to Work in Your Church?
The pastors who get the most out of Claude Code are the ones who treat it like a co-worker, not a magic button. They build Skills. They iterate. They give it context. They run a human pass on every output. And in return, they get hours back every week.
You don’t need a tech background. You don’t need a developer on staff. You need 30 minutes and a willingness to try one Skill.
If you want to think through how AI fits into your church’s workflow without losing the human touch, let’s talk. My team at REACHRIGHT has been helping churches use AI tools well since the beginning of this wave, and we’re happy to point you in the right direction whether you end up working with us or not.
Want help thinking through AI for your church?
Free 30-minute consultation. We'll talk through your church's current workflow and where AI can save your team the most hours, with or without becoming a client.
More Resources for Churches
- Best AI Tools for Churches in 2026 — The full list, including the other AI tools my team uses
- Church AI Rules: Writing Your Church’s AI Policy — Set the policy before you scale the tools
- Why Churches Use Virtual Assistants — The parallel to delegating admin work
- Free Tech Training Resources for Churches — Build broader staff tech literacy
- Best Free SEO Tools for Churches — Pair Claude Code workflows with free SEO tools for content that actually ranks