For two years, the conversation about AI in the church sounded like a debate. Should we use it? Is it safe? Does it belong anywhere near ministry? That debate is mostly over, and the numbers from this fall make it official.
A 2026 report found that more than nine in ten church leaders are now using or actively exploring AI, with only a small fraction avoiding it entirely. Close to half reach for it every day. The hesitation of a couple of years ago has quietly become ordinary habit.
So the interesting question is no longer whether AI belongs in the church. It's the one researcher Kenny Jahng named alongside that report: how do we use it well? That one is harder, and it doesn't come with a settings page.
Adoption was the easy part
Adopting a tool takes an afternoon. Deciding what it's for takes honesty.
Here's the gap worth sitting with. A separate study this fall found that most churches describe their technology as support for communication or efficiency, while only about 9% say its main purpose is discipleship. At the same time, a clear majority agree that technology plays an important role in deepening faith. We believe in what it could do for ministry, and we mostly use it to send email faster.
That isn't a failure of tools. It's a question of purpose that got skipped on the way to adoption. The new divide between churches isn't digital, between those who use technology and those who don't. It's missional, between those who know what their tools are for and those who collected them without asking.
The habit worth building: name what it's for
The fix is smaller than a strategy document. Before you add any tool, feature, or AI shortcut, say out loud what it's for and who it's meant to serve.
"We're adding this so a first-time guest can find service times in under ten seconds." That's a clear purpose, and you'll know whether it worked. "We're adding this because everyone else has it" is not a purpose, and it's how a church ends up with five logins and no idea which one helps anyone.
This one habit does quiet work. It keeps your tech stack honest, it makes the next decision easier, and it protects the parts of ministry that were never supposed to be automated in the first place.
Where this shows up on your website
Your website is where these choices become visible to the public. AI can draft your about page, write your welcome message, and answer questions in a chat box. The question is never whether it can. It's whether this particular page should carry your actual voice or a convincing imitation of it.
A reasonable rule: let AI carry the scaffolding, and keep your voice on the pages where a real person is listening for you. The welcome, the story of why your church exists, the note that greets a grieving visitor. Those earn a human.
It's worth knowing that nearly half of church leaders haven't told their congregation they use AI at all. We'd gently suggest the opposite instinct. When a tool serves a clear purpose you can name, you rarely feel the need to hide it.
Start with one honest list
You don't need a committee this week. Sit down with your team and look at the tools you already use. For each one, write a single sentence: this is for this, so that this person can do this.
The tools that survive that sentence are keepers. The ones that don't are the clutter you've been maintaining out of habit. Naming the purpose is most of the work, and it turns a vague sense of "we should probably do something about AI" into something your whole team can actually act on.
If you'd like help thinking through where AI and automation fit on your church's website without crowding out the human part, we'd be glad to talk it over. Reach out at developwithfaith.com/contact.