Two services on one Sunday: how the hours add up

A second service doubles exactly one thing: the hours of live language going out. The transcript, the summary, the content pack, the follow-up list and the glossary do not double, and a team that produces them twice is doing a morning's work it never owed.

Here is the arithmetic, and then the part nobody tells you.

How is live translation actually counted?

The meter is a Live Language Hour: one hour of one language going out live. Listeners are not metered, and neither is anything read afterwards, so a service with eleven people listening in Farsi and a service with a hundred cost the same. The pricing page says it in one line, and it is worth reading literally, because the two words that matter are live and language.

One service, one hour, two languages is two Live Language Hours. Run it every Sunday and a month is about 8.7 - a little over four Sundays, not four. That sits inside Starter, which is €97 a month for 10 hours and up to two languages.

Now add the second service. Same hour, same two languages, at eleven instead of nine: two more hours every Sunday, about 17.4 a month. Starter's ten no longer covers it. The top-up is €25 for five more hours, so two blocks bring you to twenty hours for €147 a month. Growth is €247 for 35 hours and up to five languages; it is the right buy when you need the languages or the headroom, not when you need seven more hours.

If your second service is a different congregation rather than a repeat - a German service at nine and an international one at eleven, each translated into one language - that is one hour each, about 8.7 a month again, and you are back inside Starter.

We run four languages in a single service at our own church in Vienna. That is four Live Language Hours for one Sunday morning, which surprises people more than the second service does. The count follows languages far faster than it follows services.

Do you have to meter the whole service?

No, and this is where most of the saving is. You are metering the minutes the session is live, not the minutes the doors are open. A church that translates the sermon and leaves the songs alone runs a thirty-minute session, not a ninety-minute one, and halves the number above. We wrote separately about what to translate and what to leave alone; the short version is sermon yes, songs mostly no, announcements when they carry information somebody needs.

The hour that costs you is the one nobody closed. On a two-service Sunday the eleven o'clock session is the one still running at two in the afternoon, because the volunteer who opened it went to lunch and the volunteer who would have closed it was on the nine o'clock rota. Make ending the session somebody's named job, the same way locking the building is.

What should you reuse, and what genuinely has to happen twice?

If the same message is preached twice, one recording becomes the record. Decide before the morning which one - usually the second, when the preacher has found the rhythm - and the other is your backup, not a second job. From that one recording you get the clean transcript, the summary, the full message, a small-group guide and the drafts for blog, newsletter and social, in every language you serve. Running that pipeline twice gives you two near-identical newsletters and a Tuesday spent choosing between them.

The glossary genuinely does not double. Names, place names and the terms your church uses live in Church Memory, a person on your team approves each entry, and an approval made at nine is already right at eleven. Verse references and proper nouns are where every system slips, so the second service is the one that benefits from the first service's corrections.

The follow-up list does not double either. Two services means two after-service codes, but the prayer requests, the first-time-here cards, the testimonies and the questions asked through Ask the Sermon land in one list with one status per person. That matters more than it sounds: a visitor at nine and a visitor at eleven are two people your team has to contact this week, and a team looking at two lists contacts neither.

What does happen twice: the engagement in the room. Amen, first time here, prayer request and a word to the team belong to the people who were actually present, so each service gets its own code and its own responses. That is the point of them.

And if the two services carry different messages, you have two records, two content packs and two sets of drafts, because you preached two sermons. The saving is in repeats, not in volume.

What to do this Sunday

Count your own number before you look at a plan: services a week, minutes of translated speech in each, languages going out. Multiply, then multiply by 4.35, not by four. Most churches that think they need Growth need Starter and one top-up block, and most churches that ask what a second service costs are quietly asking whether their team can survive it. The honest answer is that the hours are the small part.

Then name the person who closes the session, and name the recording that counts. Those two decisions are worth more than any setting on the page.

If you want the per-Sunday version of this with the plan numbers worked through, we did that in what a translated service costs, Sunday by Sunday. And if you would rather see it run on your own service than read about it, a demo takes sixty minutes and uses your languages, not ours.

---

Further reading: what to expect from AI church translation and what AI tools do for a church across a whole Sunday.