ChurchOS · for church staff
One place where your staff runs its work — projects, requests, meetings, policies, training and the church calendar — so your church never has to buy Asana, Teamwork, Mailchimp, Ninety or a forms tool again.
The tools you keep stay connected. The ones you were paying for to fill the gap fold in.
The gap
Church management software is built for the congregation, and the best of it says so: no general ledger, no website builder, no church-wide chat, and — in its own words — no complex project management system. Approvals exist for booking a room and nothing else. There is no policy library, no meeting cadence and no view across ministries.
So churches fill the hole with texting, styled email, a project tool, staff chat and analytics — most of which never write back, so the same person lives in four places. A mid-size church easily spends hundreds to over a thousand dollars a month on that stack before seats and fees, and the cost that hurts more is double entry and reports nobody trusts.
Every competitor fights over the congregation side. Nobody claims the staff-operations layer. That is the room ChurchOS is built for.
Principles
Your stack
Every tool a church pays for lands in one of three lanes. The walkthrough does this with your actual list.
Collapse
The staff-side tools a church can stop paying for.
Connect
Tools that stay the system of record. ChurchOS reads them.
Leave alone
Congregant-facing products. Rebuilding them creates a second system of record.
Church-only
Every church runs an annual plan, a preaching calendar, a creative cycle that feeds it, and the care of its people. Church software holds the end result; project tools do not know what a sermon series is. ChurchOS runs the process.
One calendar made of layers — preaching, services, events, groups, classes, serve teams, missions, staff and facilities — each with an owner, rules and a deadline.
A series is a first-class object, not a folder of documents, and the preaching team plans it in the same meeting system the staff already runs on.
Every series and major event produces a creative package on a countdown — the church's busiest request queue, finally run like one.
Care and preaching on the same data the staff runs on, so the pastor and the team see one picture of the church.
Running today
Built on BusinessOS, the platform we run our own firm on, with the church pack on top: ministry vocabulary, department presets and church meeting rhythms.
The platform
One product with the church pack on top and your own tools switched on — so the work, the calendar and the measures all live in the same place.
Migration
Your old task tool is imported whole and synced nightly while teams cut over one at a time, then you cancel it. One-afternoon importers for Teamwork, Asana, Monday, ClickUp, Trello, Basecamp and Notion.
Work management
Timelines and dependencies, automation rules, approvals and proofing on real files, workload by person, time tracking, and guest access for volunteers and vendors.
Planning Center
Nightly Planning Center measures on every department dashboard, a people mirror so nobody is entered twice, and campaigns sent to your Planning Center lists.
Church rhythms
The master calendar and annual plan, Series Planner pushed into Services, a creative cycle that runs every series to a Sunday Ready finish, and the pastoral layer: Care Compass, Steward, Pulpit Library, Gift Mapping and Message Studio.
Connections
Budget-to-actual from QuickBooks or Aplos, Pushpay and Tithe.ly, events and ticketing, texting, background-check status, website forms, meeting transcripts, and notifications in Google Chat or Slack.
Your church
Every church starts from the same ChurchOS with its own mix switched on. Self-serve setup, a library of shareable ministry modules and templates, and a mobile app for staff.
Request a walkthrough
Forty-five minutes. We sort every subscription you pay for into collapse, connect or leave alone, and show you what Monday looks like in one place. If it is not a fit, we will say so on the call.
“To equip his people for works of service, so that the body of Christ may be built up.”
The staff is how a church equips. ChurchOS is how the staff runs.