Motorola Solutions 2026 Capex and AI Strategy for Assist Suites Hyper

What Motorola Solutions said about allocating AI-driven solutions and Capex for Assist Suites Hyper in 2026

1) Allocation of Assist Suites Hyper inside the Assist/AI “stack” (not as a standalone add-on)

Motorola Solutions’ 2026 Q1 commentary frames Assist as the connectivity and “fabric” that links core public safety applications (911, CAD, consoles) through AI, rather than treating it as a peripheral product. Management specifically described Assist as addressing “connectivity via AI among those 3” applications and emphasized that Assist is “encompassed in the dispatcher suite,” with adoption tied to call handling offerings. ¹

In particular, Motorola stated that every VESTA NXT sales last quarter went with the Assist dispatcher suite (indicating commercial allocation of Assist capabilities within the dispatcher/command center workflow). ¹²

2) Where Hyper fits: expanding Assist into non-emergency call automation and integrating with 911

Motorola introduced Hyper at the Public Safety User Summit and described it as extending the Assist ecosystem into non-emergency call automation, while also being “tightly integrated with our 911 solutions.” ¹ Separately, management described Hyper as “injects agentic AI into our 911 call handling.” ³

So, in terms of solution allocation across the portfolio, the positioning is:

• Assist: AI connectivity across the core 911/CAD/consoles workflow (dispatcher suite; embedded in role-based suites). ¹⁴⁵
• Hyper: the next layer for automated handling of calls beyond purely emergency workflows (non-emergency call automation), integrated with 911 operations and call handling. ¹³

3) Evidence of demand-driven prioritization (which informs where resources are likely concentrated)

While the excerpts don’t provide a quantified, line-item budget specifically labeled “Hyper Capex,” they do show resource emphasis via product momentum and adoption metrics:

• Motorola reported an “800% increase in the number of completed reports” generated with Assist since December (for Command Center Records Management, with Assist attached). ⁶
• Management also described strong early product market fit for Assist Suites, including 100% of 911 VESTA NXT call handling solutions associated with the Assist dispatcher suite. ²
• Motorola stated that it built and launched AI assist capabilities across Command Center workflows (missions and records management), emphasizing “latest AI assist capabilities” within Command Center launches. ⁴

This matters for your question because it indicates that Motorola is channeling commercial and engineering attention toward Assist/Hyper capabilities that are producing measurable customer adoption and deployments—consistent with how management typically allocates effort even when exact Capex line items aren’t disclosed for each product.

4) Capex allocation for 2026: the only explicit framework given is portfolio-wide Capex, not Hyper-specific

The earnings transcript provides a high-level capital allocation framework rather than a product-by-product Capex plan for 2026:

• Motorola stated its operating cash flow expectation of “approximately $3 billion.” ⁷
• It then described allocation proportions as: 60% for share repurchases, 30% for dividends, and 10% for CapEx. ⁷

Critically, the excerpts do not break out Capex between Assist vs. Hyper (or between AI-driven solutions inside Assist Suites vs. other technology areas). Instead, the Capex “investment” discussion is broad and includes categories such as command center, video, networks, device refresh, network resiliency, and Silvus/LMR infrastructure refresh—without isolating Hyper. ⁷

So, the best-supported answer from the filings/excerpts is:

• Hyper and Assist are being prioritized as part of the AI-enabled Command Center/911 ecosystem, but
• 2026 Capex is allocated on an overall corporate basis (10% of the disclosed cash-flow allocation framework), not disclosed as a specific Hyper Capex amount. ⁷

5) What Motorola says it is funding (scope of investments that likely includes Assist/Hyper)

Motorola highlighted investments across the product portfolio and infrastructure areas, including:

• command center and hybrid/cloud solutions (where Assist capabilities operate), ⁷⁴
• network resiliency and infrastructure refresh, and
• “Silvus” and other mission-critical platform investments. ⁷

Since Hyper is described as “tightly integrated with our 911 solutions” and as agentic AI into 911 call handling, it is reasonable (but not directly quantified in the excerpts) to interpret that Hyper development/deployment sits inside these broader investment categories rather than within a separately disclosed Capex bucket. ¹³⁷

---

Bottom line (answer to your question)

• Motorola Solutions plans to allocate AI/solution emphasis by integrating Assist and Hyper deeply into the 911-to-dispatch/command workflow: Assist is positioned as AI connectivity across 911/CAD/consoles (dispatcher suite; embedded in VESTA NXT), while Hyper extends into non-emergency call automation and is integrated with 911 call handling. ¹³²
• For Capex in 2026, the disclosed plan is portfolio-wide rather than Hyper-specific: Motorola’s only explicit capital-allocation framework is that Capex is 10% of the company’s stated operating cash flow allocation framework (against a roughly $3B operating cash flow expectation), but the excerpts do not provide a specific Hyper Capex number or separate Capex allocation for Assist Suites Hyper. ⁷

Because the excerpts do not disclose a product-specific 2026 Hyper/Assist Capex line, the analysis above is limited to what is explicitly stated: solution prioritization is clearly described; Capex budgeting for Hyper specifically is not quantified in the provided material. ¹³⁷