Book a free consultation

Workflow examples

What changes, step by step. Each example starts from approved information, marks the steps AI drafts, and ends with a person approving the result.

One approved announcement, four places

The busywork AI is good at: reshaping text a person has already approved. A staff member still checks every version before it goes out.

How one church office task returns time to peopleAn illustration in three steps. Every week, the same announcement is rewritten by hand for the bulletin, the newsletter, the website, and social posts. Then one approved brief feeds an AI tool that drafts each version, and staff check and approve every draft. Finally, an illustrative example: 6 staff times 2 hours a week times 48 weeks is 576 staff hours a year, about $17,280 of staff time at $30 an hour. That is time for people, not cash saved.Every week, by handOne approved briefIllustrative exampleAI draftsNewsletterWebsiteSocial postsBulletinStaff check and approve576staff hours a year$17,280 of staff timeTime for people, not cash saved
An illustration, not a client result. 6 staff × 2 hours a week × 48 weeks = 576 hours a year, about $17,280 of staff time at $30 an hour.

Church offices

Hours are illustrations based on stated assumptions, not client results.

Approved event details to a newsletter item, website announcement, and social captions

Communications. Reviewed by: Church administrator, with approval from the ministry leader or pastor. Goes to: The church's email newsletter, website, and social media accounts, plus the bulletin and service slides where used.

Before about 5.5 hours a week

  1. Event details arrive from ministry leaders by email, text, and hallway conversation, in different formats
  2. The administrator chases missing details, then writes separate copy for the newsletter, the bulletin, the slides, the spoken announcements, and social media
  3. Details drift between versions, so the slide says 6:30 when the newsletter says 6:00
  4. Late changes mean redoing several pieces by hand

With AI about 2.5 hours a week

  1. Ministry leaders submit each event through one short form: what, when, where, who it is for, cost, how to register, and a contact role Staff
  2. The administrator or pastor approves the event details and decides what runs this week Staff
  3. An AI assistant drafts the newsletter item, the website announcement, and social captions from the approved details only, in your church's voice, plus bulletin or slide text if you use them AI drafts
  4. The administrator checks every date, weekday, time, place, and cost against the approved details and the church calendar Staff
  5. Approved pieces go into the church's email newsletter, website, and social media scheduler, and into the bulletin or slides where used Staff
Guardrails
  • Only approved event details go into the AI tool; anything missing is marked NEEDS INPUT, never guessed
  • No names or photos of children, and photos of adults only with permission
  • Prayer requests, health updates, and personal news stay out of AI tools; staff write those themselves
  • Nothing is published until a staff member approves it

Hours are illustrative only. Assumes about 2 events and 10 announcements a week, each prepared for 4 or 5 channels; your numbers will differ.

Staff meeting notes to action lists and follow-up drafts

Administration. Reviewed by: The staff member who leads the meeting, often the executive pastor or church administrator. Goes to: The staff task list, each sender's email, and the next meeting's agenda.

Before about 2 hours a week

  1. One staff member takes notes by hand while also trying to take part in the meeting
  2. The list of who agreed to do what goes out late or not at all
  3. Ministry leaders and volunteers who were not in the room hear about their tasks days later, if at all
  4. The same items come back unresolved at the next meeting

With AI about 1 hours a week

  1. The note taker keeps administrative items in one document and keeps care, prayer, personnel, and member matters out of it Staff
  2. An AI assistant drafts the decisions, an action list with owners and due dates, open questions, and a short follow-up message for each owner AI drafts
  3. The meeting lead checks every owner, date, and decision against the notes and marks anything unclear as needing an owner or a date Staff
  4. Approved follow-ups go out from each sender's own email or the church's messaging tool Staff
  5. The action list goes on the shared task list and opens the next staff meeting Staff
Guardrails
  • Pastoral care, counseling, prayer needs, personnel matters, giving, and member information never go into AI tools
  • The assistant never assigns work; missing owners and dates are flagged, not guessed
  • Official board or committee minutes follow your church's own approval process

Hours are illustrative only. Assumes 1 weekly staff meeting and 1 other administrative meeting, with about an hour of write-up and follow-up each; your numbers will differ.

Approved office documents to an organized reference and draft answers

Administration. Reviewed by: Church administrator or office manager, with a staff lead approving changes to the reference. Goes to: A shared reference folder, and replies sent from staff members' own email.

Before about 2.5 hours a week

  1. Answers to routine questions about rooms, office hours, facility rules, and event policies live in scattered documents, old emails, and one person's memory
  2. Staff retype the same answers to members, volunteers, and guests every week
  3. Outdated versions of policies and forms keep circulating
  4. When the person who knows is out, questions wait

With AI about 1.25 hours a week

  1. Staff gather the current approved documents the office answers from, such as the facility use policy, office hours, event guidelines, and volunteer handbook, and retire old copies Staff
  2. An AI assistant organizes them into one reference, with a short summary and the source document for each topic AI drafts
  3. When a routine question arrives, an AI assistant drafts a reply from the approved reference only and names the document it used; anything the reference does not cover is marked NEEDS INPUT AI drafts
  4. A staff member checks the draft against the source document, adjusts the tone, and sends it personally Staff
  5. New answers are added to the reference only after a leader approves them, and each document keeps an owner and a review date Staff
