Resource Review10 min read

ChurchStats

4.0Editor rating

A flexible church-health analytics layer for custom ministry, campus, preacher, weather, and digital metrics—easy to understand and broad in scope, but priced from $409 monthly and dependent on disciplined manual entry, metric definitions, and privacy controls.

Starting price
$409/month
Free tier
No
Platforms
Web · Mobile browser · YouTube/social analytics beta
Developer
Everprise PTY LTD
Launched
2023
Updated
Aug 9, 2026
30 daysTrial
$409/monthStarter
$589/monthGrowth
$879/monthAdvanced
$45–$65/monthExtra campus
8–60Team members/campus
2–15Social accounts/campus

The verdict

ChurchStats is a serious, configurable reporting layer for churches that want a shared view of attendance, baptisms, groups, giving, volunteers, next steps, preacher patterns, weather, and digital activity without replacing their church-management system. Flexible metrics and campus filters are useful; the $409 monthly floor is the major constraint. Run the full 30-day trial, define every metric before entering it, reconcile a representative history, and calculate whether better decisions justify at least $4,908 per year. Use aggregate data whenever possible and ask how analytics and machine-learning uses affect your congregation’s records.

Try ChurchStats

Opens churchstats.com

ChurchStats is a church-health analytics platform operated by Australian company Everprise PTY LTD and associated with founder Leio McLaren. It launched publicly around 2023 with a straightforward premise: most churches collect ministry information in spreadsheets, church-management systems, giving tools, social platforms, and weekly reports, but leadership lacks one configurable view of the trends. ChurchStats does not claim to replace Planning Center, Elvanto, or another ChMS; its FAQ positions the product as a complementary analytics layer.

Churches can define custom metrics and display live dashboards filtered by ministry, campus, date, event, pastor, series, and other dimensions. Example measures include attendance, baptisms, salvation or faith-response counts, first-time visitors, children, youth, small groups, giving, volunteers, cars, growth-track steps, Alpha participation, studies, families, signups, and next steps. Preacher Stats can compare patterns associated with speakers, and weather context can help interpret unusual attendance. A Digital Church beta brings YouTube and social account information into the same environment.

The published pricing is substantially higher than the simple data-entry interface may suggest. Starter costs $409 per month, includes eight team members and two social accounts per campus, and charges $45 monthly for each additional campus. Growth is $589, includes 25 members and five social accounts, and adds campuses at $55. Advanced is $879, includes 60 members and 15 social accounts, and adds campuses at $65. Custom plans are available. The site advertises a one-month or 30-day free trial without a credit card, migration help, training, encryption, and backups.

We reviewed the current home, feature, price, FAQ, privacy, and editorial pages. We did not open a trial, migrate church history, validate dashboard calculations, connect social accounts, test permissions or backup restore, obtain an annual quote, inspect a security package, or interview a customer. The public blog contains limited older launch-era material, so this evaluation relies mainly on the live product and policy pages. Claims about quick setup, outcomes, security, and recommendations remain vendor claims unless separately verified.

✓ The good

  • Custom metrics - churches can track the ministry measures they actually use rather than accepting a fixed vendor scorecard
  • Cross-ministry dashboard - attendance, groups, giving, visitors, next steps, volunteers, youth, children, and other domains can share one view
  • Useful filters - campus, ministry, date, event, pastor, and series dimensions can expose patterns hidden in aggregate totals
  • ChMS complement - the product does not require replacing the operational people system
  • Preacher and weather context - unusual explanatory dimensions can prevent shallow week-to-week interpretation
  • Digital Church beta - YouTube and social analytics can connect online activity with other leadership reporting
  • Generous trial - 30 days without a card is enough to test a normal reporting cycle
  • Migration and training support - the company recognizes that historical setup and staff adoption require help

