Built by a Detective,
Not a Consultant
I spent 25 years as an IMPD detective. I've worked undercover narcotics, financial crimes, digital forensics, and violent crimes. I've testified as an expert witness in state and federal court. I've seen—firsthand—what happens when departments try to run 21st-century operations on spreadsheets, whiteboards, and institutional memory.
I didn't build this software because I saw a market opportunity. I built it because I watched good officers spend hours on problems that a well-designed system could solve in minutes.
25 Years. Every Division.
When I say I understand law enforcement operations, I mean I've lived them across every major unit in a major city department.
Software Designed by Consultants Who've Never Worn a Badge Fails
"I've sat in rooms watching department after department evaluate software built by people who've never interviewed a victim, coordinated a multi-agency operation, or explained a case to a federal prosecutor. You can tell. The workflows are wrong. The terminology is wrong. The assumptions about how decisions actually get made are wrong."
— Matt Shores, Founder
- The real workflow is never the official workflow
Watch how officers actually work before you build anything. The process in the manual is not the process in the field.
- Documentation failure is operational failure
Incomplete records aren't an administrative problem — they're a liability, a safety issue, and a case-killer. Software that makes documentation harder doesn't get used.
- Speed matters at 3 AM
If a system takes 90 seconds to log an encounter, officers stop logging encounters. Every click is a decision to quit using the tool.
- Command needs visibility, not noise
Dashboards that require interpretation aren't dashboards — they're a second job. Leadership needs the answer, not the data.
- Accountability without surveillance
Audit logs protect officers as much as they protect the department. The goal is accountability, not gotcha. Officers need to know that too.
"I Saw the Problems Firsthand. Now I'm Building the Tools That Should Have Existed."
OutreachLink came out of watching law enforcement and civilian agencies try to coordinate homeless outreach using phone calls, email chains, and Google Sheets. Thirty organizations. No shared system. The same person contacted five times while someone else fell through the cracks entirely.
UnitGear came out of watching supervisors lose an entire morning trying to figure out what tactical equipment was checked out to whom before a deployment. A $5 million inventory tracked on a clipboard.
Both products are in production because I built them for the actual problem, not the textbook version of the problem. I've been in the briefings. I know what the commander needs to see. I know what the detective needs to log at 11 PM on a Tuesday.
Want to See What I Built?
Schedule a 30-minute demo. I'll walk you through the product myself — no sales rep, no deck. Just the software and how it works in the field.
Or email me directly: matthew@mshorestech.com