Guardrails
  • Only current, approved documents go into the reference, and policy wording is quoted exactly, never reworded
  • Pastoral questions, care needs, giving questions, and anything about children go straight to a person with no AI draft
  • No member contact details or personal information in the reference
  • A person reads and sends every reply

Hours are illustrative only. Assumes about 20 routine questions a week at roughly 5 minutes each to find the current document and write an answer, plus time spent searching for current versions; your numbers will differ.

Reusable office templates and onboarding resources

Administration and volunteers. Reviewed by: The person who does the task, with approval from the church administrator or a staff lead. Goes to: A shared template folder, the volunteer handbook, and the staff onboarding folder.

Before about 2.5 hours a week

  1. Guest letters, facility forms, event follow-ups, and volunteer packets are rewritten from scratch or copied from old files
  2. Training lives in one experienced person's head, so new staff and volunteers learn the job a little differently from each trainer
  3. Outdated details and reworded policy text keep showing up in reused documents

With AI about 1.25 hours a week

  1. Staff list the documents they rewrite most and the questions new people ask most, then pick three to start Staff
  2. The person who does each task shares rough notes or talks through the steps, and staff add the exact text of any approved policy the document touches Staff
  3. An AI assistant drafts a template, role guide, or onboarding checklist in a standard format, with placeholders like [Guest first name] and [Event date] AI drafts
  4. The task owner checks every step; policy wording is compared with the approved policy word for word Staff
  5. A staff lead approves each document, which goes into one shared folder with an owner and a review date Staff
Guardrails
  • Child safety and security procedures are copied word for word from the church's approved policy
  • Templates contain placeholders only, with no real member, family, or contact details
  • Pastoral letters and personnel documents stay with the pastor and staff
  • Each document has an owner and a review date, and older copies are removed

Hours are illustrative only. Assumes about 90 minutes a week recreating routine documents and an hour re-explaining tasks to new staff and volunteers; your numbers will differ.

Volunteer reminders and thank-you notes

Volunteers. Reviewed by: Volunteer coordinator. Goes to: The church's email or texting tool and the volunteer schedule.

Before about 3 hours a week

  1. Coordinators write reminders and schedule changes one message at a time
  2. Volunteers get different information depending on who sent it
  3. Thank-you notes and follow-ups slip when the week gets busy

With AI about 2 hours a week

  1. Coordinators keep a short set of message templates for reminders, changes, and thank-yous Staff
  2. An AI assistant drafts each week's messages from the schedule and the templates, using placeholders like [Volunteer first name] AI drafts
  3. The coordinator reviews each message and adds a personal note where it matters Staff
  4. The coordinator sends the messages from the church's usual email or texting tool Staff
  5. Replies and swap requests come back to the coordinator directly Staff
Guardrails
  • Volunteer contact lists stay in the church's own systems, out of AI tools
  • Messages about children's ministry use roles and times only, with no children's names
  • A person reviews and sends every message

Hours are illustrative only. Assumes about 40 volunteers across a few ministries receiving weekly reminders; your numbers will differ.

Calendar coordination

Facilities and scheduling. Reviewed by: Church administrator. Goes to: The church calendar and the facilities setup checklist.

Before about 2 hours a week

  1. Room and event requests arrive by email, text, and conversation
  2. The administrator checks the calendar by hand for conflicts
  3. Double bookings and setup needs can surface at the last minute

With AI about 1.25 hours a week

  1. Staff and ministry leaders request rooms through one form with the time, setup needs, and a contact Staff
  2. An AI step compares each request with the church calendar and flags possible conflicts AI drafts
  3. The administrator reviews each flag and confirms, adjusts, or declines the booking Staff
  4. The AI drafts a confirmation and setup note, which the administrator checks before sending AI drafts
  5. Confirmed events go on the church calendar and the facilities checklist Staff
Guardrails
  • The administrator makes every booking decision
  • Counseling appointments and other private meetings appear only as busy time and stay out of AI tools
  • The church calendar stays the single source of truth, and AI drafts never change it directly

Hours are illustrative only. Assumes about 15 room and event requests a week; your numbers will differ.

Approved sermon-transcript indexing and reuse

Media. Reviewed by: Pastor, with a media or communications staff member. Goes to: The church website's sermon archive, newsletters, and social media posts.

Before about 2 hours a week

  1. Recorded sermons sit in an archive labeled only by date and title
  2. Finding past messages on a topic means listening through hours of audio
  3. Staff rarely have time to make past teaching easy to find

With AI about 1 hours a week

  1. The pastor chooses which past sermons to include and approves their transcripts Staff
  2. An AI tool tags each transcript by topic, series, and the passages referenced, and drafts a short description AI drafts
  3. A media or communications staff member checks tags, descriptions, and any excerpts against the recording Staff
  4. The pastor approves every description and excerpt before it is shared Staff
  5. Approved entries go into a searchable sermon archive, and staff reuse approved excerpts in newsletters and social posts Staff
