There are no right or wrong answers, but I need an updated list of needs, and I'll see what we I can crank out the rest of this week. Drop your answer/need in the comments.

I recently watched a "special flower" church service that didn't read or mention a single Bible reference. This was their normal Sunday service, not some one-off event. I think they might do this twice a year in place of their "normal" service schedule. I actually rewatched the recording to make sure I hadn't missed one. I'll admit, that's a really interesting church strategy. I'll say more about this later, but my mind jumped back to one service where I afterward counted 66 Bible verses read aloud during the service. My feeling is that the right number should land somewhere well above 0 and well below 66. 𝗪𝗵𝗮𝘁 𝗱𝗼 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸? --- Most pastors don't track how many verses get discussed during a service, and that includes more than just the sermon. AI offers an easy way to count them. Take the audio or video of the entire service and have AI generate a transcript, assuming your streaming service doesn't already produce one automatically. Then ask the AI to identify every Bible verse in the transcript and show the exact verse along with its location in the Bible. It's a simple way to keep a running total.

If you run a membership community on Skool or just have a ministry website, your About page/homepage is your front door. It's where every curious visitor decides whether to step inside or quietly move on, and it's the only thing standing between them and the join button. And on Skool you get 1,000 characters to make it count. Even on your website, you should try to narrow it down to 1,000 characters. Message clarity is greater than characters used. That constraint changes everything. There's no room for a mission statement, your founding story, and a feature list. Every line has to earn its place, which is why the About pages that welcome the most new members tend to follow proven copywriting frameworks instead of winging it. The ones I see working on Skool right now: PAS (Problem, Agitate, Solution). Open with the struggle your ideal member feels, press on it, then position your community as the relief. It tells visitors "You're in the right place" in the first two lines. The value stack. A scannable bulleted list of exactly what's inside. Courses by name, calls, templates. People don't join "a community," they join a pile of specific things they can picture. Who it's for / who it's not for. A gentle filter helps the wrong-fit visitor move on and makes the right-fit visitor feel seen. On Skool, member quality is the product. Proof up top. Your most credible, specific fact belongs in the first three lines, not paragraph four. A number beats an adjective every time. Most About pages I read bury their best material and lead with their weakest. There are all kinds of variations but why pick just one? Here's where it gets interesting. I prompted Claude Fable 5, Anthropic's newest model, to master every major About page framework and rewrite landing page copy line by line. I've been testing its capabilities on my own pages, and the before-and-after surprised me. Want me to run yours through it? Comment "heck yea" and I'll DM you the results. I'm not saying it will always be better or convert better because that requires testing. This is just one example where the models are getting smart enough it doesn't always make sense to use just one specific framework when it can understand dozens and pick and choose to deliver what it thinks is the best overall version.