Turn One Sermon Into a Month of Small Group Content

Sermon-based small groups are the most popular model in the American church and the least resourced.

The logic is obvious: the whole church hears the same message Sunday, then goes deeper on it midweek. Alignment, reinforcement, one teaching thread running through the body. It works.

The execution is where it falls apart. Somebody has to write the discussion guide. That somebody is almost always the person who just spent fifteen hours preparing the sermon, and it's now Monday, and next Sunday is coming.

So one of three things happens. The guide gets written at 10pm Wednesday and it shows. Or leaders get sent a generic curriculum that has nothing to do with what was preached, which quietly kills the alignment the model existed for. Or leaders are told to "just discuss the sermon," which means twelve groups have twelve completely different conversations and three of them go somewhere nobody intended.

With fall launch about six weeks out, this is the problem to solve in August — before the groups start, not during.

What One Sermon Actually Contains

A thirty-five minute message is a substantial piece of content. Preached well, it contains:

• A biblical text, opened and explained
• A central claim
• Two to four supporting movements
• Illustrations and stories
• Objections raised and answered
• Application
• A call to respond

That is enough raw material for far more than one discussion. The material is already there. What's missing is the time to reshape it.

Here is what one sermon can become.

Asset 1: The Small Group Discussion Guide

The core deliverable. A good one has a specific shape, and most bad ones fail by being a list of comprehension questions about the sermon rather than an actual conversation.

Opening question (5 min). Low stakes, no Bible knowledge required, connected to the theme. The purpose is to get every voice in the room making sound before anything difficult is asked. A group where three people have already spoken behaves completely differently than one where nobody has.

Read the text together (5 min). Not the sermon — the passage. The group should encounter Scripture directly, not only through the summary of it.

Observation questions (10 min). What does the text actually say? This is where groups build the habit of looking before concluding. Two or three questions.

Interpretation questions (15 min). What does it mean? Where does the tension sit? This is where the sermon's supporting movements become questions rather than statements.

Application questions (15 min). What does this ask of us? Specific beats general every time. "Where in your week does this actually collide with something?" produces real conversation; "how can we apply this?" produces silence.

One commitment and prayer (10 min). Something nameable that someone will do before the group meets again, and prayer that arises from what was just discussed rather than a general request round.

Leader notes. Separate section: what the hard question in this passage is, where groups typically get stuck, what to do if nobody talks, and what's out of scope for this week.

That last piece is the one most often missing and the one volunteer leaders need most.

Asset 2: A Five-Day Devotional

The same sermon, broken into five short daily readings for the week following. Each day: a short passage, three or four paragraphs of reflection drawn from the message, and one question.

This is the asset that extends the sermon's shelf life past Tuesday. It also gives you something to send by email or text that isn't a promotion — which is rare and disproportionately valued.

Structure that works: Day 1 revisits the main text. Days 2 through 4 take one supporting movement each. Day 5 goes to application and prepares people for the following Sunday.

Asset 3: Leader Prep Notes

Distinct from the discussion guide. This is for the leader before the meeting: a summary of where the sermon went, the two or three questions likely to come up that the guide doesn't cover, the answers your church would give, and a clear note about what to escalate to a pastor rather than handle in the room.

That last part matters more than it gets credit for. Volunteer leaders are not trying to freelance theology — they end up doing it because nobody told them where the edges were.

Asset 4: The Questions the Sermon Raised

Every sermon raises questions it doesn't have time to answer. Sometimes people ask them. More often they don't, and go looking on their own.

Write those down. Four or five per message. Then answer them — briefly, in your church's actual position, not a general Christian one. These become website content, FAQ entries, follow-up email material, and answers your team can send when the question surfaces later.

Over a year this quietly becomes one of the most valuable teaching assets your church owns, because it's organized around what people actually wondered rather than what you planned to cover.

Asset 5: Follow-Up and Next Steps

One short email or text tied to the message, with one clear action. Join a group. Read this passage. Have this conversation with someone. Sign up for the class the series points toward.

Sermon series usually have a next step embedded in them. It rarely gets named.

Asset 6: Pull Quotes and Social Text

Four to six lines from the message worth repeating, written to stand alone. Not for vanity metrics — for the person who missed Sunday, and for the member who wants to send something to a friend and needs it to be shareable.

The Workflow

You can do all of this manually. Here's the honest version of what it takes:

1. Get a transcript of the sermon. Most churches already have video; transcription is cheap or free.
2. Read it and mark the structure — main claim, movements, illustrations, applications.
3. Draft the discussion guide against the shape above.
4. Split the movements into five devotional days.
5. Write leader notes for the two hardest moments in the passage.
6. List the unanswered questions.
7. Pull the quotable lines.

That's a solid two to four hours per sermon for someone who knows what they're doing. Times a twelve-week fall series, that's a part-time job nobody on your staff has room for. Which is exactly why it doesn't happen.

Two things compress it dramatically:

Delegate it. This work does not require ordination. It requires someone who knows your church, can write clearly, and will run the output past a pastor. A capable volunteer or lay leader can own this entirely.

Draft it from the sermon automatically. This is where an AI guide trained on your own teaching earns its place — not writing your sermon, but reshaping the sermon you already preached into the formats your groups need. Your content, your voice, your positions, in a different container.

The Non-Negotiable: Somebody Reviews It

Whatever produces the first draft — a volunteer, a tool, a staff member — a pastor reads it before it reaches leaders.

Not because the draft will be wrong. Usually it won't be. But a discussion guide going to twelve group leaders carries your church's teaching authority into twelve rooms you won't be in. Ten minutes of review is a small price for that.

Build the review step into the process from day one. A workflow that assumes review is fast. A workflow that adds it later never quite does.

What to Do in August

If your groups launch in September, here's a realistic pre-launch target:

• Weeks 1–2: Decide the fall series and lock the passages. Everything downstream depends on this.
• Week 2: Define your discussion guide template once, so every week's guide has the same shape and leaders stop having to re-learn the format.
• Weeks 3–4: Build the first four weeks of guides in advance. Four weeks of runway is the difference between a fall that feels prepared and one that feels like it's chasing you from mid-September onward.
• Week 4: Get the guides into leaders' hands before the first meeting, not the morning of. Walk them through the format at your leader training.

Four weeks ahead is the number. Groups that launch with four weeks banked usually stay ahead all season. Groups that launch with one week banked are behind by the third week and never recover.

One Sermon, Reused Honestly

None of this is about producing more content. Volume is not the problem — most churches are already producing more good teaching than they distribute.

The problem is that a sermon has one delivery and then stops working. The same forty minutes of preparation could be resourcing a small group on Wednesday, a devotional on Thursday morning, and a question someone types into your website at 11pm on Saturday.

The work is already done. It just needs more containers.

Bonfire pulls in your sermons, videos, and documents and generates study guides, devotionals, and discussion questions grounded in what you actually taught — in your voice, with your positions, ready for a pastor to review. One pastor described it as finally being able to hand a deacon the material to lead midweek discipleship without adding to his own week.

Start free

Try it on last Sunday's sermon.