Resource Review13 min read

Asaph

4.9App Store rating · 1 ratings

An ambitious AI workspace for sermon-aligned setlists, song analysis and local feedback—valuable as a planning assistant, risky if its theology scores become a substitute for pastoral judgment.

Starting price
Free; paid plans advertised from $12/month
Free tier
Yes
Platforms
Web · iOS · Android · Planning Center browser extension
Developer
Three Times Good Pty Ltd
Launched
2023
Updated
Aug 9, 2026
900+ worship leadersClaimed users
600+ minutesTraining library
Last 30 daysFree history
1 service · unlimited setlists · 1 adminFree capacity
5.0 from 1 ratingUS Apple rating
1.58.0, updated 1 August 2026Current iOS version

The verdict

Asaph is one of the more coherent uses of AI in church software: it starts from a congregation’s song library, sermon passage, rotation history and feedback, then produces an editable set rather than pretending to lead worship autonomously. Song 360, gap analysis and local response data could expose repetitive themes and tired repertoire. Yet “biblical soundness,” gospel-arc scoring and sentiment are interpretive judgments, the AI provider and rubric are not public, the pricing page is internally confusing, and several promoted features remain “coming soon.” Let it surface questions and options; keep pastors and worship leaders responsible for lyrics, theology, permissions and people.

Try Asaph

Opens asaph.io

Asaph is an AI-assisted worship-planning platform from Australian company Three Times Good Pty Ltd. A leader adds or imports the church’s songs, enters a sermon passage or theme and asks Asaph to generate a proposed setlist. The system considers lyrics, theological themes, song rotation, emotional energy and the order’s “gospel story” movement through glory, gravity and grace. A leader can lock a song, regenerate around it, edit everything, publish the set and ask team members for feedback after the service. The company says more than 900 worship leaders now use it.

This is not merely a random song recommender. Song 360 evaluates each song across emotion, energy, theology and themes; gap analysis identifies underused subjects such as prayer, communion or mission; rotation warnings notice songs that may need rest; feedback builds a local view of what is helping a particular congregation. The help center also advertises Messenger, Planning Center import through a browser extension and more than 600 minutes of training from Bob Kauflin, Zac Hicks, CityAlight, Citizens and others. iOS and Android apps extend the workspace beyond the browser.

The current product is also visibly mid-transition. Apple version 1.58.0, released 1 August 2026, added CSV song import and editable song keys while describing dashboard pieces as coming soon. The pricing page shows Free, Leader, Team and future Ministry tiers, yet its FAQ still says the open beta keeps paid access to “one team plan.” Leader displays both $12 and $15 per month; Team displays both $39 and $45, with malformed “billed monthly (actually)” text and “Coming Soon” labels. Those could represent annual-equivalent versus month-to-month prices, but the page does not render that distinction clearly enough to state it as fact.

This is a researched review based on the official site, help center, pricing, privacy, terms and current Apple listing. We did not create a church account, import copyrighted lyrics, generate a set, compare its doctrine rubric with a church statement, interview team members, buy a plan or audit the model. Apple reports one US rating. A single perfect rating carries no statistical weight and cannot establish the accuracy of theological analysis, quality of recommendations or health of anonymous feedback.

✓ The good

  • Context-aware generation - sermon passage, local repertoire, rotation and flow shape suggestions instead of generic popularity alone
  • Human edit control - leaders can lock songs, regenerate around them and revise the result before publishing
  • Useful free tier - one service, unlimited setlists, gap analysis, unlimited team members and 30 days of data cost nothing
  • Four-dimensional song view - emotion, energy, theology and themes invite broader evaluation than key and tempo
  • Local feedback loop - a church can learn from its own people rather than national streaming charts
  • Planning Center bridge - an extension can reduce re-entry of an existing repertoire
  • Active development - August 2026 brought CSV import, key editing, AI tone changes and security work
  • Training included - more than 600 minutes from named worship leaders and ministries broadens the product beyond automation

✗ Watch out

  • AI theology is opaque - no public rubric, model provider, source corpus or doctrinal configuration explains “biblical soundness” scores
  • Pricing page is internally inconsistent - paired monthly prices, coming-soon labels and an old one-plan beta FAQ do not reconcile
  • Several features are unfinished - dashboards, recommendations, weekly reports and parts of import/integration are marked soon or coming soon
  • Privacy policy is broad and old - a 2023 template predates the current generative workflow and does not name AI subprocessors
  • Feedback can become a popularity metric - anonymous sentiment may reward familiarity or production rather than faithful congregational worship
  • English-only Apple interface - no current localization is listed
  • Account data is cloud-dependent - song libraries, team communication, feedback and church profiles live with a young vendor
  • Negligible rating sample - one US Apple rating provides no independent quality evidence