✗ Watch out

  • Expensive entry - Starter is $409 monthly or $4,908 annually before additional campuses
  • Manual workflow burden - the FAQ emphasizes data input and migration help rather than broad automatic ChMS synchronization
  • Definition risk - flexible metrics can produce impressive but incomparable numbers when campuses or staff count differently
  • Spiritual reductionism - salvation, discipleship, generosity, and pastoral health cannot be represented faithfully by a KPI alone
  • Privacy policy allows model use - collected data may support machine-learning analytics and recommendations, requiring careful scope review
  • Limited current public proof - few recent case studies, release notes, benchmarks, or detailed implementation stories are prominent
  • Security assurance is general - encryption and backups are claimed, but no public SOC 2 or ISO certification surfaced in review
  • Digital features are beta - social data access, limits, API continuity, definitions, and accuracy may change

Best for

  • Midsize and larger churches with several ministries or campuses and a defined leadership scorecard
  • Teams that already collect weekly numbers but need consistent trend, filter, and comparison views
  • Organizations willing to assign a data owner and train contributors on common definitions
  • Churches that can justify a four-figure annual analytics budget through specific decisions
  • Leadership teams wanting aggregate ministry and digital context without replacing their ChMS

Avoid if

  • Your annual software budget cannot absorb at least $4,908 for a reporting layer
  • You have no recurring decision, owner, or meeting that will use the dashboard
  • Staff will enter numbers inconsistently or only catch up immediately before a board meeting
  • You need a proven native, bidirectional connector to a specific ChMS or finance system that has not been demonstrated
  • You intend to score individual faith, pastoral worth, or ministry success from a few quantitative fields

What ChurchStats is

ChurchStats is an aggregation and visualization layer rather than a membership database, online giving processor, check-in system, pastoral-care record, or accounting ledger. Those source systems continue to perform the operational work. ChurchStats provides a flexible place to record or bring together selected counts and compare them across time and organizational dimensions.

Its value depends more on data practice than interface. If attendance is counted differently at each campus, if one leader records unique people and another records total visits, or if “volunteer” sometimes means scheduled and sometimes checked in, the chart will amplify confusion. A metric dictionary, submission calendar, named source, validator, correction process, and leadership decision are prerequisites. The platform can make good measurement visible; it cannot make careless measurement true.

Why ChurchStats stands out: almost any ministry measure can become a shared, filterable dashboard

Many church systems report only the transactions they own. A ChMS knows check-ins, a giving platform knows donations, YouTube knows views, and a spreadsheet knows whatever one ministry typed. ChurchStats lets a church define a broader health scorecard and view it by campus, ministry, event, speaker, series, time, and external context such as weather. That flexibility can support better questions across organizational silos.

Flexibility needs boundaries. Use a small balanced set: a few outcome indicators, a few leading indicators, qualitative context, and explicit guardrails. For example, attendance trend can sit beside newcomer follow-up completion, group participation, volunteer sustainability, pastoral observations, and data completeness. Avoid a giant leaderboard. Review whether a measure produces wise care or merely pressure to report a favorable number.

Custom metrics and live dashboards: define the denominator before celebrating the chart

ChurchStats supports custom measures for worship, kids, youth, groups, baptisms, visitors, volunteers, giving, steps, programs, and local needs. Dashboards and mobile access make trends available beyond an analyst’s spreadsheet. Filters can separate campus, ministry, date, event, pastor, or series, letting leaders ask whether a movement is widespread or isolated.

Each metric needs a written name, purpose, source, owner, unit, numerator, denominator, inclusion and exclusion rules, time zone, campus logic, correction window, and privacy classification. Display unknown or incomplete data separately from zero. Reconcile totals with source records on a schedule and log restatements. When definitions change, preserve version history rather than making an old trend silently mean something new.

Preacher, weather, and digital analytics: context can illuminate or distort

Preacher Stats can associate attendance and other measures with speakers or sermon series, while weather integration offers a plausible explanation for anomalous gatherings. Digital Church beta brings YouTube and social signals into the broader view. These dimensions can help plan calendars, understand channel behavior, and ask better questions about participation.

They can also create irresponsible rankings. A speaker assigned holidays, difficult topics, small services, or a specific campus cannot be compared fairly without context. Views, reach, and followers are not people discipled. Weather correlation is not causation. Use these fields to prompt qualitative inquiry, never to shame a pastor or ministry. Document platform metric definitions because social networks change them and may provide sampled, delayed, or incomplete data.

Privacy, machine learning, and access: aggregate first and minimize the source

