Questions church leaders ask.

Churches of every size and shape — from rural church plants of 80 to multi-site congregations of 8,000. The buyers are typically Senior or Executive Pastors, Church Administrators, Operations Directors, Treasurers, and the IT folks (often a tech-savvy elder) who help with the review.

If your church currently runs on spreadsheets, paper connect cards, an aging legacy ChMS, or a giving processor that doesn't talk to your member database — you're our buyer.

A standard onboarding takes 2–4 weeks end to end: tenant provisioning, campuses and ministries, staff and volunteer imports, people & family imports, giving history import, and online giving page setup. Pilots can be running in days.

You don't need to migrate everything before you go live. Most churches start with their highest-pain area — usually guest followup or online giving — and expand as the platform proves itself.

Yes. Most churches start with one area — usually First-Time Guest Followup or Online Giving — prove out the workflow in weeks, then bring on the rest. Ministries and campuses are first-class objects in the platform: each gets its own categories, journeys, staff, dashboards, and integrations.

There is no architectural penalty for adding more later. The data model is designed for it.

Yes — this is one of the things we built first, not last. Online giving is native to the platform: tithes, designated funds, recurring gifts, pledges, ACH and card. Donors manage their own accounts. Refunds, statements, and audit trail are built in.

Payment processing runs on a PCI-DSS compliant gateway. The platform never touches a card number directly — tokenized at the form, charged via the gateway. Year-end giving statements generate automatically.

Yes. The platform installs as a Progressive Web App on iOS, Android, Windows, and Mac — no app-store approval needed. Staff and volunteers can:

Take attendance, check kids in & out, confirm volunteer slots by SMS, log a pastoral visit, take a guest-card photo, and update statuses — all from a phone. Members see their own profile, family, giving history, and statements through the same web app.

Yes. We support three import paths:

CSV import: A guided importer with field mapping and validation. Common shapes (people, families, attendance, giving history, pledges, group rosters) are supported out of the box.
Direct from your current ChMS: We've migrated from the major legacy platforms — ask us what we've seen.
API: A documented REST API and inbound webhooks for systems that prefer programmatic onboarding.

AI calls are scoped to your church, rate-limited per user, and logged for audit. The Pastoral Assistant is read-only — it analyzes ministry data, it does not modify it. Only the prompt context required for the task is sent to the model, not your entire database.

Pastoral notes and confidential prayer requests are excluded from generic AI prompts. Individual donor giving amounts are excluded from comms drafting unless explicitly required. Your data is not used to train third-party models.

You can configure your own OpenAI key per tenant, or use ours. AI features can be disabled per-tenant if your elder board requires it. Full detail is on the Security & Stewardship page.

The integrations our churches use most often are in the box:

Email: Drop-in SMTP & transactional providers.
SMS: Twilio for guest journeys, volunteer confirmations, prayer chains.
Payments: PCI-DSS compliant processor for online giving, recurring gifts, ACH.
Calendar: Google Calendar, iCal feeds, Outlook.
Accounting: Export to QuickBooks, ChMS-style fund accounting native.
Notifications: Web Push (VAPID), email, daily digest.
Custom: Public REST API and inbound webhooks (API-key authenticated) for everything else.

Per-church pricing, not per-seat. Annual or monthly billing. Discounted tiers for church plants and small congregations. No-cost pilots are available for qualifying churches. Reach out and we'll send numbers tailored to your size and ministry mix.

Yes. Pastoral notes are role-gated — visible only to the care roles you authorize. Each read of a sensitive record is access-logged with user, time, and source. Pastoral notes are excluded from generic AI prompts unless explicitly requested by an authorized role.

Confidential prayer requests can be marked private or anonymous at submission. The platform was designed under the assumption that some things really are sacred.

Likely — ask us. We'll connect you to the closest comparable church in your size, region, and denominational mix.