I Was Terrified It Would Fail in Front of My Whole Church. It Didn't.

The story of building Kerygma, and the Sunday it finally went live.

There's a moment every church media person knows too well.

The preacher is in full flow. The Word is landing. Heaven feels close. And then it comes. "Turn with me to…" And your stomach drops. You're scrambling. Typing the reference. Hunting for the right translation. Praying the verse loads before the moment passes. And half the time, by the time it's on the screen, the preacher has already moved on, and the moment has moved with him.

I lived in that moment for years. And one day I decided I couldn't live in it anymore. So I built Kerygma to end it.

This is the whole story. The silent months, the failure that nearly buried me, the morning I almost walked away, and the Sunday it all finally came alive.

It started with a problem I couldn't unsee

I've spent a long time around church media. Cameras, slides, livestreams, the lot. And the thing that always broke the flow wasn't the technology failing. It was the gap. The gap between a preacher quoting Scripture and that Scripture landing on the screen where the congregation could hold it.

When it works, nobody notices. When it lags, everybody feels it. The atmosphere leaks. Hearts that were leaning in start to drift. And the media team feels it most of all, because they're the ones in the dark at the back, sweating, trying to keep pace with a Spirit-led message that never once read the run sheet.

I kept asking myself: why is this still done by hand? We carry phones that transcribe us in real time. We have machines that understand language. So why is a human still frantically typing "John 3:16" while the preacher is already three verses ahead?

I couldn't answer it. So I started building.

The idea was simple. Making it real almost broke me.

The concept is easy to say. Kerygma listens to your service, recognises when Scripture is being spoken, whether it's a clean reference like "Romans 8:28" or a verse the preacher is quoting from his heart, and puts that passage on screen, instantly. No typing. No scrambling. No gap.

Simple to say. Brutal to build.

Because human speech is gloriously messy. Preachers misquote chapter numbers. They paraphrase. They quote half a verse, preach for ten minutes, then finish it. They switch translations mid-breath. They say "the book of First John" and "one John" and "first epistle of John" and mean the same thing. A system that only understands perfectly-spoken references is useless the moment a real, living service begins.

I'll be honest with you about how badly the early days went, because the failures are the truest part of this story.

The version that put 49 wrong verses on screen

An early build of Kerygma had its first real test in a live service. I was so sure of it. I had given it everything.

It was a disaster.

It barely caught a single reference right, and instead it threw dozens of wrong verses on the screen. Flashing passages nobody had spoken, reacting to words that merely sounded like Scripture. If you'd been in that congregation, you'd have watched the screen flicker with verses from nowhere. I wanted the ground to open and take me.

That night I went home in silence and tore the whole thing down to nothing.

And I understood, finally, what I'd done wrong. I had tried to solve a holy, human, unpredictable problem with one clever trick, when what it really needed was several honest approaches working together, each one catching what the others missed.

The morning I almost walked away

Here's the part I've never said out loud until now.

For months after that, I built in silence. No announcements. No noise. Just me, late into the night, rebuilding something I believed God had put in front of me, with nobody watching and no promise it would ever work. There's a particular loneliness to building in the dark, pouring yourself into a thing the world doesn't yet know exists.

And then one ordinary morning, I came online and discovered I wasn't alone after all. Someone else was building the same thing. Out there. Already moving.

I can't fully describe what that did to me. Months of hidden labour, and the first sign from the outside world was this: you're too late, someone's ahead of you. Something in my chest just sank. I genuinely wanted to stop. To close the laptop, delete the folders, and let it go. What's the point now?

I sat with that for a while. And then a quieter thought rose up underneath the panic. I never started this to be first. I started it because I'd stood at the back of too many services watching the moment slip while the screen sat empty. I started it for the operator sweating in the dark. I started it because it felt like mine to build.

So I made a decision. I would stop looking sideways. I would stop measuring myself against anyone else. I would go quiet, keep my head down, and simply ship the best thing I possibly could. If I was going to be in this race, I'd run my own lane and let the work speak.

That decision saved Kerygma.

How it works now (the part for the curious)

What I rebuilt is a layered system. You don't need to understand the engineering to use Kerygma, but if you're the kind of media person who likes to know what's under the hood, here's the honest version.

Kerygma listens to the service and turns speech into text in real time. Then it passes that text through several layers of detection, one after another. The first layer catches the clean, obvious references. The next catches the messy, misspoken ones. Another matches paraphrased and quoted Scripture against the actual text of the Bible, even when the words aren't exact. And the final layer uses a language model that genuinely understands context, so it can tell the difference between a preacher talking about love and a preacher actually quoting 1 Corinthians 13.

Each layer is a safety net for the one before it. That's why Kerygma can keep up with a real, unscripted, Spirit-led message, and not just a rehearsed demo.

And here's a detail I'm quietly proud of. The AI runs on your own machine, not in some distant data centre. That means it's fast, it works even when the church wifi is having a bad day, and your services stay private. Nothing about your sermon is shipped off to a server somewhere.

It's also built to stand alongside the tools you already trust, not replace them. If your team runs ProPresenter or something like it, Kerygma works with your setup. Your operator stays in control. They just stop having to scramble.

The Sunday it finally came alive

So there I was again. Live service. Kerygma running. And I won't pretend I was calm. I was afraid. You don't forget a failure like the one I'd had. I stood at the back braced for the screen to start flashing nonsense in front of the whole house.

It didn't.

The preacher quoted a verse, and Kerygma had it ready before my hand even reached the keyboard. He referenced another passage, and it was simply there. Clean, correct, present. At one point it surfaced a Scripture I hadn't even caught the preacher quoting. It was faster than I'd dared to imagine, and it caught more than I'd planned for.

I stood in the back of that room and felt something rise up in me. Not pride in the technology, but awe at what the technology served. The gap was gone. The flow held. The congregation stayed in the moment, hearts undistracted. Months in the dark, a public humiliation, a morning I nearly quit. All of it had quietly become this.

Sometimes the thing you almost gave up on is the very thing you were made to finish.

Where Kerygma is now

Since that Sunday, Kerygma has gone from a thing I built alone in my room to something running in real churches. My own church, WCI Southport, runs it live. Other churches are trialling it now, putting it through the fire of their own services, which is exactly what I want, because a real service is the only honest test there is.

And this is the part I care about most. I don't want you to take my word for any of it. I want your media team to run it during a real message and see for themselves whether the gap disappears.

If your media team is tired of scrambling

Kerygma is live now at kerygma.dev.

If you've ever watched your operator sweat through a sermon trying to keep verses on the screen, or if you've been that operator, I built this for you. There's a free way to try it, and paid plans for churches that want the full power of live detection running every single service.

Try it for one service. That's all I ask. See if it changes the way your Sunday feels.

And if it does, I'd love to hear from you. This whole journey began because I couldn't unsee a problem in church media, and the sweetest part of building it has been hearing from others who've been standing in that same frustrating moment, waiting and praying for someone to fix it.

We're only just getting started.

— David (Bob) Ukonu, founder of Kerygma