Own It or Rent It? Subscriptions, Feature Licensing, and the Fight Over Your Radio Budget
The most consequential change in public-safety technology this decade is not a new radio. It is a new invoice. The industry is moving, deliberately and fast, from "buy the equipment and own it for fifteen years" to "subscribe to the capability, forever." For a chief or a commissioner, this is not a small procurement detail. It reshapes who controls your communications, how you fund them, and what happens the year the money is tight. Here is the honest breakdown, including the parts the sales team would rather you not dwell on.
What actually changed
For most of the history of public-safety communications, the model was simple to understand even when the price was painful. You bought radios, a system, consoles. You owned them. You maintained them, you paid for the occasional upgrade, and you ran them until they were genuinely obsolete, often fifteen or twenty years. The cost was a mountain up front and a foothill every year after.
The industry has spent the last several years rebuilding around a different model, the same one that reshaped enterprise software: recurring revenue. It shows up in several forms. Radio-as-a-service, where you pay a monthly or annual fee per device instead of buying the fleet. Feature licensing, where you buy the radio but rent the capabilities inside it. Software and cloud subscriptions for dispatch, logging, location, and analytics. The common thread is that the mountain-then-foothill cost curve is being replaced by a permanent, and generally rising, annual payment. This is not an accident or a trend; it is a strategy, because recurring revenue is worth far more to a vendor than a one-time sale. Understanding that it is deliberate is the first step to negotiating it well.
The honest case for subscription
It would be easy to write this as a hit piece. That would be dishonest, because for some departments subscription is genuinely the better deal, and pretending otherwise helps no one. Steelman it first.
- No capital cliff. A full system or fleet replacement can be a seven-figure shock a small department simply cannot absorb in one budget year. A subscription turns that cliff into a predictable annual line.
- Always current. Security patches, new features, and standards updates arrive as part of the service, instead of aging out because a capital upgrade got deferred three years running.
- Someone else maintains it. For a department with no dedicated radio staff, having the vendor carry maintenance and lifecycle can be worth real money and real reliability.
- Lower barrier to entry. A small or new agency can field modern capability without the up-front capital it could never raise, which genuinely levels the field.
For a small volunteer department that cannot float a capital purchase and has no one to maintain a system, a well-structured subscription can be the difference between modern, reliable communications and limping along on failing gear. That case is real.
The honest case against
Now the other side, which is just as real and gets far less airtime in the briefing.
- You never own it. The payments do not build toward ownership. They continue for as long as you want the capability, which is to say forever, and they generally rise over time.
- Stop paying and it degrades. Miss the renewal, or lose the budget line in a bad year, and capability can be throttled or switched off, sometimes on hardware sitting right in front of you. That is a very different risk profile than owning a radio that keeps working whether or not this year's budget passed.
- Lock-in deepens. The longer you rent an ecosystem, the harder and costlier it is to leave, and the vendor knows it. Pricing power shifts to them at every renewal.
- Often more expensive over the life. Run the fifteen-year math and subscription frequently costs more in total than buying, sometimes dramatically more, because you are paying for the vendor's financing, risk, and margin every single year.
- Loss of control. The decisions about when things change, what gets deprecated, and how much it costs move from your budget meeting to the vendor's boardroom.
Feature licensing: renting the hardware you already bought
The single most controversial version of this deserves its own section, because it is the one that makes chiefs genuinely angry, and not without reason. In feature licensing, you buy the radio outright, and then you pay, often annually, to unlock capabilities that are already built into the device you own. Encryption. Location. Certain interoperability modes. Advanced trunking features. The silicon is in your hand; the capability is behind a paywall.
Defenders argue it lets a department buy only what it needs and add features later without new hardware. There is a sliver of truth to that. But for many buyers it lands as paying twice, once for the radio, then forever for the radio to do what it was physically built to do. Whatever your view, know exactly which capabilities on your radios are perpetual and which are licensed, because the answer determines what your fleet can still do the year a license lapses. A department that discovers, during a mutual-aid incident, that its encryption or interoperability quietly expired has learned this lesson the worst possible way.
For every radio and system you are quoted: which capabilities are perpetual and which are a subscription? And what specifically stops working if that subscription lapses? Get it in writing.
The budgeting trap public agencies fall into
This is where the subscription shift collides with the reality of public budgeting, and it is the part that should keep a finance officer up at night. Government budgets separate capital spending from operating spending, and they fund them from different places with different rules.
A capital purchase, buying a system or a fleet, is often exactly what grants are built to fund. Federal and state public-safety grants, bond measures, one-time appropriations: these tend to pay for things you buy and own. A subscription is an operating expense, a recurring line the general fund has to carry every year, forever, and grants usually will not touch it. So the shift from buy to subscribe quietly moves the cost of your communications from a bucket that outside money can fill to a bucket only your local budget can, and it converts a one-time approval into a permanent annual fight.
The political version is sharper still. A commissioner or council approves a capital buy once, cuts the ribbon, and moves on. A perpetual subscription is a line item that comes back every single budget cycle, competing with everything else, vulnerable in every lean year. The technology that is subscribed is the technology most likely to be cut when the money gets tight, which is to say, potentially, the year of the disaster that strains everything. Matching your funding source to your cost structure is not accounting trivia. For a public agency it is a survival question.
Running the real total cost of ownership
The only honest way to compare is a full-life total cost of ownership, and the vendor's one-page comparison is almost never it. Build your own over the real life of the system, typically ten to fifteen years, and include the parts that get left out:
- For buying: the capital purchase, plus maintenance contracts, plus mid-life upgrades, plus the subscriber-radio replacement cycle, plus a funded replacement reserve for the eventual next system.
- For subscribing: every annual payment across the full term, escalated by the real price-increase clause, not today's rate, plus anything still purchased outright, plus the exit cost if you ever leave.
Two numbers decide most of it. The first is the price-escalation clause: a subscription that looks cheaper today can overtake a purchase quickly if it rises several percent a year with no cap. The second is the discount rate you apply to future money, which is genuinely debatable, but be consistent and be honest. Run it over fifteen years, not five, and the picture often looks very different from the slide.
How to decide, and what to negotiate
There is no universally right answer, and anyone selling you one is selling. The decision turns on your capital access, your ability to maintain what you own, and how much control you need. What does not change is the list of things to pin down before you sign:
- What is perpetual versus subscribed? Line by line, hardware and features.
- What is the escalation cap? Insist on a hard ceiling on annual increases, in writing.
- What degrades if you stop paying? Exactly which capabilities, and how fast.
- Is there a buyout or ownership path? Can subscription convert to owned, and on what terms?
- Data and exit portability. If you leave, what do you keep, and what does migration cost?
- Grant-fundability. Confirm with your grant sources what they will and will not fund before you restructure your costs around subscription.
Bottom line
Subscription is neither the scam some chiefs fear nor the effortless upgrade the vendors promise. For a small department with no capital and no radio staff, it can be a genuine lifeline. For a department that could buy and maintain its own, it can be a slow, rising, control-surrendering trap dressed up as convenience. The danger is not choosing one model; it is drifting into perpetual payments without ever running the fifteen-year math and without matching the cost to a funding source that can actually carry it. Own what you must control. Subscribe to what genuinely benefits from staying current. Read the escalation clause before you read anything else. And never let your most critical communications become the line item that is easiest to cut in the year you can least afford to lose it.
RunBoard helps volunteer and small career departments keep the operational records, cost histories, and reports that turn a technology request into a defensible budget argument. The pitch lives in your SOPs; the proof lives in your data.