Victory Vida Church
One platform for every member, leader and Sunday
Victory Vida Church is a Hispanic congregation in Lawrenceville, Georgia, in metro Atlanta, led by senior pastors Emilio and Luisita Schumann. Since December 2025 WebMinds has been its engineering partner: we built Vida Home, the members’ app and the staff’s back office, and rebuilt victoryvida.com so it stays current on its own. AI drafts the Sunday message page from the livestream for the team to review, the weekly newsletter drafts itself, and events, groups and teams flow from the app to the website in real time. Ten systems in production, run by a church staff with no IT department.
Duration
Ongoing since December 2025
Started
December 3, 2025
Including 12 scheduled engines that run reminders, reconciliation, syncs and the Sunday pipeline
Staff, small-group and ministry-team leaders, members and visitors, each with role-based access
Migrated with 301 redirects; every Sunday Gemini drafts the new message from the livestream for the team to review
Segmented by role, with two-way replies between leaders and members
Victory Vida ran on scattered tools, and every Sunday its website lost the previous message.
An AI content prototype, a separate form for every event, sermon series built by hand as WordPress pages, a newsletter assembled by hand and text messages that reported as sent but never arrived left a small pastoral and administrative staff doing the work of a systems team.
- — A small staff doing systems work · small groups, ministry teams, events, payments and communication lived in spreadsheets, forms and chats, and someone had to rebuild the website by hand every week
- — Content that got lost · the site overwrote each Sunday’s message, series pages were copies of each other with repeated episodes, and there was no searchable sermon archive
- — Communication without guarantees · one email provider with no backup, text messages failing silently, and no recorded express consent or suppression list that the server would respect
- — Security inherited from a prototype · gaps from the original prototype had to be closed before the platform could take payments and hold member data with confidence
We built one serverless platform on Firebase and Vercel and turned the WordPress website into a client of that platform, so every person has one account and every piece of information is entered once.
- + Vida Home · a multi-role app for members, leaders and staff: a spiritual portal with Bible reader, audio devotionals and prayer journal, small groups run by seasons, ministry teams with service calendars, and onboarding per role
- + Events and ticketing · a public page per event with its own look, Square checkout without login that cannot double-charge and is reconciled every 30 minutes, shareable tickets, door check-in and automatic day-before reminders
- + Sunday-to-web AI pipeline · Gemini watches the Sunday livestream and drafts the message page in WordPress, with summary, key points, verses and small-group questions, for the team to review and publish
- + A self-updating website · victoryvida.com with editable sections, events, groups and teams read live from the app, a searchable archive of 66 messages in 11 series, structured SEO and llms.txt for AI search engines
- + Communications backbone · transactional email with a backup provider, SMS on an approved 10DLC campaign with express consent, a weekly newsletter that drafts itself and event contacts synced to FluentCRM
- + AI where it helps the ministry · content assistant for announcements and social posts, event pages filled in with AI, SMS rewritten for compliance, and a 40-day devotional narrated in the senior pastor’s own cloned voice, with permission
Inside the build.
Brand, interface and system — shown as they shipped.
It looks like an app and a website.
Underneath is a backend-heavy serverless platform: cloud functions, scheduled engines, database triggers, security rules on every collection, payment reconciliation, inbound webhooks and a WordPress site that reads from the platform through its own REST routes. AI drafts, people decide: nothing generated by AI is published without a human.
Payments that cannot double-charge
The idempotency key is born in the browser and reused on every retry, ambiguous errors stay retryable, and a reconciler resolves them every 30 minutes with the same stored data. Seats are reserved atomically and released if the charge fails.
An hour-long video as AI input
The Sunday pipeline picks the right livestream between two services, skips failed or short streams and keeps state per Sunday so nothing is drafted twice. It runs on its own every Sunday afternoon and Monday.
Consent as a rule, not a checkbox
The SMS audience is only members who opted in themselves; an admin can revoke consent but never grant it. New CRM contacts arrive tagged by event, and unsubscribes are never reactivated.
Failures that are no longer silent
Messages that looked sent but never arrived led to delivery receipts, per-provider logs and email that retries on a second provider when the first one fails.
Inherited security gaps closed
Payment and email keys moved server-side and rotated, the password-reset flow hardened, rate limits on public checkout, registration, ticket sharing and password reset, audited sign-in as another user, two-factor sign-in by email and AI calls through an authenticated server proxy.
Hybrid AI Coding
Senior WebMinds engineering owned the architecture and every decision with the church, while AI coding agents implemented and independent QA reviewed every sensitive change: 597 commits over 84 working days, about 95% co-written with AI agents.
Technologies & Tools
The tech stack powering this solution
Beyond the numbers, we delivered a system that transformed how this client operates.
A church website that keeps itself current
The Sunday message goes from livestream to a draft page that the team only reviews and publishes. Series are no longer overwritten: 66 messages in 11 series are searchable, and redirects preserve every old URL for search.
One platform instead of a dozen tools
Members, leaders and staff use one account for groups, teams, events, tickets, devotionals and messages, and the website reads live from the app, so nothing is updated twice. 440 members, 56 small groups, 24 ministry teams and more than 19,000 notifications.
Enterprise-grade plumbing for a church staff
Idempotent, reconciled payments, email with a backup provider, consented SMS on an approved 10DLC campaign, rate limits and security rules on 71 collections, operated by a pastoral team, not an IT department.
- Dec 2025First commit: an AI content prototype becomes a production codebase
- Jan 2026Intensive build: multiple roles, onboarding per role, two-factor sign-in, small groups by season, ministry teams, dynamic QR codes, event registration, SMS and the Bible reader
- Feb 2026Event capacity and real payments with Square through cloud functions
- Mar – Apr 2026SMS consent and an EN/ES switch for 10DLC registration; audio devotionals with daily notifications; pastoral care and first-time visitor follow-up
- May 2026VidaGol: registration, funnel, tickets and check-in for a community sports event
- Sep 2026SMS rebuilt on the server with delivery receipts, inbox and suppression list; 10DLC campaign active
- Oct 2026Email with a backup provider, public ticket checkout, the redesigned victoryvida.com with 66 messages migrated, the self-drafting newsletter and door check-in
- NextThe next phase, in planning with the church
Ready to achieve similar results?
Let's discuss how we can transform your business with a tailored digital solution.