Ministry was never meant to run through a dozen disconnected spreadsheets, sticky notes, and systems that don’t talk to each other. But for too many churches — especially smaller ones without a full-time admin staff — that’s exactly what “managing the church” looks like. Pastors end up doing data entry instead of discipleship. Volunteers lose track of who needs a follow-up call. Growth becomes a burden instead of a blessing, because the tools meant to support ministry end up competing with it for time.

I’ve been involved in ministry my entire life. Long before I ever wrote a line of code, I understood something churches live with every day: ministry rises or falls on communication — between leaders and members, between groups and congregations, between the people trying to shepherd a church and the people they’re called to serve. When that communication breaks down, so does everything built on top of it.

My career took me into the software industry, where I spent years leading teams and learning, firsthand, what separates a good tool from a bad one — not just in features, but in how it actually feels to use day in and day out.

Along the way, I used more than a few Church Relationship Management systems myself, and I kept running into the same frustrating gap. The free and low-cost options were often clunky, confusing, and hard to navigate — the kind of software that makes a volunteer give up halfway through entering a family’s information. The good ones, the ones that actually worked well, came with a price tag that put them out of reach for a lot of churches — or worse, nickel-and-dimed every additional feature until a growing church couldn’t afford to keep growing into the tool it needed.

“A church’s size or budget shouldn’t determine whether its leaders get to use software that actually works.”

So I set out to combine what I’d learned in three different worlds — software development, business leadership, and ministry — into one tool: something accessible and genuinely user-friendly, built for churches of every size and every season, not just the ones who could afford it. LighthouseChRM is the result of that conviction: that good technology, built with the right heart behind it, should serve the mission — not tax it.

A lighthouse was never the destination. Ships don’t sail toward it to arrive — they use it to find their way safely to where they’re actually headed. That’s the role we wanted this tool to play in a church’s life: not another thing to manage, not another system to feed, but something steady and dependable working quietly in the background so leaders can keep their eyes on what matters — their people, and pointing them to Jesus.

We didn’t want to build software that asks for a church’s attention. We wanted to build software that gives it back.