Six things, and every one of them is somebody's Sunday afternoon.
Written as what a person in a church office would do, not as the machinery underneath it — nobody in a church calls an interface that has no screen.
Write it once, and let Sunday post itself.
One composer, one picture, one caption — and it goes out to every account your church runs, at the time you chose, without a volunteer opening six apps on a Sunday morning.
Sunday would already be written before Saturday evening ends.
- A post written once and sent to every account you have connected
- The first comment queued with the post, so the link is not left out of the caption
- A month calendar you can look at, and a queue that keeps the order
- Pictures and video uploaded once and reused across the accounts that take them
- One announcement, waiting wherever they already look
- The link in the first comment rather than buried in a caption
- Nothing posted twice, and nothing quietly missed
What Sunday actually reached, in one place.
How far a post travelled, how many people it reached and whether the account grew — read beside the post that earned it, rather than screenshotted out of five apps on a Monday.
You would stop guessing which invitation actually did the work.
- Impressions and reach on the post they belong to
- Engagement counted the same way across every account
- Follower numbers tracked over time rather than checked by memory
- Which invitation travelled, and which one sank without trace
- Whether the account is growing or standing still
- One screen to look at on a Monday rather than five
The message a visitor sent on Friday, answered.
Direct messages read and answered from inside the admin, so the person asking about the service time gets a reply from the church rather than from whoever happened to have the password.
The question about service times would get an answer from the church.
- Messages read in the admin, in one list
- Replies sent from the church account, not a volunteer's phone
- The conversation kept where the rest of your admin work happens
- A reply from the church rather than from somebody's own account
- An answer while the question still matters to them
- The same voice, whoever happens to be on duty that week
Nobody has to remember which app the comment was on.
Comments on your posts and reviews of your church, gathered and answered in one place — the difference between a question answered on Sunday evening and one nobody sees until Thursday.
A question asked on Sunday evening would be answered on Sunday evening.
- Comments on every account, in one list
- Replies posted back to the account the comment was left on
- Reviews of your church read and answered in the same place
- A comment answered rather than left sitting under a post
- A review of your church read by somebody able to respond
- One list to work through instead of an app for each account
Boost the Easter post without leaving the screen you wrote it on.
Putting money behind a post, or running a proper campaign, from the same place the post was written — instead of a separate manager nobody on the team has the login for.
The Easter invitation would reach past the people who already follow you.
- Boost a post that is already doing well
- Build a campaign rather than only promoting a single post
- Run it on the networks your church already reaches people on
- An invitation that reaches beyond the people already following
- Money put behind the post that was working anyway
- One screen to write it on and one decision to back it
Your dashboard keeps up on its own.
When a post goes out, a comment arrives or somebody sends a message, the admin would know at that moment — not the next time a volunteer opens the page and refreshes it.
The screen would already know, before anyone thought to refresh it.
- A scheduled post that has gone out says so, without a refresh
- A new comment or message appears as it lands
- Something that failed to send says so at the time, not on Monday
- A post that failed noticed at the time rather than on Monday
- A message seen while somebody is still waiting on it
- A team that can trust the screen in front of them
Six places to post, and three places to put money behind it.
This is the list, and it is a decision rather than a starting point. Somewhere a church is not, or somewhere that would cost it more to reach than the whole feature is worth, is not on it.
Instagram
TikTok
YouTube
Facebook
Threads
Bluesky
Meta Ads
Google AdsTikTok AdsA month you can look at, before the month happens.
One post is easy. Forty across six accounts, with a different set of rules on each, is the part that eats a volunteer's week.
A TikTok post can go out publicly, to followers, or privately while somebody senior checks it first. That choice belongs to TikTok, so it would appear on the TikTok version of a post and nowhere else.
A YouTube video needs both where an Instagram photo needs neither. The composer would ask for what each destination actually wants, instead of one box that has to suit all of them at once.
Photographs and video uploaded once and carried to every account that takes them, at the size each one wants, rather than exported five times by the person with the camera.
A month grid you can look at and a queue that holds the order, so the team can see what goes out on Sunday before Sunday — and move it without rewriting it.
Is this the one your church would actually use?
Tell us which accounts you run and what Sunday morning currently costs you in people and time. What churches actually ask for is how this list gets ordered, and a request from a real ministry outranks a good idea we had on our own.
Nothing on this page is built, dated or for sale. It is a feature Harvest would run itself, written down in public so you can see the shape of it before it exists.