- Starting price
- $1,200/year
- Free tier
- No
- Platforms
- Web · SMS · Mobile browser
- Developer
- Salt and Light Company
- Launched
- 2024
- Updated
- Aug 16, 2026
The verdict
Seedling addresses a real pastoral operations problem: prayer requests arrive through scattered channels, intercessors lack context, and requesters rarely hear what happened next. Its request pages, matching, notifications, follow-up, and theme analysis could make prayer ministry more attentive. Yet these records can reveal religion, illness, abuse, grief, finances, relationships, minors, and crisis. The linked privacy text we captured said excerpts go to OpenAI and phone numbers to Twilio, but it named another company and its public short link later returned 404. Do not treat that as cosmetic. Require corrected policies, a data-processing agreement, security answers, explicit retention, AI controls, role design, and a pastoral safety process before launch.
Try Seedling ↗Opens seedling.so
Seedling is a church prayer-management platform created by Salt and Light Company. Members can submit requests by text, voice, QR code, or a public web form. Leaders can organize and match requests with intercessors, send notifications, follow up, and tell a requester that someone prayed. The product also uses AI to summarize themes, sentiment, and measures it frames as spiritual-health insight.
The workflow is appealing because it connects intake to action. A public form can accept a name, email, mobile number, and up to 1,500 characters, with fields presented as optional and separate SMS consent language. Seedling reports more than 15,000 requests and says the company began after the 2024 Lausanne gathering, with its first church customer in 2025.
The data is unusually sensitive. A prayer request may disclose diagnoses, counseling issues, alleged crimes, suicidal thinking, domestic violence, immigration status, a child’s situation, or information about a person who never consented. Seedling’s policy explicitly says request excerpts can go to OpenAI for analysis and phone numbers to Twilio for prayer notifications. Its terms say the church is controller and Seedling processor and that customer data is not used for public-model training.
We reviewed the public product, pricing, history, request form, linked privacy text, terms, and faith.tools listing without accessing an administrator account. The captured privacy text identified “Good Quests Company,” included malformed wording and an old domain contact, while the terms identify Salt and Light Company. In a fresh source check the privacy short link returned 404. That combination is a material trust and contracting problem for a pastoral-data processor, not simply an editorial typo.
✓ The good
- Closed-loop prayer - requesters can learn that a person received and prayed for their concern
- Multiple intake paths - text, voice, QR, and web options reduce dependence on one channel
- Intercessor coordination - matching and notifications can replace ad hoc spreadsheets and message chains
- Theme visibility - aggregate patterns may help leaders notice recurring needs and allocate care
- Controller roles acknowledged - terms recognize the church as controller and Seedling as processor
- No stated public AI training - terms say customer content is not used to train public models
✗ Watch out
- Broken policy access and identity - the linked notice became unavailable and the captured text named another company
- Highly sensitive content - prayer records can contain religious, medical, family, crisis, and third-party data
- AI disclosure - prayer excerpts are sent to OpenAI, which requires informed church policy and careful minimization
- Messaging exposure - Twilio receives phone numbers for notifications and introduces another processor and consent layer
- Not HIPAA-tailored - the terms warn against use where HIPAA, FISMA, or similar regimes govern interactions
- Annual starting commitment - the published church price begins at $1,200 per year and scales with usage
- Contribution language - broad licensing language in the terms should be clarified so prayer requests cannot be mistaken for public contributions
Best for
- Churches formalizing a prayer ministry with trained intercessors and defined care escalation
- Multi-channel ministries that need request ownership, notification, and follow-up in one workflow
- Leadership teams prepared to execute a data-processing agreement and security review
- Pilots using low-sensitivity requests, small roles, short retention, and optional AI
Avoid if
- Your prayer channel routinely receives therapy, protected health, abuse, self-harm, child, or legal disclosures
- The church cannot explain AI and SMS processing to requesters or offer a non-AI alternative
- You need a mature, internally consistent privacy policy and detailed security documentation before procurement
- Volunteers lack training in confidentiality, mandatory reporting, crisis escalation, and least-privilege access
What Seedling is
Seedling is workflow software for church prayer teams. It is not a clinical record system, emergency service, therapist, mandated-reporter substitute, spiritual-health diagnostic, guarantee of confidentiality, or safe destination for every disclosure simply because the request is framed as prayer.
Its AI labels and trends are organizational signals, not reliable measurements of spiritual condition. Sentiment can misread lament, cultural idiom, sarcasm, Scripture, or a carefully understated crisis. A trained person must review both the individual request and any aggregate inference before action.
Why churches value the “someone prayed” loop
Most prayer forms collect. Seedling tries to complete the pastoral loop by assigning or matching the request, notifying intercessors, recording action, following up, and signaling care back to the requester. That can convert an invisible inbox into accountable ministry.
The same accountability requires restrained access. A volunteer should see only the request needed for the assigned role; particularly sensitive submissions may need a pastor or safeguarding lead rather than a broad prayer team. The system should support that policy instead of defining it.
Request intake: accessible channels with consent choices
Churches can publish a web or QR entry point and accept text or voice requests. The reviewed form asks for optional identity and contact fields, includes SMS consent, and allows a substantial narrative.
Add a plain-language warning not to name third parties or submit emergencies, explain who will read the text, make AI processing optional, and provide a telephone or in-person path for someone who cannot safely use the form.
Intercessor matching and follow-up: ministry needs role design
Requests can be routed to intercessors, paired with notifications, and followed through to a prayed status or later contact. This is more operationally complete than an inbox or spreadsheet.
Define administrators, pastors, volunteers, and safeguarding roles before importing real data. Review access logs, remove departed volunteers immediately, ban personal screenshots and forwarding, and establish what notes may be stored.
AI themes and sentiment: potentially useful, never a diagnosis
Seedling analyzes excerpts through OpenAI to derive themes, sentiment, and organizational insights. Aggregation might help a church see rising grief, financial strain, or requests for practical care.
Minimize the text sent, strip names and third-party identifiers, define retention and model settings contractually, test demographic and cultural errors, and never use a score to rank faith, urgency, sincerity, eligibility, or pastoral attention.
Pricing
Church plan
$1,200/year
The published starting price equals $100 per month when billed annually and scales with usage and organizational growth.
Geographic pricing
Custom
Seedling invites organizations in different economic contexts to ask about adjusted geographical pricing.
Initial access
Contact vendor
Marketing says churches can start without a subscription, but no clearly defined permanent free organization plan is published.
Published church pricing starts at $1,200 per year, described as $100 per month on annual billing, and increases with use and growth.
The homepage’s invitation to start without a subscription is not enough to classify Seedling as having a durable free tier. Confirm the pilot length, included requests, renewal price, overages, cancellation, and export before signup.
Ask for geographic pricing if the standard U.S. price is not appropriate to the ministry’s context.
Budget for governance as well as software: legal and security review, volunteer training, policy writing, request triage, incident handling, and deletion work are part of the real cost.
Where Seedling falls behind
Restore the privacy link and replace its captured text with a professionally reviewed, Seedling-specific policy whose identity, contacts, dates, and scope match the terms.
Publish a subprocessor list, data locations, encryption and backup details, incident commitments, audit controls, retention periods, deletion verification, and export format.
Clarify whether prayer requests can ever be “contributions” under the broad license language and expressly exclude confidential customer content from public-use rights.
Add configurable AI opt-out, redaction, sensitive-request routing, consent records, role templates, access logs, crisis banners, third-party-data warnings, and short default retention.
Define minors, church safeguarding, mandatory-reporting support, account recovery, offboarding, and the boundary between prayer follow-up and regulated care.
Seedling vs. Flocknote vs. a church prayer form
Flocknote is a mature church communication and member-messaging system with broader lists and engagement workflows. A basic form plus a restricted pastoral inbox is cheap and controllable. Seedling is more focused on prayer assignment, intercessor action, follow-up, and thematic analysis.
Choose Seedling when prayer operations are the priority and the church can negotiate the data safeguards. Choose Flocknote when communication breadth and an established platform matter more, or a simple form when request volume is low and sensitive material should stay in a smaller circle.
Do not choose solely from the demo. Run a privacy and safeguarding exercise using fictional requests involving illness, domestic violence, a minor, suicidal intent, and a named third party; verify exactly how each is consented, routed, hidden, escalated, exported, and deleted.
The bottom line
Seedling’s product insight is strong: a prayer request should become accountable human care, not disappear into an inbox. The platform could help churches do that consistently, and its controller-processor language is a promising foundation. The present policy quality and explicit OpenAI/Twilio processing make procurement diligence nonnegotiable. A corrected privacy package, signed data terms, narrow roles, short retention, non-AI intake, crisis procedures, and trained leaders should precede real use. Until then, the 3.5 rating reflects governance risk more than the usefulness of the workflow.
Alternatives to Seedling
Frequently asked questions
How much does Seedling cost?
Published organization pricing starts at $1,200 per year, equivalent to $100 per month billed annually, with scaling and geographic pricing available.
Does Seedling have a free plan?
The site invites churches to start without a subscription, but we found no clearly defined permanent free organization tier. Confirm pilot and renewal terms directly.
Does Seedling use AI on prayer requests?
Yes. Its privacy policy says prayer-request excerpts are sent to OpenAI for analysis and relevant resources.
What does Twilio receive?
The privacy policy says phone numbers are shared with Twilio to support prayer-related notifications.
Is Seedling HIPAA compliant?
The terms say the service is not tailored for HIPAA, FISMA, or similar regulated interactions. Do not place regulated care data there without qualified review and a suitable agreement.
Why is the privacy policy a concern?
The captured text named Good Quests Company rather than Seedling’s stated operator, used an old contact domain, and contained malformed text; its linked short URL later returned 404. Those defects create uncertainty about scope and accountability.
What should a church require before launch?
A corrected policy, data-processing agreement, subprocessor and security details, explicit retention and deletion, role controls, AI choice, incident terms, and pastoral safeguarding procedures.
