GBIBEC—ChurchOperationsPlatform

A church operations platform: a public portal with seven forms, a 22-page admin behind it, four containerised sync services, and an AI layer that transcribes sermons, summarises them, and publishes the result. Everything a volunteer team would otherwise do by hand on a Sunday evening.

The work is weekly and the people are volunteers. A sermon has to be captured, transcribed, summarised, turned into a post and pushed to the site and to Instagram; a service needs its songs found, its lyrics fetched and its slides built; forms need collecting and reporting. Done manually that is hours every week, it slips the moment someone is away, and the congregation's questions go unanswered because nobody has time to answer them twice.

Each of those became a pipeline rather than a task. Sermon capture starts with the stream and stopping it triggers the summary, which can be regenerated, combined with manual notes, or handed to a notetaker — then a publish chain pushes it to the news section without retyping. Posters and post copy are generated and the images adjusted in place. A Pinecone-backed RAG chat answers congregation questions and logs every question it could not answer, so the gaps are visible rather than lost. The song library fetches lyrics, searches the web and segments them into verses, then exports service slides to PowerPoint. The syncs — YouTube live, YouTube sermons, Instagram — run as Cloud Run Jobs on Cloud Scheduler, and the embedding service runs ONNX Runtime rather than PyTorch because it is roughly a tenth of the image size.

One portal and four services now carry the weekly cycle. Over sixty API routes sit behind seven public forms and a 22-page admin, and the parts that used to be somebody's evening — transcribe, summarise, post, sync — happen on a schedule whether anyone is available or not.