- Starting price
- Free Church Health Report; subscription price not published
- Free tier
- Yes
- Platforms
- Web · Planning Center integration · Early-access onboarding
- Developer
- FlowLeed
- Launched
- 2026 early access
- Updated
- Aug 9, 2026
The verdict
FlowLeed understands the ministry question behind church analytics: not merely what happened, but who may need a conversation and who owns the next step. Its free Planning Center report, visual Flows, Church Heartbeat, Flow Moments, assignments, AI querying, and person-first dashboards form a coherent concept. The current trust foundation is not adequate for production-sensitive data. The public privacy route is an empty navigation shell; we found no public terms, DPA, security, subprocessor, AI-provider, retention, deletion, export, incident, or paid-pricing detail. Request a demo if the idea fits, but use synthetic data until those documents and controls withstand review.
Try FlowLeed ↗Opens flowleed.com
FlowLeed describes itself as a church-intelligence platform and “virtual co-pastor” that sits above an existing church management system. Its public site focuses on Planning Center data—attendance, check-ins, groups, serving, giving, milestones, contacts, and ministry activity—then organizes people into an engagement view, visual care or discipleship pipelines, reports, assignments, and AI-assisted questions. The promise is proactive care: notice a new guest without a second follow-up, a regular family whose pattern changed, a volunteer slowing down, or an engaged person ready for a next step before a staff member hunts through reports.
The free entry point is a Church Health Report. A church creates an account, connects Planning Center, and receives scores for at-risk people, volunteers, groups, and overall health; lists of engagement changes and follow-up gaps; opportunity groups such as regular attenders not in a group; leader workload; trends; and five suggested ministry actions. No card is required. The page presents this as a quick diagnostic, but it still requires access to a real church database, and therefore is not a low-consequence lead magnet.
The product beyond the report has four main modules. FlowLeed AI answers natural-language questions and drafts follow-up in a church’s voice. Flows place people in linear or recurring journeys such as new guest, new believer, baptism, volunteer care, small groups, generosity, and pastoral check-ins. Engagement Score or Church Heartbeat classifies people as thriving, active, slowing, at risk, inactive, or needing care based on selected signals. Reports and Insights show response time, assignment gaps, pathway movement, leader workload, and claimed “engagement lift.” Planning Center is presented as live; Pushpay, Subsplash, Tithe.ly, and Rock appear as coming integrations.
This is a researched early-access review. We inspected the public marketing and product pages, free-report workflow, account and early-access routes, and the linked privacy route. We did not authorize Planning Center, create people, run AI, inspect score formulas, test role permissions, confirm whether every illustrated feature is enabled, receive a price quote, review a contract, audit security, or interview churches. The public pages alternate among “Create Account,” “Get Early Access,” and “Request Early Access,” so exact availability must be confirmed. Most importantly, the privacy link currently displays no substantive policy text.
✓ The good
- The product begins with a real ministry question - identify care and next-step gaps rather than generating another operations dashboard
- The free report creates an understandable first artifact - church health, people needing attention, hidden opportunities, and five possible actions
- Flows support both destinations and rhythms - a baptism journey can complete while volunteer or pastoral check-ins recur
- Assignments make ownership visible - teams can see who is responsible, what is due, and where people have remained stuck or unassigned
- AI is presented as contextual - questions and suggestions are grounded in the church’s own data rather than generic ministry advice
- Person-first screens are easier to act on than abstract charts - a user can move from a signal to an individual and a follow-up path
- No migration is promised for Planning Center users - FlowLeed aims to add an analysis and care layer rather than replace the ChMS
- The public site distinguishes live and future integrations - Planning Center is shown first while Pushpay, Subsplash, Tithe.ly, and Rock are labeled coming
- Demo and early-access onboarding can support a controlled pilot - a church can ask detailed questions before committing if it refuses premature data access
✗ Watch out
- The public Privacy Policy route is empty - it contains site navigation and footer but no disclosure of collection, use, sharing, rights, retention, or contact
- No public terms or DPA were found - churches cannot inspect ownership, processor roles, liability, confidentiality, breach duties, audit rights, or exit commitments
- Paid pricing is undisclosed - the free report is visible, but subscription tiers, limits, users, data volume, AI usage, support, term, and renewal are not
- AI governance is undocumented - model providers, prompts, training use, retention, redaction, regions, citations, approval, and error handling are not publicly explained
- Engagement formulas are opaque - weights, windows, missing data, thresholds, false alarms, bias testing, overrides, and confidence are absent from public detail
- The free report requires sensitive ChMS access - a no-card label does not reduce the consequences of importing names, attendance, giving, serving, groups, or children
- Availability language conflicts - account creation is open while product pages still ask for early access, making live versus illustrated scope difficult to establish
- Claims are not supported by public validation - hours saved, engagement lift, ministry health grades, and recommendation quality appear as examples rather than measured evidence
- Key operational facts are missing - security controls, permissions, MFA, audit log, export, deletion, backups, subprocessors, incident response, uptime, and accessibility are not documented
Best for
- Planning Center churches exploring a people-care analytics concept and willing to begin with a vendor demo and synthetic data
- Executive or pastoral teams that can conduct formal privacy, security, legal, theological, and safeguarding review before connecting production records
- Churches with clearly documented guest, volunteer, group, baptism, giving, and pastoral-care processes that can map Flows without letting the software define discipleship
- Early adopters prepared to test score accuracy, data gaps, permissions, bias, false positives, and staff capacity in a small controlled pilot
- Ministries willing to require a written subscription order, DPA, subprocessor list, AI addendum, retention schedule, export plan, and incident commitments
Avoid if
- Your church cannot review a real privacy policy, terms, DPA, security evidence, AI data flow, and subprocessor list before authorizing Planning Center
- You need public, predictable pricing and generally available feature commitments before budgeting or procurement
- Leaders are likely to treat attendance, giving, serving, or algorithmic engagement as a measure of faithfulness, spiritual maturity, or pastoral worth
- You need a replacement ChMS for check-ins, donations, accounting, services, registrations, scheduling, communications, or member self-service
- Your team lacks people and processes to review alerts, contact individuals sensitively, correct data, honor opt-outs, and handle safeguarding disclosures
What FlowLeed is
FlowLeed is an analysis and workflow overlay, not the system where attendance, gifts, groups, or serving originate. Its homepage says Planning Center data can sync without migration or double entry. The platform then turns signals into people profiles, household views, stages, scores, milestone “Flow Moments,” assignments, alerts, dashboards, and AI conversation. Future logos for Pushpay, Subsplash, Tithe.ly, and Rock indicate intended expansion rather than current parity.
Flows are drag-and-drop pipelines with two models. Linear Flows move toward a defined endpoint such as welcome call, group, serving, membership, baptism, or training. Recurrent Flows cycle through care, check-in, encouragement, volunteer health, and leader support. The public pages correctly note that people take different paths and that discipleship should be guided rather than scripted. Still, any board necessarily imposes categories, due dates, and a definition of progress that leaders must examine.
The intelligence layer ranks or groups people using observed activity. Example screens combine missed check-ins, giving pauses, group absence, serving changes, visits, and follow-up history; FlowLeed AI answers questions such as who needs follow-up, which guests did not return, or who may be ready to serve. The system can draft a message and attach an action to a person. Public documentation does not establish whether external messages require approval, which actions can write back, or how inferences are explained and corrected.
Why church leaders consider FlowLeed: the next action is more useful than another attendance graph
Most reporting ends with a count. FlowLeed’s strongest idea is to connect a pattern to a named owner and an appropriate conversation. If a guest attended twice and no one followed up, the useful output is not a red chart; it is a visible gap, a staff member who accepts responsibility, and a human contact that respects the guest. If a volunteer’s rhythm changes, the first response should be curiosity and care, not an automated retention campaign.
Actionability magnifies both benefit and harm. A model can be wrong because a check-in failed, a family changed campuses, a giver used another method, a volunteer took an agreed break, or a person intentionally set a boundary. Staff should see source records, confidence and missingness, correct the underlying data, record “do not contact,” distinguish information from inference, and ask rather than assume. No engagement score should become discipline evidence, donor targeting, membership eligibility, staff evaluation, or a substitute for knowing the person.
Free Church Health Report: a compelling diagnostic that is already a production data decision
The report promises an overall grade plus at-risk people, volunteer, group, guest, leader-workload, trend, opportunity, and action views. Examples include people with no recent check-in, guests lacking follow-up, volunteers whose serving slowed, regular attenders outside groups, engaged people not serving, and a “top five” weekly action list. Setup is account creation, Planning Center authorization, analysis, then report—no payment card.
Before clicking Connect, demand the same diligence as a paid implementation. Obtain the OAuth scopes, data dictionary, processing purpose, retention, storage region, subprocessors, encryption, deletion, AI use, support access, logging, revocation, and export. Use a test Planning Center organization or synthetic records first. A free diagnostic can copy or analyze an entire congregation; the absence of a charge says nothing about confidentiality or reversibility.
Flows, Flow Moments, and assignments: make care work visible without mechanizing spiritual growth
Flow boards can show stage, time in stage, campus, tags, owner, status, completed contact, and the next activity. Templates cover guest follow-up, new believers, baptism, volunteers, groups, generosity, leadership, and pastoral care. Flow Moments map events such as a first visit, salvation decision, baptism conversation, first gift, group connection, or serving role. Reports expose where people accumulate, response delay, ownership gaps, and pathway completion.
Use administrative events as prompts, not a theology of maturity. A person may be spiritually growing without joining the expected sequence, and sensitive milestones may not belong in a broad staff dashboard. Define which moments are self-reported, which are inferred, who may see them, how long they remain, and how a person can correct or remove them. Limit generosity data and avoid “giver journey” language that turns pastoral care into revenue optimization.
FlowLeed AI, Engagement Score, and Reports: high-value questions with undocumented controls
Public examples show natural-language queries over people, tasks, numbers, and ministry health; suggested next steps; drafted pastoral follow-up in the church’s voice; categories such as thriving, active, at risk, inactive, new, or needing care; and trends for groups, volunteers, guests, giving, assignments, and leader load. A well-designed implementation could save hours of manual cross-report work and reveal inconsistent follow-up.
The site does not say which model sees what, whether names or sensitive fields are redacted, whether prompts train providers, how long prompts persist, how scores are calculated, whether suggestions cite exact rows, or whether a person approves every send or write. Treat AI and scores as disabled until a written architecture and live controls answer those questions. Test adversarial prompts, role escalation, cross-campus leakage, hallucinated records, stale data, discriminatory ranking, crisis language, child records, and a request to delete one individual completely.
Pricing
Free Church Health Report
Free; no credit card
Create an account and connect Planning Center to receive diagnostic scores, people and ministry signals, opportunities, and suggested actions. This is free financially, not low-risk informationally.
FlowLeed early access
Not published
A 20-minute demo request asks church role and congregation size. Product pages do not show subscription price, trial length, feature gates, record limits, users, campuses, support, AI allowances, or contract term.
Planning Center
Separate subscription
The current public workflow depends on an existing Planning Center database. Confirm which products, scopes, records, histories, and webhooks FlowLeed requires.
Implementation and governance
Church staff and advisory cost
Budget data cleanup, consent and notice, role mapping, DPA and legal review, security assessment, score validation, staff training, care capacity, export testing, and incident planning.
The free report is the only publicly priced offer. It may be valuable as a structured data audit, but connecting Planning Center creates a vendor relationship even when no card changes hands. Do not accept click-through access without knowing which agreement governs that processing.
No public subscription price means a church cannot compare cost per adult, user, campus, record, integration, AI message, report, or support tier. Ask for setup charges, minimum term, annual prepayment, renewal increase, implementation, overages, data storage, additional campuses, API access, training, cancellation, export, deletion, and tax in one written schedule.
Price the human response. A system that reveals dozens of at-risk people or missing follow-ups creates a duty to triage, contact, document, and sometimes escalate. If the church has no capacity, the dashboard can normalize unattended alerts or trigger shallow automated messages that feel worse than no system.
Early-access pricing can compensate for product risk only when data risk is controlled. Prefer a sandbox, synthetic dataset, limited fields, one ministry, short pilot, named success criteria, weekly review, no autonomous communication, complete export, and verified deletion. Do not exchange the congregation’s private history for a discount or feature influence.
Where FlowLeed falls behind
Publish a substantive privacy policy immediately and stop inviting Planning Center authorization while the linked policy route is empty.
Publish enforceable terms, a DPA, security page, subprocessor list, AI addendum, retention schedule, export and deletion procedure, incident notice, and named privacy contact.
Show transparent paid pricing with generally available versus early-access features, limits, support, trial, contract term, renewal, cancellation, and implementation cost.
Document every Planning Center OAuth scope and field, sync direction, frequency, historical depth, child-data behavior, writeback, revocation, raw import retention, and deletion cascade.
Expose score formulas, weights, thresholds, time windows, missing-data handling, confidence, source rows, church configuration, overrides, bias tests, and complete opt-out.
Explain AI providers, model routing, regions, prompt construction, training and retention, redaction, sensitive-topic safeguards, citations, role enforcement, human approval, and incident logging.
Publish independent security evidence, MFA and SSO, role granularity, audit logs, encryption, backup and recovery targets, penetration testing, uptime history, and accessibility conformance.
FlowLeed vs. FlockConnect vs. Churchlytics vs. Planning Center reports
FlowLeed and FlockConnect both aim to reveal people who may be drifting, add relationship or care workflows, and use AI above Planning Center. FlockConnect currently publishes detailed pricing, terms, privacy, AI providers, retention, human-approval rules, and a narrower live Starter scope; its distinctive relationship plans remain coming soon. FlowLeed shows more polished pipeline, score, report, and free-diagnostic concepts, but its public governance and pricing are dramatically less mature. Churchlytics represents a custom analytics route, while Planning Center lists and native reports may answer many questions without another processor.
Run a privacy-first proof, not a feature demo. Ask each vendor to trace one person from Planning Center through ingestion, inference, AI prompt, dashboard, assignment, message, export, correction, and deletion. Then test a child, household merge, campus transfer, anonymous donor, opted-out member, incorrect check-in, safeguarding note, role removal, breach, and cancellation. The vendor that produces fewer dazzling screens but clearer control may be the better pastoral choice.
The bottom line
FlowLeed has a strong product thesis and a weak public trust layer. Visual journeys, person-level ownership, a free health diagnostic, proactive care signals, contextual AI, and action-oriented reporting could help a busy team notice real people. Those same features require access to religious affiliation, attendance, giving, serving, group, household, child, contact, and pastoral information—and can generate consequential inferences. An empty privacy page is therefore not cosmetic. Until FlowLeed publishes and contractually supports privacy, terms, DPA, security, AI controls, scoring methods, retention, export, deletion, subprocessors, availability, and pricing, evaluate screens in a demo and use synthetic data. A church should never have to surrender trust in order to learn its health score.
Alternatives to FlowLeed
FlockConnectA related Church Relationship Manager with unusually detailed public privacy and human-approval documentation, though its full AI plans are still coming.
Planning CenterNative People lists, workflows, Groups, Check-Ins, Giving, and reports may solve common follow-up questions without copying data elsewhere.
CareNoteA mature pastoral-care workflow for requests, assignments, visits, follow-up, and multiple ChMS integrations.
ChurchlyticsA custom church-data audit and dashboard option for complex cross-system questions with a defined consulting budget.
ChurchStatsA church metrics and reporting route; compare data model, automation, privacy, integrations, and action workflow.Manual care review in Planning CenterWell-designed lists, workflows, owners, and a weekly human meeting can be safer and more transparent than opaque scoring.Frequently asked questions
Is FlowLeed free?
The Church Health Report is advertised as free with no card. Subscription pricing for the continuing FlowLeed platform is not publicly listed.
Is FlowLeed generally available?
The site offers account creation and a free report, while multiple product pages still say Get or Request Early Access. Ask the vendor for a written live-feature and availability matrix.
What church system does FlowLeed connect to?
Planning Center is the live integration promoted publicly. Pushpay, Subsplash, Tithe.ly, and Rock are shown as coming rather than available equivalents.
Does FlowLeed publish a privacy policy?
A Privacy Policy link exists, but on August 9, 2026 its page contained navigation and footer only—no substantive policy text. Do not authorize production data until a complete policy and DPA are reviewed.
How does the engagement score work?
Public pages name inputs such as attendance, check-ins, serving, giving, groups, communication, and milestones, but do not publish weights, time windows, missing-data rules, confidence, validation, or bias tests.
Can FlowLeed AI send follow-ups automatically?
The site says it can draft follow-ups ready to send, but public materials do not clearly document approval, writeback, provider, or prompt controls. Require a live demonstration and written human-approval guarantee.
Should I connect Planning Center for the free report?
Only after receiving and approving OAuth scopes, privacy policy, terms, DPA, subprocessors, security evidence, AI data flow, retention, export, and deletion. A sandbox or synthetic organization is the safest first test.
Sources & further reading
- FlowLeed official product site ↗
- Free Church Health Report ↗
- Early-access request page ↗
- FlowLeed AI product page ↗
- Flows product page ↗
- Engagement Score product page ↗
- Reports and Insights product page ↗
- Planning Center integration page ↗
- Published Privacy Policy route (currently contains no policy text) ↗
More Church Management Software
B1 ChurchA 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)Involv 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.
ChurchSoftwareChurchSoftware—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 AppA 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 RootA 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.MeDevelop.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.