Use case · Sunday Services
Sunday's sermon shouldn't end at the door.
The weekly rhythm: record the service, upload after church, review the dubs, and publish — so by evening every member, present or absent, near or far, has the full message in their own language.
What churches do with it
Record what you already record
Phone, camera or soundboard audio — any file works, duration detected automatically.
Dub while you rest
Pick languages after lunch; the pipeline delivers review-ready tracks within hours.
Approve with confidence
Your reviewer reads and listens to every language before anyone else does.
Publish and notify
One publish updates your page and channels; one tap texts every opted-in member.
The muhubiri effect
Same day
turnaround
Morning service, evening multilingual library — every single week.
3-5
languages typical
Most congregations cover their whole membership with a handful of tongues.
~$1.50
per sermon-minute in 3 languages
A 30-minute sermon in three languages ≈ $45 — less than the tea budget.
The weekly loop, end to end
Upload → dub → review → publish
Four steps, one person, repeatable every week without heroics.
The library compounds
Every week adds to a searchable, multilingual archive your members revisit.
Members stay in the loop
SMS notifications turn 'did you watch?' into 'which language did you watch in?'
Make this Sunday the first
Upload one sermon; publish it in three languages by supper.
Preach in every language — from $9