Fewer dropped balls
Every recurring task has an owner, a due date and a backup, so nothing depends on one person's memory.
For churches & ministries
A church operating system for every ministry department
ChurchOS gives your staff and volunteers a clear playbook for each ministry — so visitors get followed up, volunteers know where to be, and fewer things fall through the cracks between Sundays.
Built by Foundation Stone Advisors for faith-based organizations. Works alongside the church software you already use.
[Image slot — hero, 4:5]Church staff and volunteers around a table planning the week. Use a client church's own photo, with permission.
What changes
Less scrambling. More ministry.
Most church friction isn't a people problem. It's a handoff problem — the step nobody owned, the email nobody sent. ChurchOS writes those steps down and keeps them moving.
Clear department playbooks
Each ministry gets a plain written guide: who does what, when, and what "done" looks like.
Staff and volunteers aligned
New volunteers onboard faster, and staff stop re-explaining the same thing every season.
Every visitor followed up
First-time guests get a consistent, personal next step — this week, not whenever someone remembers.
Every ministry department
One playbook per department. One way of working across all of them.
Start with the department that hurts most. Add the rest when you're ready. Every playbook follows the same simple shape:
Owner — who is responsible, and who covers when they're out.
Rhythm — what happens weekly, monthly and seasonally.
Handoffs — where work passes between people or teams.
Done — what a finished, healthy week looks like.
[Image slot — 4:3]Volunteers serving at a welcome table on a Sunday morning. Real client photo only, with permission.
Guest services & first impressions
Greeting, connection cards and a follow-up sequence every first-time guest receives.
Kids & students
Check-in, safety standards, volunteer rotations and parent communication.
Groups & discipleship
Launching groups, placing people and caring for group leaders.
Worship & production
Service planning, rehearsal rhythm and Sunday run-of-show.
Care & pastoral support
Prayer requests, hospital visits and meal trains that someone actually owns.
Outreach & missions
Serve days, partner relationships and how people sign up.
Communications
Announcements, the weekly email, the calendar and who approves what.
Finance & administration
Giving records, budgets, reimbursements and month-end close.
Facilities & operations
Room requests, maintenance and Sunday setup and teardown.
How it works
Start small. Fix one thing well. Then grow.
No big-bang software rollout. You begin with one focused project, see the difference, and decide what comes next.
Friction-removal project
We find the one area causing the most strain — often guest follow-up or volunteer scheduling — and fix it with a written playbook and simple workflows your team actually uses.
Every department
Extend the same playbook shape to each ministry, so the whole staff works from one shared rhythm instead of nine separate habits.
Ongoing care
Keep playbooks current as ministries change, and add experienced operations, finance, technology or communications leadership on a part-time basis when you need it.
Quiet help, not hype
People do ministry. The system handles the reminders.
Behind each playbook, simple automation can take care of routine work. It stays in the background, and your church decides what it does.
- Reminders and follow-upsThe welcome email, the volunteer reminder, the "did anyone call them?" nudge.
- Handoffs between teamsA connection card becomes a task for the right person automatically.
- You stay in controlNothing is automated without your approval, and pastoral care always stays personal.
- Keeps your current toolsChurchOS works alongside your church management software rather than replacing it.
“[Pastor testimonial placeholder — replace with a real, approved quote from a ChurchOS church before launch.]”— [Name, Role, Church — placeholder]
[Image slot — 16:11]A pastor in conversation with a congregant after a service. Real client photo only, with permission.
Why we call it an operating system
Built on a foundation that doesn't change.
A church runs three things at once — a calling, a culture and an operation. ChurchOS puts the operation in order so the other two have room to breathe.
Spirit
Calling
Your mission and vision, the reason the church exists before anything is measured.
Romans 8:16
Soul
Culture
How your team actually makes decisions and treats people, not just how it describes itself.
Romans 12:2
Body
Operation
Staff, volunteers, budget and buildings — held in trust and run with care. This is where ChurchOS works.
1 Corinthians 6:19
Questions churches ask
ChurchOS FAQ
Straight answers about what ChurchOS is, what it costs to start, and who is behind it. Still wondering? Book a call.
What is ChurchOS?
ChurchOS is a set of written playbooks and simple workflows for each ministry department in a church — guest services, kids, groups, worship, care, communications, finance and more. Each playbook says who owns what, what happens every week, and how handoffs work, so ministry doesn't depend on one person remembering everything. It is built and delivered by Foundation Stone Advisors (FSA) as part of the BibleOS family.
Who is ChurchOS for?
ChurchOS is for pastors, executive pastors and church administrators who feel the strain of things slipping between staff, volunteers and departments. It fits churches that have outgrown “everyone just knows” and want clear, repeatable ways of working without hiring a large operations team.
Does ChurchOS replace our church management software (ChMS)?
No. ChurchOS sits alongside the church management software you already use for people, giving and check-in. It defines how each department works and connects the steps between people and tools, so you get more out of the systems you already pay for instead of migrating to new ones.
Is ChurchOS an AI product?
ChurchOS is people-first. Its core is clear department playbooks written with your team. Where it helps, quiet automation handles routine work like reminders, follow-up emails and task handoffs, and your church decides what is automated. Pastoral care, discipleship and decisions stay with people.
How do churches get started?
Most churches start with a focused friction-removal project that fixes one painful area, such as visitor follow-up or volunteer scheduling. From there, churches can extend playbooks to every department and add ongoing support. Book a friction-removal call to scope the right first project.
Who is behind ChurchOS?
ChurchOS is built by Foundation Stone Advisors (FSA), a management consulting firm founded by Eric Jaffe that serves faith-based businesses, nonprofits and churches. FSA combines operations consulting with automation and its own business operating system platform, and can provide fractional operations, finance, technology and marketing leadership when a church needs it.
Why is it called an “operating system”?
Because a church, like a computer, runs best when everything rests on one stable core. In ChurchOS that core is Scripture and your church's calling; the playbooks are the everyday operation built on top of it. The name is a metaphor; the work itself is practical and plain.
The BibleOS family
One framework for churches, nonprofits and businesses.
ChurchOS shares its foundation with operating systems for faith-based nonprofits and businesses, all built and supported by Foundation Stone Advisors. See how UnifiedOS runs church operations.
ChurchOS
Department playbooks for churches and ministries.
You are hereFor nonprofitsCampaigns, volunteers, donors and outcomes for faith-based nonprofits.
Explore UnifiedOS →BusinessOSAn operating framework for faith-driven companies, from hiring to governance.
Explore BusinessOS →Foundation Stone AdvisorsThe consulting team behind every BibleOS product.
Visit FSA →Next step
Tell us where things keep slipping.
A short call to find your church's biggest point of friction and scope a focused first project. No software to buy up front, and no pressure.