Best for

  • Worship leaders who already maintain a defined congregational song library
  • Churches wanting set suggestions connected to a sermon passage and recent rotation
  • Teams willing to treat AI analysis as prompts for discussion rather than doctrinal authority
  • Multi-service ministries that can benefit from cross-service analytics when those features are active
  • Planning Center users prepared to review imported data and permissions carefully

Avoid if

  • Your church will accept theology or “gospel story” scores without human review
  • You need stable, unambiguous pricing and a finished enterprise feature set today
  • You cannot place lyrics, sermon references, team data or feedback in a cloud AI workflow
  • You want full scheduling, volunteer rostering, chord charts, licensing and presentation in one mature suite
  • Your congregation lacks a healthy process for interpreting anonymous worship feedback

What Asaph is

Asaph combines five functions that are often scattered across Planning Center, spreadsheets, chat, surveys and streaming research. Its library stores songs and analysis. The setlist generator proposes an order from Scripture or a theme. Gap and rotation tools examine the repertoire over time. Messenger distributes plans and training. Post-service feedback creates a local response record. The named product comes from the biblical musician Asaph, associated with Psalms 50 and 73–83 and David’s worship leadership.

A normal workflow begins by importing from Planning Center, CSV or Asaph’s own library, depending on which current route is active. The leader enters a passage or theme, generates candidates, locks essential songs and regenerates alternatives. Energy charts and a glory–gravity–grace visualization show the proposed service arc. After publication, team members can view and discuss the set, then submit feedback that contributes to song health and trend data. One-time email codes replace normal passwords.

Asaph is not an ordained leader, theologian, copyright licensor or substitute for rehearsal. It detects patterns in data and language according to hidden rules. A congregation still needs people who know its doctrine, pastoral needs, vocal range, musicians, service structure, cultural setting and licensing obligations. The right mental model is a specialized planning analyst whose work is always reviewed.

Why local song health is more useful than another global popularity chart

Most worship discovery tools tell leaders what other churches stream, report or purchase. Asaph tries to answer a different question: what is happening in this congregation? Its recommendations can use the local repertoire, recent rotation and anonymous response. A song popular everywhere may be unfamiliar here; an older song may carry deep communal memory; a musically impressive selection may repeatedly leave volunteers unable to participate. Over time, local history can reveal those differences.

Feedback remains evidence to interpret, not a vote on truth. People may rate a song highly because it is new, nostalgic, loud, easy or associated with an emotional moment. A minority language group or less vocal participant may be invisible in an aggregate. Leaders should collect qualitative context, watch for sample size, never punish dissent and avoid asking software to determine whether worship “worked.” Use trends to ask better pastoral and musical questions, then speak with people face to face.

AI setlist generation and the glory–gravity–grace arc

The generator accepts a sermon passage or theme, analyzes available songs and proposes a sequence based on theology, thematic connection, rotation and energy. Songs can be locked while the rest regenerate, and the leader can edit the result manually. A chart visualizes musical energy. Another models a “gospel story” arc using glory, gravity and grace, helping a team notice whether a service names God’s character, human need and divine grace rather than stacking unrelated favorites.

That framework can be clarifying without being universal. Christian services follow many scriptural and liturgical shapes, and not every gathering or set needs to fit three plotted stages. A lament may dwell in grief; Communion may organize the whole movement; a lectionary service may already have its own sequence. Never assume a chart proves theological completeness. Read every lyric in context, compare it with the sermon passage and the church’s confession, ask what the congregation is being invited to say, and let leaders override the model freely.

Song 360, gap analysis and rotation: strong questions behind opaque scores

Song 360 analyzes emotion, energy, theology and themes. Gap analysis looks across the library for underused subjects such as prayer, Communion or mission, while freshness and rotation data identify songs repeated heavily or left dormant. The App Store also names quartile performance reports, theological keyword breakdown and per-song sentiment trends. Version history shows the analysis growing through emotional scores, sermon-song comparison and improved passage input.

The concern is provenance. Asaph says it evaluates doctrinal themes and “biblical soundness” but does not publish the model, prompt, theological rubric, Bible edition, commentary sources, confidence levels or denominational settings. Keyword presence cannot determine whether a lyric uses a biblical term faithfully, and absence of a word does not prove absence of a doctrine. Treat every score as a lead for human reading. The vendor should expose why a category was assigned, cite the lines involved and let churches configure their own review criteria.

