The only AI sermon tool built for mainline pastors

Your sermon stays yours.
Saturday can too.

Sermon Helper handles the bulletin liturgy, the music director's hymn list, the children's moment, the daily devotionals, and the pre-Sunday Bible study — work that wasn't going to get done anyway. Built on the Book of Common Worship by a Stated Clerk. Free for Peaks pastors during the 2026 beta.

Why we built this

Your congregation will never tell you.
Your sermons will.

The congregation is too kind. The elders are too political. Your spouse is too close. The presbytery colleague hears you preach once a year. So pastors drift — same six texts, the same illustration for the fifth time, lament missing while the congregation buries members. The first time most pastors hear what was actually happening in their preaching is on sabbatical, six years too late.

Sermon Helper reads your full sermon archive and gives you the report a sabbatical would. What you preach too often. What you've never preached. The illustrations you keep falling back on. The themes your congregation needs that you haven't gotten to. Free with every account.

"ChatGPT does not love my people."

— Rev. Dr. Andy Morgan, First Presbyterian Church Knoxville (PCUSA)

He's right. ChatGPT doesn't love your people either. Cold AI sounds evangelical-flavored, hallucinates verses, gives you generic boilerplate where you need full Great Thanksgiving. That's because every other AI sermon tool was built for non-denominational, evangelical, or Baptist preaching — with a denomination dropdown bolted on later.

Sermon Helper is the first one built for mainline pastors as the default. Trained on the Book of Common Worship. Lectionary-aware. Knows your hymnal. Reformed sacramental theology baked in, not retrofitted. Magisterium did this for Catholic. Nobody had done it for the rest of us. Now somebody has.

The week we know about

Three things every mainline pastor recognizes
but doesn't say out loud.

Saturday isn't yours anymore

You're physically in the room while writing the bulletin Friday at 9. Your spouse asked when you were going to be present this weekend. The kids stopped asking if you'd be at the soccer game. "Single parent with a roommate" is what one pastor's wife called the marriage during prep weeks. It's not nothing.

Your music director is frustrated

She needs the hymn list four to six weeks out so anthems get rehearsed and soloists prepare. She gets it Wednesday for Sunday. Or you get a tune that sounded fine on the page and bombs in the room, and you're frustrated. The relationship is a low-grade fire that gets worse every Lent.

You tried ChatGPT. It lacked a soul.

That's not our line — it's a quote, the most-repeated descriptor of AI sermons among preachers. "Generic and a little bit eerie" is the runner-up. You closed the tab. Then read in CT that 64% of pastors are using it now and wondered if you're the holdout.

What we don't do

We don't write your sermon.
We write the work around it.

Brad East said the drudgery is part of the point. Chip Hardwick called sermon prep "part of the magic that God works in us as we preach." They're right. Sermon writing is formation, not a chore to be optimized.

So we don't touch it. Sermon Helper handles the bulletin liturgy, the music director's hymn list, the children's moment, the daily devotionals, the social meditations, and the post-Sunday cascade — the derivative work that wasn't getting done anyway. There's also a 7-phase prep pipeline if you want it (research help, outline options, illustration ideas) — but Phase 4 is your turn, and Phase 7 lets you write the sermon yourself if you want. The drudgery stays sacred. The work around it doesn't have to.

Preaching Insights Report

What every pastor learns on sabbatical —
without taking one.

Upload your archive once. Sermon Helper reads every sermon and gives you the kind of read you can only get when someone reviews three years of your preaching at once. Free with every plan.

"You've cited Paul four times more than the Gospels."

Self-image vs. corpus reality. Most preachers think they preach broader than they do. The data nearly always disagrees.

"You've used the rock-climbing illustration four times in 18 months."

Cosine-similarity clustering catches recycled stories. Tells you what to retire.

"You've preached lament three times in 142 sermons."

Theme gaps surfaced against your archive plus a Reformed coverage frame. Honest, not judgmental.

Plus a Preaching Plan output: a 13-week forward calendar with text + theme suggestions that close the gaps the report surfaced, a list of biblical books and themes you haven't preached on, and a few series ideas. Run on 30+ sermons. Regenerate any time.

The work around the sermon

One Sunday in.
A week of ministry out.

