Built from the hours
after the call.

LeoPen was born from my real experience in the field. I spent years in law enforcement experiencing firsthand the challenges that consume valuable time and energy—none more frustrating than the hours spent writing reports after an incident.

Technology was moving quickly everywhere else, yet officers were still wrestling with outdated documentation workflows while the expectations for accuracy and accountability kept rising.

What stayed with me was not just the paperwork. It was knowing what it feels like to write a use-of-force report at 4 a.m., aware that every sentence may later be scrutinized in court. A general-purpose technology company can understand algorithms, but it does not automatically understand that responsibility.

When modern AI became capable of helping with complex, structured writing, I saw an opportunity—but I also saw the gap. Existing tools were not built around law enforcement's source material, agency policy, review boundaries, or the simple rule that the officer's facts and judgment must remain in control.

So I started building LeoPen—not another general-purpose AI product with a thin coat of law enforcement paint, but a documentation and review workspace shaped by someone who has been there. The goal is not to replace officer judgment. It is to give officers back their most valuable resource: time to actually police.