Public-sector technology programs fail for a specific reason more often than any other: the business case is written after the decision, to justify it, instead of before it, to make it. This engagement inverted that order.
Discovery before design
The work began with functional analysis and field research rather than a vendor evaluation. The question was not “which connected-officer platform should we buy” but “where does an officer’s shift actually go, and how much of it is recoverable?” Those are different questions and they produce different roadmaps.
Sizing the opportunity honestly
The modelling deliberately used conservative assumptions. A business case that projects 300% ROI on aggressive numbers gets discounted by every reviewer it passes; one that projects 300% on conservative numbers survives review. In a procurement environment with genuine public accountability, the credibility of the estimate is worth more than the size of it.
From pilot to rollout
The pilot was scoped to be small enough to fund without a lengthy approval cycle and representative enough that its results could be extrapolated across the service. That combination is what turned a single pilot into an approved service-wide rollout.