ChurchStats’ privacy policy names Everprise PTY LTD and describes collection of account, contact, social-auth, device, usage, cookie, and related information. It says information can support analytics and recommendations through machine-learning models and can contribute to aggregated church analytics by area or location. The policy references service providers, international transfers, Stripe, analytics and remarketing, retention as necessary, user rights, and Google API Limited Use requirements.

Ask precisely which church-submitted fields enter model development or aggregate regional products, how de-identification is tested, whether customers can opt out, and what subprocessors receive connected social or church data. Prefer counts over names. Never put counseling, prayer, health, child protection, disciplinary, immigration, or other sensitive narratives into a general metric system. Enforce named roles, MFA, least privilege, backups, auditability, account offboarding, retention limits, export, and verified deletion. General encryption claims are not a complete assurance program.

Pricing

Free trial

30 days

No credit card is advertised. Use a complete reporting cycle, at least two ministries, one correction, one export, role testing, and a leadership meeting. A three-minute setup claim is not a migration estimate.

Starter

$409/month

Includes eight team members and two social accounts per campus. Additional campuses cost $45 per month each. Confirm metric, history, dashboard, support, export, storage, and beta-feature entitlements.

Best value

Growth

$589/month

Raises capacity to 25 team members and five social accounts per campus. Additional campuses cost $55 monthly. This may fit a church with distributed ministry ownership better than shared Starter credentials.

Advanced

$879/month

Includes 60 team members and 15 social accounts per campus, with extra campuses at $65 per month. Ask which advanced capabilities differ beyond published account capacity.

Custom plan and annual billing

Quote required

The site exposes an annual-billing option and custom plans but did not provide dependable annual totals in accessible text. Obtain the full term, discount, implementation, training, support, renewal, and cancellation language.

Starter costs $409 per month, making the minimum published annual run rate $4,908 before extra campuses or possible taxes. Two additional campuses would bring the monthly figure to $499 and the yearly figure to $5,988. The economics are difficult for a small church unless the platform replaces substantial consulting, spreadsheet, and leadership labor.

Growth is $589 monthly, or $7,068 for twelve months at the month-to-month rate, and Advanced is $879, or $10,548. The main published capacity differences are team members and connected social accounts, so ask for a complete tier comparison before assuming higher plans add analytical sophistication.

Campus expansion compounds: $45 on Starter, $55 on Growth, and $65 on Advanced per additional campus each month. Define campus carefully. A school, online gathering, language congregation, service location, or church plant might be treated differently by the contract.

Migration, data cleanup, staff input, metric workshops, validation, and leadership adoption are implementation costs even when vendor support is included. Measure them during the trial. A dashboard no one trusts or opens is expensive at any subscription price.

The site includes an annual toggle but accessible research did not expose reliable annual figures. Ask for a written annual total, term length, payment timing, renewal price, refund rules, data access during nonrenewal, and export window. Never calculate procurement from a graphical toggle that does not state the controlling contract.

Where ChurchStats falls behind

Small-church affordability. A $409 monthly floor conflicts with broad small-church accessibility language; a limited low-volume tier would make the mission more credible.

Integration transparency. Public documentation should distinguish manual entry, CSV import, direct ChMS connectors, API sync, social beta access, refresh cadence, failures, and source-of-truth behavior.

Security evidence. A public trust center should cover certifications, testing, hosting regions, encryption, backup restore, availability, incident notice, subprocessors, MFA, audit logs, retention, and deletion.

Model-use controls. The privacy policy’s machine-learning and aggregated-location language needs product-specific explanations, field boundaries, opt-outs, and de-identification assurance.

Current proof and roadmap. Recent release notes, implementation guides, customer cases, uptime, and beta maturity would help buyers judge momentum beyond the 2023 launch material.

ChurchStats vs. Church Metrics vs. native ChMS reports vs. a custom dashboard

ChurchStats offers flexible church-specific metrics, contextual filters, preacher and weather dimensions, and digital beta features at a premium price. Church Metrics is a more focused self-service choice for basic recurring counts. Compare metric definition, campus support, roles, imports, exports, historical migration, active development, and actual annual cost with representative data.

