I came to church safety from two directions most people never combine. I write software, and I wore a badge.
Before I ever stood a post at a sanctuary door, I built software for a living. I earned a computer science degree and spent my early career as a programmer, a systems administrator, and a network engineer. Then I changed direction. I started my law enforcement career on September 11, 2003, two years to the day after I sat at a programmer's desk and watched the towers come down on live television. I won't pretend that morning didn't push me toward public service. I gave the next 20 years to the Cleburne Police Department here in Texas, promoting from patrol officer up through corporal, sergeant, and lieutenant.
The last stretch of that career is the part that matters most for what we built. I finished in administrative and technical command: running our 911 communications center, serving as the agency's CJIS security officer (the person responsible for protecting sensitive criminal justice data), and leading the selection and rollout of the systems my officers lived on every shift, from dispatch and records to body cameras.
"I was the cop who spoke fluent IT, and the IT guy who had actually worked the street."
Very few people sit in both chairs. I did, for two decades.
One case I'll carry the rest of my life. In 2015, some human trafficking volunteers told me Johnson County and Cleburne had a problem with online trafficking, adults and minors both. They were right. I wrote the proposal to the Texas Attorney General's office that started the whole thing rolling, an online sting going after the people who use the internet to target children. It grew into a multi-agency operation with the AG's human trafficking division, and the goal was never just arrests. It was rescue. That work is some of the best and the worst I've ever done as a cop.
"When people ask why child protection sits at the center of everything we build, I don't have to reach for an answer."
For the last 14 years, I have also led the safety team at my church, Pathway. I have watched it grow from a mid-sized congregation into a megachurch, and the weight of protecting it grew right along with it. Standing that post taught me something no software vendor ever understood:
"A church safety team is not a security guard with a logo. It is a ministry."
The job is to protect God's people so the church can do its real work, reaching one more soul for Jesus, and to do it without ever becoming the thing visitors are afraid of.
Here is the honest version of why N4 Safety exists. The tools to take ordinary, faithful volunteers and grow them into quiet professionals, vetted the right way, trained to a real standard, documented well enough to stand up in court, did not exist. So we built them, my team and I, the same way every honest tool gets made: by people who needed it first.
I'll tell on myself, because it's the clearest way to explain what we're building. My documentation has never been where it needs to be. For years it was scattered notes and procedures that lived in my head, a paper trail that wouldn't have survived the first hard question from a lawyer or a grieving parent. It's better now, and it's getting better as we build N4 Safety, but I don't have it all figured out. That's the honest part.
"If it isn't written down, it didn't happen, and you can't prove you did the right thing."
A church can do everything right in the moment and still be sued out of existence because nobody wrote it down. We're building our way out of that in our own team, and we're inviting others along for the journey. Progress, not perfection.
That is the whole idea behind N4 Safety. Build a team of quiet professionals. Defend the people God has entrusted to your church. Protect the mission from those who would love nothing more than to tear it down. We did not build this to sell it. We built it because we needed it. Now we want to put it in your hands.