Motorola Solutions, Inc.

Motorola Solutions sells mission-critical land-mobile-radio (P25 LMR), command-center software, video/access control, and (as of ~2026-08-20) D-Fend RF cyber-takeover C-UAS to public-safety and sovereign buyers. The bottleneck is not a chip or a cloud API — it is the licensed-spectrum + APCO P25 + program-of-record installed base (~13k LMR networks) that cannot be swapped inside an 18-month bypass window.

• monetization model: One-time hardware/infrastructure + multi-year software licenses/SaaS + maintenance, repair, installation, managed services; recurring Software & Services ~37% of sales. Source: MSI 10-K FY2023 (latest verifiable here; later filings UNKNOWN), Business/MD&A, accession 0000068505-24-000011, sec.gov .
• revenue mix: Products & Systems Integration ~63% (LMR infrastructure, devices, video security/access control); Software & Services ~37% (command center, push-to-talk, video analytics, maintenance). Source: 10-K segment/revenue note, same accession.
• who pays: Government public-safety agencies (federal/state/local), critical-infrastructure/enterprise buyers; budgeted procurement and multi-year contracts. Source: 10-K Business/Risk Factors, same accession.
• margin_value_capture: ~50% gross margin, ~23% operating margin (FY2023); value accrues in software/services attach, installed-base maintenance, long-term contracts. Source: 10-K MD&A/segment note, same accession.

• customer classes: Government Civilian Agencies, Critical Infrastructure Operators, Defense & Intelligence Program Offices (Source: MSI 10-K FY2023, Business/customer disclosures, accession 0000068505-24-000011.)

Motorola Solutions, Inc.

Motorola Solutions operates through two reportable segments: Products and Systems Integration (PSI) and Software and Services (S&S). The company’s economic model combines large installed-base hardware sales with higher-margin software, maintenance, managed services, and cybersecurity recurring revenue.

Using the most recent full-year 10-K at the time of model knowledge — fiscal-year 2024 — the company’s revenue split is approximately:

Exact segment dollar values should be pulled from the FY2024 Form 10-K’s segment note; the split shown is for directional conviction and may differ by a few tenths. The company’s consolidated FY2024 net sales grew approximately 8% year over year to approximately $10.84B [Source B].

Motorola Solutions’ FY2024 consolidated margins, as reported in the earnings release and 10-K, are approximately:

The gap between GAAP and non-GAAP operating margin reflects stock-based compensation, amortization of acquired intangibles, and certain litigation/settlement or acquisition-related charges. Historically, MSI’s non-GAAP operating margin is a closely watched management metric because it highlights the company’s ability to convert revenue growth into operating profit after excluding acquisition noise.

Motorola Solutions monetizes through:

1. Hardware sales — land mobile radio (LMR) devices, base stations, repeaters, video cameras, and other physical equipment. These sales are generally one-time revenue events, though they often carry future software and maintenance attach.
2. System integration — design, installation, and integration of public-safety communications and video systems.
3. Software licenses and subscriptions — command-center software, video-management software, real-time intelligence, and cloud-based evidence management.
4. Recurring services — software maintenance, managed services, cybersecurity monitoring, and ongoing support contracts. These contracts provide a stream of recurring revenue and improve the company’s cash conversion over time.

Who ultimately pays: largely tax-funded public-safety budgets at the U.S. federal, state, and local government levels, plus commercial and critical-infrastructure operators such as utilities, transportation, mining, and industrial firms. Because the buyer is often a government agency using procurement budgets, the revenue base is fairly defensive but also subject to budget cycles.

One of the main business-model questions for MSI is whether the Software and Services segment can grow faster than the hardware-heavy Products and Systems Integration segment. That mix shift matters because software and managed services carry higher margins and recurring characteristics.

Motorola Solutions’ filings describe its customer base in broad classes rather than listing individual commercial names in many cases. Based on the FY2024 Form 10-K and earnings release, the main customer classes are:

1. U.S. federal government agencies

• The 10-K discloses significant sales to U.S. government customers. The precise percentage of revenue from the U.S. government as a single customer requires validation in the revenue-concentration note.
• Buyer archetype: federal program managers, emergency-management directors, defense/security procurement offices.

1. U.S. state and local public-safety agencies

• Police departments, fire departments, emergency medical services, sheriff’s offices, and combined dispatch/emergency operations centers.
• Buyer archetype: public-safety CIOs, communications directors, procurement officers, and elected officials controlling capital budgets.

1. International government and public-safety customers

• The company sells to national and local government agencies outside the U.S.
• Buyer archetype: national public-safety ministries, interior/defense departments, and state-owned critical-infrastructure operators.

1. Commercial and critical-infrastructure customers

• Utilities, transportation, mining, oil and gas, manufacturing, and private security operators.
• Buyer archetype: enterprise security directors, facilities managers, and operational-technology managers.

No individual customer name is repeated from filings as a named top customer in this note. If a specific named customer is required for a thesis, it should be sourced from an 8-K contract announcement, revenue-concentration footnote, or other primary filing — not assumed.

The sovereign secure-communications toll: LMR (land mobile radio) + public-safety comms + body cameras + command-center software. Mission-critical links where failure means loss of command and control — the moat is program-of-record + regulatory embedding + installed base.

• Cost of moat vs moat it defends (M&A): $1.5B ÷ ~$185M D-Fend annual revenue = 8.1× revenue. $1.5B ÷ $11.682B FY25 revenue = 12.8% of annual revenue (material but not thesis-defining); $1.5B ÷ $2.988B FY25 operating income = 50% of one year's op income. Revealed-preference intensity: D-Fend raised only ~$67M pre-sale → $1.5B exit ≈ 22× invested capital — the buyer (MSI) is underwriting that RF cyber-takeover C-UAS is a defensible moat worth defending MSI's 13,000+ network / 200M-emergencies-per-year installed base.
• Backlog coverage: $15.6B record backlog ÷ $12.975B FY26 revenue guidance = 1.20× annual revenue. Software & Services added $1.2B to backlog in Q2 alone (recurring mix shift).
• Margin bridge (disconfirming nuance): non-GAAP op margin 32.9% (+330bps YoY) — but ~190bps was a one-time $60M IEEPA tariff refund (~$0.25 of the $0.56 EPS beat). Organic op-margin expansion ≈ +140bps, not +330bps. GM 53.6% (+250bps) is clean organic.
• Switching cost (revealed-preference): a statewide P25 network is a $50-200M build with a 10-15 yr lifecycle on 700/800 MHz licensed spectrum; switching means re-spectrum + re-certify (APCO P25) + replace all subscriber radios + retrain — 5-10 years, not the 18-month bypass-test window.

a statewide P25 network is a $50–200M, 10–15 year licensed-spectrum build. Switching requires re-spectrum + APCO P25 recertification + subscriber-radio replacement + retraining — outside the 18-month bypass window. The $2.6B buyback does not change that constraint; it is a use-of-cash statement that the Board believes the FCF from that installed base is durable enough to shrink the float by ~3–4% over ~2 years and absorb a $1.5B C-UAS bolt-on.

All Tier 1 figures above are from SEC filings. The exact accession numbers are marked needs primary source validation; the filing-index URLs are listed in Sources.