A Visitor Is Not a Lead

Most church software was not designed for churches. It was adapted from software designed to sell things, and it brought its vocabulary with it. Visitors became leads. Members became retention. A family that stopped coming became churn. The weekly work of a congregation, who showed up, who gave, who opened the newsletter, was rolled into a single number and called engagement, which is the word the attention industry uses for the thing it harvests.

I have spent forty years in software and I know exactly how this happens, because I have done it. Nobody sits down and decides to describe a congregation as a sales funnel. A team builds a product for one market, usually a commercial one, and then notices that churches also have contacts and events and payments, and ports the product across. The data model fits well enough. The words come along for free, because renaming them is work nobody is paid for, and because the people doing the port do not think of words as part of the product.

Words teach you what to see

They are wrong about that, and the error matters more in a church than almost anywhere else.

A pastor who opens a dashboard every morning and reads the word pipeline begins, slowly and without ever deciding to, to see one. That is not a weakness of pastors. It is how language works on everyone. The categories you are handed become the categories you think in, and a tool you use daily hands you its categories hundreds of times a year.

So consider what the inherited words teach. A visitor who is a lead is someone to convert, and conversion in that vocabulary means a completed transaction, not a changed life. A member who is retention is someone to keep, which quietly makes their leaving a failure of the institution's grip rather than a question about their soul. A family that is churn is a number that went down. Not a household where something happened: a job lost, a marriage strained, a diagnosis, a quiet hurt from someone in the pews. The word churn does not ask what happened. It asks what the rate is.

And engagement, the worst of them, teaches that the measure of a congregation's life is how much it interacts with the software. A church whose members open the app every day is engaged. A church whose members are sitting with each other in hospital rooms and not looking at their phones is, by that metric, in decline.

What we are trying to do instead

At SoapBox we are trying to refuse the inheritance, and I want to be honest that it is harder than it sounds, because the inherited words are also the words that software people know, and every engineer who joins us arrives fluent in them.

A first-time visitor is a guest. Not a prospect, not a lead. A guest is someone you welcome and feed and make no demands of, and whose return you hope for without engineering it. The word changes what the follow-up looks like. You do not nurture a guest. You thank them for coming.

A member who has gone quiet is a person we have not heard from. That phrasing points at the right action, which is to find out how they are, not to win them back. The question a pastor should be asking about a quiet household is not "how do we re-engage them" but "what happened, and do they need something." The software can surface that someone has gone quiet. It should not tell the pastor what the silence means.

Giving is giving. It is not revenue and it is not a conversion event. We take no cut of it and we never hold it, and we try to keep the language around it as plain as the rule: the gift goes to the church. Nobody is being upsold at the offering.

And there is no funnel, because a church is not trying to get people to buy. It is trying to be a body, and bodies do not have funnels. They have members, which is an old word that the business world borrowed from the church and not the other way around.

The church already has better words

The part I find most striking is that churches never needed our vocabulary. They have their own, two thousand years old, and it is more precise than anything the sales world ever invented, because it was developed by people thinking carefully about exactly this: how a community of people who did not choose each other holds together over time.

Member. Guest. Neighbor. Shepherd. Flock. Elder. Deacon, a word that means servant. Fellowship, which is not an event on a calendar but a condition. Pastoral care, which has no equivalent in a sales organization because a sales organization does not care for anyone; it manages accounts. Every one of these words carries a theory of what a person is and what the community owes them. None of them can be swapped for a metric without losing the theory.

A piece of software that uses those words, and resists adding its own, is doing something more important than being on brand. It is declining to re-educate the pastor. It is saying, in effect, that the church knows what it is doing and the tool's job is to serve that, not to import a model of human beings from an industry whose model of human beings is that they are wallets with attention attached.

Why a founder cares about nouns

I know how this sounds coming from a technology founder. Vocabulary is soft. Features ship; words do not appear on a roadmap. But I have watched enough products shape the organizations that adopted them to believe that the nouns are the product, and that everything else is implementation. A church that spends five years looking at a dashboard built on sales words will, at the end of those five years, be a slightly different church, and not because anyone chose it.

So we are trying to give the words back. A visitor is not a lead. A member is not retention. A family that stopped coming is not churn; it is a family, and something happened, and the right response to that is a phone call, not a campaign. The software should learn the church's words. The church should never have to learn ours.