Sound familiar?
What churches and ministries tell us before a project starts.
- A visitor fills in a card on Sunday, and by Wednesday nobody has reached out.
- Volunteer schedules are texted around and someone always misses it.
- The same announcement is typed into the bulletin, the website and the email.
- Year-end giving statements are a scramble every January.
- Our church software does most of what we need, but it does not talk to anything else.
What we build
Each one is a working piece you can open and check when it's done.
Visitor follow-up
A connection card or web form starts a short sequence: a welcome message, a task for a pastor or greeter, and a reminder if no one has made contact.
n8n, Make and Zapier automation CRM setup and lead pipelinesVolunteer scheduling and reminders
Teams and roles kept in one list, with reminders before each service and a simple way to swap or say no.
Booking and scheduling systems Google Sheets and Apps Script automationOne announcement, every channel
Write it once and have it appear in the email list, the website events page and the screen slides.
API integrations and data syncEvent and class sign-ups
Registration for retreats, classes and trips with a count, a waitlist, reminders and a check-in list.
Web apps and MVPs Stripe integration and billingGiving statements and reports
Gift records from your giving tool collected into the layout your treasurer prefers, with year-end statements prepared for review.
ETL and data pipelines Python scripts and utilitiesSmall-groups and care tracking
Who is in a group, who has not been contacted, and who needs a call, in one list that pastors and leaders can share.
Notion and Airtable systemsChurches software we work with: Planning Center, Breeze, Pushpay, Subsplash, Church Community Builder.
And the general tools around it: Google Sheets, Mailchimp, WordPress, Zoom, Slack, Zapier, Make, Google Drive.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Visitor card to a phone call
Example: a church of two hundred wants each Sunday card typed into a form, a welcome text sent that afternoon, and a task given to the greeter team to call by Wednesday.
A web form, text messages, task remindersExample project
Sunday volunteer reminders
Example: a children's ministry coordinator wants every volunteer reminded on Thursday, with a link to swap a week, and a list of open spots by Friday morning.
Google Sheets, reminders, a swap formExample project
Year-end giving packet
Example: a treasurer exports the year's gifts and gets a statement per household in the church's format, ready to review and send in January.
Exported gift records, Google Sheets, PDF outputQuestions people ask first
Do we have to leave our church management system?
No. We connect what you have to forms, email and calendars. If something cannot be done, we say so in the scope.
Can volunteers run it?
That is the aim. We build it with plain tools and write notes in plain language, so a volunteer can change a message or a list.
Who owns what you build?
You do. It is built in your own accounts, and you get notes on how it works so your team can change it without us.
How do we start?
Tell us which tools you use and the one thing that wastes the most time each week. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com