Team feedback, Messenger and imports: where church data accumulates

Teams can share setlists, discuss plans in Messenger, view training, react and submit anonymous feedback. The help center says a Planning Center browser extension imports songs, while the August 2026 release added CSV song import and key editing. Unlimited team members are advertised across tiers; admin and service counts are what change. Team and future Ministry levels aim to add automated reporting and cross-service comparison.

These conveniences consolidate sensitive context: member identity, church profile, messages, sermon passages, private songs, lyrics, service history and anonymous responses. Anonymous to another team member does not necessarily mean anonymous to the platform administrator or vendor, and the public docs do not explain thresholds or re-identification safeguards. Import only material the church is licensed and authorized to store. Restrict admins, define a feedback-retention policy, export critical records and never use sentiment data to evaluate a volunteer’s spirituality or employment.

Pricing

Best value

Free

$0 forever

No credit card required. Includes one service, unlimited setlists, gap analysis, one admin, unlimited team members and the last 30 days of data. The comparison table says recommendations and private songs are not included. It is enough to evaluate the basic workflow without a timed trial.

Leader

$12 or $15 USD/month shown

For one service and one admin, adding unlimited data history, future gap-analysis recommendations and private songs. The page renders $12 monthly beside $15 “billed monthly (actually)” without a clear billing-cycle label. Confirm the final checkout amount and renewal period rather than assuming $12 is month-to-month.

Team

$39 or $45 USD/month shown

Starts with two services, unlimited admins, future automated reports and cross-service analytics; each additional service is advertised at $10 per month. As with Leader, the page shows two prices and a Coming Soon state. Verify whether the selected plan is currently purchasable and which advertised features are live.

Ministry

Custom · coming soon

Planned for multi-location operations with unlimited services and locations, Song 360, reports, suggestions, community and curation tools. This is roadmap material, not a generally available plan to budget against.

Early supporter

$240 or $480 USD/year

The separate Support Us page offers Grow and Scale contributions tied to a promised 10% or 25% lifetime discount on future paid plans, subject to program rules and active supporters. This is not the same as buying the current Leader or Team tier; read the discount examples before contributing.

The free plan is substantial: unlimited setlists and team members, one service, one administrator, basic gap analysis and 30 days of data with no card. A small church can learn whether the generator and feedback rhythm are useful before accepting recurring billing.

The published paid pricing is not clean enough to quote as a single checkout promise. Leader displays $12 and $15 per month; Team displays $39 and $45, plus $10 per extra service. The likely explanation is discounted versus month-to-month billing, but the visible text does not name an annual term and includes the stray word “actually.” This review reports both amounts rather than inventing the missing label.

The same page simultaneously describes multiple tiers, marks several as Coming Soon and says that during open beta there is one team plan for all available features. This may be a migration between models. Screenshot the checkout, identify which features are live, confirm currency and tax, and ask support whether downgrading removes history beyond 30 days.

Terms say subscriptions renew indefinitely until cancellation, fees are generally paid in advance and change-of-mind refunds are not promised. The terms name Chargebee as payment provider, while the current pricing FAQ says cards are processed via Stripe. That is another documentation mismatch worth confirming at checkout.

The Support Us program is separate. Grow costs $240 per year for a stated 10% lifetime discount and Scale $480 for 25%, with discount examples based on how many active team supporters participate. Contribute only if supporting development is worthwhile on its own; the value of a discount on future prices and tiers cannot be guaranteed today.

Where Asaph falls behind

Pricing clarity is the most visible weakness. A church budget needs one active price, billing term and feature state per tier. The current page gives paired prices, duplicated Ministry copy, malformed monthly language, “Coming Soon” buttons and an open-beta FAQ describing a different one-plan model.

AI transparency trails the ambition of the claims. Calling an analysis theological or biblically sound requires more than marketing. Publish model providers, data handling, evaluation rubrics, Scripture and source references, limitations, correction mechanisms and change logs when the scoring system changes.

Privacy documentation predates the present product. The April 2023 policy is a broad Australian template that lists contact, address, age, payment, analytics, advertising, geolocation, third-party information and international cloud providers, but it does not name the AI service, song-lyric processing, message and feedback retention or exact subprocessors.

Terms and pricing disagree about payments. Terms name Chargebee; the pricing page says Stripe. Terms contain duplicated and oddly numbered sections and say the platform is a no-cost service while also defining paid tiers. Legal pages need a current product-specific edit.

