Loading
Church scheduling and operations
Sunday morning has a lot of moving parts. This is where they live.
One directory, one roster system, one scheduling engine — behind serving teams, small groups, Bible classes, services, events and check-in. Build a team once and it is already an audience, a class register and a scheduling pool.
Flat pricing by the size of your congregation, with every module included. You are never billed per person, so a directory that remembers everyone who has ever visited costs the same as one that does not.
from $49a month, whole church16modules, all included9roles enforced server-side
Built once, used everywhere
Six things, built properly, instead of forty features
Most church software grows a separate roster for every feature that needs one — one for groups, another for teams, a third for classes, a fourth for mailing lists. Then a volunteer's phone number is right in three of them. These six are the whole system, and every module consumes them rather than keeping a copy.
Person
One directory record per human being. Every roster, assignment, check-in and message resolves to it, so no module keeps its own copy of a phone number to go stale.
Collective and membership
Teams, small groups, Bible classes and mailing lists are one thing with a type. Build a roster once and it is an audience, a class register and a scheduling pool.
Schedulable and assignment
One scheduling engine. A position on a service plan, a seat on a class rota and a slot at an event all invite, accept, decline and swap through the same flow.
Attendance
A record in its own right, not a by-product of a kiosk. A check-in station writes it, and so does a teacher marking a register or an usher counting heads.
The communication pipeline
Audience, template, channel, delivery log — in that order, every time. The in-app inbox is a channel on the same pipeline rather than a second system.
Files
One file service with real permissions, inherited from whatever the file is attached to. A background-check document is not readable by everyone who can see a lesson plan.
What a church gets
The modules your week actually runs on
All 13 advertised modules read real data today. The native apps, SMS and year-end statements still on the roadmap are named there rather than papered over here.
People and households
Available nowThe directory, with the family structures churches actually have — including a child who belongs to two households. Per-person privacy, duplicate detection, and a merge tool that repoints everything.
Services and scheduling
Available nowService types, plans, and the order of service. Assignments go out, volunteers accept or decline from a link with no login, and auto-fill respects blockouts, conflicts, and whose turn it is. The live orchestrator keeps the service moving from the booth.
Check-in and attendance
Available nowStation-based check-in with kids security codes, guardian pickup matching, classroom companion mode, parent pages on presenter screens, guest signup, and per-station questions — built so Sunday morning keeps moving.
Giving
Available nowFunds, batches and contributions on an offline ledger — envelope entry, soft credits, anonymous gifts — with person as the donor of record and household as the statement unit. Year-end tax statements come next on the same ledger.
Bible classes and curriculum
Available nowClass rosters, a versioned curriculum library, lesson schedules, and Promotion Sunday that previews every grade move before anyone clicks execute — including remapping children onto their next classroom.
Forms
Available nowA builder with conditional fields, public fill links protected by Turnstile, and submissions that match to existing people for review rather than silently creating duplicates. The same forms bind as check-in questions on a station.
Where the build is
You should know how early this is before you talk to us
This is a product under construction, and the plan is published rather than implied. Directory, scheduling, check-in, classes, forms, signage and the giving ledger already read real data. Phase 3 is still open for the offline web-kiosk queue and web-push delivery; the same table drives the app's own dashboard — so it cannot say one thing here and another once you are inside.
Scheduling coreTeams and positions, service plans, assignments, blockouts, iCal feeds.
Sunday morning opsCheck-in (stations, security codes, companion classrooms, parent pages, self-checkout, offline kiosk queue), events and recurrence, public forms, locations and floor plans, live order-of-service, and web-push delivery — all reading real data.
DepthSoftware half shipped: Bible class planner, curriculum library, Promotion Sunday, custom roles, whitelabel domains, form conditionals, label templates, print-job enqueue, per-station check-in questions, and Twilio SMS (refuse-until-configured). Still deferred: the iPad kiosk that drives label printers.
Tell us about your church
We are bringing churches on a few at a time, by hand, so that the first ones get the product built around what they actually do on a Sunday. Tell us your size and what you are running now, and we will tell you honestly whether this is ready for you yet.
No card, no trial clock, and no obligation — this is a conversation, not a checkout.