Discovery · 60 minutes
We choose one workflow, the first three screens, the data path, and what success looks like. The clock starts when access and sample data are ready.
Custom Church Dashboard
A custom church dashboard you own—and know how to keep building.
We choose one important workflow, build a focused first version, and put the code and controls in your church’s hands. After one discovery call and one hands-on handoff, your team can make safe changes, ship improvements, and add features with AI—without waiting on a developer for every idea. Just as important, they learn a repeatable way to turn ideas into safe, tested improvements with AI agents—a skill set that will grow more valuable as agents become part of everyday work.
Quoted after discovery based on workflow, data, and custom features · focused builds usually take 2–3 weeks after access is ready
Working dashboard + source codeChurch-owned accountsSafe-edit + rollback playbook
What it can look like
A clear view of the work your team is already doing.
These fictional dashboards use synthetic data. They show the kind of dashboard a church can grow into—not a promise that every module shown is included in the focused first version.
Sample Church Hub
Last 13 weeksOverview
Weekly trend
Attendance momentum
This period
Highlights
47first-time guests
31next steps
82Church Health
Sample Church Hub
Last 13 weeksAttendance
Weekly trend
Attendance and guests
AttendanceGuests
Average mix
Attendance categories
Adults68%
Kids18%
Youth8%
Online6%
Sample Church Hub
Last 13 weeksEngagement
Participation
Engagement distribution
Worship86%
Groups62%
Serving41%
Giving58%
Next steps36%
Aggregate view
Engagement segments
SegmentPeopleSignal
Highly engaged724Growing
Connected986Steady
At risk408Needs attention
The process
Two calls. One focused build. A valuable new capability on your team.
I build the framework
I design, build, test, and deploy the focused first version. You get concise async updates without another calendar full of meetings.
Handoff · 90 minutes
Your staff owner makes a real change, verifies it, deploys it, and rehearses a rollback. You leave with the code, the accounts, and a safe way to keep improving it.
More than a dashboard
Your team leaves with a new way to build.
The dashboard solves the first problem. The handoff teaches a repeatable loop your staff can use again: define the outcome, ask an AI agent to plan a small change, review the work, test it, deploy it, and know when to roll back or escalate. That skill travels to the next report, workflow, or ministry idea.
Shape the idea
Turn “I wish this did…” into one small change with a clear outcome and definition of done.
Build with an agent
Give the agent the right context and guardrails, then review the plan and the actual changes instead of blindly accepting them.
Ship it safely
Test before release, deploy through version control, roll back when needed, and escalate work that touches data, access, or infrastructure.
Focused by design
Enough to solve one real problem—and a foundation you can grow.
Included in your dashboard build
- One core workflow and up to three core screens
- One approved data path
- Your church’s brand and a production deployment
- Source code and production accounts owned by your church
- A repo guide that teaches your AI assistant the safety rules
- Discovery, hands-on handoff, rollback rehearsal, and 14 days of support
Safe ownership
Ownership without pretending every change is low-risk.
Your staff can handle the everyday improvements. The handoff also makes the red lines explicit.
Safe for your team
- Copy and labels
- Colors and layout
- Filters and existing metric settings
- New pages that follow an approved pattern
- Normal deploys and rollbacks
Bring in Ryan or a developer
- Database migrations
- Authentication and roles
- Secrets and environment variables
- Production integrations and webhooks
- Personal or financial data exports
- Destructive changes and major upgrades
Fit and ownership
Questions churches ask before they build.
Do we need a developer on staff?
No. You need one curious, dependable staff owner who can follow the playbook and knows when to escalate a high-risk change.
Is this the full analytics platform in the example?
No. The example shows the design ceiling. A focused first version starts with one workflow and up to three screens; additional modules are phased and priced separately.
What do we own?
Your church owns the source code, data, and production accounts. Optional office hours or Care are available, but ownership is not tied to an ongoing retainer.
What if we just want turnkey church analytics?
Church Pulse is the managed option for standard Planning Center analytics. A Custom Church Dashboard is for one workflow your church wants to own and extend.
What skill will our team learn?
A repeatable AI-assisted building loop: define a small outcome, give an agent context and guardrails, review what it proposes and changes, test it, deploy or roll back, and escalate high-risk work. The same loop applies to future reports, workflows, and ministry ideas.
Can you keep building it for us?
Yes. Additional modules can be fixed-scope follow-ons, or Ryan can own the ongoing roadmap inside a fractional engagement.
Honest boundaries
What a dashboard can decide — and what it can't.
A dashboard earns its keep by showing the right numbers sooner. It does not replace the conversation those numbers are supposed to start.
Questions it answers well
- Which ministry's attendance is actually growing when the total looks flat
- Whether giving households are shrinking behind a healthy dollar total
- Which budget lines are running hot before year-end makes it a crisis
- Which volunteers are quietly serving three-plus times a month and heading for burnout
- Whether second-time guests are returning — the number that measures the church, not the reach
Questions that stay with leadership
- Why a trend is happening — numbers start the conversation; they don't finish it
- Pastoral judgment calls — no chart should decide how you shepherd a person
- Data hygiene — a dashboard on top of messy check-ins reports messy check-ins faster
- Priorities — leadership still chooses what to act on; the dashboard just ends the guessing
Where the data comes from
Built on the systems you already run.
These are generic examples of the kinds of sources a focused dashboard reads — Discovery confirms your church's actual data path. (The example dashboards above use synthetic data.)
Church management system
Attendance, check-ins, groups, and volunteer scheduling from tools like a ChMS export or API — typically the richest source for people-side metrics.
Giving platform
Gifts and giving-household counts. Connected read-only, so the dashboard can show trends without ever touching the money itself.
Accounting ledger
Budget-vs-actual by category from your ledger's reports. This is how over-budget lines surface monthly instead of at year-end.
The spreadsheet someone maintains by hand
Every church has one. Often the first win is simply replacing the weekly copy-paste ritual with a screen that's already current.
Deciding what belongs on the first screen? Read the church dashboard KPI guide and the numbers every church should watch weekly. For the wider operating picture, see the church operations guide — or explore the rest of the free tools.
Start with the one screen your team wishes it had.
Bring the workflow that lives in a spreadsheet, a weekly report, or one person’s head. We’ll decide whether a focused church-owned dashboard is the right answer.