Free website audit for any church
We build and run
your church’s back end.
From the website where guests meet you to the systems behind it, we connect what you use, automate the weekly work and run it, so your staff spend the week on people. No guest or volunteer falls through the cracks.
Your church runs on a dozen systems that don’t talk to each other.
So staff carry people between them by hand: retyping cards, copying sign-ups, rebuilding the same report every month.
None of it has a foundation underneath.
No single record of a person, no one owner of the logins, and nothing that runs when the person who knows it is away.
Firm Foundation builds the layer underneath, and runs it.
One foundation under the systems you already use. We build it, host it and keep it running, so the weekly work happens without anyone retyping it.
The front door
Guests who search first meet your website before your lobby.
For most guests, a church with a poor website might as well not exist N1, and younger guests start their search online N2. Then the page sends them to an email address, a paper card or last month’s events. Most of the church websites we read offered no next step a guest could take from the page N3.
The problem, drawn
Church websites, read the way a guest reads them
Six things a first-time guest looks for. Each column is an audit done on real churches, best to worst. Not one had all six.
FF. 3.1read 2026-10-10
Churches, best to worst
- Service times on the first screen
- A form to plan a visit
- A way to sign up to serve
- A group finder you can search
- A next step beside the livestream
- Nothing out of date or broken
Church 01 · Craft CMS
Guest parking is explained on the About page, not anywhere a guest would look.
- Has it: Service times on the first screen
- Missing: A form to plan a visit
- Has it: A way to sign up to serve
- Missing: A group finder you can search
- Missing: A next step beside the livestream
- Has it: Nothing out of date or broken
What we build
A next step on every page that asks for one
Two or three fields, a reply the same day, and a named person on your staff who knows they’re coming. Pick a path, then compare.
What a guest sees
Messages
Good to meet you yesterday, Sam. Parents of young kids meet Wednesdays. Want us to save you a seat?
What your staff see
ResultA family met at the door by name.
The follow-through
A guest fills out the card. Then nobody calls.
Follow-up, volunteer sign-ups and the weekly announcements run by hand, through whoever has time that week. Church leaders name communication and volunteer coordination as the two problems they most want technology to fix N4. And people are ready to serve: weekly church volunteering is back above where it was before the pandemic N5.
The problem, drawn
What happens to a connection card
In one survey of first-time guests who left their contact details, most never heard back within the month N6. The grid draws that survey as a hundred guests.
FF. 4.1first-time guests, 2015 to 2016
Mostfirst-time guests who left their details never heard back within the month.
The build sends every reply. Whether a guest comes back is still up to them, and to you.
What we build
The weekly work, run for you
Pick one to see a week before the build and after it. The staff time on each is an example, not a measurement.
FF. 4.2Guest follow-upExample
Every connection card becomes a reply the same day, a named person to call and a return visit tracked.
Sunday, 12:10
Draft text, waiting for your approval
Hi Sam, it was good to meet you Sunday. Groups start again next week. Want us to save you a seat?
Staff time, exampleAbout 20 minutes a week, approving drafts
Built inside what you run
We work in your accounts. Nobody moves to a new platform.
- Planning Center
- Pushpay
- Tithe.ly
- Rock RMS
- Breeze
- Google Workspace
- Microsoft 365
The foundation
Too much depends on the one person who knows.
Most churches have key roles they still need to fill N7, so the logins, the people data and the monthly reports live with whoever set them up. Scammers read the staff page too N8, and most church leaders worry about data privacy N9. We build the layers underneath, write them down and run them.
The fix, drawn
Four layers, built in order and run together
Most churches buy a tool for each problem. We build the layers underneath every tool, in order, and keep them working.
01 / 04
Infrastructure
Accounts, domains, email, devices and access. Every login has an owner, every account is documented, and nobody gets locked out when a staff member leaves.
02 / 04
Data
One clean record per person across Planning Center, giving, forms and email. Duplicates merged, addresses current, and every system reading the same list.
03 / 04
Automation
Guest follow-up, volunteer scheduling and monthly reports run on their own. Staff approve anything that goes out under the church’s name.
04 / 04
AI
A private assistant that knows your calendar, policies and people, and agents that route every pastoral need to a person on your staff.
In this layerdomains, email, devices, logins, access
What we build
What we run underneath
Pick one to see a week before the build and after it. The staff time on each is an example, not a measurement.
FF. 5.2People dataExample
One clean record per person across Planning Center, giving, forms and email.
One record
Every system reads this one record.
Staff time, exampleA few minutes, reviewing merges
How a church starts
Start with a look, not a contract.
- FF. 6.1Free for any church
01
Website audit
We read your public site on a phone, the way a first-time guest does, and send you what we find within 24 hours. No logins.
- FF. 6.2Free for founding churches
02
Blueprint
We map every system you run and who touches it, then pick the first builds with you.
- FF. 6.3No cost for a month
03
First month
We build and run the first builds for a month, so you judge the work before you pay for it.
- FF. 6.4Priced by scope
04
Retainer
We keep it running, add the next builds and answer your staff every day. The Blueprint sets the scope.
FF. 7.1
What we never do
Two lines we don’t cross.
AI never does pastoral care
It never counsels, prays with or answers someone in crisis. It hands them to a person on your staff, every time.
We never move money
We report on and reconcile giving. We never start a transfer or touch payment settings.
Who we are
Two believers building for the church.
Firm Foundation is Gavin Munroe and Caleb Newton. We build and run software for a living, and we started this so church staff could get their week back.
- Gavin MunroeProduct and delivery
- [NEED: one line from Gavin, in his words]
- Caleb NewtonPartnerships and contracts
- [NEED: one line from Caleb, in his words]
“But God’s firm foundation stands.”
Start with your website.
Send us your church’s site. We read it the way a first-time guest does and send back what we find. Free, and no logins.
Free website audit