Sermon Craft
How to Turn Your Sermon Into a Devotional and a Small-Group Guide
A pastor's guide to turning Sunday's sermon into a five-day devotional and a small-group discussion guide, with a worked example, question templates, and where AI helps or hurts.
Jon Horton · November 8, 2026 · 13 min read
It's Wednesday, 4:40 in the afternoon. Your phone buzzes. It's the couple who lead the small group on the east side of town. "Hey Pastor, what are we discussing tonight? Should we just do Sunday's sermon?"
You say yes. Of course you say yes. Then you realize they're going to stand in a living room in three hours with nothing but a fuzzy memory of a message you spent fourteen hours preparing.
That moment is where most sermons go to die. Not in the pulpit. In the week after.
This guide is about the week after. How to take one sermon and turn it into a five-day devotional your people can read on their own, and a small-group guide a volunteer can actually lead. Not more content. The same word, met again.
The seed on the path
Jesus told a story about a farmer who scattered seed. Some of it fell on the path, and before it could do anything, the birds came and ate it (Matthew 13:4). The seed was good. The sower was faithful. It just never got a second chance to go into the ground.
James says something similar about hearing without doing. It's like looking at your face in a mirror, walking away, and immediately forgetting what you look like (James 1:23-24).
Sunday is sowing. And sowing matters. But a sermon heard once and never touched again is seed on the path. By Tuesday, the birds have it.
That's the real reason to turn a sermon into a devotional or a discussion guide. You've probably heard it called repurposing, which makes it sound like content marketing. It isn't. It's giving the word a second and third chance to take root, in the quiet of someone's kitchen on Thursday morning and around a coffee table on Wednesday night.
Think about what that means in practice. The person who was distracted by a crying toddler during your second point gets to meet it again. The man who heard the application and felt a tug he didn't act on gets asked about it, by name, by people who love him. That's not marketing. That's discipleship.
Start with one sentence
Before you write a single devotional or discussion question, write your big idea at the top of a blank page. One sentence. The thing you'd want someone to say if a friend asked them, "What was the sermon about?"
Everything downstream flows from that sentence. The devotional is that sentence, slowed down across five days. The small-group guide is that sentence, tested against real lives. If you can't write it, no devotional format will save you, and you'll end up summarizing your outline instead of extending your message.
If the sentence won't come, that's worth knowing too. Here's how to find the big idea of a sermon before you preach it next time.
For the rest of this guide, I'll use one example. Say you preached Matthew 6:25-34, Jesus on worry. Your big idea:
Your Father already knows what you need, so you're free to seek His kingdom first.
Hold on to that. We'll build everything from it.
Part 1: Turning a sermon into a devotional
Simplify. Don't summarize.
This is the mistake almost everyone makes the first time. They take a 35-minute sermon and try to squeeze all of it into five short readings. Every point, every cross-reference, every illustration, compressed. The result reads like lecture notes, and nobody finishes Day 2.
A devotional isn't a shorter sermon. It's a slower one.
Your sermon had to move. It had thirty-some minutes to get a room full of people from the text to Monday. A devotional has the opposite job. It gets to sit with one thing at a time. So instead of asking "How do I fit everything in?", ask "What deserves a whole morning?"
A five-day shape that works
Here's a structure I'd start with. It isn't sacred. But it walks a reader from the text to their own life in a way that mirrors how the sermon worked, at a walking pace.
- Day 1: The text. Read the passage slowly. One observation they might have missed on Sunday.
- Day 2: The big idea. Your one sentence, unpacked. Why it's true, from the text itself.
- Day 3: The tension. The hard question the passage raises. Where it pushes back on us.
- Day 4: The picture. One illustration or story from the sermon, retold. Just one.
- Day 5: The response. What changes. A concrete step and a prayer.
Each day gets the same four parts:
- A short Scripture reading. Two to five verses, not the whole passage every day.
- A reflection. 150 to 250 words. Written to one person, not a crowd.
- One question. Not three. One they can actually sit with.
- One line of prayer. Something they can pray in their own words.
That's roughly a five-minute read. Long enough to matter. Short enough to finish before the coffee's ready.
What it looks like, worked out
Here's the skeleton for the Matthew 6 sermon:
Day 1: Look at the birds (Matthew 6:25-27). Jesus doesn't start with a command. He starts with an invitation to look. Most of us read past "look at the birds" as decoration. It isn't. It's the whole method. Question: When did you last stop long enough to notice something God is caring for?
Day 2: Your Father knows (Matthew 6:31-32). The big idea, slowed down. Worry assumes nobody's paying attention to what we need. Jesus says the opposite, and he says it twice. Question: What need are you carrying right now as if no one knows about it?
Day 3: The tension of tomorrow (Matthew 6:34). "Do not worry about tomorrow" can sound naive when the mortgage is due Friday. Name that honestly. Jesus isn't saying tomorrow won't have trouble. He says it will. Question: Which of tomorrow's troubles are you trying to carry today?
Day 4: The story. Retell the one illustration from Sunday that landed hardest. If you told a story about your grandmother's garden, tell it again here in three paragraphs, and stop.
Day 5: Seek first (Matthew 6:33). The response. Not "worry less," which no one has ever done on command, but "seek first," which is something a person can actually start tomorrow morning. Question: What would seeking His kingdom first look like in the first ten minutes of your day?
Notice what's missing. The word study on merimnaō you spent an hour on. Your second cross-reference. The joke that worked in the first service. All good things. They stayed on Sunday, where they belonged.
Write it while it's warm
The best time to write a sermon devotional is Monday morning. You know exactly what you meant. You remember which line made the room go quiet and which point you'd cut if you preached it again. By Thursday, you'll be in next week's text and this one will have cooled.
An hour on Monday is enough for five short days once you have the shape.
Part 2: Turning a sermon into a small-group guide
Why sermon-based groups work
There's a well-worn model here. Larry Osborne made the case for sermon-based small groups in Sticky Church, describing how North Coast Church built its groups around the weekend message instead of a separate curriculum. His point was that closing the back door of a church matters at least as much as opening the front one, and that people who talk through Sunday's sermon together on Wednesday tend to stick.
Whether or not you run your whole group ministry that way, the logic holds. A group discussing the sermon isn't starting from zero. The text has already been explained. The big idea has already been named. The group gets to spend its hour on the part a sermon can never do for anyone: what this means for me, here, this week.
The group isn't a rerun
This is where most sermon discussion guides go wrong. They walk back through the outline point by point. "In the first point, Pastor said... What did he mean?" That turns a living room into a quiz.
You already did the observation and interpretation work from the pulpit. One church's general sermon discussion guide says it well: most of that work is done by the pastor in the sermon, so the group is the place to go deep on application.
So give observation and interpretation a few minutes, enough to get the text back in the room. Then spend most of the hour on what difference it makes.
A guide a volunteer can lead
Here's a shape for a 60 to 75 minute group. Eight to twelve questions is plenty. You won't get to all of them, and that's a good sign.
- An opener (5 minutes). A question anyone can answer, about life, not the text. It gets people talking before it gets them thinking.
- Read the passage aloud. Every time. Even if they heard it Sunday.
- Two or three questions about the text. What do you notice? What surprised you? What does this tell us about God?
- Three or four application questions. This is the heart of it.
- One "this week" question. A specific next step, said out loud to people who'll ask about it next week.
- Prayer. Built from what came up, not a closing formality.
Then add a short leader's note at the top. One paragraph. Your big idea, what you'd love the group to walk away with, and anything sensitive to watch for. If you preached on worry, a group leader should know that someone in the room might be in a genuine crisis, and that "just trust God more" is not the response you're hoping they'll give.
Writing questions people will actually answer
The best discussion questions have more than one good answer. If a question has a right answer, it's a quiz, and the quietest person in the room will never risk getting it wrong.
Compare:
Weak: "What does Jesus tell us not to worry about in verse 25?"
Better: "Jesus mentions food and clothing. What would he name if he were talking to you this week?"
Weak: "Is worry a sin?"
Better: "Where's the line between responsible planning and the kind of worry Jesus is talking about? How do you know when you've crossed it?"
The better versions can't be answered from the page. They can only be answered from a life.
Here's a full set for the Matthew 6 sermon:
Opener: What's something you used to worry about that seems small now?
The text:
- Jesus tells us to "look at the birds" and "consider the lilies." Why do you think he points to creation instead of just giving a command?
- He mentions that our Father "knows that you need" these things. How does that change the way you hear "do not worry"?
Application:
- What's taking up the most worry space in your mind this week?
- Jesus says worry can't add a single hour to your life. Where have you seen that be true for you?
- What does "seek first the kingdom" look like on an ordinary Tuesday, not in theory but in your actual schedule?
- Who in your life seems to carry worry well? What do they do differently?
This week: What's one thing you'll hand to God each morning this week instead of carrying it yourself? Who here can ask you about it next week?
Part 3: The smaller extensions
A devotional and a group guide do most of the work. A few lighter touches help the sermon reach people who won't do either.
- A recap email or newsletter blurb. Three sentences and the big idea. Not a summary of the outline, an invitation to keep thinking. End with one question.
- A social post. One line from the sermon that stands on its own, plus the reference. Resist the urge to post five.
- Podcast or video show notes. The big idea, the passage, and two sentences on who this message is for.
If you want help producing these at scale, especially video clips, there are good tools built for exactly that. Here's an honest rundown of sermon repurposing tools and Pulpit AI alternatives, matched to the job each one does.
Where AI helps, and where it hurts
You can absolutely use AI to turn a sermon into a devotional or a discussion guide. Plenty of pastors already do. But it's worth knowing what you're handing off.
Most repurposing tools start from the recording. They transcribe Sunday's sermon, then rewrite it into new formats. That works, with one weakness: the tool is reconstructing your meaning from an audio file, the way a stranger in the back row would. It can grab a joke as if it were a point. It can miss the line you'd say was the whole sermon. And it will write in a confident, generic voice that sounds a lot like everyone else's devotional.
So whatever you use, read every line before it goes out. Your name is on it. Your people will hear it as you.
Here's where we land, and I'll say plainly it's our own tool, so weigh it accordingly. Sermons.app is an AI sermon coach, not a sermon generator. It asks you questions while you prepare, and you write the sermon. Because your thinking already lives in the app, the big idea you landed on, the illustrations you chose, the ones you cut, our repurposing works from your prep instead of a transcript. You get a devotional, a small-group guide, a newsletter blurb, an article, podcast notes, and social posts drafted from your own words, and every one is fully editable. You stay the author. Your sermons are yours, and they're never used to train any AI model. Repurposing lives on our Pastor Pro plan. You can see everything that's included.
But you don't need us to do any of this. The five-day shape and the question set above work just as well on a legal pad.
A few common questions
How long should a sermon devotional be? Aim for a five-minute read per day: a few verses, 150 to 250 words of reflection, one question, and a line of prayer. Five days is a good default for a weekly sermon.
Should small-group questions follow the sermon outline? Not point by point. Use the big idea as the spine and spend most of your questions on application. The sermon already explained the text.
How many discussion questions do I need? Eight to twelve for a 60-minute group. Plan for not reaching them all.
Who should write these, the pastor or a volunteer? Write at least the big idea and the leader's note yourself. A volunteer or staff member can shape the rest from there. They'll do it better with your one sentence in hand than with a sermon recording.
One step this Monday
The sermon you preach this Sunday deserves more than one hearing. Not because it needs more reach, but because the people who heard it need more than one chance to let it take root.
You don't have to build a whole system this week. Just do one thing. On Monday morning, write your big idea at the top of a blank page. Under it, write three questions a group could talk about for an hour. Then send it to one small-group leader before they have to text you on Wednesday afternoon.