journey-all-2026-04-02
=== JOURNEY REPORT: cwa-board-leader-evaluation === Date: 2026-04-02 Persona: Board Leader Mark (55, Elder/Chair of operations committee, tech comfort: high) Goal: "I need to evaluate ChurchWiseAI for my church and bring a recommendation to the board meeting next Tuesday." Property: churchwiseai.com Entry: https://churchwiseai.com
STEP 1: homepage -- https://churchwiseai.com/
Q1 (SEE): The dominant element is a bold hero headline: "No Visitor Left Behind. No Prayer Request Forgotten." Below it, a subheading: "Theologically-aware AI care agents that answer calls, capture prayer requests, and follow up with visitors 24/7." Three trust badges are visible: "39 Ministry Tools," "17 Traditions," "218K+ Churches." Two CTAs compete for attention: "See Plans & Pricing" and "Try the Demo." The navigation includes Products, Pricing, Features, Resources, Contact, and "Try a Live Demo." Further down: sections on "Meet Your AI Ministry Team" with Care Agent and Coordinator Agent descriptions, common pastor concerns (FAQ), and a phone number in the footer: (888) 603-0316.
Q2 (SPEC): [PASS] Hero communicates AI for churches -- "AI care agents" in the subheading [PASS] Clear value proposition -- "answer calls, capture prayer requests, follow up with visitors 24/7" [PASS] Trust indicators present -- 39 Ministry Tools, 17 Traditions, 218K+ Churches [PASS] Product capabilities mentioned -- voice ("answer calls"), chat, 24/7 [PASS] Pricing CTA immediately visible ("See Plans & Pricing") [CONCERN] Homepage leads with emotional/ministry language ("No Visitor Left Behind") rather than direct product description -- persona risk for a business executive
Q3 (PERSONA): "I'm Mark, 55. The headline is emotional -- 'No Visitor Left Behind' -- and that's fine for pastors, but I need to know what this thing DOES. I scan down and find 'AI care agents that answer calls, capture prayer requests, and follow up with visitors 24/7' -- okay, now I'm getting somewhere. That's a product description I can put in a memo. The 39 Ministry Tools and 17 Traditions numbers catch my eye. I click 'See Plans & Pricing' within 20 seconds. The homepage didn't waste my time, but it took 10 seconds too long to get to the point. I'd have preferred 'AI Phone & Chat Agents for Churches' as the headline."
Q4 (BETTER): 1. [HIGH IMPACT] Add a one-line product description ABOVE the emotional headline: "AI that answers your church's phone and chat 24/7" -- business evaluators need the category in 3 seconds 2. [MEDIUM IMPACT] Add a "For Board Members" or "Evaluate for Your Church" CTA that links to a one-page summary with pricing, security, ROI 3. [LOW IMPACT] Show a 30-second video auto-playing (muted) of the chatbot in action in the hero
Q5 (GOAL): Step 1 of 5. Goal: "Evaluate ChurchWiseAI for board presentation." Mark understands the product category within 30 seconds. The hero communicates enough to proceed. Progress: 20%. Path: CLEAR (Pricing link visible). Risk: LOW. Momentum: GAINING.
VERDICT: PASS
STEP 2: pricing -- https://churchwiseai.com/pricing
Q1 (SEE): Three main tiers dominate: Starter ($14.95/mo), Pro ($34.95/mo, marked "Most Popular"), and Suite ($59.95/mo). A channel selector shows Chat Only, Voice Only, and Voice + Chat options. Pro is visually highlighted. Each tier lists features in bullet points. An annual/monthly toggle is present with "2 months free" on annual. Below the main tiers: add-on products (Premium Church Page $9.95, Sermon Illustrations $9.95, AI Starter Kit $4.95). Trial messaging: "14-day free trial" on chat plans. Footer: "No long-term contracts. Cancel anytime."
Q2 (SPEC): [PASS] Clear tier names -- Starter, Pro, Suite [PASS] Prices visible -- $14.95 to $99.95 range [PASS] Feature comparison present with bullet lists per tier [PASS] "Most Popular" badge on Pro [PASS] Annual savings shown with toggle ("2 months free") [PASS] Cancellation language present -- "No contracts. Cancel anytime." [PASS] Agent counts match features.yaml -- Starter has Care + Coordinator (2); Pro has all 4 [PASS] Tool counts match -- 12, 35, 39 [CONCERN] Three channel options (Chat, Voice, Voice+Chat) x 3 tiers = potentially 9 price points visible. Mark needs to explain this in one sentence to the board.
Q3 (PERSONA): "I'm Mark, 55. I see three tiers -- good, not too many. Pro at $34.95/mo for chat is flagged 'Most Popular' -- that's my anchor. The Voice + Chat bundle at $49.95-$99.95 is where I'll focus for the board since our church needs both. Let me do the math: Pro Voice + Chat is $79.95/mo or about $960/year. That's less than a part-time receptionist. I can present this. The annual toggle saves money but voice plans are monthly only -- that's a wrinkle I need to explain. The 14-day free trial on chat is good but I wish voice had a trial too. Feature comparison is clear enough for a one-page memo. I have what I need on pricing."
Q4 (BETTER): 1. [HIGH IMPACT] Add a "Recommended for churches of [X] members" tag to each tier -- board members need to self-select without reading every feature 2. [HIGH IMPACT] Add a "Total Annual Cost" calculator or at minimum show annual totals per tier (not just monthly) -- board members budget annually 3. [MEDIUM IMPACT] Add a "Why no annual for voice?" tooltip -- otherwise board members will ask and the pastor won't know 4. [LOW IMPACT] Add a "Download pricing comparison PDF" button -- board members want to circulate a document, not share a URL
Q5 (GOAL): Step 2 of 5. Goal: "Evaluate ChurchWiseAI for board presentation." Mark has concrete pricing. He can write the budget line item. The channel matrix (Chat/Voice/Both) adds slight complexity but is manageable. Progress: 40%. Path: CLEAR. Risk: LOW. Momentum: STEADY.
VERDICT: PASS
STEP 3: security-and-privacy -- https://churchwiseai.com/privacy
Q1 (SEE): A comprehensive privacy policy with 17 clearly-labeled sections. The page begins with "Who We Are" and proceeds through data collection categories, AI-specific practices, call recording, data retention, security, user rights, children's privacy, international transfers, cookies, email compliance, automated decision-making, and breach notification. The document is text-heavy but well-organized with section headings. Key details visible: AES-256 encryption, SOC 2-compliant providers, named third-party processors (OpenAI, Anthropic, Google, Twilio, Cartesia), prayer request data handling, voice recording retention (90 days), PIPEDA/CCPA compliance, and a privacy contact email.
Q2 (SPEC): [PASS] Data storage addressed -- AES-256 encryption via Supabase on AWS [PASS] Third-party AI processors NAMED -- OpenAI, Anthropic, Google, Twilio, Cartesia [PASS] Prayer request confidentiality addressed -- express consent required, pastoral data access controls [PASS] Call recording handling detailed -- 90-day retention, transcripts 1 year, caller notification at start [PASS] Data deletion rights specified -- processed within 30 days [PASS] GDPR/CCPA mentioned -- PIPEDA primary, CCPA/CPRA compliance stated [PASS] Children's privacy (COPPA) addressed -- not intended for under 13, parental consent required [PASS] Cancellation data retention -- 90-day read-only, then permanent deletion [PASS] "We do not sell personal information" -- explicit statement
Q3 (PERSONA): "I'm Mark, 55. This is a solid privacy policy -- better than most SaaS tools I've evaluated. They name their AI providers (Anthropic, Google, OpenAI) which is exactly what I need for the board memo. Prayer request data has explicit consent requirements and role-based access -- I can tell the board 'only authorized staff see prayer requests.' Voice recordings kept 90 days, transcripts 1 year -- reasonable. API data not used to train models -- that's the key line I'll quote. The 30-day deletion after cancellation with 90-day reactivation window is fair. I'm satisfied on security. My only concern: no SOC 2 certification of ChurchWiseAI itself, only of their providers. But for a startup, that's acceptable."
Q4 (BETTER): 1. [HIGH IMPACT] Add a "Security Overview for Decision Makers" one-page summary at the TOP of the privacy page -- board members won't read 17 sections, they need 5 bullet points 2. [MEDIUM IMPACT] Add a "Data Flow Diagram" showing: Church Data -> Supabase (AWS) -> AI Provider (API only, no training) -> Response 3. [MEDIUM IMPACT] Add specific mention of SOC 2 Type II certification status (or timeline to obtain) 4. [LOW IMPACT] Add a downloadable "Security & Compliance Summary" PDF that board members can circulate
Q5 (GOAL): Step 3 of 5. Goal: "Evaluate ChurchWiseAI for board presentation." Mark passed the security gate. The privacy policy is thorough, names processors, addresses prayer requests explicitly. Progress: 60%. Path: CLEAR. Risk: LOW. Momentum: STEADY.
VERDICT: PASS
STEP 4: demo -- https://churchwiseai.com/demo
Q1 (SEE): The demo page offers two major interactive options: (1) A live chatbot interface embedded on the page with pre-built scenarios (grief support, prayer requests, crisis response, pastoral connect, theological questions) and "Try this scenario" buttons; (2) Voice agent phone numbers -- US: (469) 615-2221 and Canada: (365) 825-4095 -- that can be called live with no signup. The page explicitly positions this as "No Obligation" with "Ask anything. No pressure, no hard sell." Agent cards show tool inventories. A "Schedule a call" CTA is available for live sales demos. The demo church is Grace Community Church.
Q2 (SPEC): [PASS] Interactive experience available -- live chatbot embed with scenario buttons [PASS] Phone number available for voice demo -- US and Canada numbers listed [PASS] No login wall -- "No Obligation" messaging, fully accessible [PASS] Book-a-call option present -- "Schedule a call" CTA [PASS] Multiple demo scenarios available -- grief, prayer, crisis, pastoral, theological [PASS] This is exactly what a board meeting needs -- a phone number anyone can call live
Q3 (PERSONA): "I'm Mark, 55. This is perfect for the board meeting. I can project this page, let the chatbot run a grief support scenario live, AND give the board the phone number (469) 615-2221 to call during the meeting. No one needs to sign up for anything. The scenario buttons make it easy to show specific capabilities without fumbling. This is the strongest page I've seen so far. I'm writing this demo page URL in my board recommendation right now. The only thing missing is a pre-recorded video walkthrough for board members who prefer watching to interacting."
Q4 (BETTER): 1. [MEDIUM IMPACT] Add a 2-minute video walkthrough of a complete chatbot conversation for board members who prefer passive evaluation 2. [MEDIUM IMPACT] Add a "Board Meeting Demo Kit" section with: (a) phone number to call, (b) 5 suggested test questions, (c) what to watch for in the responses 3. [LOW IMPACT] Add a QR code for the phone number so board members can scan and call from their own phones during the meeting
Q5 (GOAL): Step 4 of 5. Goal: "Evaluate ChurchWiseAI for board presentation." Mark has a live demo he can present. Phone number + interactive chat + no signup = ideal for a board meeting. Progress: 80%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 5: comparison-and-roi -- https://churchwiseai.com/compare
Q1 (SEE): The comparison page lists six alternatives: Answering Services ($200-500+/mo), Voicemail systems, Generic Chatbots ($0-300+/mo), Tawk.to (free, requires live staff), Intercom ($74+/mo per seat), and ChatGPT. Each alternative has a positioning paragraph. A dedicated "Why not just use ChatGPT?" section addresses the most common board objection: ChatGPT lacks church-specific knowledge, can't take action, has no theological guardrails, and no integrations. An ROI Calculator is referenced (/voice#roi) but no specific ROI numbers appear on this page. No case studies or testimonials are present. Cancellation terms are not mentioned here.
Q2 (SPEC): [PASS] Alternatives listed -- 6 competitors/alternatives compared [PASS] "Why not ChatGPT?" addressed directly and in detail [PASS] Cost comparison -- answering services at $200-500+/mo vs CWA [PASS] Competitive positioning -- purpose-built for churches vs generic tools [FAIL] No ROI data or time-saved metrics on this page -- ROI Calculator is referenced but lives elsewhere -- SPEC VIOLATION [FAIL] No case studies or testimonials -- Mark has nothing to cite from a real church -- SPEC VIOLATION [FAIL] No cancellation terms on compare page -- board members checking here for lock-in risk won't find it -- PERSONA RISK [CONCERN] ROI Calculator link goes to /voice#roi which is a different page -- the compare page itself lacks quantitative ROI
Q3 (PERSONA): "I'm Mark, 55. The ChatGPT comparison is exactly what I needed -- I can copy these four points verbatim into my memo. The cost comparison to answering services ($200-500+ vs $49.95) is compelling. But where are the hard numbers? How many calls does the AI handle per month? What's the average response time? How many visitor contacts get captured? I need at least ONE case study from a real church -- '350-member Baptist church saved 15 hours/week' -- something I can put in front of the board. Without that, I'm making the ROI argument myself and hoping the board trusts my judgment. The 'Why not ChatGPT?' section saves me from the biggest objection, but 'Why not hire a part-time receptionist?' is unanswered. That's what my treasurer will ask."
Q4 (BETTER): 1. [HIGH IMPACT] Add 2-3 concrete ROI metrics ON this page: "Average church handles 47 calls/week through the AI" or "87% of prayer requests captured vs 23% before CWA" 2. [HIGH IMPACT] Add at least one case study -- even from a demo/beta church -- with real numbers 3. [HIGH IMPACT] Add a "vs. Hiring Staff" comparison section -- board treasurers will ask this 4. [MEDIUM IMPACT] Add a "Board FAQ" section: cancellation policy, data portability, staff adoption, multi-user access 5. [MEDIUM IMPACT] Make the ROI Calculator accessible from this page (embed or prominent link)
Q5 (GOAL): Step 5 of 5. Goal: "Evaluate ChurchWiseAI for board presentation." Mark has pricing, security, a live demo, and competitive positioning. He's MISSING hard ROI numbers and case studies. He can write the recommendation but it will be weaker without quantitative proof. Progress: 85%. Path: COMPLETE but with gaps. Risk: MEDIUM (board may ask for ROI data Mark doesn't have). Momentum: SLIGHTLY DECLINING.
VERDICT: CONCERN Missing ROI metrics, case studies, and "vs. hiring staff" comparison leave Mark without quantitative ammunition for the board presentation.
========================================================================
OUTCOME VERIFICATION [VERIFIED] Pricing page shows clear monthly costs that can be summarized in one sentence -- "Pro Voice+Chat: $79.95/mo" [VERIFIED] Privacy policy addresses prayer request data handling explicitly -- consent required, role-based access [VERIFIED] Demo page offers no-signup experience -- chatbot + phone numbers, no login wall [NOT VERIFIED] Comparison page does NOT address "Why not just use ChatGPT?" with a specific standalone competitor name... wait, it does -- VERIFIED. "Why not just use ChatGPT?" section exists.
FAILURE MODE CHECK "Homepage is all emotional ministry language" -- CLEAR (functional product description present in subheading) "Pricing has more than 4 visible tiers" -- CLEAR (3 tiers with channel options, not 4+ tiers) "No Most Popular recommendation" -- CLEAR (Pro marked "Most Popular") "Privacy policy doesn't mention prayer requests or voice recordings" -- CLEAR (both explicitly addressed) "Demo requires signup" -- CLEAR (no signup required, fully open) "No competitive comparison" -- CLEAR (6 alternatives compared, ChatGPT section detailed) "No case studies or social proof" -- TRIGGERED -- no case studies, no testimonials on compare page "No easy cancellation language" -- CLEAR (on pricing page: "Cancel anytime. No contracts.") "No multi-user/team mention" -- CLEAR (Suite tier mentions "role-based team access, 9 roles")
========================================================================
SUMMARY Steps completed: 5/5 Steps passed: 4 Steps with concerns: 1 Steps failed: 0 Goal achieved: PARTIAL
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: 1. Compare page lacks concrete ROI data (time saved, calls handled, visitor follow-up rates) -- referenced calculator lives on a different page 2. No case studies or testimonials from real churches anywhere in the evaluation journey
P1 GOAL BLOCKED: None
P2 PERSONA RISKS: 1. Homepage leads with emotional language before product description -- business evaluators need the category in 3 seconds 2. No "vs. hiring staff" comparison -- the treasurer's objection is unanswered 3. No downloadable PDF for board circulation (pricing summary or security overview)
P3 IMPROVEMENTS: 1. Add "Board Meeting Demo Kit" with phone number, test questions, and talking points 2. Add church-size recommendation badges on pricing tiers 3. Add annual total cost calculator 4. Add Security Overview one-pager at top of privacy policy 5. Add "For Board Members" evaluation landing page
TOTAL FINDINGS: 10 (2 P0, 0 P1, 3 P2, 5 P3)
========================================================================
RECOMMENDATION The CWA board leader evaluation journey is STRONG on the fundamentals: pricing is clear, security is thorough, the demo is excellent (phone number + no-signup chatbot), and the ChatGPT comparison is well-written. However, the journey falls short on quantitative proof -- no ROI metrics, no case studies, no "vs. hiring staff" comparison. A systematic board evaluator like Mark will notice these gaps. The recommendation is CONDITIONALLY PASSING for launch -- the product can sell to individual pastors today, but board-driven purchases (which represent larger churches and higher-value contracts) need ROI ammunition. Priority fix: add 2-3 concrete metrics and one case study to the compare page.
=== JOURNEY REPORT: cwa-chatbot-training === Date: 2026-04-02 Persona: Pastor Tom (44, Lead pastor at 180-member community church, tech comfort: medium) Goal: "I just signed up for ChurchWiseAI. I need to train the chatbot with my church's information and verify it works before sharing it with my congregation." Property: churchwiseai.com Entry: https://churchwiseai.com/admin/[token]
STEP 1: training-tab-overview -- https://churchwiseai.com/admin/[token]
Q1 (SEE): This is a CSR page -- WebFetch cannot render the client-side content. Per acceptance spec (starter-chat.md #E30-E37), the Training tab should show sub-sections: Church Knowledge, This Week, FAQs, Theology, Agents, Safety, Simulator, and Progress. A progress indicator should show completion percentage. The training workflow is the core onboarding experience for new subscribers.
Q2 (SPEC): [N/A] Cannot verify via WebFetch -- CSR page requires authentication [CHECK] Per acceptance spec, training tab should have progress indicator and clear sub-sections [CHECK] Per acceptance spec, Church Knowledge should be the first/prominent section
Q3 (PERSONA): "I'm Tom, 44. I just paid $14.95 and I'm staring at a dashboard I've never seen before. I need to know: What do I do FIRST? If there's a progress bar that says '0% complete -- start with Church Knowledge,' I'll click that. If I see 8 sub-tabs with no indication of priority, I'll freeze. I'm not a tech person -- I'm a pastor who just made a financial commitment. The first 5 minutes in this dashboard determine whether I feel smart or stupid. Please don't make me feel stupid."
Q4 (BETTER): 1. [HIGH IMPACT] Add a guided onboarding wizard that walks Tom through each section in order, not just tabs he has to figure out 2. [HIGH IMPACT] Pre-populate fields with examples: "e.g., Sunday 9:00 AM and 11:00 AM Traditional Service" so Tom knows the expected format 3. [MEDIUM IMPACT] Add a "Quick Start" option: "Just add service times and a welcome message to get started -- you can add more later" 4. [LOW IMPACT] Add a "Watch: 2-minute setup walkthrough" video link at the top of the training tab
Q5 (GOAL): Step 1 of 5. Goal: "Train the chatbot and verify it works." Tom needs to understand the training workflow. The training tab's clarity determines whether Tom proceeds or calls for help. Progress: 10%. Path: UNCLEAR (cannot verify). Risk: MEDIUM (first-time dashboard experience is critical). Momentum: NEUTRAL.
VERDICT: CONCERN Cannot visually verify. CSR page -- acceptance spec and Playwright tests are the authoritative source. Risk is the first-time onboarding UX.
STEP 2: church-knowledge -- https://churchwiseai.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per starter-chat.md #E30, Church Knowledge should contain text areas for: church description, service times, staff, ministries, and welcome message. Auto-save or explicit save button should be present. Character limit indicators and help text explaining what good content looks like should guide the user.
Q2 (SPEC): [N/A] Cannot verify field presence via WebFetch [CHECK] Spec requires help text/examples in text fields [CHECK] Spec requires auto-save or explicit save button [CHECK] Spec requires character limit indicators
Q3 (PERSONA): "I'm Tom, 44. I type 'Sunday 9:00 AM and 11:00 AM, Wednesday 7:00 PM Bible Study' into the service times box. Was that enough? Should I mention that doors open at 8:30? Should I say 'nursery available'? I need help text -- show me what a GOOD entry looks like, not just an empty box. If there's an example that says 'Sunday: 9:00 AM Traditional Worship, 11:00 AM Contemporary Worship (nursery available for both services)' -- I'll model mine after that. Without examples, I'm guessing, and I'll second-guess everything I type."
Q4 (BETTER): 1. [HIGH IMPACT] Add example/placeholder text in each field showing the ideal format and level of detail 2. [HIGH IMPACT] Add a "How much is enough?" indicator -- "You've entered enough for basic chatbot responses. Add more for better answers." 3. [MEDIUM IMPACT] Auto-save with visible confirmation ("Saved 2 seconds ago") -- losing work is trust-destroying 4. [LOW IMPACT] Add a "Import from your website" button that scrapes basic church info from their existing website
Q5 (GOAL): Step 2 of 5. Goal: "Train the chatbot and verify it works." Tom is adding core church data. This is the foundation for accurate responses. Progress: 30%. Path: ON TRACK if fields are clear. Risk: MEDIUM (no help text = guessing). Momentum: CAUTIOUSLY POSITIVE.
VERDICT: CONCERN Cannot verify help text quality or save UX. CSR page risk: empty fields without examples will overwhelm a medium-tech-comfort pastor.
STEP 3: theology-and-agents -- https://churchwiseai.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per starter-chat.md #E33-E34, the Theology section should have a selector with 17 traditions. Agent configuration should show available agents (Coordinator and Care for Starter tier) with personality/tone settings and a preview of agent behavior.
Q2 (SPEC): [N/A] Cannot verify tradition selector or agent config via WebFetch [CHECK] Spec requires 17 traditions in selector [CHECK] Spec requires agent personality/tone settings [CHECK] Starter tier should show 2 agents (Coordinator + Care), not 4
Q3 (PERSONA): "I'm Tom, 44. I picked 'Non-denominational' from the tradition dropdown -- that was easy. But now there's something about 'agents' and I see 'Coordinator Agent' and 'Care Agent.' What do those mean? I'm a pastor, not an AI engineer. If there's a plain-English explanation like 'The Coordinator Agent is your digital receptionist -- it answers questions about service times, events, and directions. The Care Agent handles prayer requests and sensitive conversations with empathy,' then I get it. If it just says 'Coordinator' and 'Care' with a toggle, I'm confused and I'll leave them at defaults without understanding what I just configured."
Q4 (BETTER): 1. [HIGH IMPACT] Add plain-English descriptions of each agent's role with real conversation examples 2. [MEDIUM IMPACT] Add a tone preview: "Your chatbot will sound like this: 'Hey there! Welcome to Community Church...'" vs "Good morning. Thank you for reaching out to Community Church..." 3. [MEDIUM IMPACT] Make agent configuration OPTIONAL for first-time setup -- sensible defaults that work out of the box 4. [LOW IMPACT] Add a "Preview my chatbot personality" button that generates a sample conversation based on current settings
Q5 (GOAL): Step 3 of 5. Goal: "Train the chatbot and verify it works." Theology and tone set. The chatbot should now reflect Tom's church personality. Progress: 50%. Path: ON TRACK. Risk: MEDIUM (agent config jargon). Momentum: STEADY.
VERDICT: CONCERN Cannot verify. Agent terminology risk -- "Coordinator" and "Care" are internal product terms, not pastor vocabulary.
STEP 4: simulator -- https://churchwiseai.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per starter-chat.md #E36, the Simulator should provide a chat interface within the dashboard where Tom can type messages and see chatbot responses. Responses should use church-specific data from the training sections.
Q2 (SPEC): [N/A] Cannot verify simulator functionality via WebFetch [CHECK] Spec requires chat simulator interface within dashboard [CHECK] Spec requires responses to use church-specific trained data
Q3 (PERSONA): "I'm Tom, 44. This is my moment of truth. I type 'What time is Sunday service?' and I hold my breath. If the chatbot says '9:00 AM and 11:00 AM' -- exactly what I entered -- I'm going to smile and feel like a genius. If it says 'I can help you find information about our services' without giving the actual times, I'm going to think this doesn't work and I wasted $14.95. I'll test 3 more questions: 'Where is the church?', 'Who is the pastor?', and 'Do you have kids ministry?' If it nails at least 3 out of 4, I'm ready to share this with my wife."
Q4 (BETTER): 1. [HIGH IMPACT] Add suggested test questions: "Try asking: 'What time is Sunday service?' or 'How do I visit for the first time?'" 2. [MEDIUM IMPACT] Show which training section the answer came from: "Source: Church Knowledge > Service Times" 3. [MEDIUM IMPACT] Add a "Train more" prompt when the chatbot gives a generic answer: "The chatbot couldn't find this info. Add it in Church Knowledge." 4. [LOW IMPACT] Add a side-by-side view: left panel = what you trained, right panel = how the chatbot uses it
Q5 (GOAL): Step 4 of 5. Goal: "Train the chatbot and verify it works." If the simulator works correctly, Tom's confidence will be high. Progress: 70%. Path: ON TRACK. Risk: HIGH (if simulator gives wrong/generic answers, Tom loses all confidence). Momentum: CRITICAL MOMENT.
VERDICT: CONCERN Cannot verify simulator accuracy. This is the make-or-break step. If the simulator returns generic responses instead of trained data, the entire journey fails.
STEP 5: public-chat-page -- https://churchwiseai.com/chat/[slug]
Q1 (SEE): This is a partially-SSR page but requires a specific church slug. The public chat page should show: church branding (name, logo), a chat input field, a welcome message from the chatbot, and responses that match trained church data. Without a specific slug to test, this is partially verifiable.
Q2 (SPEC): [N/A] Cannot verify specific church's public chat page without a real slug [CHECK] Spec requires church name and branding on public chat page [CHECK] Spec requires welcome message from chatbot [CHECK] Spec requires responses matching trained data
Q3 (PERSONA): "I'm Tom, 44. I opened the public chat page in a new tab and... does it have our church name? Is the welcome message warm and inviting? I'm looking at this through my congregation's eyes now. I'll send this link to my wife first -- if she says it looks professional and the answers are right, I'll share it with the deacons. If the chat page shows a generic 'ChurchWiseAI' brand instead of 'Community Church,' I'll be embarrassed and won't share it."
Q4 (BETTER): 1. [HIGH IMPACT] Add a "View Chat Page" button in the dashboard that opens the public URL in a new tab 2. [MEDIUM IMPACT] Add a "Share with your congregation" section with pre-written text for email, bulletin, and social media 3. [MEDIUM IMPACT] Add QR code generation for the chat page URL (for bulletins and lobby displays) 4. [LOW IMPACT] Add a "First impressions check" -- the dashboard reminds Tom to test the public page from a different device
Q5 (GOAL): Step 5 of 5. Goal: "Train the chatbot and verify it works." GOAL ACHIEVED if the public chat page shows Tom's church name and the chatbot answers "What time is Sunday service?" with the correct times. Progress: 90%. Path: NEARLY COMPLETE. Risk: MEDIUM (branding and data accuracy). Momentum: POSITIVE.
VERDICT: CONCERN Cannot verify public chat page rendering or data accuracy without a live church slug. Visual verification requires Playwright or manual testing.
========================================================================
OUTCOME VERIFICATION [UNTESTABLE] Public chat page displays church name and branding -- requires live church subscription [UNTESTABLE] Chatbot response to 'service times' includes trained times -- requires live chatbot interaction [UNTESTABLE] Simulator and public chat produce consistent responses -- requires authenticated access
FAILURE MODE CHECK "Training tab has no progress indicator" -- UNTESTABLE (CSR page) "No help text or examples in text fields" -- UNTESTABLE (CSR page) "Church Knowledge doesn't auto-save" -- UNTESTABLE (CSR page) "Simulator is broken or hidden" -- UNTESTABLE (CSR page) "Chatbot gives generic response ignoring trained data" -- UNTESTABLE (requires live interaction) "Public chat page shows default branding" -- UNTESTABLE (requires live subscription) "Lag between saving training data and chatbot updating" -- UNTESTABLE "No 'View Chat Page' link from dashboard" -- UNTESTABLE (CSR page) "Agent configuration is too technical" -- UNTESTABLE but HIGH RISK based on terminology analysis
========================================================================
SUMMARY Steps completed: 5/5 Steps passed: 0 Steps with concerns: 5 Steps failed: 0 Goal achieved: UNTESTABLE (all steps are CSR, require auth)
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: None verifiable
P1 GOAL BLOCKED: None verifiable
P2 PERSONA RISKS: 1. Agent terminology ("Coordinator," "Care") is product jargon, not pastor vocabulary -- needs plain-English descriptions 2. Empty training fields without examples will overwhelm a medium-tech-comfort pastor 3. Simulator accuracy is the make-or-break moment -- generic responses destroy confidence
P3 IMPROVEMENTS: 1. Add guided onboarding wizard 2. Pre-populate fields with format examples 3. Add suggested test questions to simulator 4. Add "View Chat Page" button with congregation sharing tools 5. Add "Quick Start" minimum viable training option 6. Add tone preview for agent configuration
TOTAL FINDINGS: 9 (0 P0, 0 P1, 3 P2, 6 P3)
========================================================================
RECOMMENDATION This entire journey is UNTESTABLE via WebFetch because all 5 steps are CSR admin dashboard pages. Every step is marked CONCERN due to inability to visually verify. The persona risks identified (agent jargon, empty fields, simulator accuracy) are based on acceptance spec analysis and are HIGH PRIORITY for Playwright/manual testing. This journey CANNOT be evaluated as passing or failing until the admin dashboard is tested with a live account. Recommend: run Playwright e2e tests against the admin dashboard training flow with the demo church account, or conduct a manual walkthrough with the founder.
=== JOURNEY REPORT: cwa-admin-monday-morning === Date: 2026-04-02 Persona: Church Admin Linda (47, Full-time church office admin, tech comfort: medium) Goal: "It's Monday morning. I need to check what happened over the weekend -- any prayer requests, visitor contacts, callback requests, or missed calls." Property: churchwiseai.com Entry: https://churchwiseai.com/admin/[token]
STEP 1: dashboard-overview -- https://churchwiseai.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per starter-chat.md #D25-D28, the Overview tab should show: stat cards (conversations, prayer requests, visitor contacts, callbacks), a recent activity feed, a getting started checklist (if incomplete), and share links for chat/care pages.
Q2 (SPEC): [N/A] Cannot verify stat cards or activity feed via WebFetch [CHECK] Spec requires stat cards with counts [CHECK] Spec requires recent activity feed [CHECK] Spec requires time-filtered data (this week vs all-time)
Q3 (PERSONA): "I'm Linda, 47. It's 8:15 AM Monday. I open my bookmarked dashboard and I need the story in 10 seconds: 'This weekend: 4 prayer requests, 2 visitor contacts, 1 callback.' If the stat cards show all-time totals -- '147 total conversations' -- that tells me nothing about this weekend. I need THIS WEEK or SINCE LAST MONDAY filtering. If I have to click into each tab to figure out what happened over the weekend, I'm already behind. The overview needs to be a newspaper headline, not a spreadsheet."
Q4 (BETTER): 1. [HIGH IMPACT] Add "Since last login" or "This weekend" filter to stat cards -- the #1 use case for Monday morning 2. [HIGH IMPACT] Add priority indicators: red badge on callbacks, amber on crisis prayer requests 3. [MEDIUM IMPACT] Add a "Monday Morning Summary" email that arrives at 7:00 AM with the weekend digest 4. [LOW IMPACT] Add a customizable dashboard layout -- Linda wants callbacks first, prayer requests second
Q5 (GOAL): Step 1 of 4. Goal: "Check weekend activity and know what to prioritize." Linda needs the weekend summary in one glance. If stat cards are time-filtered, she's on track. Progress: 25%. Path: CLEAR if overview is time-filtered. Risk: MEDIUM (all-time stats are useless for triage). Momentum: NEUTRAL.
VERDICT: CONCERN Cannot verify. Time-filtering of stat cards is critical for this persona's workflow.
STEP 2: requests-tab -- https://churchwiseai.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per starter-chat.md #G50, the Requests tab should show a unified list of all request types (prayer/visitor/callback) with type, timestamp, name, message/reason, and status (new/in-progress/resolved). Filtering and sorting should be available.
Q2 (SPEC): [N/A] Cannot verify request list or filtering via WebFetch [CHECK] Spec requires unified list of all request types [CHECK] Spec requires type filtering and sorting [CHECK] Spec requires status indicators (new/in-progress/resolved)
Q3 (PERSONA): "I'm Linda, 47. I click the Requests tab and I need to sort by type immediately. Callbacks first -- those people asked to be called back and they're waiting. Then prayer requests with crisis language -- 'hospital,' 'death,' 'emergency.' Then visitor contacts for the welcome team. If everything is in a flat date-sorted list, I have to scan 20 items to find the 1 callback buried between 19 general prayer requests. That's 10 minutes I don't have. Give me a type filter or at minimum sort callbacks to the top."
Q4 (BETTER): 1. [HIGH IMPACT] Add automatic priority sorting: callbacks > crisis prayers > visitor contacts > general prayers 2. [HIGH IMPACT] Add visual type badges: red for callbacks, amber for crisis, blue for visitors, gray for general 3. [MEDIUM IMPACT] Add a "needs attention" flag that highlights items no one has acted on yet 4. [LOW IMPACT] Add batch actions: select multiple items and assign to prayer team in one click
Q5 (GOAL): Step 2 of 4. Goal: "Triage weekend activity." Linda needs priority-ordered triage capability. Progress: 50%. Path: DEPENDS on filtering capability. Risk: HIGH (flat list = missed callbacks). Momentum: AT RISK.
VERDICT: CONCERN Cannot verify. Priority sorting and type filtering are essential for Linda's 30-minute triage workflow.
STEP 3: calls-tab -- https://churchwiseai.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per starter-voice.md #G49, the Calls tab should show: call log with timestamp, caller info, duration, AI summary, tools used, and escalation status. Expandable rows should show full transcripts.
Q2 (SPEC): [N/A] Cannot verify call log or transcripts via WebFetch [CHECK] Spec requires call log with timestamps and AI summaries [CHECK] Spec requires expandable transcript rows [CHECK] Calls tab may not be visible if church has chat-only plan
Q3 (PERSONA): "I'm Linda, 47. I need to know: Did anyone call who needs a callback? Did the AI handle things correctly? Were there any calls it couldn't handle? I'm not reading every transcript -- I want the AI summary for each call with an 'Action needed' flag on anything that requires human follow-up. If the calls tab just shows a list of phone numbers and durations with no context, I'll skip it and never check it again."
Q4 (BETTER): 1. [HIGH IMPACT] Add "Action needed" flag on calls that triggered escalation or where the caller asked for a human 2. [MEDIUM IMPACT] Add AI-generated "Monday morning call summary" -- "12 calls this weekend. 10 handled fully. 2 need follow-up." 3. [LOW IMPACT] Add call recording playback for calls flagged as needing review
Q5 (GOAL): Step 3 of 4. Goal: "Review voice interactions from the weekend." Linda has reviewed both chat and voice channels. Progress: 75%. Path: ON TRACK. Risk: MEDIUM (voice tab usability). Momentum: STEADY.
VERDICT: CONCERN Cannot verify. Call summary quality and "action needed" flags determine whether Linda uses this tab.
STEP 4: take-action -- https://churchwiseai.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per starter-chat.md #G50, status update controls should be available on each request. Ability to mark as new/in-progress/resolved. Notes field for internal comments.
Q2 (SPEC): [N/A] Cannot verify status controls or notes fields via WebFetch [CHECK] Spec requires inline status updates (not full-page navigation) [CHECK] Spec requires notes field for handoff information
Q3 (PERSONA): "I'm Linda, 47. I need to update 7 items in the next 15 minutes. If I have to click into each item, wait for a page load, change a dropdown, type a note, save, go back to the list, and repeat -- that's 2 minutes per item, 14 minutes total. Inline editing -- click the status dropdown right in the list, type a quick note, done -- that's 30 seconds per item, 3.5 minutes total. The difference between inline and page-by-page is the difference between finishing my triage in 30 minutes and falling behind all day."
Q4 (BETTER): 1. [HIGH IMPACT] Ensure inline status updates -- no page navigation required 2. [HIGH IMPACT] Add a notes field visible in the list view (not hidden behind a click) 3. [MEDIUM IMPACT] Add a "Forward to pastor" button that emails a summary of selected items 4. [MEDIUM IMPACT] Add assignment dropdown: "Assign to: Pastor John / Prayer Team / Welcome Team" 5. [LOW IMPACT] Add keyboard shortcuts for power users: 'h' for handled, 'p' for in-progress
Q5 (GOAL): Step 4 of 4. Goal: "Complete weekend triage within 30 minutes." GOAL ACHIEVED if Linda can view, prioritize, update, and hand off within her time window. Progress: 100% (if inline updates work). Path: COMPLETE. Risk: MEDIUM (depends on inline UX). Momentum: FINISHING.
VERDICT: CONCERN Cannot verify inline update capability. This is the critical workflow step.
========================================================================
OUTCOME VERIFICATION [UNTESTABLE] Dashboard shows stat cards with counts -- CSR page, requires auth [UNTESTABLE] Requests tab displays items with type, timestamp, and status -- CSR page [UNTESTABLE] Status can be updated without full page navigation -- CSR page
FAILURE MODE CHECK "Dashboard shows only zeros with no indication" -- UNTESTABLE "Requests tab requires page refresh for new items" -- UNTESTABLE "No unified view" -- UNTESTABLE "No priority/urgency indicators" -- UNTESTABLE but HIGH RISK per persona analysis "Calls tab not visible" -- UNTESTABLE (depends on plan) "Status updates require full page reload" -- UNTESTABLE but CRITICAL for workflow "No timestamp or sorting" -- UNTESTABLE "Dashboard takes more than 5 seconds to load" -- UNTESTABLE
========================================================================
SUMMARY Steps completed: 4/4 Steps passed: 0 Steps with concerns: 4 Steps failed: 0 Goal achieved: UNTESTABLE
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: None verifiable
P1 GOAL BLOCKED: None verifiable
P2 PERSONA RISKS: 1. Stat cards showing all-time totals instead of "this week" makes Monday morning triage impossible 2. Flat request list without type filtering or priority sorting misses urgent callbacks 3. Page-by-page status updates (vs inline) will exceed Linda's 30-minute triage window
P3 IMPROVEMENTS: 1. Add "Monday Morning Summary" automated email at 7:00 AM 2. Add priority sorting: callbacks > crisis prayers > visitors > general 3. Add "Forward to pastor" email summary button 4. Add assignment dropdown for team delegation 5. Add "Action needed" flags on voice calls requiring follow-up
TOTAL FINDINGS: 8 (0 P0, 0 P1, 3 P2, 5 P3)
========================================================================
RECOMMENDATION Like the chatbot training journey, this entire journey is UNTESTABLE via WebFetch. All 4 steps are CSR admin dashboard pages. The persona risks identified are critical for the daily workflow of the #1 dashboard user (church admin). Priority testing needed: (1) Are stat cards time-filtered? (2) Can requests be filtered by type? (3) Are status updates inline? These three questions determine whether the Monday morning workflow is viable. Recommend Playwright tests with the demo church data.
=== JOURNEY REPORT: pewsearch-find-church === Date: 2026-04-02 Persona: Sarah (29, Young professional recently relocated, tech comfort: high) Goal: "I just moved to Nashville and I'm looking for a welcoming Baptist church near my apartment." Property: pewsearch.com Entry: https://pewsearch.com
STEP 1: homepage -- https://pewsearch.com/
Q1 (SEE): A modern, visually striking homepage with a video background hero section. The dominant headline reads "Find Your Church Home" with supporting text: "Search 218,000+ churches across the US and Canada." A prominent search bar with placeholder text "Search by name, city, or denomination..." sits in the hero. Quick-access denomination buttons: Baptist, Catholic, Methodist, Lutheran, Presbyterian, Pentecostal, Non-denominational, and "200+ more." State shortcuts: Texas, California, Florida, Georgia. Ministry filters: Youth Groups, Bible Study, Wheelchair Accessible, Food Banks. Glass-morphism design effects, gradient text overlays. Navigation: Browse, Pro Website, Pricing, Contact, Help, About.
Q2 (SPEC): [PASS] Search bar prominent -- center of hero section [PASS] Church count indicator -- "218,000+ churches" displayed [PASS] Clean, modern design -- video background, glass-morphism, gradient overlays [PASS] Denomination filter available -- quick-access buttons for 7+ denominations [PASS] Location input available -- state shortcuts and search bar accepts city [CONCERN] No explicit "location" input field separate from the main search bar -- location may need to be typed as part of the search query
Q3 (PERSONA): "I'm Sarah, 29. This looks GOOD. Video background, modern design, 218,000+ churches -- this isn't some janky church directory from 2003. The search bar is obvious and the Baptist button is RIGHT THERE as a quick filter. I tap 'Baptist' and type 'Nashville' in the search bar. This already feels better than Google Maps for finding a church because it's specifically designed for this. I'm staying."
Q4 (BETTER): 1. [MEDIUM IMPACT] Add a combined search: denomination + location in one query (e.g., "Baptist churches in Nashville") rather than separate fields 2. [LOW IMPACT] Add a "Near Me" button that uses geolocation for mobile users 3. [LOW IMPACT] Add a tagline like "America's Largest Church Directory" near the church count for social proof
Q5 (GOAL): Step 1 of 4. Goal: "Find a welcoming Baptist church near my apartment." Sarah is impressed by the modern design and has a clear search path. Progress: 20%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 2: search-results -- https://pewsearch.com/directory?q=baptist&location=Nashville+TN
Q1 (SEE): 181 results returned (Page 1 of 9). Each result card shows: church name (bold heading), denomination tag ("Baptist"), star rating with review count, 2-line description preview, address with map pin icon, phone number, hours (when available), website URL, and a church photo. Filter badges show active search parameters. Pagination with Previous/Next buttons and "1/9" indicator. First results include Nashville First Baptist (4.5 stars, 120 reviews), Mt. Zion Baptist (4.8 stars, 93 reviews), Forest Hills Baptist (4.6 stars, 73 reviews).
Q2 (SPEC): [PASS] List of churches matching Baptist in Nashville -- 181 results [PASS] Each result shows church name, denomination, address [PASS] Photos present on result cards [PASS] Service times/hours shown (when available) -- "Thursday: 8AM-12PM" visible [PASS] Description preview visible (2-line preview) [PASS] Star ratings visible with review counts [PASS] Pagination present (9 pages) [CONCERN] Service times shown as "hours" (Mon-Sat schedule) rather than "Sunday worship service times" specifically -- this may confuse Sarah who wants SUNDAY SERVICE times
Q3 (PERSONA): "I'm Sarah, 29. 181 results -- that's a lot, but I'll scroll the first page. Photos catch my eye immediately. Nashville First Baptist has a photo and 4.5 stars with 120 reviews -- that's a trust signal. The descriptions help me judge vibe: 'connecting Jesus to people, people to community' sounds welcoming. Forest Hills Baptist says 'Gospel-centered congregation welcoming diverse backgrounds' -- that's the kind of language I'm looking for. I'm clicking on 2-3 of these. My one frustration: the 'hours' shown are office hours, not Sunday service times. I need to know if there's a 9 AM or 11 AM service, and that's not visible in the cards."
Q4 (BETTER): 1. [HIGH IMPACT] Show SUNDAY WORSHIP TIME prominently in result cards (not office hours) -- this is the #1 info seekers want 2. [MEDIUM IMPACT] Add a "Welcoming" or "Contemporary" filter -- Sarah is specifically looking for churches that signal modern and inclusive 3. [MEDIUM IMPACT] Add distance from search location to each result card 4. [LOW IMPACT] Add infinite scroll option instead of pagination -- Sarah is used to Instagram/TikTok scroll patterns
Q5 (GOAL): Step 2 of 4. Goal: "Find a welcoming Baptist church near my apartment." Sarah has 181 results with photos, descriptions, and ratings. She can shortlist 2-3 churches. Progress: 50%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 3: church-detail -- https://pewsearch.com/churches/nashville-first-baptist-church-nashville-tn
Q1 (SEE): Church name: "Nashville First Baptist Church" with Baptist denomination tag. Rating: 4.5 stars (120 reviews). Address: 108 7th Ave S, Nashville, TN 37203 with embedded OpenStreetMap. Hours listed (Sunday 9AM-12PM, Monday-Friday schedules, Saturday closed). Description: "downtown faith community dedicated to connecting Jesus to people, people to community, and community to mission." Contact: phone (+1 615-664-6000), website (nashvillefirst.org), social media links (Twitter, YouTube, Facebook, Instagram). Amenities: free parking, wheelchair accessible. A "Claim This Church" button and "Free Correction" option visible. Nearby church listings shown.
Q2 (SPEC): [PASS] Church name and denomination displayed [PASS] Full address with embedded map [PASS] Service times present -- Sunday 9AM-12PM [PASS] Description/About section present [PASS] Contact info with phone, website, social media [PASS] Directions available via embedded map [PASS] Amenities listed (parking, accessibility) [FAIL] No "What to Expect" section -- spec requires first-time visitor guidance -- SPEC VIOLATION [CONCERN] Sunday hours show "9AM-12PM" but don't specify whether that's one service or multiple (9AM and 11AM are separate services at most Baptist churches)
Q3 (PERSONA): "I'm Sarah, 29. The church page looks professional. I can see it's downtown, there's free parking (important!), and it's wheelchair accessible. Sunday 9AM-12PM gives me a time window but I'm not sure -- is there one service at 9 or two at 9 and 11? The description sounds welcoming: 'connecting Jesus to people, people to community, and community to mission.' But where's the 'What to Expect' section? I haven't been to church in 5 years and I'm nervous. I need someone to tell me: What do I wear? Where do I park? Will someone greet me? Can I just slip in the back and observe? Without that, I'm going to this church's actual website to find out, and if THEY don't have it, I might not go."
Q4 (BETTER): 1. [HIGH IMPACT] Add a "What to Expect" section for all churches (even auto-generated: "Most Baptist churches welcome visitors. Dress is typically casual. Greeters will welcome you at the door.") 2. [HIGH IMPACT] Clarify service times: "Sunday: 9:00 AM Traditional Service, 11:00 AM Contemporary Service" instead of "9AM-12PM" 3. [MEDIUM IMPACT] Add a "Plan Your Visit" action box with: directions button, calendar reminder button, "What to wear" note 4. [LOW IMPACT] Add a "Share this church" button for Sarah to text to her friend
Q5 (GOAL): Step 3 of 4. Goal: "Find a welcoming Baptist church near my apartment." Sarah has found a church with address, service times, and a welcoming description. Missing: "What to Expect" for a nervous returner. Progress: 75%. Path: MOSTLY CLEAR. Risk: MEDIUM (no "What to Expect" raises anxiety for a hesitant returner). Momentum: SLIGHTLY DECLINING.
VERDICT: CONCERN Missing "What to Expect" section is a spec violation and a significant persona risk for a hesitant church returner.
STEP 4: plan-visit -- https://pewsearch.com/churches/nashville-first-baptist-church-nashville-tn
Q1 (SEE): Same detail page. Sarah is now in decision mode. She has: address with embedded map (can get directions), Sunday 9AM-12PM time slot, church website link (nashvillefirst.org), phone number. No "Plan Your Visit" CTA or first-time visitor section. No "RSVP" or "I'm Coming" button. The "Get Directions" link goes to Google Maps.
Q2 (SPEC): [PASS] Directions/map link present -- embedded map + "Get Directions" [PASS] Service times visible -- Sunday 9AM-12PM [CONCERN] No first-time visitor information on PewSearch -- relies on church's own website [CONCERN] No option to save/bookmark the church for later
Q3 (PERSONA): "I'm Sarah, 29. Okay, I've decided. Nashville First Baptist, Sunday morning. I'll tap 'Get Directions' and save it to my Maps. The service is sometime between 9 and 12 -- I'll aim for 9:30 to be safe. I wish there was a 'Save this church' button so I can compare it to the other two I'm looking at. I'll screenshot the page instead. I have enough to go -- address, time window, and the website if I want more info. I'll send this to my friend Ashley and see if she wants to come."
Q4 (BETTER): 1. [HIGH IMPACT] Add a "Save to My List" feature (even without account -- cookie-based) for comparing multiple churches 2. [MEDIUM IMPACT] Add a "First Visit Checklist" auto-generated section: parking, service time, what to wear, who to ask for 3. [MEDIUM IMPACT] Add "Add to Calendar" button that creates a calendar event with the church name, address, and service time 4. [LOW IMPACT] Add a "Text this to a friend" share button
Q5 (GOAL): Step 4 of 4. Goal: "Find a welcoming Baptist church near my apartment." Sarah has the address, a time window, and directions. She can visit next Sunday. Missing: "What to Expect" and specific service time details. Progress: 85%. Path: COMPLETE (enough to visit). Risk: LOW (Sarah will likely visit). Momentum: POSITIVE.
VERDICT: PASS
========================================================================
OUTCOME VERIFICATION [VERIFIED] Search results return Baptist churches in Nashville -- 181 results [VERIFIED] At least one church detail page shows service times -- Nashville First Baptist shows Sunday 9AM-12PM [VERIFIED] Church detail page includes address with directions -- embedded map and "Get Directions" link
FAILURE MODE CHECK "Homepage search is confusing" -- CLEAR (modern, single search bar, denomination shortcuts) "Search returns irrelevant results" -- CLEAR (181 Baptist churches in Nashville) "No photos on any church listing" -- CLEAR (photos visible on result cards) "Service times missing from results and detail pages" -- CLEAR (present, though format could be improved) "Church detail page has no description" -- CLEAR (description present) "No What to Expect or first-time visitor guidance" -- TRIGGERED -- no "What to Expect" section on church detail pages "Map/directions link is broken or missing" -- CLEAR (embedded map + Get Directions) "Page loads slowly on mobile" -- UNTESTABLE (WebFetch doesn't measure mobile load time) "Search results are paginated with tiny page numbers" -- CLEAR (Previous/Next buttons with clear pagination)
========================================================================
SUMMARY Steps completed: 4/4 Steps passed: 3 Steps with concerns: 1 Steps failed: 0 Goal achieved: PARTIAL
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: 1. No "What to Expect" section on church detail pages -- critical for first-time visitors and hesitant returners
P1 GOAL BLOCKED: None
P2 PERSONA RISKS: 1. Service times shown as "hours" (office hours format) rather than specific worship service times with descriptions 2. No "Save" or "Compare" functionality for evaluating multiple churches
P3 IMPROVEMENTS: 1. Show Sunday worship time prominently in search result cards 2. Add "What to Expect" auto-generated section for all churches 3. Add "Add to Calendar" button 4. Add distance from search location to result cards 5. Add "Plan Your Visit" action box on detail pages
TOTAL FINDINGS: 8 (1 P0, 0 P1, 2 P2, 5 P3)
========================================================================
RECOMMENDATION The PewSearch find-church journey is STRONG on search quality and design -- the homepage is modern, search returns relevant results with photos and descriptions, and the detail page has essential information. The missing "What to Expect" section is the biggest gap for the target persona (hesitant church returner). This is a P0 spec violation because first-time visitors -- PewSearch's primary audience -- need anxiety-reducing content before they'll walk through a church door. Service time formatting (office hours vs worship services) is a secondary but meaningful issue. The journey is CONDITIONALLY PASSING for launch -- Sarah can find a church and visit, but the experience doesn't address her emotional needs as a returner.
=== JOURNEY REPORT: pewsearch-claim-listing === Date: 2026-04-02 Persona: Pastor David (60, Senior pastor 18 years, tech comfort: low) Goal: "I found our listing on PewSearch with the wrong service times. I want to claim it and fix the information." Property: pewsearch.com Entry: https://pewsearch.com
STEP 1: find-church -- https://pewsearch.com/
Q1 (SEE): Same PewSearch homepage as above. Clean search bar with "Search by name, city, or denomination..." placeholder. David will type his full church name.
Q2 (SPEC): [PASS] Search bar accepts church name [PASS] Search interface is simple and clear
Q3 (PERSONA): "I'm David, 60. I type 'First Baptist Church of Franklin' into the search bar slowly, with two fingers. I press Enter and wait. If my church appears in the first 3 results, I know I'm in the right place. If I get 50 'First Baptist' results and have to scroll through pages, I'll ask my office manager to deal with this."
Q4 (BETTER): 1. [MEDIUM IMPACT] Add autocomplete/typeahead that shows matching church names as David types 2. [LOW IMPACT] Add a "Find Your Church" button specifically for pastors/leaders (rather than the general search)
Q5 (GOAL): Step 1 of 5. Goal: "Claim listing and fix service times." David needs to find his specific church. Search precision is the gate. Progress: 10%. Path: CLEAR. Risk: LOW (if search is precise). Momentum: CAUTIOUS.
VERDICT: PASS
STEP 2: church-listing -- https://pewsearch.com/churches/[slug]
Q1 (SEE): Church detail page (similar to Nashville First Baptist structure). The page shows church name, denomination, address, service times (potentially wrong), description, contact info, and amenities. Critically: a "Claim This Church" button is visible, along with a "Free Correction" button for basic info updates.
Q2 (SPEC): [PASS] Church detail page with existing information displayed [PASS] "Claim This Church" button visible [PASS] "Free Correction" alternative available for basic updates [CONCERN] Claim CTA leads to a PAID flow ($9.95/mo) -- this may surprise David who just wants to fix the service time
Q3 (PERSONA): "I'm David, 60. I see our church and... the service time says 10 AM. That's WRONG -- we moved to 9 AM two years ago. I see a 'Claim This Church' button and a 'Free Correction' button. Wait -- two buttons? Which one do I click? I just want to fix the time. If 'Claim' means paying money, I want 'Free Correction.' But if 'Free Correction' just sends an email that takes weeks, I want 'Claim.' I need clearer labeling: 'Fix a mistake (free)' vs 'Manage your listing (from $9.95/mo).'"
Q4 (BETTER): 1. [HIGH IMPACT] Clarify the two CTAs: "Report a Correction (free, reviewed in 48 hours)" vs "Claim & Manage Your Page ($9.95/mo, instant access)" 2. [MEDIUM IMPACT] Add a tooltip on "Claim" that explains what claiming includes and that it costs $9.95/mo 3. [LOW IMPACT] Highlight wrong information: "Is this information out of date? Let us know."
Q5 (GOAL): Step 2 of 5. Goal: "Fix the wrong service times." David found the claim button. The free vs paid path distinction is the decision point. Progress: 30%. Path: UNCLEAR (two paths, unclear which to choose). Risk: MEDIUM (David may choose the wrong path). Momentum: HESITANT.
VERDICT: CONCERN Two CTAs ("Claim" and "Free Correction") without clear differentiation create decision paralysis for a low-tech-comfort user.
STEP 3: claim-flow -- https://pewsearch.com/claim/[slug]
Q1 (SEE): The claim page prominently displays "$9.95 USD/month" throughout. Form fields: Your Name (required), Your Email (required, "using your church email is recommended"), Your Role (dropdown: Senior Pastor, Associate Pastor, etc.), Church Family (pre-populated from database, e.g., "Baptist"), confirmation checkbox for authorized representative. The CTA button reads "Continue to Payment -- $9.95 USD/mo." Below: "Secured by Stripe. Cancel anytime. No contracts." A "Submit a free correction" alternative link is available.
Q2 (SPEC): [PASS] Claim form with name, email, role fields [PASS] Role dropdown includes relevant options (Senior Pastor first) [FAIL] Claim is NOT free -- costs $9.95/mo. Spec says "No payment required for basic claim" -- SPEC VIOLATION [PASS] Privacy assurance via Stripe badge [PASS] "Submit a free correction" alternative available [CONCERN] A pastor who just wants to fix service times is being asked to pay $9.95/mo -- significant friction
Q3 (PERSONA): "I'm David, 60. I clicked 'Claim This Church' and now I see $9.95 PER MONTH. I just want to fix the service time! I don't want to pay for a 'Premium Church Page.' Let me look for that 'free correction' link... I see it: 'Submit a free correction.' But wait -- if I do the free correction, how long does it take? Will someone review it? The premium claim says 'your page is live instantly' -- the free correction might take weeks. I'm torn. I don't want to spend $9.95/month on something I'll use once. But I also don't want the wrong time listed for another month. I'll try the free correction first and come back to premium if it doesn't work."
Q4 (BETTER): 1. [HIGH IMPACT] Add a FREE basic claim tier: name, email, role -- instant access to edit service times, description, and contact info. Reserve premium for photos, analytics, and verified badge. 2. [HIGH IMPACT] Make the free correction process transparent: "We'll review and update within 48 hours" with status tracking 3. [MEDIUM IMPACT] Add a one-time payment option for basic edits ($4.95 one-time) instead of monthly subscription 4. [LOW IMPACT] Add a "Why claim?" explainer: benefits of claiming vs free correction
Q5 (GOAL): Step 3 of 5. Goal: "Fix the wrong service times." David is at a paywall. His goal (fix one piece of information) doesn't require a $9.95/mo subscription. The free correction path exists but is less visible and slower. Progress: 40%. Path: SPLIT (paid = instant, free = delayed and uncertain). Risk: HIGH (David may abandon). Momentum: DECLINING.
VERDICT: CONCERN The $9.95/mo paywall for basic information correction is a significant persona barrier. The "free correction" alternative exists but is secondary and lacks transparency.
STEP 4: verification -- https://pewsearch.com/claim/[slug] (post-submission)
Q1 (SEE): Per the claim page content, after payment: "Your page is live instantly. We pre-populate it with your existing information and you can edit everything from your church dashboard right away." The magic link will be sent by email. If David chose the free correction path, the confirmation experience would differ (likely a simpler acknowledgment).
Q2 (SPEC): [PASS] Success messaging present for the paid path -- "page is live instantly" [PASS] Clear next steps: email with dashboard link [CONCERN] Free correction path confirmation experience is unclear -- may not provide a clear timeline [PASS] "Secured by Stripe" trust messaging
Q3 (PERSONA): "I'm David, 60. If I paid: 'Your page is live instantly' is reassuring -- I like that. I'll watch for the email with the dashboard link. If I submitted a free correction: I need to know when the change will happen. 'We'll review your submission and update the listing within 48 hours' -- that would give me peace of mind. If it just says 'Thank you for your submission!' with no timeline, I'll worry that it went into a black hole."
Q4 (BETTER): 1. [MEDIUM IMPACT] For free corrections: add a specific timeline ("Updated within 48 hours") and status tracking email 2. [LOW IMPACT] Add a "Bookmark this page to check for updates" prompt
Q5 (GOAL): Step 4 of 5. Goal: "Fix the wrong service times." David has submitted a claim or correction. The path forward depends on which route he chose. Progress: 70%. Path: ON TRACK (paid) or UNCERTAIN (free). Risk: LOW (paid) or MEDIUM (free). Momentum: REBUILDING.
VERDICT: PASS
STEP 5: admin-dashboard -- https://pewsearch.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per pewsearch-premium.md, the PewSearch admin dashboard should show editable church information including service times, description, contact info, and a save button. A preview of how changes appear on the public listing should be available.
Q2 (SPEC): [N/A] Cannot verify admin dashboard via WebFetch -- CSR page [CHECK] Spec requires editable service times field [CHECK] Spec requires save confirmation [CHECK] Spec requires preview of public listing changes
Q3 (PERSONA): "I'm David, 60. I clicked the magic link and I'm in the dashboard. I need one thing: where do I change the service time from 10 AM to 9 AM? If there's a field labeled 'Service Times' that I can see without scrolling, I'll change it, hit Save, and be done. If I have to navigate through tabs, find 'Church Details,' scroll to 'Schedule,' and figure out a time picker, I'll be here for 20 minutes. Just let me type '9:00 AM' in a box and click Save."
Q4 (BETTER): 1. [HIGH IMPACT] Make "Service Times" the first editable field on the dashboard -- it's the #1 reason pastors claim listings 2. [MEDIUM IMPACT] Add a "Changes appear on your listing within 1 hour" confirmation after saving 3. [LOW IMPACT] Add a "Preview Your Page" button that shows the public listing with the changes applied
Q5 (GOAL): Step 5 of 5. Goal: "Fix the wrong service times." GOAL ACHIEVED if David can update the service time and see confirmation of the save. Progress: 95% (assuming dashboard works). Path: COMPLETE (if service times field is findable). Risk: LOW. Momentum: FINISHING.
VERDICT: CONCERN Cannot verify admin dashboard UX. Service times field visibility is the critical success factor.
========================================================================
OUTCOME VERIFICATION [UNTESTABLE] Claim form submits successfully -- requires live submission (won't write to prod) [UNTESTABLE] Admin dashboard allows editing of service times -- CSR page [UNTESTABLE] Public listing reflects updated information -- requires actual data change
FAILURE MODE CHECK "Church not found in search" -- CLEAR (search works, churches found) "No Claim button visible" -- CLEAR ("Claim This Church" button visible on detail pages) "Claim form requires credit card" -- TRIGGERED -- claim IS a paid flow ($9.95/mo), though free correction exists as alternative "Verification email goes to spam" -- UNTESTABLE "Magic link expires before David clicks it" -- UNTESTABLE "Admin dashboard is too complex" -- UNTESTABLE (CSR page) "No preview of changes" -- UNTESTABLE (CSR page) "Changes don't appear on public listing" -- UNTESTABLE "Claim flow breaks on mobile" -- UNTESTABLE
========================================================================
SUMMARY Steps completed: 5/5 Steps passed: 2 Steps with concerns: 3 Steps failed: 0 Goal achieved: PARTIAL
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: None (the paid claim model is a business decision, not a spec violation -- but the free correction path addresses the persona's need)
P1 GOAL BLOCKED: 1. Pastor David's goal is to fix one piece of information. The primary "Claim" path requires $9.95/mo. The free correction path exists but is secondary, with no transparent timeline. This creates a significant barrier for low-tech-comfort pastors.
P2 PERSONA RISKS: 1. Two CTAs ("Claim" vs "Free Correction") without clear differentiation create decision paralysis 2. $9.95/mo for basic information correction feels disproportionate for a one-time need 3. Free correction path lacks transparent timeline and status tracking
P3 IMPROVEMENTS: 1. Add a free basic claim tier for service times + contact info only 2. Clarify CTA labeling: "Fix a mistake (free)" vs "Manage your page ($9.95/mo)" 3. Add autocomplete/typeahead in search 4. Make service times the first editable field in admin dashboard 5. Add free correction status tracking
TOTAL FINDINGS: 9 (0 P0, 1 P1, 3 P2, 5 P3)
========================================================================
RECOMMENDATION The PewSearch claim journey has a fundamental tension: Pastor David wants to fix ONE wrong piece of information for free, but the primary claim path costs $9.95/mo. The "free correction" alternative exists and addresses this, but it's secondary in the UI and lacks transparency on timeline. For launch, this is CONDITIONALLY PASSING -- the free correction path prevents a hard block, but the UX makes the paid path feel like the only option. Priority fix: (1) Make "Free Correction" equally prominent alongside "Claim," and (2) Add transparent timeline to the free correction process. Long-term: consider a free basic claim tier that allows editing service times and contact info without payment.
=== JOURNEY REPORT: sermonwise-first-sermon === Date: 2026-04-02 Persona: Pastor Rachel (38, Reformed PCA pastor, tech comfort: medium) Goal: "I need to prepare a Reformed sermon on Romans 8:28-30 for this Sunday." Property: sermonwise.ai Entry: https://sermonwise.ai/sermons
STEP 1: landing-page -- https://sermonwise.ai/sermons
Q1 (SEE): The hero headline reads "Sermons & Homilies, Faithful to Your Tradition." Below: "less time wrestling with structure -- and more time shepherding." The page lists 17 theological traditions including Reformed explicitly. A how-it-works section shows 4 steps: Enter Scripture, Choose Your Tradition, Pick Your Style (Expository, Topical, Narrative, Homily, Devotional), Generate Your Outline. CTAs: "Start Free -- 2 Outlines/Month" and "Get Started Free." Free tier details: 2 outlines/month, all 17 traditions, RAG-powered illustrations, export. Pro: $19.95/mo.
Q2 (SPEC): [PASS] Hero mentions tradition-aware sermon preparation -- "Faithful to Your Tradition" [PASS] Reformed tradition explicitly listed among the 17 [PASS] Free signup CTA visible -- "Start Free -- 2 Outlines/Month" [PASS] Expository style explicitly listed as an option [PASS] No credit card mentioned for free tier [PASS] Homily mentioned -- signals non-Protestant-only tool
Q3 (PERSONA): "I'm Rachel, 38. 'Faithful to Your Tradition' -- okay, that's a good start. I scan the tradition list and... Reformed is there. Not just 'Presbyterian' or 'Calvinist' -- 'Reformed.' That's my word. And 'Expository' is listed as a style option. This tool was built by someone who knows that Reformed pastors do expository preaching. The free tier gives me 2 outlines/month -- enough to test it this Sunday without paying. I'm clicking 'Start Free.'"
Q4 (BETTER): 1. [MEDIUM IMPACT] Add tradition-specific social proof: "Used by 50+ PCA pastors" or "Built with Reformed exegetical standards" 2. [LOW IMPACT] Add a direct link to the Reformed sermon example in the Showcase from the landing page 3. [LOW IMPACT] Mention specific Reformed-compatible features: "Covenant theology lens," "Ordo salutis integration"
Q5 (GOAL): Step 1 of 6. Goal: "Prepare a Reformed sermon on Romans 8:28-30." Rachel sees Reformed explicitly listed, Expository available, free tier with no credit card. Trust earned. Progress: 15%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 2: signup -- https://sermonwise.ai/sermons/signup
Q1 (SEE): Signup form with fields: Full Name, Primary Tradition (dropdown), Email, Password, Confirm Password. A checkbox for email updates. Google OAuth option ("Sign up with Google"). CTA: "Create Free Account." Below: "No credit card required." The tradition dropdown includes "Reformed (Presbyterian, PCA, OPC)" as an explicit option among 17 traditions.
Q2 (SPEC): [PASS] Signup form with email and password [PASS] Tradition selector present with 17 options [PASS] "Reformed (Presbyterian, PCA, OPC)" explicitly available -- better than just "Reformed" [PASS] No credit card required -- explicitly stated [PASS] Google OAuth option for fast signup
Q3 (PERSONA): "I'm Rachel, 38. The tradition dropdown has 'Reformed (Presbyterian, PCA, OPC)' -- they listed MY denomination (PCA). That's not a generic 'Reformed' checkbox; someone actually knows what PCA means. No credit card -- I appreciate that. I fill in my name, select Reformed, enter my email and password. Done in 90 seconds. The Google sign-in would have been even faster but I'll use email for a new tool I'm testing."
Q4 (BETTER): 1. [LOW IMPACT] Pre-select the tradition from the landing page click (if Rachel clicked from a "Reformed" filter, pre-fill it) 2. [LOW IMPACT] Add a brief note under the tradition selector: "This shapes your sermon's theological vocabulary and exegetical approach"
Q5 (GOAL): Step 2 of 6. Goal: "Prepare a Reformed sermon on Romans 8:28-30." Signup complete. Tradition selected. Zero friction. Progress: 25%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 3: dashboard -- https://sermonwise.ai/sermons/app
Q1 (SEE): CSR page -- referencing acceptance spec. Per sermonwise-pro.md, the dashboard should show a prominent "New Sermon" button, a getting started guide for first-time users, and the selected tradition in the profile/header.
Q2 (SPEC): [N/A] Cannot verify dashboard via WebFetch -- CSR page [CHECK] Spec requires prominent "New Sermon" button [CHECK] Spec requires tradition shown in profile/header
Q3 (PERSONA): "I'm Rachel, 38. I just created my account and I'm in the dashboard. I don't want a tutorial -- I want to generate a sermon NOW. If there's a big 'New Sermon' button right in the center, I click it immediately. If I have to navigate through 'Library > New > From Scratch > ...' I'm losing patience. One click to start generating. That's all I need."
Q4 (BETTER): 1. [HIGH IMPACT] For first-time users: auto-open the generation form -- skip the empty dashboard entirely 2. [LOW IMPACT] Show "Your tradition: Reformed (PCA)" in the header as a trust reinforcement
Q5 (GOAL): Step 3 of 6. Goal: "Prepare a Reformed sermon on Romans 8:28-30." Dashboard should be a one-click bridge to generation. Progress: 35%. Path: CLEAR (if New Sermon button is prominent). Risk: LOW. Momentum: HIGH.
VERDICT: CONCERN Cannot verify. CSR page. The critical check is whether "New Sermon" is immediately visible.
STEP 4: sermon-configuration -- https://sermonwise.ai/sermons/app/new
Q1 (SEE): CSR page -- referencing acceptance spec. Per sermonwise-pro.md, the generation form should include: Scripture input field, structure type selector (Expository should be available), tradition pre-filled from signup, and length target selector.
Q2 (SPEC): [N/A] Cannot verify form fields via WebFetch -- CSR page [CHECK] Spec requires Scripture input for "Romans 8:28-30" [CHECK] Spec requires Expository as a structure option [CHECK] Spec requires tradition pre-filled from signup (Reformed) [CHECK] Spec requires length target (Rachel wants 25 minutes)
Q3 (PERSONA): "I'm Rachel, 38. I type 'Romans 8:28-30' in the Scripture field. I look for 'Expository' in the structure dropdown -- it better be there, and ideally it should be the DEFAULT for Reformed tradition. If the default is 'Topical,' this tool doesn't understand me. I check that 'Reformed' is pre-filled from my signup -- yes? Good. I set length to 25 minutes. Everything looks right. I click Generate and hold my breath."
Q4 (BETTER): 1. [HIGH IMPACT] Default structure to "Expository" when tradition is Reformed -- this is THE Reformed preaching method 2. [MEDIUM IMPACT] Show a brief description of each structure type: "Expository: verse-by-verse through the passage" 3. [LOW IMPACT] Add a "Preaching notes" text area for Rachel to add context (e.g., "This is part of a Romans series, week 4")
Q5 (GOAL): Step 4 of 6. Goal: "Prepare a Reformed sermon on Romans 8:28-30." Configuration complete. Generation is the next make-or-break step. Progress: 50%. Path: CLEAR. Risk: LOW (if form is straightforward). Momentum: HIGH.
VERDICT: CONCERN Cannot verify. CSR page. The critical check: is Expository the default for Reformed tradition?
STEP 5: sermon-generation -- https://sermonwise.ai/sermons/app/new (output)
Q1 (SEE): CSR page -- referencing acceptance spec and showcase examples. Per sermonwise-pro.md and the showcase, a Reformed sermon on John 3:16 was titled "The Golden Chain: God's Sovereign Love from Eternity to Light" with three-point expository format centered on "sovereign grace, election." For Romans 8:28-30, the expected output should follow the golden chain of redemption (foreknew, predestined, called, justified, glorified) with Reformed theological vocabulary.
Q2 (SPEC): [N/A] Cannot verify generated output via WebFetch -- CSR page, requires live generation [CHECK] Spec requires clear sections (title, introduction, body, application, conclusion) [CHECK] Spec requires Reformed theological content (sovereignty, covenant, grace) [CHECK] Per showcase: Reformed sermons use "sovereign grace, election" framing
Q3 (PERSONA): "I'm Rachel, 38. The sermon is loading and... I'm reading the first paragraph. Does it handle predestination in verses 29-30 correctly? If it treats 'foreknew' as 'God saw who would choose Him' (Arminian foreseen faith), I'm closing this tab forever. If it reads 'foreknew' as covenantal foreknowledge -- God's sovereign, relational, choosing knowledge -- then this tool understands Reformed theology and I'm a customer for life. I'm also checking: Does it walk through the golden chain? Foreknew, predestined, called, justified, glorified -- that's the backbone of Romans 8:29-30. If it skips any link, the exegesis is incomplete."
Q4 (BETTER): 1. [HIGH IMPACT] Add theological accuracy review: show which tradition-specific sources were used (Westminster Confession, Calvin's Institutes, etc.) 2. [MEDIUM IMPACT] Add a "Theological check" indicator: "This sermon was generated using Reformed theological sources" 3. [LOW IMPACT] Add inline commentary: "This interpretation follows covenantal foreknowledge (cf. WCF 3.1)" -- builds trust in theological accuracy
Q5 (GOAL): Step 5 of 6. Goal: "Prepare a Reformed sermon on Romans 8:28-30." Sermon generated. Theological quality is the make-or-break criterion. Progress: 80%. Path: ON TRACK (if theology is correct). Risk: HIGH (one Arminian interpretation and Rachel is done permanently). Momentum: CRITICAL MOMENT.
VERDICT: CONCERN Cannot verify. The showcase proves Reformed content is possible. Live generation quality is the ultimate test.
STEP 6: review-and-export -- https://sermonwise.ai/sermons/app/new (export)
Q1 (SEE): CSR page -- referencing acceptance spec. Per sermonwise-pro.md and pricing page, export options include: Word, PDF, and Google Docs. Editable text area or rich editor should be available. Save to library option.
Q2 (SPEC): [N/A] Cannot verify export functionality via WebFetch -- CSR page [CHECK] Spec requires editable text area [CHECK] Spec requires PDF export (critical for Rachel's workflow) [CHECK] Spec requires save to library
Q3 (PERSONA): "I'm Rachel, 38. The sermon is theologically sound (assuming it passed step 5). Now I need to edit the application section -- I always add church-specific illustrations. The editing interface needs to feel like Google Docs, not a chat window. And I NEED PDF export for my physical sermon notes binder. I print my notes, mark them up with a pen, and preach from paper. If there's no PDF export, I'll copy-paste into Word and format it myself -- but that's friction I shouldn't have to deal with for $19.95/month."
Q4 (BETTER): 1. [MEDIUM IMPACT] Add a "Pulpit Mode" export: large font, wide margins, pagination optimized for reading while standing 2. [LOW IMPACT] Add a "Preach timer" estimate next to the word count 3. [LOW IMPACT] Add collaboration: "Share draft with my associate pastor for feedback"
Q5 (GOAL): Step 6 of 6. Goal: "Prepare a Reformed sermon on Romans 8:28-30." GOAL ACHIEVED if Rachel has an editable, exportable Reformed sermon on Romans 8:28-30 with correct theological content. Progress: 95% (assuming theology passed). Path: COMPLETE. Risk: LOW (export is standard functionality). Momentum: FINISHING.
VERDICT: CONCERN Cannot verify. CSR page. Export to PDF is the key deliverable.
========================================================================
OUTCOME VERIFICATION [UNTESTABLE] Generated sermon contains Reformed theological markers -- requires live generation [UNTESTABLE] Sermon follows expository format through Romans 8:28-30 -- requires live generation [UNTESTABLE] Export to PDF produces downloadable file -- requires authenticated access
FAILURE MODE CHECK "Landing page doesn't mention Reformed" -- CLEAR (Reformed explicitly listed) "Signup requires credit card" -- CLEAR (no credit card required) "Tradition selector missing Reformed" -- CLEAR ("Reformed (Presbyterian, PCA, OPC)" present) "Generated sermon uses Arminian theology" -- UNTESTABLE (requires live generation) "Sermon treats foreknew as foreseen faith" -- UNTESTABLE (requires live generation) "No export option" -- UNTESTABLE (CSR page, but pricing page lists PDF/Word/Docs) "Generation takes more than 30 seconds" -- UNTESTABLE
========================================================================
SUMMARY Steps completed: 6/6 Steps passed: 2 Steps with concerns: 4 Steps failed: 0 Goal achieved: PARTIAL (landing and signup verified; generation and export untestable)
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: None verifiable
P1 GOAL BLOCKED: None verifiable
P2 PERSONA RISKS: 1. If Expository is not the default structure for Reformed tradition, it signals the tool doesn't understand Rachel 2. Theological accuracy of Romans 8:29 treatment (foreknew = covenantal foreknowledge vs foreseen faith) is untestable but CRITICAL
P3 IMPROVEMENTS: 1. Default structure to Expository for Reformed tradition 2. Add theological source attribution ("This interpretation follows WCF 3.1") 3. Add "Pulpit Mode" export (large font, wide margins) 4. Auto-open generation form for first-time users 5. Add tradition-specific social proof on landing page
TOTAL FINDINGS: 7 (0 P0, 0 P1, 2 P2, 5 P3)
========================================================================
RECOMMENDATION The SermonWise landing page and signup are EXCELLENT for Rachel's persona -- Reformed is explicitly listed with PCA/OPC detail, Expository is a named style, and no credit card is required. The journey is PASSING for the SSR steps. The CSR steps (dashboard, generation, export) are UNTESTABLE and represent the highest-risk portion of the journey. The theological accuracy of the generated sermon is the ultimate make-or-break -- one Arminian interpretation of Romans 8:29 would permanently lose this persona. The showcase proves Reformed output is possible. Recommend: generate a test sermon on Romans 8:28-30 with Reformed tradition and evaluate theological accuracy manually.
=== JOURNEY REPORT: sermonwise-catholic-homily === Date: 2026-04-02 Persona: Pastor Maria (52, Catholic priest, tech comfort: medium) Goal: "I need a Catholic homily for this Sunday's readings from the Revised Common Lectionary." Property: sermonwise.ai Entry: https://sermonwise.ai/sermons
STEP 1: landing-page -- https://sermonwise.ai/sermons
Q1 (SEE): Same landing page as above. Hero: "Sermons & Homilies, Faithful to Your Tradition." The page explicitly mentions "Homily" as a style option and states "lectionary-based homily generation is built in for Catholic and Anglican traditions." Catholic is listed among the 17 traditions.
Q2 (SPEC): [PASS] Hero mentions tradition-aware preparation -- "Faithful to Your Tradition" [PASS] Catholic explicitly listed among traditions [PASS] "Homily" explicitly mentioned as a style -- "Liturgical traditions also access homily-specific methods" [PASS] Lectionary-based generation mentioned -- "lectionary-based homily generation is built in for Catholic and Anglican traditions" [PASS] Free tier available
Q3 (PERSONA): "I'm Maria, 52. I see 'Sermons & Homilies' in the hero -- the word 'Homilies' is right there. That's unusual for a tech tool. And then I read 'lectionary-based homily generation is built in for Catholic and Anglican traditions.' This tool was designed for someone like me. It understands that I don't choose my Scripture -- the lectionary assigns it. I'm genuinely impressed. I'm clicking 'Start Free.'"
Q4 (BETTER): 1. [MEDIUM IMPACT] Add a direct "Catholic Homily" example link from the landing page to the showcase 2. [LOW IMPACT] Mention specific Catholic features: "Connects First Reading, Psalm, and Gospel" -- the heart of lectionary preaching
Q5 (GOAL): Step 1 of 6. Goal: "Prepare a Catholic homily from this Sunday's lectionary readings." Maria sees Catholic and Homily explicitly. Lectionary integration mentioned. Trust earned immediately. Progress: 15%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 2: signup -- https://sermonwise.ai/sermons/signup
Q1 (SEE): Same signup form. The tradition dropdown includes "Roman Catholic" as a specific option (distinct from Eastern Orthodox, Anglican/Episcopal, etc.).
Q2 (SPEC): [PASS] "Roman Catholic" available in tradition dropdown (not just "Catholic") [PASS] No credit card required
Q3 (PERSONA): "I'm Maria, 52. I look for 'Roman Catholic' in the dropdown and... it's there. Not just 'Catholic' -- 'Roman Catholic.' That matters to me. They also have 'Eastern Orthodox' and 'Anglican/Episcopal' separately, which tells me the taxonomy is genuine, not a checkbox. I select Roman Catholic, enter my email, and create the account. Smooth."
Q4 (BETTER): 1. [LOW IMPACT] Add "Fr." or "Rev." as title options in the name field -- Catholic priests use formal titles
Q5 (GOAL): Step 2 of 6. Signup complete with Roman Catholic tradition. Progress: 25%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 3: dashboard -- https://sermonwise.ai/sermons/app
Q1 (SEE): CSR page -- referencing acceptance spec. Maria expects a lectionary-based starting point, ideally showing this Sunday's assigned readings.
Q2 (SPEC): [N/A] Cannot verify lectionary integration via WebFetch -- CSR page [CHECK] Spec mentions lectionary calendar access for Catholic tradition [CHECK] Dashboard should show "New Sermon/Homily" button
Q3 (PERSONA): "I'm Maria, 52. I'm looking for a way to start from this Sunday's lectionary readings. If the dashboard says 'This Sunday's Readings: [First Reading], [Psalm], [Gospel]' and I can click 'Generate Homily' from that -- I'll be amazed. If it just says 'Enter your Scripture passage' with a blank field, I have to go to another website to look up the readings first. That's not a dealbreaker, but it's a missed opportunity to show that this tool understands Catholic workflow."
Q4 (BETTER): 1. [HIGH IMPACT] Add "This Sunday's Readings" widget for Catholic and Anglican users -- auto-populate from the lectionary calendar 2. [MEDIUM IMPACT] Label the "New" button "New Homily" (not "New Sermon") for Catholic users 3. [LOW IMPACT] Show the liturgical season in the header (e.g., "5th Sunday of Easter, Year B")
Q5 (GOAL): Step 3 of 6. Path from dashboard to lectionary-based homily. Progress: 35%. Path: DEPENDS on lectionary integration. Risk: MEDIUM (manual lookup = friction). Momentum: AT RISK.
VERDICT: CONCERN Cannot verify. Lectionary integration is the critical differentiator for Catholic users.
STEP 4: homily-configuration -- https://sermonwise.ai/sermons/app/new
Q1 (SEE): CSR page -- referencing acceptance spec and landing page content. The landing page confirmed "Homily" is a style option alongside Expository, Topical, Narrative, and Devotional. Roman Catholic should be pre-filled from signup.
Q2 (SPEC): [N/A] Cannot verify form fields via WebFetch -- CSR page [CHECK] "Homily" should be available as a structure type (confirmed on landing page) [CHECK] Tradition should be pre-filled as Roman Catholic [CHECK] Length should default to 8-12 minutes for Catholic tradition
Q3 (PERSONA): "I'm Maria, 52. I enter this Sunday's readings (or ideally they're pre-populated from the lectionary). I select 'Homily' as the structure -- not 'Expository' or 'Topical.' If the default length for Catholic is 25 minutes, the tool doesn't understand that Catholic homilies are brief -- 8-12 minutes, integrated into the Mass. If it defaults to 10 minutes when I select 'Roman Catholic' and 'Homily,' that's a sign of deep understanding."
Q4 (BETTER): 1. [HIGH IMPACT] Default length to 10 minutes when tradition = Roman Catholic and structure = Homily 2. [MEDIUM IMPACT] Add a "Lectionary date" field that auto-populates readings when a date is selected 3. [LOW IMPACT] Add a "Connect readings" checkbox: "Link First Reading, Psalm, and Gospel thematically"
Q5 (GOAL): Step 4 of 6. Configuration for a Catholic homily. Progress: 50%. Path: ON TRACK. Risk: MEDIUM (length default matters). Momentum: STEADY.
VERDICT: CONCERN Cannot verify. Length default and Homily structure availability are critical.
STEP 5: homily-generation -- https://sermonwise.ai/sermons/app/new (output)
Q1 (SEE): CSR page. Per the showcase, the Roman Catholic example exists and would use Catholic theological vocabulary. The expected output should: connect First Reading to Gospel through the Responsorial Psalm, reference the Catechism or Church Fathers, and be 8-12 minutes (800-1400 words).
Q2 (SPEC): [N/A] Cannot verify generated content -- CSR page [CHECK] Spec requires Catholic theological markers (Eucharist, Magisterium, Tradition, Catechism) [CHECK] Spec requires lectionary reading connections (First Reading + Psalm + Gospel) [CHECK] Spec requires homily-appropriate length (800-1400 words)
Q3 (PERSONA): "I'm Maria, 52. I'm reading the generated homily. My critical test: Does it connect the First Reading to the Gospel through the Responsorial Psalm? This is the heart of Catholic lectionary preaching -- the readings are chosen to illuminate each other. If the homily treats the Gospel in isolation and ignores the First Reading, it's a Protestant sermon with Catholic words on top. I'm also checking for Catholic vocabulary: 'sacramental grace' not 'getting saved,' 'communion of saints' not 'prayer warriors,' 'Eucharist' not 'communion.' One 'personal relationship with Jesus' or 'sinner's prayer' and I know this isn't actually Catholic."
Q4 (BETTER): 1. [HIGH IMPACT] Add Catechism reference citations (CCC paragraph numbers) in the generated text 2. [MEDIUM IMPACT] Add a "Liturgical Notes" section: connections to the Eucharistic prayer, the season's collect, or the proper prayers of the day 3. [LOW IMPACT] Add a "Parish context" field: "Our parish is celebrating [First Communion / mission trip / etc.]"
Q5 (GOAL): Step 5 of 6. Homily generated. Catholic theological quality determines success. Progress: 80%. Path: ON TRACK (if theology is Catholic). Risk: HIGH (Protestant vocabulary = failure). Momentum: CRITICAL MOMENT.
VERDICT: CONCERN Cannot verify. Catholic theological accuracy is the make-or-break criterion.
STEP 6: review-and-export -- https://sermonwise.ai/sermons/app/new (export)
Q1 (SEE): CSR page. Export should include PDF (essential for printing for the ambo), Word, and Google Docs.
Q2 (SPEC): [N/A] Cannot verify -- CSR page [CHECK] Spec requires editable output [CHECK] Spec requires PDF export (critical for ambo use)
Q3 (PERSONA): "I'm Maria, 52. I need to add a reference to our parish's recent mission trip in the application section. The editing needs to be clean -- I'm not a coder. Then I export to PDF and print it for the ambo. The font should be readable at arm's length (14pt+), and the layout should be clean. If the PDF looks like a screenshot of a web page, I'll reformat it in Word."
Q4 (BETTER): 1. [MEDIUM IMPACT] Add "Ambo Format" PDF template: large font (14pt), wide margins, clear section breaks 2. [LOW IMPACT] Add "Print Preview" before export
Q5 (GOAL): Step 6 of 6. Goal: "Catholic homily based on this Sunday's lectionary readings." GOAL ACHIEVED if Maria has an 8-12 minute Catholic homily connecting the readings, with Catholic theological vocabulary, ready to print. Progress: 95%. Path: COMPLETE. Risk: LOW. Momentum: FINISHING.
VERDICT: CONCERN Cannot verify. CSR page. PDF export functionality is essential.
========================================================================
OUTCOME VERIFICATION [UNTESTABLE] Homily references Catholic sources -- requires live generation [UNTESTABLE] Homily connects at least two lectionary readings -- requires live generation [UNTESTABLE] Homily length is appropriate (800-1400 words) -- requires live generation
FAILURE MODE CHECK "Landing page never says 'homily'" -- CLEAR ("Sermons & Homilies" in hero) "No 'Roman Catholic' option in tradition selector" -- CLEAR (present in dropdown) "No lectionary integration" -- UNTESTABLE (landing page mentions it but CSR page can't verify) "Protestant terminology in output" -- UNTESTABLE "Homily doesn't connect the readings" -- UNTESTABLE "Default length is 25 minutes" -- UNTESTABLE "No Catechism or Magisterium references" -- UNTESTABLE
========================================================================
SUMMARY Steps completed: 6/6 Steps passed: 2 Steps with concerns: 4 Steps failed: 0 Goal achieved: PARTIAL (landing and signup verified; generation untestable)
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: None verifiable
P1 GOAL BLOCKED: None verifiable
P2 PERSONA RISKS: 1. No lectionary calendar integration would force Maria to look up readings on another site -- friction 2. Default length must be 8-12 minutes for Catholic Homily, not 25 minutes
P3 IMPROVEMENTS: 1. Add "This Sunday's Readings" widget for Catholic users 2. Default length to 10 minutes for Catholic + Homily 3. Add Catechism citation numbers (CCC paragraph references) in generated text 4. Add "Ambo Format" PDF template (large font, wide margins) 5. Label button "New Homily" for Catholic users
TOTAL FINDINGS: 7 (0 P0, 0 P1, 2 P2, 5 P3)
========================================================================
RECOMMENDATION The SermonWise Catholic homily journey is EXCELLENT on landing page and signup -- "Homilies" in the hero, "lectionary-based homily generation" explicitly mentioned, "Roman Catholic" in the tradition selector. Maria would be impressed. The CSR steps (dashboard, configuration, generation, export) are UNTESTABLE but the landing page promises align with Catholic needs. CONDITIONALLY PASSING -- the SSR steps earn trust. The critical verification needed: (1) Is there lectionary calendar integration? (2) Does "Homily" structure default to 8-12 minutes? (3) Does the generated content use Catholic vocabulary and connect readings? Recommend manual testing with a live Catholic homily generation.
=== JOURNEY REPORT: itw-find-illustration === Date: 2026-04-02 Persona: Pastor James (51, Teaching pastor at 400-member evangelical church, tech comfort: medium) Goal: "I'm preaching on grace this Sunday and I need a compelling illustration that my congregation will remember." Property: illustratetheword.com Entry: https://illustratetheword.com
STEP 1: homepage -- https://illustratetheword.com/
Q1 (SEE): Hero: "Sermon Illustrations that bring Scripture to life" with the tagline "Tell stories they can't forget." A compelling stat: "70% of a sermon is forgotten within 48 hours." A search bar is prominent with the description "The largest tradition-aware sermon illustration library." Browse categories: By Topic (Faith, Grace, Love, Forgiveness, 200+), By Scripture, By Emotion, By Tradition (17), By Source Type (Movies, history, poetry), Children's Ministry. Sample illustrations visible with titles and preview text. Library size: "53,000+ illustrations across 17 traditions." Premium: $9.95/month.
Q2 (SPEC): [PASS] Search bar for illustrations -- prominent, center of page [PASS] Topic/theme browse categories -- Grace, Faith, Love, etc. [PASS] Sample illustrations visible -- multiple titles and previews shown [PASS] Value proposition clear -- "53,000+ illustrations," "Tell stories they can't forget" [PASS] Premium pricing visible -- $9.95/month [PASS] Free content available -- browse and preview all 53,000+
Q3 (PERSONA): "I'm James, 51. It's Thursday night and I need a grace illustration by Saturday. This homepage gets me immediately -- '70% of a sermon is forgotten within 48 hours' -- that's exactly why I'm here. 53,000+ illustrations is a massive library. I see 'Grace' right there in the topic categories. I'm clicking it now. The homepage didn't waste my time with marketing -- it showed me the search bar and sample content immediately. This is a tool for pastors, built by someone who understands sermon prep."
Q4 (BETTER): 1. [MEDIUM IMPACT] Add a "This week's most popular" section showing trending illustrations 2. [LOW IMPACT] Add a "Quick search" shortcut: "Preaching on grace? Start here" -- direct link to grace-filtered results 3. [LOW IMPACT] Show the total number of grace illustrations in the category button: "Grace (2,400+)"
Q5 (GOAL): Step 1 of 4. Goal: "Find a compelling grace illustration." James has a clear path: search bar + topic categories + massive library. Progress: 20%. Path: CLEAR. Risk: LOW. Momentum: HIGH.
VERDICT: PASS
STEP 2: search-results -- https://illustratetheword.com/illustrations?q=grace
Q1 (SEE): The page shows a large results set from the 53,000+ library. Result cards display: illustration title, Scripture reference, source type (Sermon Illustration, Movie Analogy), 2-3 lines of preview text, tradition tags, and lock icons for premium content. Filter options: type (Stories, Poetry, Quotes, Biblical Insights, Historical, Movie Analogies, Devotionals, Tradition Perspectives), sort (Top Rated, Newest, Oldest), author filters. Pagination: "Page 1 of 2,214." Visible titles include movie analogies (To Kill a Mockingbird, Hacksaw Ridge, Just Mercy, Hotel Rwanda, Life Is Beautiful) and sermon illustrations.
Q2 (SPEC): [PASS] Search returns results for "grace" -- 2,214+ pages of results [PASS] Illustration titles visible with preview text [PASS] Themes/tags visible (Scripture references, source types) [PASS] Premium indicators present (lock icons) [PASS] Filter options available (type, sort, author) [PASS] Pagination present [CONCERN] The results may not be specifically filtered to "grace" topic -- some visible titles seem thematically tangential (Creation's Beauty, Shame). The search may be returning a broad set rather than precisely grace-themed results. [CONCERN] Preview text is only 2-3 lines -- James needs enough to judge quality without clicking into each one
Q3 (PERSONA): "I'm James, 51. 2,214 pages of results -- that's overwhelming but also reassuring that I'll find something fresh. I scroll through the first page. Movie analogies: Hacksaw Ridge, Just Mercy, Life Is Beautiful -- these are powerful films but are they specifically about GRACE or just generally inspiring? The previews are short -- 2-3 lines. I need to click into each one to judge quality, which is slower than I'd like. I'm looking for something I haven't used before... 'Forty-Six Years of Holy Stubbornness' -- that title catches my eye. I'll click that. But I notice lock icons on most cards -- I might need premium access for the good stuff."
Q4 (BETTER): 1. [HIGH IMPACT] Improve search relevance: ensure "grace" results are specifically about grace (unmerited favor, gift), not just tangentially related 2. [HIGH IMPACT] Show 4-5 lines of preview text instead of 2-3 -- enough to judge quality without clicking 3. [MEDIUM IMPACT] Add a "Fresh this week" filter to surface recently added illustrations 4. [LOW IMPACT] Add a "Not the usual suspects" filter that excludes the most commonly used illustrations
Q5 (GOAL): Step 2 of 4. Goal: "Find a compelling grace illustration." James has abundant results. Needs better filtering to find the gem. Progress: 45%. Path: ON TRACK. Risk: MEDIUM (relevance and preview depth). Momentum: STEADY.
VERDICT: CONCERN Search relevance may be too broad (returning tangentially related results) and preview text is too short to judge quality without clicking into each illustration.
STEP 3: illustration-detail -- https://illustratetheword.com/illustrations/[slug]
Q1 (SEE): Cannot fetch a specific illustration detail page without knowing a real slug. Based on the homepage sample, detail pages should show: full illustration text (or premium gate with preview), author/source attribution, related Scripture references, related illustrations, and save/bookmark options.
Q2 (SPEC): [N/A] Cannot verify specific illustration page without a real slug [CHECK] Spec requires full text or premium gate with adequate preview [CHECK] Spec requires source attribution [CHECK] Spec requires related illustrations
Q3 (PERSONA): "I'm James, 51. I clicked into an illustration and I'm reading it slowly, imagining how it would land from the pulpit. I'm checking three things: (1) Is the theology of grace correct -- unmerited favor, not just kindness? (2) Will both the 70-year-old deacon and the 25-year-old new Christian connect with it? (3) Is it fresh enough that my congregation hasn't heard it? If the full text is behind a paywall and I can only see 2 sentences, I can't judge quality. Show me at least the first paragraph before asking me to pay."
Q4 (BETTER): 1. [HIGH IMPACT] Show at least the first 100 words of every illustration free -- enough to judge quality before subscribing 2. [MEDIUM IMPACT] Add a "How to use this illustration" section with sermon integration tips 3. [LOW IMPACT] Add a "Similar but different" section showing alternative illustrations on the same theme
Q5 (GOAL): Step 3 of 4. Goal: "Find a compelling grace illustration." James is evaluating quality. The preview depth determines whether he can judge before subscribing. Progress: 65%. Path: ON TRACK. Risk: MEDIUM (paywall transparency). Momentum: STEADY.
VERDICT: CONCERN Cannot verify illustration detail page content. Key risk: is enough preview shown to judge quality before subscribing?
STEP 4: save-and-use -- https://illustratetheword.com/illustrations/[slug]
Q1 (SEE): Cannot verify specific illustration page functionality. Per homepage and search results: lock icons suggest premium access is required for full text. Copy and save functionality would be premium features.
Q2 (SPEC): [N/A] Cannot verify copy/save functionality [CHECK] Spec requires copy to clipboard [CHECK] Spec requires source attribution displayed [CHECK] Spec requires save to library/favorites
Q3 (PERSONA): "I'm James, 51. I found an illustration I want to use. I need to copy the text cleanly -- no weird formatting -- and paste it into my Google Doc. I also need the source attribution for integrity. If there's a 'Copy' button that gives me the text + 'Source: [author/title]' in one click, that's perfect. If I have to manually select text, copy, then separately find the attribution, that's friction but manageable. If the full text requires a $9.95/month subscription, I'm evaluating: Is this better than what I find on Google? If the quality of what I've seen is high, $9.95/month is a no-brainer for a pastor who uses illustrations every week."
Q4 (BETTER): 1. [HIGH IMPACT] Add a "Copy with Attribution" button that includes the illustration text + source in one clipboard action 2. [MEDIUM IMPACT] Add a "Export to Sermon Notes" feature that formats the illustration with a sermon-ready header 3. [LOW IMPACT] Add a "Used this illustration? Rate it" feedback loop
Q5 (GOAL): Step 4 of 4. Goal: "Find a compelling grace illustration." GOAL ACHIEVED if James finds, reads, and copies a fresh grace illustration with proper attribution. Progress: 85% (assuming quality illustration found). Path: COMPLETE. Risk: LOW. Momentum: POSITIVE.
VERDICT: CONCERN Cannot verify copy/save functionality or paywall behavior. The critical gate: is enough content free to judge quality?
========================================================================
OUTCOME VERIFICATION [VERIFIED] Search for "grace" returns relevant sermon illustrations -- 2,214+ pages of results [CONCERN] Results may include tangentially related content, not exclusively grace-themed [N/A] Illustration detail page full text -- cannot verify without specific slug [N/A] Source attribution on detail page -- cannot verify without specific slug
FAILURE MODE CHECK "Search returns zero results for grace" -- CLEAR (massive result set) "All results behind paywall with insufficient preview" -- CONCERN (lock icons on most cards, 2-3 line previews) "Illustration quality is low" -- UNTESTABLE (can't read full illustrations) "No copy/save functionality" -- UNTESTABLE "No source attribution" -- UNTESTABLE "Search is slow" -- CLEAR (results loaded) "No related illustrations suggested" -- UNTESTABLE "Mobile experience broken" -- UNTESTABLE "Premium gate gives no indication of quality" -- CONCERN (short previews behind lock icons)
========================================================================
SUMMARY Steps completed: 4/4 Steps passed: 1 Steps with concerns: 3 Steps failed: 0 Goal achieved: PARTIAL
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: None
P1 GOAL BLOCKED: None
P2 PERSONA RISKS: 1. Search relevance may be too broad -- "grace" results include tangentially related content 2. Preview text (2-3 lines) is insufficient to judge illustration quality from the results page 3. Lock icons on most cards with short previews make it hard to evaluate before subscribing
P3 IMPROVEMENTS: 1. Improve search relevance for topic-specific queries 2. Show 4-5 lines of preview text per result card 3. Add "Copy with Attribution" one-click button 4. Add "Fresh this week" filter 5. Show first 100 words free on all illustrations
TOTAL FINDINGS: 8 (0 P0, 0 P1, 3 P2, 5 P3)
========================================================================
RECOMMENDATION The ITW find-illustration journey has a STRONG homepage and search experience -- the library is massive (53,000+), categories are well-organized, and the value proposition is clear. The persona risks center on search relevance (are results specifically about grace or broadly related?) and preview depth (2-3 lines is not enough to judge quality). For a pastor in Thursday-night sermon-prep mode, the ability to quickly evaluate illustrations from the results page -- without clicking into each one -- is essential. CONDITIONALLY PASSING for launch. Priority fix: increase preview text length and improve search relevance for topic queries.
=== JOURNEY REPORT: cross-pewsearch-to-cwa === Date: 2026-04-02 Persona: Pastor Mike (48, PewSearch Premium subscriber, tech comfort: medium) Goal: "I already manage my church on PewSearch. I want to understand what ChurchWiseAI is and whether the AI chatbot/voice agent is worth adding." Property: pewsearch.com -> churchwiseai.com Entry: https://pewsearch.com/admin/[token]
STEP 1: pewsearch-admin -- https://pewsearch.com/admin/[token]
Q1 (SEE): CSR page -- referencing acceptance spec. Per pewsearch-premium.md, the PewSearch admin dashboard should contain a CWA upsell banner mentioning AI chatbot/voice agent with a CTA linking to churchwiseai.com.
Q2 (SPEC): [N/A] Cannot verify admin dashboard via WebFetch -- CSR page [CHECK] Spec requires CWA upsell banner in PewSearch admin
Q3 (PERSONA): "I'm Mike, 48. I'm in my PewSearch admin dashboard updating service times for Easter. I notice a banner that says something about AI -- 'Answer calls 24/7 with an AI church assistant' or similar. I'm mildly curious but I don't want PewSearch pushing products at me. If the banner is a small, informative card (not a full-page popup), I'll click to learn more. If it pops up every time I log in, I'll be annoyed."
Q4 (BETTER): 1. [HIGH IMPACT] Make the CWA banner contextual: "Your church receives X calls/week. Let AI handle the routine ones." (using PewSearch data) 2. [MEDIUM IMPACT] Allow dismissing the banner ("Don't show again") to respect the user's choice 3. [LOW IMPACT] Time the banner to appear after Mike has completed his primary task (editing), not before
Q5 (GOAL): Step 1 of 5. Goal: "Understand CWA and decide if it's worth adding." Mike noticed the upsell. If the banner is informative, he'll investigate. Progress: 10%. Path: STARTING. Risk: LOW. Momentum: CURIOUS.
VERDICT: CONCERN Cannot verify CWA upsell banner presence in PewSearch admin. CSR page.
STEP 2: cwa-landing-from-pewsearch -- https://churchwiseai.com/?ref=pewsearch
Q1 (SEE): The CWA homepage with ?ref=pewsearch parameter. WebFetch confirms: NO customization for PewSearch referrals. The page is identical to the regular homepage. No mention of PewSearch integration, no "Welcome PewSearch customer" messaging, no contextual landing experience. PewSearch appears only in the footer as a related product.
Q2 (SPEC): [FAIL] No PewSearch-referral customization -- the ?ref=pewsearch parameter has NO effect on the page content -- SPEC VIOLATION [FAIL] No mention of how CWA relates to or enhances PewSearch -- products feel unrelated -- SPEC VIOLATION [PASS] Product explanation is clear (from the standard homepage) [PASS] Pricing is one click away
Q3 (PERSONA): "I'm Mike, 48. I clicked the banner from PewSearch and landed on... what looks like a completely different company's website. There's no mention of PewSearch anywhere above the fold. No 'Welcome, PewSearch customer' message. No explanation of how this relates to the product I'm already paying for. Am I in the right place? Is this made by the same people? I see 'ChurchWiseAI' in the logo -- not 'PewSearch.' I'm confused about the relationship. If the landing page said 'You already manage your church on PewSearch. ChurchWiseAI adds AI-powered phone and chat agents to your church's toolkit,' I'd understand immediately."
Q4 (BETTER): 1. [HIGH IMPACT] Create a PewSearch-specific landing page (or at minimum, dynamic hero copy when ?ref=pewsearch is present): "You already use PewSearch for your church directory. Add AI-powered phone and chat agents to answer calls and capture visitors 24/7." 2. [HIGH IMPACT] Show the relationship: "From the WiseAI ecosystem -- the same team that built PewSearch" 3. [MEDIUM IMPACT] Pre-populate the user's church name from PewSearch data when they click through 4. [LOW IMPACT] Add a "PewSearch customers save X%" or "Your church info transfers automatically" messaging
Q5 (GOAL): Step 2 of 5. Goal: "Understand CWA and decide if it's worth adding." Mike landed on CWA but the connection to PewSearch is invisible. Products feel like separate companies. Progress: 25%. Path: UNCLEAR (relationship between products not explained). Risk: HIGH (Mike may leave, confused). Momentum: DECLINING.
VERDICT: FAIL No PewSearch-referral customization. Products feel unrelated. Mike doesn't understand the connection.
STEP 3: pricing-evaluation -- https://churchwiseai.com/pricing
Q1 (SEE): Standard CWA pricing page (as evaluated in Journey 1). Three tiers, Pro highlighted as "Most Popular." Pro plan includes "Pro Website ($19.95 value)" which is a PewSearch product -- this is the one indirect connection.
Q2 (SPEC): [PASS] CWA pricing with clear tiers [CONCERN] No PewSearch bundle or integration pricing visible [CONCERN] The Pro plan includes "Pro Website ($19.95 value)" but doesn't explain that this IS a PewSearch feature [CONCERN] No total cost calculation showing PewSearch + CWA combined
Q3 (PERSONA): "I'm Mike, 48. I'm already paying $9.95/month for PewSearch Premium. Now CWA wants $14.95-$99.95/month on top of that. Total: $24.90 to $109.90/month. That's a lot for a 250-member church. I see 'Pro Website ($19.95 value) included' on the Pro plan -- wait, is that related to my PewSearch page? If so, does my current $9.95 Premium get upgraded to Pro Website automatically? Or am I paying for two overlapping things? Nobody is explaining this to me."
Q4 (BETTER): 1. [HIGH IMPACT] Add a "Already a PewSearch customer?" section on the pricing page that explains how the products work together and whether Premium is included/upgraded 2. [HIGH IMPACT] Show a combined pricing view: "PewSearch Premium ($9.95) + CWA Pro Chat ($34.95) = $44.90/month total" 3. [MEDIUM IMPACT] Offer a PewSearch customer discount or bundle acknowledgment 4. [LOW IMPACT] Add a FAQ: "I already have PewSearch Premium. Do I need to pay separately?"
Q5 (GOAL): Step 3 of 5. Goal: "Decide if CWA is worth the additional cost." Mike knows the CWA price but can't calculate the total cost including PewSearch. No bundle clarity. Progress: 45%. Path: UNCLEAR (pricing relationship unresolved). Risk: HIGH (overlapping costs = confusion). Momentum: STALLED.
VERDICT: CONCERN No PewSearch customer acknowledgment on pricing page. Combined cost is unclear.
STEP 4: demo-experience -- https://churchwiseai.com/demo
Q1 (SEE): Same demo page as evaluated in Journey 1. Interactive chatbot, phone numbers, no signup required.
Q2 (SPEC): [PASS] Demo available without signup [PASS] Interactive chatbot and phone numbers [PASS] Multiple demo scenarios
Q3 (PERSONA): "I'm Mike, 48. The demo is good -- I can call the number and hear the voice agent. I imagine Mrs. Johnson calling at 2am about the potluck and getting a friendly, helpful response instead of voicemail. That's the value. But I'm still not sure how this connects to my PewSearch page. Will the chatbot know my church information from PewSearch? Will my PewSearch listing link to the chatbot? These integration questions are unanswered."
Q4 (BETTER): 1. [HIGH IMPACT] Show integration examples: "Your PewSearch listing gets a 'Chat with us' button when you add CWA" 2. [MEDIUM IMPACT] Demo with a PewSearch-connected church showing the integration in action
Q5 (GOAL): Step 4 of 5. Goal: "Decide if CWA is worth adding." Mike sees the product value but integration with PewSearch is unclear. Progress: 65%. Path: ON TRACK (product value clear). Risk: MEDIUM (integration uncertainty). Momentum: REBUILDING.
VERDICT: PASS
STEP 5: signup-decision -- https://churchwiseai.com/onboard
Q1 (SEE): The onboard page was fetched as the pricing page (likely redirect or CSR rendering). Per acceptance spec, the onboard flow should include: church search that finds Mike's church (already in the database from PewSearch), plan selection, and Stripe checkout. The key question: does the church search pre-populate from PewSearch data?
Q2 (SPEC): [N/A] Cannot verify onboard form functionality -- partially CSR [CHECK] Spec requires church search that finds existing churches [CHECK] Spec requires Mike's church to appear pre-populated with PewSearch data
Q3 (PERSONA): "I'm Mike, 48. I decided to try CWA. I click 'Get Started' and land on the onboard page. If I search for my church name and it appears immediately -- pre-populated with the name, address, and denomination from my PewSearch listing -- I'll feel like these products are genuinely connected. If I have to re-enter my church name, address, city, state, denomination, and service times FROM SCRATCH when all of that is already in PewSearch... I'll be frustrated. 'Don't these systems talk to each other?'"
Q4 (BETTER): 1. [HIGH IMPACT] Pre-populate church data from PewSearch when onboarding from a PewSearch referral 2. [HIGH IMPACT] Add "We found your church from PewSearch" messaging during onboard 3. [MEDIUM IMPACT] Auto-link PewSearch Premium subscription to CWA account for unified billing reporting
Q5 (GOAL): Step 5 of 5. Goal: "Start a CWA subscription with church data from PewSearch." GOAL ACHIEVED if Mike can find his church and start CWA without re-entering information already in PewSearch. Progress: 80%. Path: PARTIALLY CLEAR. Risk: MEDIUM (data pre-population uncertainty). Momentum: CAUTIOUSLY POSITIVE.
VERDICT: CONCERN Cannot verify church search or data pre-population. CSR page.
========================================================================
OUTCOME VERIFICATION [UNTESTABLE] PewSearch admin has CWA upsell banner -- CSR page [NOT VERIFIED] CWA homepage explains product for PewSearch referrals -- NO customization detected [UNTESTABLE] CWA onboard finds churches from PewSearch database -- CSR page
FAILURE MODE CHECK "No CWA upsell visible in PewSearch admin" -- UNTESTABLE (CSR) "Upsell banner is too aggressive" -- UNTESTABLE (CSR) "CWA landing page has no mention of PewSearch integration" -- TRIGGERED -- no PewSearch mention above the fold "Mike can't find his church in CWA onboard search" -- UNTESTABLE (CSR) "Pricing doesn't acknowledge existing PewSearch customers" -- TRIGGERED -- no PewSearch customer section on pricing "Demo requires signup" -- CLEAR (no signup required) "CWA and PewSearch use different logins" -- TRIGGERED -- separate products, separate auth "The referral link (ref=pewsearch) doesn't modify the landing experience" -- TRIGGERED -- confirmed no modification
========================================================================
SUMMARY Steps completed: 5/5 Steps passed: 1 Steps with concerns: 3 Steps failed: 1 Goal achieved: PARTIAL
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: 1. CWA homepage ignores ?ref=pewsearch parameter -- no PewSearch-specific messaging or experience 2. No cross-product relationship explanation anywhere in the journey
P1 GOAL BLOCKED: 1. PewSearch customers land on CWA with no context about the relationship between products -- feels like a different company
P2 PERSONA RISKS: 1. Combined cost (PewSearch + CWA) is unclear -- Mike can't calculate total spend 2. No acknowledgment of existing PewSearch subscription on CWA pricing page 3. Separate logins/accounts create friction for cross-product customers
P3 IMPROVEMENTS: 1. Create PewSearch-specific landing page with relationship explainer 2. Add "Already a PewSearch customer?" section on CWA pricing page 3. Show combined pricing view 4. Pre-populate church data from PewSearch during CWA onboard 5. Add integration examples ("Your listing gets a Chat button")
TOTAL FINDINGS: 11 (2 P0, 1 P1, 3 P2, 5 P3)
========================================================================
RECOMMENDATION The cross-property journey from PewSearch to CWA is the WEAKEST of all 10 journeys. The ?ref=pewsearch parameter has zero effect on the CWA landing page -- there is no PewSearch-specific messaging, no relationship explanation, no pricing acknowledgment, and no data sharing. Pastor Mike would feel like he clicked an ad for a random company, not a related product from the same ecosystem. This journey is NOT PASSING for launch. Priority fixes: (1) Create a PewSearch-referral landing variant, (2) Add "Already on PewSearch?" to CWA pricing, (3) Explain the WiseAI ecosystem relationship. Without these, the cross-sell from PewSearch to CWA will have a near-zero conversion rate.
=== JOURNEY REPORT: cross-itw-to-sermonwise === Date: 2026-04-02 Persona: Pastor Karen (43, Baptist teaching pastor, ITW Premium subscriber, tech comfort: medium) Goal: "I use ITW for illustrations. I want to know if SermonWise can help me with full sermons." Property: illustratetheword.com -> sermonwise.ai Entry: https://illustratetheword.com
STEP 1: itw-sermon-prep -- https://illustratetheword.com/
Q1 (SEE): The ITW homepage shows illustrations library with search, browse categories, and sample content. Looking for SermonWise cross-promotion: the footer links include "SermonWise AI" under the company section. No banner, sidebar, or contextual CTA promoting SermonWise is visible in the main content area or hero section.
Q2 (SPEC): [FAIL] No prominent SermonWise cross-promotion visible -- only a footer link -- SPEC VIOLATION [FAIL] No pain-point-specific messaging ("Tired of 12+ hours on sermon prep?") -- SPEC VIOLATION [PASS] SermonWise AI link exists in the footer
Q3 (PERSONA): "I'm Karen, 43. I'm on IllustrateTheWord searching for this week's illustration. I don't see ANYTHING about SermonWise on the main page. There might be a link in the footer but I never scroll to footers when I'm in search mode. If there was a banner that said 'Love our illustrations? Get a full AI sermon outline to go with them -- try SermonWise free,' I'd absolutely click it. But there's nothing. The cross-sell from ITW to SermonWise isn't happening."
Q4 (BETTER): 1. [HIGH IMPACT] Add a contextual SermonWise banner: "Found your illustration? Now generate the rest of your sermon. Try SermonWise Free." 2. [HIGH IMPACT] Add SermonWise cross-promotion on illustration detail pages: "Use this illustration in a full AI-generated sermon outline" 3. [MEDIUM IMPACT] Add a "Complete Your Sermon" CTA after a user saves/copies an illustration 4. [LOW IMPACT] Add SermonWise mention in the ITW email newsletter
Q5 (GOAL): Step 1 of 5. Goal: "Discover and evaluate SermonWise from ITW." Karen did NOT notice SermonWise from the ITW homepage. The cross-sell failed at step 1. Progress: 5%. Path: BLOCKED (no visible cross-promotion). Risk: HIGH. Momentum: NOT STARTED.
VERDICT: FAIL No prominent SermonWise cross-promotion on ITW. Only a footer link. Karen would never discover SermonWise from her ITW workflow.
STEP 2: sermonwise-landing -- https://sermonwise.ai/sermons
Q1 (SEE): (Assuming Karen found SermonWise through another channel.) Same landing page as evaluated in previous journeys. Hero: "Sermons & Homilies, Faithful to Your Tradition." 17 traditions listed. Baptist (SBC, Independent) explicitly present. Free tier available.
Q2 (SPEC): [PASS] SermonWise landing page with clear value proposition [PASS] Baptist tradition explicitly listed [PASS] Free tier available without credit card [CONCERN] No mention of ITW integration or combined value for existing ITW subscribers
Q3 (PERSONA): "I'm Karen, 43. Let's pretend I found SermonWise through a friend instead of ITW. The landing page is good -- Baptist is listed, free tier available, 17 traditions. But there's no mention of IllustrateTheWord anywhere. I'm already paying $9.95/month for ITW. If SermonWise acknowledged that -- 'ITW Premium subscriber? Your illustrations integrate directly with SermonWise outlines' -- I'd feel like this ecosystem was designed for me. Instead, it feels like two unrelated products."
Q4 (BETTER): 1. [HIGH IMPACT] Add ITW integration messaging: "Your ITW illustrations work seamlessly in SermonWise outlines" 2. [MEDIUM IMPACT] Show combined value: "ITW ($9.95) + SermonWise ($19.95) = Your complete sermon prep toolkit for $29.90/month" 3. [LOW IMPACT] Add a "Used ITW? Get 1 month free on SermonWise" promotion
Q5 (GOAL): Step 2 of 5. Goal: "Evaluate SermonWise for full sermon preparation." Karen understands the product. No ITW acknowledgment. Progress: 25%. Path: ON TRACK (for product evaluation). Risk: MEDIUM (no ecosystem feeling). Momentum: MODERATE.
VERDICT: CONCERN No ITW integration messaging. Products feel disconnected.
STEP 3: showcase-quality-proof -- https://sermonwise.ai/sermons/showcase
Q1 (SEE): The showcase page displays 17 complete sermon examples based on John 3:16-21, covering multiple traditions. A "Baptist (Distinctive)" example is present. All examples are freely visible with PDF download. 12 sermon methods supported. 300K+ curated sources referenced. 5 voice/style dimensions shown.
Q2 (SPEC): [PASS] Baptist tradition example available in the showcase [PASS] Full sermon text visible without login [PASS] PDF download available [PASS] Quality indicators present (300K+ sources, 12 methods, 5 style dimensions)
Q3 (PERSONA): "I'm Karen, 43. I click into the Baptist example and start reading it like I'm grading a seminary student's paper. Is the exegesis original or just a summary of every commentary? Is the application specific ('When your neighbor's marriage is falling apart and they call you at midnight...') or generic ('We should all show more love')? Does it sound like it was written by a pastor or by an algorithm? I'm reading carefully... The showcase has Baptist-specific content and it's freely visible. That's good -- I can judge quality before committing. If this is genuinely good, $19.95/month is nothing compared to the 5+ hours/week it could save me."
Q4 (BETTER): 1. [MEDIUM IMPACT] Add a "SBC-specific" label on the Baptist example (Karen identifies as SBC specifically) 2. [LOW IMPACT] Add a "Compare with your own sermon" prompt: "Generate a sermon on the same passage and compare quality side by side"
Q5 (GOAL): Step 3 of 5. Goal: "Evaluate quality of SermonWise output." Karen can read a full Baptist sermon example. This is the quality gate. Progress: 50%. Path: CLEAR. Risk: MEDIUM (quality is subjective). Momentum: BUILDING.
VERDICT: PASS
STEP 4: signup-and-first-sermon -- https://sermonwise.ai/sermons/signup
Q1 (SEE): Same signup page as evaluated previously. Tradition dropdown includes "Baptist (SBC, Independent)." No credit card required. No ITW subscriber recognition or SSO.
Q2 (SPEC): [PASS] Free signup without credit card [PASS] Baptist (SBC, Independent) in tradition selector [FAIL] No ITW subscriber recognition -- Karen creates a completely separate account -- SPEC VIOLATION [FAIL] No SSO or account linking between ITW and SermonWise -- PERSONA RISK
Q3 (PERSONA): "I'm Karen, 43. I'm creating ANOTHER account? I already have an ITW account with my email. Why isn't there a 'Sign in with your ITW account' option? Or at minimum, when I enter my email, a message that says 'Welcome back! We see you're an ITW Premium subscriber.' Instead, I'm creating a fresh account as if I've never used any ChurchWiseAI product before. These products don't talk to each other. That's disappointing."
Q4 (BETTER): 1. [HIGH IMPACT] Add SSO or account recognition: "Sign in with your ITW account" or "We see you're an ITW subscriber -- welcome!" 2. [MEDIUM IMPACT] Pre-populate email from a referral link that carries ITW account context 3. [LOW IMPACT] Add a welcome banner for ITW subscribers: "As an ITW Premium subscriber, you get X additional benefit"
Q5 (GOAL): Step 4 of 5. Goal: "Try SermonWise and generate a first sermon." Karen is signing up. Separate account creation is friction but not a blocker. Progress: 70%. Path: ON TRACK. Risk: LOW (she'll complete signup despite friction). Momentum: SLIGHTLY DECLINING.
VERDICT: CONCERN No ITW account recognition. Separate accounts for the same ecosystem feel disconnected.
STEP 5: evaluate-and-decide -- https://sermonwise.ai/sermons/app
Q1 (SEE): CSR page -- referencing acceptance spec. Karen would see her dashboard with the generated sermon, editing tools, and export options. Upgrade CTA for Pro features would be visible.
Q2 (SPEC): [N/A] Cannot verify dashboard via WebFetch -- CSR page [CHECK] Spec requires generated sermon with Baptist markers [CHECK] Spec requires editable output with export [CHECK] Spec requires Pro upgrade CTA
Q3 (PERSONA): "I'm Karen, 43. I generated my first sermon and I'm comparing it to my usual process. If this saves me even 4 hours/week on structure and exegesis, the combined $29.90/month (ITW + SermonWise) is under $2/hour of time reclaimed. That ROI is clear. But the two products feel completely separate -- different logins, different dashboards, no 'Insert ITW illustration' button in the SermonWise editor. I'll use both tools, but the workflow will be: generate sermon in SermonWise, find illustration in ITW, manually copy illustration into the sermon. That works, but it's not the integrated experience I hoped for."
Q4 (BETTER): 1. [HIGH IMPACT] Add "Insert ITW Illustration" button in the SermonWise editor 2. [HIGH IMPACT] Show combined ROI: "You saved 5.5 hours this week using ITW + SermonWise together" 3. [MEDIUM IMPACT] Add a combined subscription: "Get both for $24.95/month (save $5.85)" -- rewards ecosystem loyalty 4. [LOW IMPACT] Add a workflow guide: "How to use ITW and SermonWise together for complete sermon prep"
Q5 (GOAL): Step 5 of 5. Goal: "Decide if SermonWise is worth $19.95/month on top of ITW." Karen has generated a sermon. Quality determines the decision. The lack of integration is disappointing but not blocking. Progress: 90%. Path: COMPLETE. Risk: LOW (if quality is high). Momentum: POSITIVE (product value) but DISAPPOINTED (no integration).
VERDICT: CONCERN Cannot verify sermon quality. No ITW integration in the SermonWise experience.
========================================================================
OUTCOME VERIFICATION [NOT VERIFIED] ITW has visible SermonWise cross-promotion -- only footer link, no banner [VERIFIED] SermonWise landing page mentions Baptist tradition [VERIFIED] Showcase includes a Baptist sermon example [NOT VERIFIED] Signup acknowledges ITW subscribers -- no recognition
FAILURE MODE CHECK "No SermonWise cross-promotion visible on ITW" -- TRIGGERED -- only footer link "Cross-promotion is generic" -- N/A (no cross-promotion exists to evaluate) "SermonWise landing page doesn't mention Baptist" -- CLEAR (Baptist listed) "Showcase has no Baptist example" -- CLEAR (Baptist Distinctive example present) "Signup requires credit card" -- CLEAR (no credit card) "Generated sermon is generic" -- UNTESTABLE "No mention of ITW integration" -- TRIGGERED -- no ITW mention anywhere on SermonWise "Export is broken" -- UNTESTABLE "Free tier too limited" -- CONCERN (2 outlines/month -- may be enough to judge)
========================================================================
SUMMARY Steps completed: 5/5 Steps passed: 1 Steps with concerns: 3 Steps failed: 1 Goal achieved: PARTIAL
FINDINGS BY SEVERITY
P0 SPEC VIOLATIONS: 1. No SermonWise cross-promotion on ITW beyond a footer link -- the discovery path is broken 2. No ITW subscriber recognition on SermonWise signup -- separate accounts with no ecosystem acknowledgment
P1 GOAL BLOCKED: 1. ITW-to-SermonWise cross-sell relies on a footer link Karen will never see during active illustration searching
P2 PERSONA RISKS: 1. Products feel like separate companies -- no integration messaging, no shared accounts 2. Combined cost ($29.90/month) with no bundle discount feels like two separate bills 3. No "Insert ITW Illustration" in SermonWise editor -- workflow stays manual
P3 IMPROVEMENTS: 1. Add contextual SermonWise banner on ITW illustration pages 2. Add SSO or account recognition across ITW and SermonWise 3. Show combined pricing and ROI 4. Add "Insert ITW Illustration" button in SermonWise editor 5. Add ecosystem bundle discount
TOTAL FINDINGS: 11 (2 P0, 1 P1, 3 P2, 5 P3)
========================================================================
RECOMMENDATION The ITW-to-SermonWise cross-sell journey is FAILING at step 1 -- there is no prominent cross-promotion on ITW. Karen would never discover SermonWise from her ITW workflow. Even if she finds SermonWise through another channel, the products feel completely disconnected: separate accounts, no integration messaging, no bundle pricing, no shared features. This journey is NOT PASSING for launch. The cross-sell strategy depends on ITW being a discovery channel for SermonWise, and that channel is currently closed. Priority fixes: (1) Add contextual SermonWise banner on ITW pages, (2) Add SSO or account recognition, (3) Show combined value messaging. These are prerequisite for cross-property revenue generation.
========================================================================
=== COMBINED JOURNEY SUMMARY === Date: 2026-04-02 Journeys run: 10
| Journey | Persona | Steps | Passed | Concerns | Failed | Goal |
|---|---|---|---|---|---|---|
| cwa-board-leader-evaluation | Board Leader Mark (55) | 5 | 4 | 1 | 0 | PARTIAL |
| cwa-chatbot-training | Pastor Tom (44) | 5 | 0 | 5 | 0 | UNTESTABLE |
| cwa-admin-monday-morning | Admin Linda (47) | 4 | 0 | 4 | 0 | UNTESTABLE |
| pewsearch-find-church | Sarah (29) | 4 | 3 | 1 | 0 | PARTIAL |
| pewsearch-claim-listing | Pastor David (60) | 5 | 2 | 3 | 0 | PARTIAL |
| sermonwise-first-sermon | Pastor Rachel (38) | 6 | 2 | 4 | 0 | PARTIAL |
| sermonwise-catholic-homily | Pastor Maria (52) | 6 | 2 | 4 | 0 | PARTIAL |
| itw-find-illustration | Pastor James (51) | 4 | 1 | 3 | 0 | PARTIAL |
| cross-pewsearch-to-cwa | Pastor Mike (48) | 5 | 1 | 3 | 1 | PARTIAL |
| cross-itw-to-sermonwise | Pastor Karen (43) | 5 | 1 | 3 | 1 | PARTIAL |
TOTALS: 49 steps across 10 journeys Steps passed: 16 Steps with concerns: 31 Steps failed: 2 Goals fully achieved: 0 Goals partially achieved: 8 Goals untestable: 2
TOTAL FINDINGS ACROSS ALL JOURNEYS: P0 SPEC VIOLATIONS: 7 P1 GOAL BLOCKED: 3 P2 PERSONA RISKS: 22 P3 IMPROVEMENTS: 52 TOTAL: 84
TOP 10 CRITICAL FINDINGS:
-
[P0] CROSS-SELL BROKEN: CWA homepage ignores ?ref=pewsearch -- no PewSearch-specific messaging. PewSearch-to-CWA cross-sell has near-zero conversion potential. (cross-pewsearch-to-cwa, Step 2)
-
[P0] CROSS-SELL BROKEN: No SermonWise cross-promotion on ITW beyond a footer link. Karen would never discover SermonWise from ITW. (cross-itw-to-sermonwise, Step 1)
-
[P0] NO CASE STUDIES: CWA compare page has no case studies, testimonials, or concrete ROI metrics. Board evaluators have no quantitative proof to present. (cwa-board-leader-evaluation, Step 5)
-
[P0] NO ECOSYSTEM RECOGNITION: ITW subscribers get no acknowledgment on SermonWise signup -- separate accounts, no SSO, no shared identity. (cross-itw-to-sermonwise, Step 4)
-
[P1] CROSS-PRODUCT DISCONNECT: Products across the WiseAI ecosystem feel like separate companies with no relationship explanation, no shared accounts, no combined pricing. (cross-pewsearch-to-cwa + cross-itw-to-sermonwise)
-
[P1] CLAIM FLOW FRICTION: PewSearch claim flow leads with $9.95/mo payment, but the persona (Pastor David) just wants to fix ONE wrong service time for free. The free correction path is secondary and lacks timeline transparency. (pewsearch-claim-listing, Step 3)
-
[P0] MISSING "WHAT TO EXPECT": PewSearch church detail pages have no "What to Expect" section -- the #1 anxiety-reducer for first-time church visitors and hesitant returners. (pewsearch-find-church, Step 3)
-
[P2] CSR DASHBOARD UNVERIFIABLE: 3 full journeys (15 steps) are entirely CSR admin pages that cannot be evaluated via WebFetch. Agent jargon, empty training fields, and simulator accuracy are HIGH RISK but unverified. (cwa-chatbot-training, cwa-admin-monday-morning)
-
[P0] NO "VS HIRING STAFF" COMPARISON: CWA compare page doesn't address the treasurer's objection: "Why not just hire a part-time receptionist?" (cwa-board-leader-evaluation, Step 5)
-
[P2] SEARCH RELEVANCE: ITW search for "grace" returns tangentially related results with only 2-3 lines of preview -- insufficient to judge quality from the results page. (itw-find-illustration, Step 2)
========================================================================
TESTING PLATFORM IMPROVEMENT SUGGESTIONS:
-
Add a "CSR page simulator" capability that uses Playwright to capture screenshots of admin dashboards and inject them into journey evaluations, eliminating the 15 UNTESTABLE steps.
-
Create a "cross-property referral tester" that automatically checks whether ?ref= parameters modify landing page content across all properties.
-
Add automated "search relevance scoring" for ITW and PewSearch that measures how precisely search results match the query topic (not just keyword presence).
-
Build a "persona voice validator" that checks Q3 responses against the persona's tech_comfort and key_concerns to ensure the voice stays authentic.
-
Add a "combined pricing calculator" test that verifies all cross-property pricing combinations are documented and accessible to users who subscribe to multiple products.