Mosaic Church
Winter Garden, FL
Prepared by Ministry of Order for The Church Executive AI Workshop · June 4, 2026 · Orlando
In the room: Joel Coffman (Executive Pastor of Development) and Danny Volz (Administration).
Where you're starting from
Mosaic brings development-focused leadership and a dedicated administrator. Joel's mandate as XP of Development maps cleanly onto the builds that connect generosity, the weekly operating picture, and facility economics — and Danny is positioned to own the operational plumbing behind them. This set is chosen to serve a development XP: the numbers that inform growth, stewardship, and the use of resources.
Your recommended builds
1. Church Operations Intelligence — the weekly picture, with development in view
One dashboard for the six numbers leadership watches each week — attendance, giving vs. budget, volunteer fill, guest pipeline, facility load, care queue — plus an AI-written Monday narrative. For a development role, the giving-vs-budget and guest-pipeline tiles are the heartbeat; this puts them beside everything else on one page. → Full brief: ideas/01-church-operations-intelligence.md
2. Giving Pattern Analyzer — generosity insight, governed carefully
Directly in a development XP's wheelhouse — but built with the guardrails the brief specifies: aggregate trends shared broadly, plus a tiny "worth a pastoral check" list to exactly two people, no AI on donor data, anomaly detection by plain statistics. This gives you cohort retention and recurring-vs-one-time mix as stewardship insight — never as a pressure tool. → Full brief: ideas/08-giving-pattern-analyzer.md
3. Facility Utilization Heatmap — steward the second-biggest line item
Room-by-room, hour-by-hour utilization with a cost-per-hour overlay. Most church rooms sit empty most of the week; this turns that into a dollars conversation and a "repurpose or reschedule" recommendation. Lowest-sensitivity build in the set — a good one for Danny to run. → Full brief: ideas/12-facility-utilization-heatmap.md
4. Board Packet & Decision Memory — institutional memory
A light Airtable/Notion system for agendas, decision logs, and review reminders so the board stops re-deciding settled questions. With a 2009-tenured XP, Mosaic has institutional history worth capturing in a searchable form. → Full brief: ideas/09-board-packet-decision-memory.md
Your 90-day path
| Quarter | Move |
|---|---|
| Q1 (0–90 days) | Stand up the Operations Intelligence dashboard with the numbers you have clean. Agree the giving-analytics governance model (2-person rule) before building it. |
| Q2 | Build the Giving Pattern Analyzer's aggregate layer. Have Danny build the Facility Utilization Heatmap with a real cost basis. |
| Q3 | Add giving anomaly detection + the gated check-in list; stand up Board Decision Memory; take facility findings into 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; aggregate before analysis; keep the named check-in list to two people; "private, but not secret." Build and demo on synthetic data, never the real giving export.
Full idea library and the other churches' packets are on the Ministry of Order briefs hub.