Start a project

AI for churches, without the hype.

A guide for pastors and the small teams around them. Where AI genuinely lightens the load, where it has no business being, and the guardrails a church should insist on before anyone opens a chat window. No pitch — just what we'd tell a friend who leads a congregation.

Sunday is always coming

Most pastors didn't answer a call to run a small non-profit, but that's what the week looks like. The sermon, the people, and the admin all land on the same desk, and the admin never asks first.

01

The message

Study, prayer, outlining, illustrations, slides, the discussion guide for small groups. The one thing no one else can do for you, squeezed into whatever hours are left over.

02

The inbox nobody sees

The bulletin, the newsletter, event announcements, the website that's two months stale, volunteer schedules, thank-you notes, and the grant that's due Friday.

03

The people you carry

Hospital visits, the couple in crisis, the new family from last Sunday nobody followed up with, the volunteer who's quietly burning out. This is the calling. It's also what gets crowded out.

Where it genuinely helps

Think of it as a capable, tireless assistant who has read a lot but knows nothing about your people. Good at first drafts, summaries, and lists. Not a decision-maker, not a shepherd. Used that way, it gives hours back.

Administration & communications

The weekly load that isn't ministry, but has to get done.

This is the safest, highest-return place to start, because the stakes are low and the volume is high. Every one of these is a first draft you still read before it goes out.

  • Bulletin and announcement drafts from your notes
  • Newsletter first drafts, in your church's voice
  • Event copy written once, then reshaped for the website and social
  • Volunteer scheduling and reminder messages
  • New-visitor follow-up notes you review before they send
  • Donor thank-yous and grant-letter first drafts
  • Website updates: sermon pages, the calendar, staff bios
Rule of thumb: AI drafts, a person sends.
Study & sermon prep, under your authorship

A research assistant for the study, not a voice in the pulpit.

Used honestly, it works like a very fast commentary shelf and a patient conversation partner. The theology, the conviction, and the words you preach stay yours.

  • Background research and cross-references to check against trusted sources
  • Three outline shapes for a passage, so you can pick one, or none
  • Illustration ideas to vet, not stories to repeat as your own
  • Small-group discussion questions from your finished sermon
  • A midweek devotional or newsletter reflection from Sunday's message
You remain the author. Nothing goes out that you didn't shape and sign.

Where AI is not the answer

We'd rather lose a project than tell you AI belongs somewhere it doesn't. Here's where we'd ask you to keep it out. Not because the tools can't produce words, but because the words aren't the point.

✕ Keep this human
✕

The preached word

Research and outlines, yes. The sermon itself, what you believe, what you've wrestled with, what your people need to hear this week, is yours. Your congregation can tell.

✕

Pastoral care

Hospital rooms, funerals, the knock on the office door. No draft, no template, and no summary of a grieving person's situation fed into a tool.

✕

Counsel and confidentiality

What people tell you in confidence never gets typed into an AI tool, consumer or otherwise. Not to summarize it, not to "get advice."

✕

Theological and leadership decisions

It will give you a confident answer to anything, including things that are wrong. Doctrine, discipline, and direction belong to your leaders, the Word, and prayer.

✕

Member data without guardrails

Names, giving records, attendance, prayer requests. If it's in a spreadsheet, it doesn't get pasted into a free chat window. Ever.

✕

Anything you'd hesitate to explain

If you'd be uncomfortable telling the congregation how something was made, that's your answer. It's a good test for every use on this page.

Guardrails worth insisting on

None of this is complicated, but it has to be decided on purpose. These four are the ones we'd set up before a single volunteer logs in.

01
Guardrail · 01

No member data in consumer tools.

Free chat tools can use what you type to train their models. Church data belongs in accounts set up for an organization, with that switched off, and a short written rule everyone knows. For what it's worth, Nerdware doesn't use your data to train AI models either.

02
Guardrail · 02

Someone owns the accounts.

One admin structure, not six personal logins. Who can use which tool, for what, and what they can't paste in. When a volunteer rotates off, their access goes with them.

03
Guardrail · 03

It sounds like your church.

A newsletter that reads like a press release gets ignored. Give the tools your voice, your vocabulary, and your way of talking about faith, so drafts start close to right.

04
Guardrail · 04

Training, not just logins.

Most church AI efforts die in week three, when the one enthusiastic volunteer gets busy. A short, repeatable way to do the common tasks, written down, outlasts the enthusiasm.

Start small, and in the right order

You don't need a strategy. You need one task off your plate that's been there for a year. Pick it, set the guardrail, and judge it on a Tuesday afternoon instead of in a vendor demo.

We've built for church teams before, a discipleship-cohort platform (DiscipleLink) and the Engaging Heaven Church website, so we know what a volunteer-run Tuesday looks like.

01

Pick one task

The weekly bulletin, the newsletter, or visitor follow-up. Low stakes, high repetition, and a person still sends it. That's the first one.

02

Set the guardrail first

Decide what never goes in before anyone types anything. A one-page rule, in plain English, pinned where the volunteers can see it.

03

Widen only when it's earned

If it saved real hours for a month, add the next task. If it didn't, stop. Nothing on this page is mandatory. Stewardship is the measure.

If you'd like a hand setting it up right, that's The Backbone →

The questions pastors actually ask

Straight answers. If yours isn't here, send it through the contact page and a real person will reply.

Research, cross-references, and outline ideas are what commentaries and study Bibles have always given you. Using a faster one isn't cheating. Preaching words you didn't write, believe, or wrestle with is a different thing, and it was a problem long before AI. Keep the authorship yours, and tell your people how you study. Most congregations respect honesty far more than they fear tools.
It should never be pasted into a free consumer chat tool. Use accounts set up for an organization with training switched off, a written rule for what never goes in, and one admin who owns access. Nerdware doesn't use your data to train AI models, and we set up your tools so the vendors don't either.
Often it fits a volunteer-run church better than a staffed one, because the admin load is spread thin and that's exactly where volunteers burn out. The guardrail matters more, not less: a simple written rule and one owner. Start with a single repeated task a volunteer already does.
Honestly, the tool matters less than the setup. Any of the major assistants will draft a bulletin. What matters is an organization account, data controls, your voice loaded in, and someone who knows how to use it. We'll recommend specifics once we've seen how your week actually runs.
It will if you let it. Out of the box these tools write in a flat, slightly corporate register. The fix is to give them your vocabulary, your tone, and examples of your best newsletters, and to keep a person who edits before anything sends. Then it sounds like you, faster.
Yes. Event pages, sermon summaries, staff bios, and keeping the calendar current are low-risk, high-value uses. We built the Engaging Heaven Church site around the staff who keep it updated, and that's usually the real problem, not the design.
A conversation first. If AI isn't the right next step for your church, we'll say so. If it is, we get AI set up right with guardrails, put agents and skills in the hands of your non-technical team, build a shared knowledge base, and train people so it sticks: a short enablement sprint, then a monthly retainer. No church package, no pressure.

Want to talk it through?

Talk it through with usSee The Backbone