Pre-Sunday (generated Mon–Tue)

  • Bible study — one 60–75 min Wednesday session
  • Bulletin liturgy — full BCW set, Great Thanksgiving on communion Sundays
  • Music director handoff — hymn picks against your hymnal, familiar-tune substitutions (HYFRYDOL, NETTLETON)
  • Children's moment — full script, prop list, anticipated kid questions
  • Daily devotionals — six (Mon–Sat) walking the congregation toward Sunday
  • Social meditations + brand-colored visual cards
  • Newsletter article + email teaser + slide outline

Post-Sunday (generated Mon–Tue after preaching)

  • Blog post — web-optimized adaptation, not transcript
  • YouTube metadata + chapter markers + thumbnail prompt
  • 3–5 short-form clips with timestamps, hooks, captions
  • Four staggered social follow-ups (day-of, day-after, mid-week, week-later)
  • Pull-quote graphics — ready-to-post 1080×1080 cards, brand-colored
  • Searchable archive entry with your "what worked" notes

Series-level (occasional)

Series arc check, graphic concept, confirmation/youth tie-in, end-of-series Bible-study booklet.

The lines we don't cross

Pastor approves first.
Always.

  • Nothing auto-publishes. No "post to Facebook on Sunday" button. Outputs land in files; you decide what goes live.
  • Hallucination flags on every claim. Bible verses, illustrations, attributions — tagged verified or needs pastor verification. Especially Scripture. Especially Brueggemann.
  • We don't store raw archives. We extract metadata for the Insights Report, then discard the originals. The work-product (cascade outputs, profiles) is yours to export anytime.
  • Counseling and session deliberations are off-limits. The product is forbidden from generating content involving them. Hard line.
  • Your sermons don't train someone else's chatbot. Paid AI tiers (Anthropic Claude, xAI Grok), no training on traffic.
The 2026 beta

Free for Peaks pastors
while we tune it.

Built by Pastor Dave Baker, Stated Clerk of the Presbytery of the Peaks (M.Div. Princeton Theological Seminary), for the pastors he sees every month. Free during the beta — full pipeline, no card, no contract. Tell us what's wrong; we'll fix it before public launch.

Pastors outside Peaks: a few testers from neighboring presbyteries are being invited. Email Pastor Dave to be considered.

Real obstacles. Real answers.

The questions every workshop gets.

Is using AI for any of this cheating?

An "eager but sometimes mistaken intern" is the framing pastors keep landing on, and we'd agree. The sermon is yours; AI handles the derivative work. If you opt into the prep pipeline, AI is a research assistant and outline architect — but Phase 4 is pastor-input-only, and Phase 7 lets you write the manuscript yourself if you want.

I tried ChatGPT once. It was bad.

Most pastors have. Cold ChatGPT has nothing to work with. Sermon Helper starts with your sermon archive, your church website, and a 90-minute onboarding conversation that builds two profiles. The first cascade you run already sounds like you preaching to your people. The difference between cold-prompting and profile-aware is the difference between generic Reformed boilerplate and a sermon for this congregation on this Sunday.

What about pastoral care and confidential matters?

Sermon Helper is forbidden from generating content involving counseling, specific members with sensitive details, or session deliberations. We're a pastor-led product — this is a hard line, not a feature flag.

What denominations are supported?

Default is PCUSA, with bulletin liturgy trained on the Book of Common Worship. UMC, Episcopal, ELCA, RCA, ECO, EPC, ACNA, evangelical Presbyterian all supported. Non-mainline (SBC, Pentecostal, non-denominational) works, but onboarding takes a longer conversation about worship culture.

My sermon archive is a mess.

Typical case. .docx, .pdf, .txt, .md all supported. Upload everything you have — even with inconsistent filenames, even scanned. Date-uncertain sermons get flagged so you can fix dates inline. The Insights Report works on whatever you've got; the more you upload, the sharper it gets.

How is this different from Pulpit AI / Sermon Shots / Sermonary?

Three things. Mainline by default — we're the only one. The others are evangelical-coded with denomination dropdowns. Real BCW liturgy — full Great Thanksgiving, not vague evangelical fragments. Honest archive feedback — the Insights Report is unique to Sermon Helper. No competitor reads your full archive and tells you what you've been preaching too much, what you're missing, or what illustrations you've recycled.

One sermon in

A week of ministry
out.

Sign in to the beta and run a cascade on this week's sermon. Or schedule a 20-minute demo and we'll run one on a sermon from your archive. No card. No pitch. Just the pipeline running on real text.