Should you build it yourself?
An honest decision framework. The maintenance burden, the bus factor, and the questions to answer before you write anything.
Read
What a department can now build without a software team
Build it yourself
AI-assisted development has genuinely changed what a technically-minded officer can build in a week. This track covers what is realistic, what is not, and how to avoid building something nobody can maintain after you retire.
In this track
Building internal tools with AI assistance
What tools like Claude Code and Lovable make possible for someone who is not a developer, using a real example.
Read
Connecting the systems you already have
Pulling data out of CAD and RMS through their APIs, and automating the reporting nobody wants to do by hand.
Read
Workshop: build a department dashboard in a day
A hands-on session taking a group from incident export to a working dashboard their department can use.
Workshop
3 of these are readable now
Those pieces carry our framing of the subject, the outside reading we could verify, and the questions to put to a vendor. The full guides are still being written. Everything marked planned is outline only. If something here is wrong, missing, or in the wrong order for how a department actually works, that is worth knowing now.
Send a note