I'm the operations department for a 700-person church

Last Wednesday I configured a firewall rule, fixed a finance integration, stood up a decision log for senior leaders, debugged a React component, approved a facilities work order, and helped a volunteer reset their password. That was before lunch.

My title is Executive Pastor. In practice, I carry executive responsibility for operations, finance, technology, facilities, HR, communications infrastructure, and data analytics at a church that’s grown from 200 to 700 people in under five years — with a staff team of 10 FTEs. I don’t just manage these functions. I architect the systems they run on.

If your first reaction is “that’s not sustainable,” you’re right. If you work in church operations, your second reaction is probably “yeah, that sounds about right.”

Nobody plans to become a one-person operations department. I’ve spent 15 years in church planting across three churches — from admin, to assistant pastor, to lead pastor — environments where “doing a lot with a little” isn’t a mindset, it’s a job requirement. The scope expands the same way every time: someone has to do it, you’re the person who figured out how to do it, and the responsibilities quietly accumulate until you’re managing domains you never trained for.

Finance showed up because someone needed to understand the budget. HR showed up because someone needed to handle onboarding paperwork. IT showed up because someone needed to set up email accounts. Facilities showed up because the HVAC broke and I was the one who called the vendor.

Each responsibility made sense on its own. Put together, it became a full operations department with one employee.

To be clear: I work with an exceptional team. Our lead pastor is one of the best vision casters and communicators I’ve been around. Our pastors are deeply effective in their areas — youth, kids, care, worship. The staff here are specialists, and they’re good at what they specialize in. The reason the operational scope lands on one person isn’t that nobody else is contributing. It’s that everyone else is rightly focused on ministry, and the infrastructure that holds all of it together doesn’t have a natural owner — until someone becomes one.

The role spans at least seven distinct domains, many of which would be standalone roles in a larger organization:

Technology and infrastructure. Azure cloud services, self-hosted applications, device management, network architecture, security policies, vendor relationships, and internal tools I built because nothing off the shelf did what we needed.

Finance. Budget management, giving analytics, donor follow-up workflows, audit prep, and compliance.

HR and staff support. Onboarding, offboarding, policy documentation, background checks, and the employee handbook nobody reads but everyone needs.

Facilities. Work orders, vendor contracts, safety compliance, and the Sunday morning checklist that keeps the building operational.

Communications infrastructure. Staff communications systems, internal platforms, and the architecture that keeps information flowing between departments.

Data and analytics. Giving forecasts, attendance trends, and the dashboards that help leadership make decisions with numbers instead of instinct.

Organizational systems. Knowledge base architecture, workflow design, platform administration, and the connective tissue between all of the above.

That last one is the part nobody talks about. The individual functions are hard. The integration layer — making sure finance, facilities, HR, tech, and communications don't operate as disconnected silos — is where the real complexity lives.

Two reasons.

First, because the resources available for church operations people are mostly bad. They're either too churchy ("God-honoring spreadsheets!"), too corporate ("implement a stakeholder alignment matrix"), or too shallow ("five tips for organizing your desk"). The people doing this work — the solo ops lead at a growing church, the executive pastor covering nine departments, the admin who somehow became the IT director — deserve better.

Second, because I've spent years building systems that actually work in this context, and I think some of them are worth sharing. Not as theory. As real infrastructure, real decisions, and real architecture that runs in production every day.

I built a knowledge base system with version-controlled Markdown, automated deployment to WordPress, and structured metadata that makes documents findable and maintainable. I'm building a self-hosted chat platform to replace Slack and cut thousands in annual licensing. I built a giving analytics dashboard that forecasts cash flow. I designed onboarding workflows, facilities checklists, and HR policies that actually get followed — because I designed them to be followed.

None of it is magic. All of it is hard-won.

This is The Ops Pastor. This is the resource I wish I had when I first inherited operations - when building and running infrastructure in a context where the budget is small, the team is lean, and the mission matters too much to let it rot.

I'll share what I've built, what I've broken, and what I'd do differently. Over time, I'll also be packaging some of these systems into tools and templates for other people in this role. But the writing comes first, and it's free.

If you run operations at a church or small nonprofit — especially if half your job exists because nobody else had time to pick it up — this is for you.

Subscribe to the newsletter. One email a week. No fluff.