The framework
Channels, sizes and lead times, set once per church in its own terminology. Every schedule is generated from it, and a rule changed in the framework changes every event scheduled after the change.
Promotion planning for churches
Promo Engine builds a church's promotion schedule from three inputs: the event's date, its size, and a framework the church sets once. Every newsletter mention, post, announcement and poster is written with a publish date, a due date and a person on it, up to six weeks ahead. Nothing is sent or published by the software.
$29 a month per church. Free for 15 days, no card. Built by a church communications director, in a working church.
How it works
Most churches promote every event for the same length of time, and the large events are not distinguished from the small ones. Promo Engine sets the length of the run from the event's size.
A name, a date and a size, typed in by anyone on the team, or an event Promo Engine read off the calendar the church already publishes and asked about.
Three sizes by default: the whole church, one group, a handful. Each size is a set of rules in the framework: which channels, how many weeks before the event, which weekday, and how many days of lead each piece gets.
Every piece is written with a channel, a publish date and a due date, and handed to a person. Each person sees their own pieces on their list, in their calendar and in the chat tool the church connects. Publishing is done by people.
What you get
One product, with all six parts included. None of them is an add-on, and none is charged per person.
Channels, sizes and lead times, set once per church in its own terminology. Every schedule is generated from it, and a rule changed in the framework changes every event scheduled after the change.
One list, ordered by urgency: late pieces, pieces with no one on them, then your own pieces, then your team's.
Every campaign with its piece count, how many are done, how many are late, and its schedule. Moving the event date moves the unfinished pieces to the new dates; finished pieces keep theirs.
Paste the address of the calendar the church already publishes and Promo Engine reads it every hour, asking about any event with nothing promoting it yet, with the schedule one press away.
Drafts the words for a piece from its brief, in the church's own terminology, when a person asks for one. It sends nothing and publishes nothing.
A message in Slack, Google Chat or Microsoft Teams when a piece is handed to someone, an email in every case, and a calendar feed of each person's own pieces.
Works with
Promo Engine posts into Slack, Google Chat or Microsoft Teams, and reads a calendar published from Planning Center, Google, Apple or Outlook. Nothing is moved out of the tools a church already runs.
Pricing
Free for 15 days, no card. Cancel anytime. No per-seat pricing. Everything in Promo Engine included.
Every church
$29
a month, per church
Free for 15 days. No card.
The whole product, for everyone on the staff, on one subscription per church. The first 15 days are free and no card is taken until they end.
Questions
The answers apply whether or not a church signs up. Anything not covered here: contact@engine.church.
The length of the run depends on how much of the church the event affects. An event for nearly everyone, such as a Christmas service or a church weekend, is promoted over six weeks, with the pieces spaced so that interest builds toward the date. An event for a group the church can name in a sentence is promoted over four weeks. An event for a small group or a serving team is promoted over two, to that group only. Promoting every event for the same length of time is the most common error, and it leaves the large events indistinguishable from the small ones.
Fewer times than a team tends to assume, and further apart. A six-week run across a newsletter, social and Sunday announcements is about ten pieces of work, spaced to increase toward the date rather than repeat evenly. The practical limit is on the number of different asks live at once: two across all channels in one week is the ceiling before response to all of them falls.
The date a piece is seen is not the date the work has to exist. A story email sent on a Monday needs a person asked, a reply and an edit, which is about ten days of lead time; a reminder text is written the day before. Planning against publish dates alone is the usual reason a church finds out on a Sunday that a piece was needed on the Wednesday before. Promo Engine records both dates on every piece.
Moving the date moves every unfinished piece with it, keeping the same weekday and the same lead time, so a Sunday announcement stays on a Sunday. Assignments, briefs and notes are kept, and finished pieces keep their original dates.
No. Planning Center handles services, people and giving. Promo Engine handles the promotion around them: what is announced, on which channel, how far ahead, and by whom. It reads the calendar Planning Center publishes and raises any event on it that no campaign covers.
A volunteer sees only their own pieces: a list of what they have been assigned, each with a deadline and a link to the brief. They are notified in the chat tool the church connects when a piece is assigned, and the piece appears in their own calendar. There is nothing for them to configure.
Given a piece's brief and its channel, it drafts the words in the church's own terminology, when a person asks for one. It does not choose the message, the voice or the creative direction, and it does not send or publish anything. A person presses every button.
$29 a month per church. Free for 15 days, no card. Cancel anytime. No per-seat pricing. Everything in Promo Engine included.
Engine, a small company at engine.church, built by a church communications director in a working church. Promo Engine is its one product.
Setup is three screens and asks for no card. The first schedule is on your list before it closes.
Promo Engine keeps your theme and the other choices you make on this site in your own browser. No tracking cookie and no advertising. What is stored