Digi’s recurring revenue needs an acquisition and cash-flow test

Digi reported on November 11, 2026 that September-end annualized recurring revenue was $197 million. Fourth-quarter operating cash flow reached $42 million, with its increase chiefly affected by tax factors. Results

Those figures begin an inquiry rather than settle it. Is this industrial-connectivity business building a durable capacity to charge for service without needing another acquisition? Our analytical approach separates scale, its source and cash returns. A change in revenue mix becomes more persuasive when those elements reinforce one another.

A run-rate is not a promise

Digi defines ARR by annualizing the month-end value of billable subscription contracts. SEC filing It is a point-in-time measure, not revenue already recognized over a year. A closing snapshot cannot establish when customers joined, whether they will renew or how service costs will evolve.

Consider a hypothetical factory paying for remote monitoring. Installing hardware starts the relationship; continued payment depends on reliable alerts, maintenance and useful responses to exceptions. This is an explanatory example, not a verified Digi customer case. Connectivity alone does not establish willingness to purchase every additional service. Conversely, continued service need not require replacing equipment each year.

Counting connected devices is therefore insufficient, as is counting contracts labelled subscriptions. Can a customer explain the benefit when renewal arrives? Does additional billing entail substantial deployment, support or processing costs? Can services on the installed base persist when new equipment purchasing slows? These questions reveal more than relabelling a hardware company as a software company.

Customer dependence also differs from supplier pricing power. Embedding a system in daily work may raise replacement costs, but customers can still demand discounts, clearer service commitments or data portability. Staying does not imply accepting any price. Renewal analysis should therefore consider bargaining alternatives as well as contract duration. Winning renewal through useful performance and retaining a contract because migration is difficult can produce similar short-term numbers but different long-term resilience. The evidence here does not establish which applies to Digi; that gap should remain explicit rather than disappear behind the word “sticky.”

Acquired scale has a capital cost

On January 27, 2026, Digi announced its roughly $50 million cash acquisition of Particle, then reporting approximately $20 million in ARR. Announcement Subscription growth consequently needs an acquisition lens, rather than an assumption that all expansion reflects existing customers spending more.

Acquisition is not inherently inferior to internal development. A working product, developer relationships and deployed systems may fill gaps faster than building from scratch. Combined distribution may create new opportunities. But opportunity and realization occupy different levels of evidence. Adding acquired contracts changes the business perimeter; keeping those customers and expanding useful service after integration is the subsequent operating test.

The investment denominator matters too. An attractive standalone business can produce disappointing buyer returns if purchase price, integration spending or financing costs are too high. Assessing growth quality does not require opposing acquisitions. It requires making the cost of obtaining growth visible alongside its scale.

Dividing purchase price by ARR cannot by itself establish whether a transaction is cheap. ARR is not profit, does not deduct every future service cost and does not guarantee permanent contracts. Without retention, service-margin and capital-requirement evidence, a concise multiple conceals rather than resolves uncertainty.

Sensors need a commercial bridge to services

On October 1, 2026, Digi announced a proposed $130 million cash purchase of Disruptive Technologies, whose disclosed 2025 revenue and ARR were $15 million and $4 million. Deal announcement A proposed transaction is not a completed one; expected benefits are not realized earnings.

Sensing capability becomes a service relationship only through customer decisions. Easier deployment may help, but enterprises must still determine who maintains the equipment, how information enters existing workflows and whether staff actually spend less time handling problems. Solving those issues could support a lasting relationship. Merely adding another screen to inspect might not.

An installed device base therefore cannot automatically be counted as future subscription customers. Purchasing agreements, budgeting cycles and operating habits can all affect conversion. Two interpretations deserve room: hardware access may support service expansion, while integration complexity may postpone returns. Announcements do not replace subsequent operating evidence.

Cash requires a causal explanation

Cash arriving and cash recurring at the same rate are different propositions. Tax-payment timing can improve available funds without independently demonstrating stronger customer demand. The resulting financial flexibility is real; mechanically annualizing one quarter may nevertheless overstate sustainable generation.

Differences between earnings and operating cash flow are not automatically warning signs either. Collections, supplier payments and prepayments move cash between periods. A better assessment spans several periods, asks whether operating profit and cash converge, and includes acquisition spending, debt service and maintenance investment. A single metric can indicate a direction, not complete the argument.

The useful follow-up is whether acquired customer relationships survive integration, whether continuing service delivers practical value and whether cash returns cover the capital needed to obtain and maintain those capabilities. Repeatable operational improvement would strengthen an optimistic interpretation. Retention pressure, rising costs or delayed integration would support caution. Defining those tests is more useful than prematurely declaring either a successful software transformation or untrustworthy acquisition-led growth. This is business analysis, not investment advice.