The accusation comes up fast.
"That's computerized plagiarism." "You're outsourcing the work God called you to do." "Your congregation deserves a pastor, not a machine."
I heard versions of all three this week in a UMC clergy group online. And I want to give them a real answer.
Start with the plagiarism question, because it's the most serious one.
Here's the question I asked back: what's your take on using Bible commentaries and other preaching resources to integrate ideas someone else had first? Where do we draw the line on what constitutes plagiarism and what is thoughtful integration?
Nobody calls Matthew Henry a plagiarist for writing a commentary. Nobody accuses the pastor who reads Craddock or Brueggemann and works their insight into a sermon of stealing. The tradition of pastoral study is built on standing in the stream of theological thinking that came before you — reading widely, wrestling honestly, and letting what you find shape what you say.
AI is trained on human creativity. It models human language, human reasoning, human theological reflection. Using it is not categorically different from reading a commentary. The question is the same question it's always been: are you thinking for yourself, or are you letting someone else do the thinking and calling it yours?
That's the real line. Not the tool. The posture.
There is a version of AI sermon prep that is plagiarism.
You open ChatGPT, type your scripture reference, and paste the output into your notes. You stand up Sunday and deliver it. Your congregation listens to a sermon written by a language model for a generic pastor about a generic text. They don't know. You do.
That's the hollow version. I've been there. It feels wrong because it is wrong. Not because the tool wrote it — because you handed the most important work over to a machine and called it good enough.
There is also a version of AI sermon prep that is the opposite.
You sit down with the text. You open a coaching tool. It asks you questions instead of handing you answers. What's the tension in this passage? What does your congregation actually believe that the text is about to challenge? Where are you in this story?
You answer honestly. The coach pushes back on the vague answers. You go deeper. You name the thing you didn't want to name.
That's not plagiarism. That's study. The sermon that comes out the other side is yours — built from your thinking, your wrestling, your congregation's particular grief and hope and stubbornness.
The environmental question is harder and I want to be honest about it.
AI energy use is real. Data centers consume electricity at scale. Choosing to use AI-based tools is a decision that has environmental weight, and dismissing that concern is not something I'm willing to do.
What I'd say is this: the question isn't whether AI uses energy. The question is what it's being used to do. Research tools, medical diagnostics, agricultural modeling — these are uses worth the cost. A pastor using a coaching tool to think more carefully about a sermon they're going to preach anyway seems to me a reasonable use. But I hold that lightly. If someone tells me they've made a different calculation, I respect it.
The deeper question underneath all of this:
Is AI replacing the preacher?
No. It can't. The sermon I preached last Sunday at Jacksonville First — about a grain of wheat falling to the ground and dying — came from a farm I had to let go, a hospitalization, a month in a camper with nothing left to hold onto. No AI built that. No AI could. It came from a life.
What SermonCoach does is ask the questions that push me back toward that life. Back toward the specific person, the specific moment, the specific thing I know is true that the congregation needs to hear. It doesn't replace the preacher. It makes the preacher go deeper.
That's the distinction worth making.
SermonCoach is a Socratic coaching tool for sermon prep. It doesn't write your sermon. It asks questions until you write it yourself. First three sermons are free — try it here.