Why churches and startups have more in common than you think.
Grand vision, limited resources, fluid context. The surprising overlap between two seemingly opposite worlds — and what each can learn from the other.
A pastor and a startup founder walk into a coffee shop. You'd expect them to talk past each other — one stewarding a centuries-old institution, the other trying to ship a product before the runway runs out. But sit with the conversation for ten minutes and something odd happens: they start finishing each other's sentences.
I've spent the last decade working in both worlds. I was a product designer at a startup, and I've consulted with churches trying to figure out how to stay faithful in communities that no longer speak their language. The surface differences are obvious — one sells software, the other proclaims a gospel. But the deeper I've gone in each, the more I've been struck by how much of the work is the same.
What they share
Both churches and startups carry a grand vision. A startup wants to change how people work, or travel, or eat, or connect. A church wants to announce a different way of being human in the world. Neither vision comes with adequate resources — both are chronically underfunded relative to the size of the thing they're trying to do. That mismatch shapes everything: the urgency, the improvisation, the constant need to prioritize.
Both operate in what I've come to call a fluid context. For startups, the market shifts — new technology arrives, purchasing behavior evolves, a competitor eats their lunch. For churches, the neighborhood shifts — gentrification reshapes who shows up, cultural values drift, the language of faith stops translating. In both cases, the team that built the thing is not necessarily the team equipped to navigate what comes next.
Both need strong leadership with a clear vision, the communication skills to articulate it, and the capacity to mobilize a team around it. Both depend on community support — startups seek out investors who believe in the thesis, churches depend on members and donors who give generously. Both have to earn and re-earn the loyalty of the people they serve. Both face real obstacles: startups face failure and competition, churches face declining attendance and internal conflict. Both require resilience.
Where they diverge
The differences are real, and they matter. Startups ultimately orient toward growth and financial viability — they exist to capture a market. Churches orient toward something else: a higher purpose, a faithfulness, a witness. Most churches have long histories and inherited traditions; most startups are young and built deliberately against tradition. And the deepest divergence is the one a friend of mine describes as follow the Spirit versus follow the money:
Churches & startups — commonalities and differences
A church can't simply self-determine its direction the way a startup can; it's trying to discern and follow. A startup can't simply wait on the Spirit; it has to make defensible decisions with partial information and ship. These are not small differences. They shape what strategy even means in each context.
The existential stakes are different — and that's a problem for the church
Here's something uncomfortable. A startup that stops being effective goes out of business. The feedback loop is brutal and fast: if users don't return, revenue dries up, and within a few quarters the lights go off. The market punishes ineffectiveness quickly.
A church that stops being externally effective does not, in most cases, close. As long as there are members who give, the lights stay on. The feedback loop is slow, muffled, and deeply confusing to read. Many churches have been coasting on legacy membership for a generation, their external witness ineffective in a way that would have bankrupted any startup years ago.
I don't say this to shame anyone. I say it because the absence of immediate consequence is a real liability. It allows churches to mistake survival for faithfulness. It allows us to avoid the kind of honest self-assessment that startup teams do every week because they have to. Churches have the luxury of slow decline — and that luxury is quietly killing a lot of them.
What churches can borrow
Over the last two decades, startups have developed a rich toolkit for navigating fluid contexts: lean startup methodology, design thinking, user research, agile iteration, honest measurement, the minimum viable product. These tools are not neutral — they carry assumptions about what matters and how to decide. But they can be adopted with discernment, and they're extraordinarily useful.
A church that talks to the people it's trying to reach — actually interviews them, actually listens, actually lets their answers reshape the ministry model — is doing user research. A church that prototypes a new gathering before committing a five-year budget to it is running a lean experiment. A church that measures not just attendance but the depth of relationships formed, the theological formation happening, the neighborhood's perception — that church is doing the equivalent of a thoughtful product dashboard.
None of this replaces prayer, preaching, the sacraments, or the work of the Spirit. It supplements them with a kind of strategic humility — an acknowledgement that context matters, that we can be wrong, that the thing we did last year may not be the thing the next year needs.
What startups can borrow
Less often discussed, but just as real: startups have something to learn from churches too. Most startup teams burn out because they chase metrics without a clear why. They optimize for growth because growth is measurable, and they lose the sense of larger purpose that sustained the founders through the early years. Churches know something about long time horizons, about vocation, about the discipline of stewardship over ownership. Churches know that some of the most important work is invisible and unquantifiable.
The best product teams I've worked with behave a bit like small, healthy churches: clear about their mission, patient with each other, willing to measure the right things rather than the easy ones, invested in the formation of their people and not just the output of their work.
One approach, two contexts
This is what "Missional by Design" is actually about. It's not a claim that churches should become startups, or that startups are secretly churches. It's an observation that the design work in both contexts is more similar than we usually admit — and that if we're honest about that overlap, we can bring the best tools from each tradition to bear on the deepest questions in the other.
Grand vision. Limited resources. Fluid context. Stewardship. A human-centered posture. These five things sit in the middle of both circles. If you're building in either world — and especially if you're building at the intersection — they are the ground you're standing on.