Oviedo City Church
Oviedo, FL
Prepared by Ministry of Order for The Church Executive AI Workshop · June 4, 2026 · Orlando
In the room: Dr. Pete Geiger (Lead Pastor) and April Mae (Business Operations / Finance Director).
Where you're starting from
Oviedo City is finance-strong: you're bringing a dedicated Business Operations / Finance Director to the workshop. That's unusual and valuable — it means the financially-oriented builds have an immediate, capable owner in April, rather than landing on an already-stretched lead pastor. The recommendation leans into that strength: generosity analytics, the weekly operating picture, and facility economics.
Your recommended builds
1. Giving Pattern Analyzer — built for a finance director, governed carefully
Giving data carries early pastoral signal, but it's among the most sensitive data you hold. The right design — and the one this brief specifies — is aggregate trends shared broadly, plus a "households worth a pastoral check" list that goes to exactly two people and nowhere else. No AI ever touches donor data; the anomaly detection is plain statistics. April is exactly the right owner for this, with the governance guardrails built in. → Full brief: ideas/08-giving-pattern-analyzer.md
2. Church Operations Intelligence — the weekly picture
One dashboard fusing the six numbers leadership watches each week, with an AI-written Monday narrative. With a finance director on staff, the giving-vs-budget tile is already well-fed; this brings attendance, volunteers, guests, facility, and care alongside it. → Full brief: ideas/01-church-operations-intelligence.md
3. Facility Utilization Heatmap — turn empty rooms into dollars
The building is your largest line item after staff, and most rooms sit empty most of the week. This maps room-by-room utilization with a cost-per-hour overlay — reframing "we need more space" as "we need different scheduling." A natural fit for a finance-led team, and the lowest-sensitivity build in the set. → Full brief: ideas/12-facility-utilization-heatmap.md
4. Board Packet & Decision Memory — stop re-deciding
A light system for agendas, decision logs, and review reminders, so the board stops re-deciding the same thing every year. Mostly discipline plus a simple Airtable/Notion base; AI only drafts the quarterly brief. → Full brief: ideas/09-board-packet-decision-memory.md
Your 90-day path
| Quarter | Move |
|---|---|
| Q1 (0–90 days) | April stands up the Giving Pattern Analyzer's aggregate layer with the 2-person governance model agreed first. Begin the Operations Intelligence dashboard. |
| Q2 | Build the Facility Utilization Heatmap with a real cost basis. Add giving anomaly detection + the tightly-gated check-in list. |
| Q3 | Stand up Board Decision Memory; take the facility cost-per-used-hour findings into budget planning. |
The one rule that governs all of it
From the workshop's security model: donor giving is maximum-sensitivity — never put it into a consumer AI, and never let a lapsed-giver list become a fundraising or judgment tool. "Private, but not secret." Aggregates inform leadership; the named list reaches only two people. Build and demo on synthetic data.
Full idea library and the other churches' packets are on the Ministry of Order briefs hub.