Native Planning Center, Elvanto, giving, accounting, and social reports keep information close to its source and may cost nothing extra. They fall short when leadership needs one reconciled cross-system scorecard. Before adding ChurchStats, improve saved reports and a simple leadership cadence to prove that integration—not inconsistent practice—is the remaining problem.

A custom Churchlytics or general BI engagement can match unusual systems and ownership requirements but introduces implementation, maintenance, and consultant dependency. ChurchStats has a faster productized path. Custom work can be better where automated connectors, security architecture, data warehouse control, or specialized definitions are nonnegotiable.

The bottom line

ChurchStats brings welcome flexibility to church analytics. Custom metrics, ministry and campus filters, preacher and weather context, and a digital beta can turn scattered weekly counts into a leadership rhythm. It is especially relevant where an existing ChMS stores people but does not give leaders the shared scorecard they need. The product must earn its premium price through real decisions. During the 30-day trial, build only a small approved metric set, migrate enough history to expose data problems, test permissions, verify calculations, and use the dashboard in an actual meeting. Ask difficult privacy and model-use questions. If leaders act differently and staff spend less time reconciling spreadsheets, the cost may be justified; if the result is simply more colorful counting, keep the source reports and invest elsewhere.

Alternatives to ChurchStats

Frequently asked questions

How much does ChurchStats cost?

Current monthly pricing is $409 for Starter, $589 for Growth, and $879 for Advanced. Additional campuses cost $45, $55, or $65 per month respectively. Custom and annual terms require a quote or checkout confirmation.

Does ChurchStats offer a free trial?

Yes. The official site advertises one month or 30 days with no credit card required. Use a full reporting cycle and representative history rather than evaluating an empty dashboard.

Does it replace Planning Center or another ChMS?

No. ChurchStats says it complements church-management systems such as Planning Center or Elvanto. The ChMS remains the operational people system; ChurchStats is the configurable analytics and dashboard layer.

What can a church track?

Examples include attendance, visitors, baptisms, faith responses, groups, giving, kids, youth, volunteers, growth steps, programs, cars, signups, families, speakers, weather, and selected YouTube or social measures. Custom definitions are central.

Are integrations automatic?

Do not assume that every ChMS metric syncs automatically. Public material emphasizes custom entry and migration help, while Digital Church connections are beta. Require a demonstration of each exact source, direction, field, refresh, and failure path.

Is ChurchStats secure?

The FAQ claims encryption and backups, and the privacy policy describes commercial safeguards. We did not find a prominent public SOC 2 or ISO certification. Ask for current technical controls, independent testing, subprocessors, roles, logs, restore evidence, incident terms, and deletion.

Should a church measure salvation or discipleship?

A church can record defined events such as baptism, a stated decision, group participation, or a completed next step. It should not treat a count as a complete measure of spiritual life, compare people as scores, or let reporting pressure replace pastoral wisdom.

Sources & further reading

More Church Management Software

B1 Church 4.9A genuinely free, open-source church platform - app, website, giving and check-in on one database - run by an Oklahoma nonprofit. The catch is not the price - it is that the vendor own docs call the native app deprecated.Involv Chat (church.chat) 4.9Involv Chat combines ministry-team messaging, rosters, blocked dates and service scheduling in a focused church workspace—useful when leaders protect volunteer consent and resist turning attendance or gifts data into a spiritual score.ChurchSoftware 4.9ChurchSoftware—formerly StoreHouse—offers an unusually broad church-management core for $0, including giving, check-in, accounting and a shared mobile app, while charging transparently for vendor-heavy extras.Pastor Notes App 4.9A two-app system that lets leaders publish sermon notes and invite live congregational response while attendees use the free Bible Notes companion—but its pricing math, refund terms and app privacy disclosures need correction before a church commits.Take Root 4.9A low-cost, offline-friendly relationship tracker built specifically for evangelism and discipleship follow-up—more intentional than a spreadsheet, but its old generic privacy policy does not adequately describe the sensitive ministry data the product exists to hold.Develop.Me 4.9Develop.Me packages course building, cohorts, discussion, assignments, gamification and mobile learning for churches and mission-driven organizations—with unlimited learners on paid plans, but a vague free tier and a 2022 website privacy notice leave procurement questions open.
Try ChurchStats