Built for churches. Built by a pastor.
Your website, your sermons, your giving, your events and your follow-up in one place — instead of four tools that don't talk to each other and a stack of connect cards in a drawer.
Not open yet. This page is here so you can say you're interested before it is, and so you know exactly what you'd be waiting on.
Nobody tells you they couldn't find the service time.
They decide before they ever call
Somebody drives past your sign on a Tuesday and looks you up that night. They want four things: when you meet, where to park, what happens to their kids, and whether anyone is going to single them out.
If your site makes them hunt for any of it, they don't email you to ask. They just don't come.
Four tools that have never met
The giving page is on one platform, the directory is in software nobody has opened since the last administrator left, and the texts go out from somebody's personal phone.
Every one of those was a reasonable decision when it was made. Together they're a system nobody designed.
The cards from Sunday are in a drawer
They're in there because the person who used to type them in moved away, and nobody picked it back up.
The part that actually costs you isn't the software. It's the family who filled out a card in September and never heard from anyone.
One system. Three jobs. The three a church actually has.
Not a directory, not a database project, and not something that needs a volunteer to babysit it. Three things that have to work, connected so a person who fills out a card on Sunday is the same person your giving records and your follow-up already know about.
Your website In development
Built around the four things a first-time family is actually looking for, in the order they look for them. Service times and which door. Parking. What happens with their kids, including check-in and security. What you believe, in plain English, with the full statement a click away.
- One clear next step on the page: plan your visit
- Service times and campus details in one place, so they're right everywhere at once
- Your sermons, newest on the front and the rest in an archive people can search
- Your small groups, listed where somebody can actually find one and say they're coming
- Your own address, not a page on somebody else's platform
- You can edit it yourself afterward without calling anybody
Giving In development
Online, recurring, and by text, with your funds named the way they should read on a year-end statement. Gifts land in your account — nobody here touches the money.
- Your fund list: general, missions, building, benevolence, whatever you actually use
- Givers can cover the processing fee so the full amount reaches you, at your discretion
- Annual giving statements handled where they already are, rather than duplicated
- Who may see individual giving is a setting you decide on purpose, not a default somebody else picked
Follow-up In development
The card a visitor fills out goes somewhere, a real person gets told, and a week later you can see who was contacted and who wasn't. Prayer and care requests route to the person you name — never a shared inbox, never a bulk list.
- Connect card, prayer request, baptism interest, next steps, volunteer signup
- Texting that's registered properly under your church's own legal name
- Event registration for VBS, camps, trips and the seasons that need it
- Care requests with the routing written down, so nothing sensitive lands where it shouldn't
- On a larger plan: the next-steps paths — plan your visit, new member, first-time guest — written once and walked automatically
Your men's conference. Your women's retreat. The student trip.
The events people pay for are the ones that turn into a spreadsheet, a group text, and somebody tracking who still owes a deposit on the back of a bulletin. Those run inside the same system that already knows who these people are.
What we do In development
- Registration with a deposit now and a balance later, tracked per person
- Payment on the same rails as your giving — one processor, one set of records
- Waivers, medical and dietary forms built into the signup instead of chased afterward
- Event check-in: who actually showed up at the retreat, who still owes, who never came
- The registration list is your church's people list, so a first-time guest at a conference doesn't become a second record
What we don't do — kids' check-in
We don't do Sunday morning children's check-in, and we're not going to. Not a tease, not a roadmap item.
There are genuinely good systems built for exactly that — Planning Center, KidCheck and others — with security tags, guardian matching and pickup rules worked out over years. If you have a children's ministry, use one of them. A half-built check-in is worse than none, because it's a promise about somebody's child that you have to keep in a crowded hallway at 10:42 on a Sunday.
Event check-in and kids' check-in are different jobs. We do the first one. We'll sit beside whoever does the second.
Who sees who gave what.
Most church software answers that question for you. You should answer it yourself.
Every church has a position on whether the pastor sees individual giving records. Some are convinced he should, so he knows where people are. Some are just as convinced he shouldn't, so the pulpit stays clean. Both are defensible, and both have been argued in good faith for a long time.
What isn't defensible is finding out which one your software picked for you after a deacon notices something he shouldn't have been able to see. So we ask it on the setup form, in plain words, before anything is built — pastor and finance team, finance team only, or finance team with the pastor on request. Whatever you pick is what gets built, and the build defaults to the narrower reading.
The same principle runs through the rest of it. Prayer requests don't go to a shared inbox. Care notes don't ride along on a data import. Youth contacts stay out of bulk texting until a guardian is on file. None of that is a feature anybody brags about. It's just what it costs to be trusted with a congregation's information.
How giving gets turned on
- Your church applies to the payment processor itself — your legal entity, your bank account, your name on it. We can't do it for you, and wouldn't want to.
- A human reads the application. That takes days, not minutes, and it sometimes comes back asking for one more document. That's normal, not a rejection.
- Everything else keeps getting built while you wait — the site, the forms, the follow-up.
- When you're approved, we connect the giving page, send one real dollar through it to prove the whole path, and refund it.
What you'll need in front of you
- Legal name
- EIN
- Bank account
- An officer who can sign
No determination letter? That's normal. A church is tax-exempt without ever applying for one, so most don't have it. Incorporation papers and a bylaw page do the same job.
Honestly: not open yet.
The same system has been running at a campus ministry for a while now — giving, people, events, the website, the texting. That part isn't theoretical. What's new is pointing it at a church, where the questions are different enough to be worth doing properly rather than renaming the campus version and hoping.
What already exists: the setup form a church fills in, the part that reads your current website and pulls your logo and colors so you don't retype them, and the whole platform underneath. What doesn't exist yet: a church running on it. The first few will get more of my attention than anybody who comes later, and they'll also be the ones who find the things I haven't thought of.
If you want a pitch with a launch date on it, I don't have one. If you want to be told when it's ready and roughly what it'll cost before anyone else is, that I can do.
A pastor who got tired of dropping things
David Stone has spent decades in ministry. He preaches, he serves as an elder at his church, and he works with pastors and church planters who are worn out in ways their congregations don't see. He also runs a marketing company, which is a strange combination until you've watched a good church lose a family because nobody followed up on a card.
At 40 he was diagnosed with ADHD, which explained a lot. He had two options: keep pushing through the mess and hope nothing important hit the floor, or build systems that filtered the noise instead of adding to it. He picked the second one, and he's been building them ever since.
The campus version came first, because that's where he was serving and that's where the pain was. Churches kept asking for the same thing. The honest answer was that a church isn't a campus ministry with different words — the giving question is different, the privacy question is different, and nobody visiting a church website cares about any of it except whether their kids will be safe and whether they'll be singled out. So it's being built as its own thing.
He didn't set out to build church software. He set out to stop watching good churches lose people to a drawer full of connect cards.
Before you send that email
Is any of this actually built?
The platform underneath is, and it's been running a campus ministry for a while — giving, people, events, website, texting. The church version of the setup is built. What doesn't exist yet is a church running on it. I'd rather tell you that now than discover it together in month two.
Do we have to leave the software we already use?
Not necessarily. Plenty of churches want to keep their existing people software and just fix the website, the giving, and the follow-up. That works, as long as we decide up front which system owns which piece of information. Two systems both convinced they're right about somebody's address is its own kind of mess.
Do you do kids' check-in?
No, and we won't. Planning Center, KidCheck and others have spent years on security tags, guardian matching and pickup rules, and they're good at it. Use one of them. We do event check-in — the retreat roster, who showed up, who still owes a balance — which is a different job. We'll sit beside your check-in system, not replace it.
Can we put our sermons and small groups on it?
Yes, both. Sermons with the newest on the front and an archive behind it. Small groups listed so somebody looking for one can find it and say they're coming, instead of emailing the office and waiting.
Who sees individual giving?
Whoever you say. It's asked on the setup form in plain words — pastor and finance team, finance team only, or finance team with the pastor on request — and the build defaults to the narrower answer. It's a policy decision, not a settings question, and it's much easier to set now than to unwind later.
We don't have a 501(c)(3) letter. Is that a problem?
No, and it's the normal case. A church is tax-exempt without ever applying, so most churches have never had a determination letter. Incorporation papers and a bylaw page do the same job for the payment processor. If you're under a denominational group ruling, that letter works too.
Do we have to be Baptist?
No. I am, and I'm not going to pretend otherwise, but none of this has a doctrinal position baked into it. It's a website, a giving page, and follow-up. Your statement of faith is yours and it goes on your site in your words.
How long does it take?
The build is fast. The two waits aren't mine to hurry: a payment processor has to approve your church before you can take a card, which runs on days, and the phone carriers have to register your church before you can text in bulk, which runs on two to four weeks. Both start after we talk, and everything else gets built while they run.
What does it cost?
Not set yet, and I'm not going to invent a number to fill the space on this page. When the church pricing is real, the people on the list hear it first.
Who is this for?
Small and mid-sized churches who can't staff a communications director, where somebody's already doing the website at night and the follow-up is honest work falling through honest cracks. If you've got a full communications team and software that works, you don't need me.
Tell me what's breaking, and I'll tell you honestly whether this fixes it.
No demo to sit through, because there isn't one for churches yet. Just a short email from you about where your church is stuck, and a straight answer back — including "that's not what this is for," if that's the true answer.
It's me reading these, not a form.