When Two Companies Own the Stack, Their Roadmap Becomes Your Doctrine

Axon just signed Maricopa County to a roughly $45 million, ten-year agreement that bundles body cameras, conducted energy devices, drones, cloud storage, evidence management, and AI report writing under one vendor on one contract (Axon: Public Safety Goes AI, https://seekingalpha.com/article/4892942-axon-public-safety-goes-ai). Motorola Solutions is racing the same direction by acquisition, pulling in RapidDeploy on the 911 side and putting $1.5 billion into counter-drone, landing it in direct competition over who owns the entire public safety stack rather than a piece of it (Motorola Solutions Leans Into AI Public Safety Deals, https://www.sahmcapital.com/news/content/motorola-solutions-leans-into-ai-public-safety-deals-and-raised-outlook-2026-05-10). Read the trade coverage and it all sounds like a market story. Mergers, contracts, earnings calls, the language of a boardroom.

But it arrives on our trucks as doctrine.

What Axon and Motorola Just Did

Step back from the features for a second, because the features are the distraction. The thing that actually changed is the unit of sale. It moved from a tool to a platform, and the length of the commitment moved from a budget cycle to a decade. When one company owns the camera, the storage, the records, and the AI that reads all three, those pieces stop being things you can swap out one at a time. They become one thing you either keep or rip out whole.

Axon is building toward owning the full chain of an incident, from the device on the officer to the AI that drafts the narrative to the cloud that stores the evidence. Motorola is buying its way to the same place from the dispatch side, stitching together 911 call handling, communications, and security into a single offering. Two companies, racing to be the one vendor a public safety agency never has to leave. The competition between them is real, and it is fierce, and it is still a competition over the same prize: the whole stack, not a slice of it.

Fire Gets to Watch the Movie First

Here is the part that should feel like a gift, if we are honest enough to use it. Fire is a few steps behind law enforcement on this. The big platform plays are landing in policing first, which means we get to watch the movie before we are the ones in it.

But the stack is already consolidating around us. CAD, records management, the ePCR, the scheduling system, the analytics layer, all of it increasingly sold as one integrated suite by a shrinking set of vendors, with AI baked in as the reason to go all the way. Picture your next records-system procurement. The pitch will not be a better RMS. It will be a platform that does the RMS, the scheduling, the ePCR, and AI report drafting, priced so the bundle beats buying the best individual pieces, on a ten-year term. Say yes, and you have handed one company the spine of your information operation until 2036. The convenience is genuine. So is the dependency, and the dependency is the part nobody reads aloud in the demo.

Who Actually Writes Our Doctrine

The fire service has always set its own standards the hard way. Through consensus that took years to build. Through NFPA. Through the local protocol that a medical director argued for and signed and stood behind. Through the slow, contested, deeply human process of a service deciding how it does the work and who answers for it.

Consolidation pressures every piece of that. When a handful of companies own the platform thousands of agencies run on, their product roadmap quietly becomes the operating doctrine. The features they choose to build decide what “modern” looks like for the whole service. The ones they choose not to build simply do not happen, and most of us never even learn they were possible. That is not a purchase. That is a transfer of authorship, and it happens without a vote, a hearing, or a single line in a policy manual.

The unsettling part is how natural it feels. You adopt the platform because it solves a real pain, and then you start shaping your workflow to fit what the platform does well. The sense that you chose your operating model is a habit, not a fact. The model chose you, the day you signed.

What “Modern” Means When a Vendor Defines It

Run it forward. If the dominant platform builds its triage logic a certain way, that becomes how a thousand comms centers triage, not because anyone debated it on the merits, but because it is what the system does by default. If it structures the incident narrative a certain way, that structure becomes the standard report, and a generation of company officers learns to think inside the shape a product manager drew. Your operational practice starts getting set by a vendor’s release schedule instead of your own judgment about your own community.

The small and rural departments feel this first and hardest, because they get whatever the giant ships, with the least ability to push back, customize, or walk away. They are the most captive customers in the most consolidated market, and they are also a huge share of the American fire service.

I build software for this service, so I have a foot in both camps, and I will admit the uncomfortable thing. I sat through one of these all-in-one pitches and caught myself nodding at the bundle math before I caught what the bundle math was nodding away. That is how it gets you. Not with a bad product, but with a good one that quietly makes the decision feel already made.

The Authors and the Renters

So the work in front of us is not really about features, and it never was. It is about staying the author of our own doctrine even while we are the customer of someone else’s platform. That means being explicit, on purpose and in writing, about which of our practices are ours to decide and must never bend to a default setting, and where we are genuinely glad to adopt the vendor’s way because it is better than ours. It means agencies banding together, through their associations and their joint purchasing power, to shape the roadmap instead of accepting it one department at a time.

And there is an opening here, for anyone willing to build into it. The consolidation leaves real room for focused, fire-specific tools precisely where the giants ship generic, because a company optimizing a platform for the largest possible market will always leave the particular needs of the back of a medic unit on the floor. The fire service deserves tools shaped by people who have stood in the doorway of a working call. That standard does not soften because the vendor got bigger. If anything, it matters more.

The platform will keep consolidating no matter what any single department does. What is still ours is whether we walk into these deals as authors who know which practices are not for sale, or as renters who take the defaults and call them doctrine. The tools were never the decision. The authorship was, and that one is still on the table.

Robert Grand is a Battalion Chief at Eugene Springfield Fire with 24 years of service. He writes Frontline Intelligence, a newsletter on operational doctrine, technology, and leadership in Fire & EMS.

If this landed, share it with someone in Fire & EMS who needs to hear it.