The Assistant
Monday used to be spreadsheets
Think of the person who keeps your community running. The church administrator, the membership director, the volunteer coordinator. Their week starts with four tools open, a pile of exports, and a guess about who has quietly slipped away.
It doesn’t have to. A built-in AI assistant tells your team who needs them this week, and why, and drafts the next step. Your team decides.
30 minutes with our team. No pitch, no pressure.
A week with the assistant
Your assistant reads everyone’s whole story so your team doesn’t have to, and brings them the people, the reasons and the words. Nothing reaches a member until someone on your team says yes.
Monday, 8am
The briefing
One screen: who arrived, who’s drifting, which group went quiet, which gifts stopped. Each item gives its reason and a next step.
Before: Open four tools, export, compare, guess.
Monday, 8:10
Drafts, ready to send
A welcome for each first-time guest, a check-in for each drifting regular, a thank-you for each first gift, in your own voice. Edit, approve, send.
Before: A blank email, twelve times.
Tuesday
Ask anything
“Which volunteers serve every week and haven’t had a break since spring?” Type it and get the list, with the records behind it.
Before: Ask someone to build a report, and wait.
Wednesday
One post, every channel
Write the announcement once. The assistant fits it to push, email and text, and suggests who should get it.
Before: The same post in four places.
Thursday
Set it up in a sentence
“Saturday serve day at the garden, 9am, 20 spots, remind people Friday night.” The event, sign-up and reminders are drafted for you to check and publish.
Before: Twenty fields across two tools.
Friday
The board report, drafted
The month in plain English, from your own data, with every figure linked to where it came from.
Before: A weekend in spreadsheets.
Sunday
After the gathering
Check-ins land on the record. By evening: who came for the first time, who came back a second time, and which group each might fit.
Before: A clipboard and a memory.
Who needs you this week, and why
Pick the kind of community you run. The briefing is an example of what your team would open on Monday morning; beside it are two jobs the assistant does in that setting.
Every first-time guest, followed up
Sunday’s new faces arrive Monday morning with a welcome drafted for each, and a group suggested with the reason.
From Sunday’s sermon to Wednesday’s study
The talk becomes a study guide, discussion questions and a summary for group leaders to review and send. A scoped add-on.
Your assistant runs in your cloud, on your own data, under your own account. It sees only what the person asking may see, never trains anyone’s model on your members, and drafts rather than sends.
How the assistant handles your dataEverything it can help with
Grouped the way your team thinks about the work. Each item says which build includes it; “Add-on” means a scoped add-on priced in your estimate. See the tiers.
Know
The Monday briefing, for each staff member and each leader
Community
A reason behind every flag, never a bare score
Community
Plain-English questions about your community, answered with the records behind the answer
Community
Alerts when a group, campus or chapter changes pace
Community
Welcome
First-time guest follow-up, drafted for each person
Community
Group suggestions with the reason (“new to the city, has two kids”)
Community
Onboarding that adapts to what someone told you
Community
Automated group formation for large cohorts
Add-on
Communicate
Write once, fitted to push, email and text
Community
Drafts in your organization’s voice, learned from your past posts
Community
Who should get this, and who has already heard it three times
Community
Translation for multilingual communities
Add-on
Care
Follow-up reminders on care notes, visible only to the people who should see them
Community
Prayer and help requests routed to the right person
Community
Anything that reads as a safeguarding concern goes straight to a named person
Community
Serve and gather
Rota suggestions that spread the load and flag burnout
Community
Events, sign-ups and reminders set up from a sentence
Community
An after-event summary: first-timers, returners, no-shows
Community
Give and renew
A thank-you drafted for every first and returning gift
Community
Stopped gifts sorted into “card expired” and “worth a call”
Community
Renewal flags for associations and paid memberships
Community
CE progress reminders before a deadline
Community
Report
Board report drafted from your real numbers, every figure sourced
Community
Summaries for each chapter, campus or group leader
Community
Grant report narrative for nonprofits
Add-on
Content and learning
Image descriptions and captions for accessibility
Community
A sermon or talk turned into a study guide, discussion questions and a summary
Add-on
Course quiz and certificate drafts
Add-on
Set up and move in
Import help: maps spreadsheet columns, finds likely duplicates, asks before merging
Every build
“How do I…?” help inside the admin
Community
A review queue for posts, and spam caught before anyone sees it
Community
For members
Search that answers: “When’s the youth retreat and what do I bring?”
Add-on
A help assistant that hands off to a named person
Add-on
All of it inside your own iOS and Android app
Full Platform
Six commitments it keeps
The same terms as the rest of your platform: you own it, and it answers to your team. What you own, in plain terms.
- Runs in your cloud
- On your own data, under your own AI provider account. We set it up; you own the account.
- Never trains on your members
- Your provider account runs under business terms that exclude training on your data.
- Sees only what you may see
- It follows your roles and permissions. Care notes stay with the people allowed to read them.
- Drafts, and your team sends
- Every message to a member waits for a person to approve it. You can switch on automatic sending for low-risk jobs you choose, like event reminders. Anything pastoral is never automatic.
- Shows its reasons
- Every flag says why, and links to the records behind it. No unexplained scores.
- Logged and switchable
- Every suggestion and every send is logged. Any feature can be turned off, and usage cost is visible every month.
What it costs to run
AI usage is paid to your own provider at cost, like hosting, with no markup and no platform fee. We estimate it in your scope.
What it won’t do
It won’t send to a member without a person saying yes, unless you switch it on for a low-risk job.
Every message to a member waits for a person to approve it. You can switch on automatic sending for low-risk jobs you choose, like event reminders. Anything pastoral is never automatic.
It won’t handle anything pastoral automatically.
Care notes and pastoral follow-up always wait for a person. Automatic sending can never be switched on for them.
It won’t train anyone’s model on your members.
Your provider account runs under business terms that exclude training on your data.
It won’t hand you a score without a reason.
Every flag says why, and links to the records behind it. No unexplained scores.
It won’t replace your staff.
It does the legwork: the reading, the sorting, the first draft. Your people keep the judgment and the relationships. It gives them their week back.
Questions about the assistant
Give your team their week back
Tell us where your team’s time goes, and we’ll show you what the assistant would take off their plate, in a platform you own. You get a range on the call, and a straight answer if a build isn’t right for you yet.
30 minutes with our team. No pitch, no pressure.