Is Church Translation Software Worth It? An ROI Answer for Small Churches

Picture a sixty-person church in a market town. Two Polish families started coming eight months ago. Nobody on staff speaks Polish. The question that comes up at the leadership meeting isn't "should we get translation software," it's "can we justify spending anything at all on two families out of sixty?"

That's a fair question, and most articles about church translation software dodge it by assuming the answer is always yes. It isn't always yes. This one works through the actual maths, including the cases where the honest answer is "don't bother yet."

Full disclosure: I built Voco, one of the tools that fits this exact situation. I'll tell you plainly where it doesn't make sense too. Prices checked August 2026.

The small-church objection

"We only have two Spanish speakers" is the objection I hear most, and it's usually said a little defensively, as if needing translation for a small number of people is somehow less legitimate than needing it for a large number. It isn't. The objection is really pointing at cost-per-person, and that's worth answering directly rather than dismissing.

What it actually costs per person reached

At Voco's Church plan, £12/week plus VAT is roughly £624 a year. Split across two Spanish speakers who attend most weeks, that's £312 per person per year, or about £6 per person per week. Split across a full congregation of sixty who all benefit from the option existing (visitors, hard-of-hearing members who prefer reading captions, that one grandparent who's never quite mastered English after forty years), the number drops to about £10 per person per year.

Compare that to a paid human interpreter at UK rates (roughly £45/hour, minimum call-out of two to three hours), which for the same two Spanish speakers works out to £4,420-£8,840 a year for one language, or £2,210-£4,420 per person per year. The AI subscription is somewhere between 7 and 14 times cheaper per person reached, for a smaller number of languages served by the human option and a much larger number served by software (Voco covers 50+ simultaneously; a paid interpreter covers exactly one).

That doesn't make the human interpreter the wrong choice. It might still be the better choice for those two families specifically, if the relationship and warmth matters more than breadth of coverage. It just means the cost-per-person argument against software doesn't actually hold up once you do the sum.

What one welcomed family is worth

This is harder to put a number on honestly, so let's try both ways.

Not in money: a family who understands the sermon, the announcements, the prayer requests, week after week, is a family who can actually belong. They can serve on a rota. They can bring a friend. Their kids can explain what they heard to their grandparents over Sunday lunch instead of translating on the fly themselves, which is its own quiet burden lifted (this comes up constantly in refugee and immigrant ministry writing: kids doing real-time translation for parents is exhausting and role-inverting for a child). A family that stays is a family that eventually gives, serves, and invites others. None of that starts if they can't understand what's happening in the room.

In money, if you want it: UK church giving research broadly suggests regular attenders who become members give meaningfully more than occasional visitors. Even a modest per-household annual gift from one retained family, compounded over several years, comfortably exceeds a year of software cost. This isn't a precise figure and I won't pretend it is. But directionally, retaining even one household pays for the tool many times over, on giving alone, without counting anything else a family contributes.

When it's genuinely NOT worth it

Here's the part most vendor content skips, and it's the part that actually makes the rest of this believable.

• A genuinely monolingual congregation with no visitors. If nobody in your building, ever, speaks anything but English, and you get essentially no first-time visitors from other language backgrounds, there's no problem to solve. Don't buy a solution looking for a problem.
• You've got one family, they're fluent enough to manage, and they've told you they don't want it. Ask before you assume. Some bilingual families genuinely prefer to follow along in English as part of language-learning or simply don't want the visibility of being "the ones who need the phone." Their preference matters more than your instinct to help.
• Your real barrier is welcome, not language. Translation software doesn't fix a congregation that doesn't make eye contact with visitors, doesn't invite people to lunch, or treats non-English speakers as a project rather than people. Fix that first. Software on top of a cold welcome just gives people a very clear translated understanding of how unwelcome they feel.
• You genuinely can't run the tech. If there's no reliable wifi, no one willing to own the five-minute weekly setup, and no realistic path to fixing that soon, it will fail quietly and nobody will use it, which is worse than not having it.

Being honest about these is what should make you trust the rest of this piece more, not less.

Give it a month before you commit

If you're on the fence, don't commit to a year. Give it a month:

1. Week 1: Set it up once, test the audio, and quietly tell the two or three families who'd benefit that it exists. Don't announce it church-wide yet.
2. Week 2: Ask directly: did it help? Was the accuracy good enough? Was the QR code easy to find and use?
3. Week 3: Announce it more broadly (bulletin, screen slide) and see if anyone else picks it up who you didn't expect: visitors, hard-of-hearing members, anyone.
4. Week 4: Decide, with real usage data instead of a guess, whether to commit.

Voco's 7-day free trial gives full access to the Church tier with no card required, which covers the whole of week one for free. See the comparison built specifically for small churches and the FAQ if you're weighing this up, and start the trial here when you're ready to run the test properly.

The size of the room has never really been the point. This works in a small group as well as it works in a main service. A phone on a table in a Farsi prayer meeting. Somebody speaking Portuguese in a Portuguese group. A midweek gathering where two people need it and nobody else does.

It is not only for the church with a dozen languages on a Sunday morning. Two people who can follow properly, instead of nodding along and catching a third of it, is worth six pounds a week on its own.

The maths says it's cheap. Whether it's worth it depends on whether you've actually got someone to reach. Most small churches that ask the question already know they do.

Frequently asked questions

What should churches know about the small-church objection?

"We only have two Spanish speakers" is the objection I hear most, and it's usually said a little defensively, as if needing translation for a small number of people is somehow less legitimate than needing it for a large number. It isn't. The objection is really pointing at cost-per-person, and that's worth answering directly rather than dismissing.

What should churches know about what it actually costs per person reached?

At Voco's Church plan, £12/week plus VAT is roughly £624 a year. Split across two Spanish speakers who attend most weeks, that's £312 per person per year, or about £6 per person per week. Split across a full congregation of sixty who all benefit from the option existing (visitors, hard-of-hearing members who prefer reading captions, that one grandparent who's never quite mastered English after forty years), the number drops to about £10 per person per year.

What should churches know about what one welcomed family is worth?

This is harder to put a number on honestly, so let's try both ways.

What should churches know about when it's genuinely not worth it?

Here's the part most vendor content skips, and it's the part that actually makes the rest of this believable.

First published on Medium.