The Offering Should Never Pass Through Us
Early in building SoapBox, we made a decision that quietly closed the door on an obvious way to make money. We decided we would never hold a church’s money. Not for a month. Not for a day. Not for the length of a database transaction.
To anyone who has spent time in financial technology, that sounds like leaving cash on the table, and it is. The standard playbook is almost irresistible in its elegance. You place your platform in the middle of the flow. Money moves from the giver, through an account you control, and out to the recipient a few days later. In the gap, you take your percentage, and — more quietly — you earn interest on the float while all that money waits. At scale, the float alone can become the business. I spent enough years building payment companies that I could have designed that version of SoapBox in my sleep. Investors understand it in a sentence.
We said no. When someone gives to their church through SoapBox, the money goes directly to that church’s own account. It does not stop in a SoapBox balance, because there is no SoapBox balance. There is no wallet. We take no cut of the offering. The gift a person makes on a Sunday morning is in the church’s hands, not ours, and the truth is it was never anywhere else. We built the plumbing so that the money has nowhere to pause inside our walls.
There is a practical reason for this, and I’ll be honest about it because it matters. The moment you hold other people’s money, you become something like a bank. You are a money transmitter, regulated as one, and rightly so — the rules exist because that position of trust has been abused before. We did not want to be a bank pretending to be a church app. Staying out of the middle keeps us out of a category we have no business occupying.
But the regulatory answer is the smaller answer. The deeper one is about what an offering actually is.
An offering is not a transaction. When the plate goes down the row, or the giving screen opens on a Sunday, something is happening that a checkout cart does not capture. A person is participating in the life of a congregation. They are saying, with money, that this community and its work are theirs. Scripture is blunt about the connection: “For where your treasure is, there your heart will be also” (Matthew 6:21, ESV). The gift and the heart travel together. When you route a gift like that through a corporate account, even for three business days, even perfectly and honestly, you have inserted yourself into a sacred exchange as a party that does not belong there.
Think about it from the pastor’s side. If a pastor would not hand the Sunday offering to a stranger at the door and say “hold this for me, I’ll collect it Thursday,” why should a piece of software earn that trust automatically, just because it has a nice interface and a reassuring logo? Trust is not a default setting. The most honest thing a technology company can do with a church’s money is arrange never to be trusted with it in the first place. Build the system so the question never has to be asked.
I won’t pretend the decision was free. It made the product harder to build and, in some ways, poorer. Direct payouts to hundreds of separate church accounts are messier than one central pool we control. We gave up the float, the easy percentage, the tidy revenue line that would have made certain conversations with investors much shorter. We make our money elsewhere — on the tools, the subscriptions, the software a church chooses to pay for because it makes their work lighter. We do not make it on the offering, and we designed it so that we cannot, even if a future version of us were tempted.
That last part is the point I keep coming back to. Good intentions are not a design. It is not enough to promise you will handle the money well; the promise has to be built into the architecture so that breaking it would take real effort rather than a quiet policy change. The most reliable way to protect the offering is to make sure it never touches you at all.
There is a version of this whole industry that treats a congregation’s generosity as a revenue stream to be optimized — a flow to sit astride, meter, and monetize. I understand the appeal. I have built companies on flows like that, and there is nothing wrong with charging fairly for real work. But the offering is not that kind of flow. It is closer to a prayer than a purchase, and you do not install a tollbooth on a prayer.
So we made our decision, and we live with what it cost. The offering should never pass through us. It should pass through the church, straight to the widow’s rent that gets quietly covered, the youth trip that gets funded, the roof that finally gets fixed, the missionary who gets sent. Our job is not to stand in that stream and take our cut as it goes by. Our job is to get out of the way of the sacred — to make the giving simple, and then to disappear from it completely.
That is the kind of technology I want to build for the church: the kind you forget is there, precisely because it never asked to be trusted with the one thing that was never ours to hold.