Guardrails
  • AI describes and organizes the pastor's own words and adds no new teaching
  • Names and personal stories about members are removed before processing
  • Nothing is published without the pastor's approval

Hours are illustrative only. Assumes about 2 hours a week spent finding, describing, and posting past messages; your numbers will differ.

Small businesses

The same pattern for meetings, proposals, inquiries, and procedures.

Meeting notes to reviewed action items

Leadership. Reviewed by: Meeting lead. Goes to: The team's task list or project tracker and the shared meeting notes folder.

Before about 3 hours a week

  1. Someone takes rough notes while also trying to take part in the meeting
  2. The notes get typed up later, often a day or two after the meeting
  3. Action items sit inside paragraphs, so owners and due dates get missed
  4. Follow-up depends on memory and a long chain of emails

With AI about 1 hours a week

  1. With everyone's consent, the meeting lead records and transcribes the meeting in a tool your organization has approved Staff
  2. An AI assistant drafts a summary of decisions, action items, owners, and due dates from the transcript AI drafts
  3. The meeting lead reviews the draft, corrects names and dates, and removes anything that should stay off the record Staff
  4. Approved action items go into the team's task list, and the summary goes to attendees the same day Staff
Guardrails
  • Record or transcribe only with attendees' consent and only in approved tools
  • Keep HR, legal, and personnel discussions out of transcribed meetings
  • Nothing is assigned until the meeting lead confirms owners and due dates

Hours are illustrative only. Assumes about 4 meetings a week with roughly 45 minutes of note cleanup and follow-up each; your numbers will differ.

First drafts of proposals

Sales. Reviewed by: Sales lead or owner. Goes to: The client's file in your customer records system or shared drive.

Before about 4 hours a week

  1. Each proposal starts from a blank page or a copy of an old one
  2. Scope, pricing, and terms are pieced together by hand from past files
  3. Details from the sales conversation are spread across notes and emails
  4. Each draft takes a couple of hours, so proposals can go out days after the call

With AI about 2 hours a week

  1. After each call, the salesperson fills in a short intake form with the client's needs, scope, and timeline Staff
  2. An AI assistant drafts the proposal from the intake form, your approved template, and your current service descriptions AI drafts
  3. The salesperson edits the draft for fit and tone and fixes anything the AI missed or got wrong Staff
  4. The sales lead checks pricing, scope, and terms against the current rate sheet Staff
  5. The final proposal is saved to the client's file and sent from your usual system Staff
Guardrails
  • Prices and terms come from your current rate sheet and are checked by a person every time
  • Use placeholders like [Client name] while testing, and keep client financial details out of unapproved tools
  • No proposal goes out without a final human review

Hours are illustrative only. Assumes about 2 proposals a week at roughly 2 hours each; your numbers will differ.

Organizing incoming inquiries

Customer service. Reviewed by: Office manager or customer service lead. Goes to: Your shared inbox, help desk, or customer records system.

Before about 5 hours a week

  1. Inquiries arrive through the website form, email, and voicemail
  2. Someone reads each one and decides who should handle it
  3. Urgent requests can wait behind routine questions
  4. Answers to common questions get typed fresh each time

With AI about 3 hours a week

  1. Website, email, and voicemail inquiries arrive in one shared inbox that the office manager watches Staff
  2. An AI step sorts each inquiry by type and urgency and suggests who should handle it AI drafts
  3. For common questions, the AI drafts a reply from your approved answers AI drafts
  4. A staff member checks the sorting, edits each draft, and sends replies personally Staff
  5. Complaints and sensitive messages go straight to a person with no AI draft Staff
Guardrails
  • Nothing is sent automatically; a person reads every reply before it goes out
  • Complaints, billing disputes, and legal or health matters skip the AI draft
  • Draft replies use only your approved answers and current policies

Hours are illustrative only. Assumes about 60 inquiries a week at roughly 5 minutes each to sort and answer; your numbers will differ.

Consistent SOPs and onboarding material

Operations. Reviewed by: Task owner and department manager. Goes to: Your shared procedures library and new-hire onboarding checklist.

Before about 4 hours a week

  1. Much of the know-how lives in a few experienced people's heads
  2. The standard operating procedures (SOPs) that exist use different formats and are often out of date
  3. New hires learn by shadowing, and each trainer teaches the task a little differently

With AI about 2 hours a week

  1. An experienced employee talks through a task or shares rough notes Staff
  2. An AI assistant turns the walkthrough into a step-by-step SOP using your standard template AI drafts
  3. The employee who does the task checks every step and adds what the draft missed Staff
  4. A manager approves the SOP and adds it to the shared procedures library Staff
  5. Approved SOPs become onboarding checklists for new hires Staff
Guardrails
  • Someone who does the task signs off on every step before it is published
  • Each SOP lists an owner and a last-reviewed date
  • Passwords, account numbers, and personnel details stay out of drafts

Hours are illustrative only. Assumes a manager spends about 4 hours a week writing procedures and answering repeat training questions; your numbers will differ.

Start with a conversation.

Bring one task your staff repeat every week. We’ll sketch how it could work, and tell you honestly whether it’s worth it.

Book a free consultation