Faith-based organizations · AI native transformation
A small church office, with time back for its people.
A neighborhood church runs on a part-time office manager and a team of volunteers. We helped them bring AI into the weekly bulletin, the website, and common questions, with clear privacy rules and a person reviewing every word.
- Client
- A neighborhood church
- Type
- AI native transformation
- Scope
- 4 weekly tasks, 6 staff and volunteers
- Result
- About 6 hours a week back
Context and goals
Each week the office writes a bulletin, updates the website and calendar, answers the same questions by phone and email, and posts news for families.
The church wanted help with the routine work, without sharing private information about members or losing its own voice.
What success looks like
- A person reviews and approves every draft before it goes out.
- No private member information goes into an AI tool.
- The bulletin, website, and posts work for people who use screen readers or large print.
- Volunteers can spot a scam message that claims to come from the pastor.
What we measured
We sat with the office manager and volunteers, timed each weekly task, and noted every place where member information was used.
Hours saved each week, by task
- Weekly bulletin3 hours
- Common questions2 hours
- Website and calendar1 hour
About 6 hours a week, with a person reviewing every draft.
| Task | Before | After | Who reviews |
|---|---|---|---|
| Weekly bulletin | About 5 hours, a scanned PDF | About 2 hours, tagged, with a large print version | Office manager |
| Common questions | Answered one at a time | Plain answers on the website | Pastor |
| Website and calendar | Updated in two places | Updated once, from one calendar | Office manager |
| Scam messages | No plan | A simple check and report step | Every volunteer |
What we found
- The good news: the team already had templates and a steady weekly rhythm.
- The bulletin took about 5 hours a week, much of it copying and reformatting.
- The same 20 questions made up most phone calls and emails.
- The bulletin was posted as a scanned PDF, which screen readers cannot read.
- Members had received gift card scam emails that pretended to be from the pastor.
The path to good
- We set up the AI assistant included in the church’s office software, with written rules for what can and cannot go into it.
- We built a bulletin template that drafts from the calendar, with headings and a large print version, and a person reviews every word.
- We wrote plain answers to the 20 common questions for the website, and the pastor reviewed each one.
- We trained the team in a two-hour session, including how to spot and report impersonation scams.
Follow-up
A month later, the office had about 6 hours a week back, the bulletin was posted as a tagged file with a large print version, and volunteers had reported two scam messages before anyone replied.
All case studies are samples. Each is based on our past work or on our audits of publicly available websites, documents, and social media. Names and details have been changed to protect privacy.
Before you buy
We start with a free light audit.
We prepare it for you and send you what we find.
- We check your homepageKeyboard, screen reader, contrast, and zoom.
- We review one public documentTags, headings, image descriptions, and language.
- We fix one public document freeYou get it back fixed, with a before and after.
- We send you what we findA short written summary you can share with your team.