Roadmap is mixed into the live offer. Dashboard, CSV import, recommendations, weekly reports and Planning Center functions appear as coming soon in some current surfaces while version notes say some have arrived. A dated feature-status page would prevent buying expectations from outrunning reality.

The platform does not replace mature worship operations software. Volunteer scheduling, service plans, chord and lyric licensing, presentation, multitracks, rehearsal files, stage communication and check-in remain elsewhere. The Planning Center extension reduces duplication but does not make Asaph the system of record.

Ratings and adoption claims are weak evidence. “900+ worship leaders” is vendor-reported without methodology, while one US Apple rating says nothing about hundreds of teams. There are no public accuracy benchmarks for song analysis or controlled outcomes for participation.

Asaph vs. Planning Center Services vs. WorshipTools

Asaph is an analysis and recommendation layer. Planning Center Services is the mature operational system for scheduling people, arranging service orders, attaching files, managing plans and coordinating volunteers. Asaph can import songs from Planning Center, but it does not replace that operational depth. A church already using Services should treat Asaph as an optional companion and decide whether the added AI insight justifies another database and subscription.

WorshipTools combines planning with a broader church-music ecosystem: presenter software, charts, music access, scheduling and team workflows. PraiseCharts and MultiTracks concentrate on licensed arrangements, keys, stems and rehearsal resources. Those products help a team perform and present selected songs. Asaph’s distinctive question comes earlier: which songs should be selected, in what flow, and what patterns does the church’s own history reveal?

A spreadsheet may still be the best alternative for a small church with twenty stable songs, one weekly service and strong human communication. Asaph becomes more compelling when rotation, multiple services, feedback and sermon alignment create real planning overhead. It becomes less compelling when a team wants software to make interpretive decisions it has not learned to discuss together.

The bottom line

Asaph takes a more responsible shape than a generic “AI worship leader.” It uses a bounded song library and sermon context, shows its suggestions, lets people lock and revise songs, and tries to learn from a local congregation. Its glory–gravity–grace view, energy arc, theme gaps and rotation warnings can uncover habits a hurried planner misses. Unlimited free setlists and team members make the concept genuinely testable. But the words “theology” and “biblical soundness” carry responsibility the public docs have not met. No rubric or AI provider is named, privacy language predates the generative workflow, and payment documents conflict. Pricing and roadmap states are so muddled that a church cannot confidently budget from the public page alone. Use the free tier with a small, authorized library. Compare every analysis with the full lyrics, Scripture, church teaching and the people who will sing. Invite feedback but interpret it compassionately. Ask Asaph for current privacy and billing answers before importing private material or subscribing. The platform can be a sharp second set of questions. It should never become the final voice on what a congregation sings.

Alternatives to Asaph

Frequently asked questions

What does Asaph do?

Asaph imports or stores a church’s song library, generates editable setlists from a sermon passage or theme, analyzes energy and theological themes, tracks rotation, collects team feedback and supports team messaging and training.

Is Asaph free?

Yes. The Free tier is advertised at $0 forever with no card, one service, unlimited setlists, basic gap analysis, one admin, unlimited team members and 30 days of history. Some advanced recommendations, private songs, longer history and reports belong to paid or future tiers.

How much do Asaph paid plans cost?

The pricing page shows Leader at both $12 and $15 USD per month and Team at both $39 and $45, plus $10 for each extra service. It does not render the billing-period distinction clearly and marks parts as coming soon. Confirm the actual checkout terms with Asaph.

Can Asaph replace Planning Center?

Usually no. Asaph can import songs through a Planning Center extension and adds AI analysis, but Planning Center remains much deeper for volunteer schedules, service operations, files and church administration. They are better viewed as companion tools.

Can Asaph determine whether a worship song is biblically sound?

It claims theological and biblical-soundness analysis, but no public rubric, model, source corpus or confidence method is available. Its score can flag lyrics for human attention; pastors and worship leaders remain responsible for interpreting the whole song in context.

How does Asaph use church data and AI?

The product says AI analyzes songs, sermon passages, history and local feedback. Its 2023 privacy policy broadly allows cloud providers and international processing but does not name an AI provider or current prompt-retention terms. Ask support before uploading confidential sermons, private lyrics or sensitive feedback.

Does Asaph have iPhone and Android apps?

Yes. The official help center advertises iOS and Android, and Apple lists a native iPhone/iPad app requiring iOS 15 or later. The Apple interface is English only, and the US listing has one rating.

Sources & further reading

More Worship Apps

Try Asaph