← All posts · July 24, 2026

The real cost of letting a sermon die on Sunday

Michael Tuszynski

Founder, Church Media Squad

A sermon works hard for one hour

Your pastor spent 10 to 15 hours this week on that message. Studying the text, wrestling with the application, writing and rewriting until it said what it needed to say. That's real time, and it went somewhere real.

Then Sunday happened. The sermon reached the room. Everyone in the seats heard it once, and for most of them, that was the only time they'd hear it at all.

That hour doesn't reach the family that missed church for a soccer tournament. It doesn't reach the guy who's been meaning to visit but hasn't yet. It doesn't reach the members scrolling their phones on Tuesday, looking for something worth stopping for. It doesn't reach anyone outside that building on that day.

Ten to fifteen hours of preparation, and the message touches one room, one time. Everyone else who could have heard it never does, unless somebody turns it into something they can find later.

The six hours nobody budgeted for

That "somebody" is usually you. And turning a sermon into a week of content by hand is not a quick task. It's a real project with real steps.

You pull the audio or video. You find the quotable moment, the one line that will actually stop someone's scroll. You cut a clip, or if you can't cut video, you write around it instead. You draft captions for however many platforms your church actually uses. You build a graphic, or ask someone else to, and then wait. You write the email newsletter blurb. Maybe you pull together a discussion guide for small groups, if anyone's going to use it.

Add it up honestly and you're looking at about 6 hours. Every week. Not once. Every week, for as long as your church keeps preaching sermons, which is to say forever.

Six hours a week comes to roughly 300 hours a year. That's not a rounding error in a comms director's schedule. That's close to two full months of full-time work, spent entirely on rebuilding content that already exists, instead of creating anything new.

And that time was supposed to go somewhere else. It was supposed to go toward the events calendar nobody's updated since spring. Toward the welcome sequence for new members that's been "in progress" for a year. Toward actually planning next quarter instead of reacting to this week. Toward things that only you can do, because turning one file into five different posts isn't actually one of them.

The quiet feed teaches people something

The part that's easy to miss doesn't show up on a spreadsheet.

When your church's feed goes quiet Monday through Saturday, you're not just missing an opportunity. You're sending a message, whether you mean to or not. The message is: this church speaks once a week, on Sunday, and otherwise has nothing to say.

People learn that. They stop checking. They stop expecting anything between Sundays, and eventually they stop expecting much from Sunday either, because a place that only shows up once a week starts to feel optional the other six days.

Compare that to a church whose feed has something worth seeing on Tuesday. A clip from the sermon. A question for reflection. A line that stuck with someone. It doesn't have to be constant. It has to be present. Presence is what tells people the church is a place that's thinking about them outside the building, not just waiting for them to show up again.

That's the compounding cost of letting a sermon die on Sunday. It's not just the content you lost. It's the six days of silence that follow it, week after week, quietly teaching your congregation to expect less.

Run the math on your own church

Grab a piece of paper. This takes two minutes and it's worth doing before you decide whether any of this matters for your church specifically.

Start with sermons. Most churches preach about 50 a year. Multiply that by the 10 to 15 hours your pastor spends preparing each one, and you get 500 to 750 hours of pastoral work every year, that reaches the room exactly once per sermon and then stops.

Now look at reach. Write down your average Sunday attendance. Then write down your total following across every platform your church actually posts to. For most churches, the second number is bigger, sometimes two or three times bigger, because it includes past members, extended family, former visitors, and people who found you online and never walked in.

That gap is the point. Your sermon already has an audience larger than your sanctuary. It's just not getting the content that audience would actually see.

Last step. Take one sermon from this year and ask honestly: where did it go after Sunday? If the answer is nowhere, that's not a one-time miss. That's the pattern, every week, for every sermon on your calendar this year.

Why this doesn't get fixed

None of this is a mystery to church staff. Most comms directors already know the sermon should live longer than one service. The problem isn't awareness. It's that the fix keeps losing to everything else on the calendar.

Turning a sermon into a week of content isn't anyone's whole job. It's a slice of somebody's job, usually the same person who's also running the website, printing the bulletin, and managing three social accounts by themselves. When Monday morning arrives with an event to promote and a graphic that's due, the sermon from yesterday quietly moves to the bottom of the list. The urgent always beats the important, and the sermon is important, not urgent, so it loses most weeks.

Hiring your way out of it doesn't pencil out either. A part-time content person runs well over a thousand dollars a month in most markets, and a full-time one runs several times that. Six hours a week is 24 hours a month, so buying that time back for $97 comes to about $4.04 an hour, which no hire comes close to. Most churches this size can't justify a new position to solve a six-hour-a-week problem, even though the problem is real.

So the job often lands on a volunteer instead. Someone who loves the church and says yes the first few times, then starts missing weeks once the season gets busy, then stops showing up to the task altogether. Nobody blames them. Six hours a week, unpaid, indefinitely, was never a sustainable ask in the first place.

That's why this doesn't get fixed by trying harder or asking someone to care more. It gets fixed by making the work take six minutes instead of six hours.

The sermon deserved better than one hour

There's a simple idea underneath all of this. A message that reached people on Sunday should keep reaching them all week. It shouldn't die because one person on staff ran out of hours to give it.

The pastor didn't put in 10 to 15 hours so the message could live for 60 minutes and then disappear. The message deserves to keep going after the service ends. That's not a marketing problem. It's just letting the sermon do the rest of the work it was already capable of doing.

What to say to whoever holds the card

If you're the one doing the six hours but not the one who approves the spending, here's the sentence to forward:

"There's a tool that turns Sunday's sermon into a full week of posts, graphics, and writing in a few minutes. It's $97 a month, saves me about 6 hours a week, and the first sermon's free so we can see it before we pay a thing."

That's the whole pitch. No card required to try it, no risk in asking. Whoever holds the budget can see the actual output before deciding anything.

How Extend the Sermon fits in

Extend the Sermon takes the sermon you already recorded and turns it into 14 to 18 finished pieces, clips, social posts, a blog, a discussion guide, an email draft, in 20 to 50 minutes. You upload the file or paste a link, and you get back a week's worth of content built from what your pastor already said, in the voice your church already uses.

It's $97 a month for one sermon a week, and $40 a month for each additional sermon after that. That works out to about $24 per sermon at one a week, or about $14 if you preach four. Cancel anytime. The first sermon is free, no card needed, so you can see exactly what comes back before anyone has to approve a line item.

Everything we make is yours to post, send, and keep.

If you want to see the process end to end, read how Extend the Sermon works. If you'd rather just see it work on your own sermon, that's faster.

Get your free sermon