Consider a machinery manufacturer: the product is delivered to the factory floor, the invoice is issued, and the relationship largely ends there. A maintenance contract means a site visit once or twice a year; a breakdown triggers an emergency call. Revenue is one-time, and the customer relationship is reactive. Now imagine that machine generating continuous data, the manufacturer reading that data, and instead of selling the machine, selling its operating hours or the output it produces. This question sits at the heart of what the Internet of Things — IoT — means for business models.
IoT is a technical infrastructure that enables physical products to generate real-time data through sensors and network connectivity. In Turkey, the concept is still on the margins of industrial conversation; as broadband infrastructure strengthens and corporate network investments grow, the first pilot applications are beginning to appear in industrial settings. But the fundamental question is not technical — it is strategic: how does a company convert one-time product revenue into a recurring income stream tied to usage or performance? Answering that question requires rebuilding the core logic of the business model.
In the traditional model, value is realized at the moment the product changes hands. In the new model, value accumulates with every hour the product operates. This is referred to in the literature as ‘product as a service’ or ‘outcome-based selling.’ Rolls-Royce selling flight hours rather than jet engines is the most frequently cited example. For a Turkish SME manufacturing industrial compressors, medical imaging equipment, or agricultural machinery, a similar transition is theoretically possible — but it requires technical, financial, and organizational preconditions to align simultaneously.
From a business model perspective, three concrete benefits stand out. First, revenue predictability: monthly or usage-based billing replaces one-time sales, stabilizing cash flow and simplifying budget planning. Second, a deeper customer relationship: as long as the product is in the field generating data, the manufacturer can monitor the customer’s operations closely and offer value-adding recommendations. Third, a competitive barrier: a rival product may offer a price advantage, but replicating the operational data and established relationship of an incumbent system takes time. When customers run a total cost of ownership (TCO) analysis, switching costs become a meaningful deterrent.
The practical challenges stand directly opposite these opportunities. First, the infrastructure cost of a connected product is high: sensor hardware, data transmission networks, and the software layer all require significant upfront investment. For most Turkish SMEs, the return on investment (ROI) timeline remains uncertain, partly because usage-based pricing models are not yet mature on the customer side either. Buyers are accustomed to purchasing a product outright; leasing or paying per use creates conceptual resistance. Beyond that, service contracts need new legal frameworks and billing processes — and most existing ERP and accounting systems are not built to manage recurring revenue streams or usage-based invoicing.
From an enterprise software standpoint, this transition directly affects the scope of ERP systems. An ERP built around product sales focuses on inventory, order management, and invoicing. A company moving to a service model needs to add new dimensions: contract management, usage metering, automated billing, and customer-level profitability analysis. Solutions addressing these needs exist in the market, but at SME scale in Turkey, fully implementing these capabilities typically requires customization and consulting investment. Standard modules in off-the-shelf packages often fall short when managing hybrid business models where product sales and service contracts coexist.
For a manager evaluating this transition, the critical question is straightforward: can usage intensity in the existing customer base be measured, and is that usage predictable enough to support a recurring revenue stream? If the product’s usage pattern is consistent and customers are open to the model, the shift makes sense. Starting with a pilot outside the current ERP infrastructure — using a separate contract and billing system — is a practical way to contain risk before committing to a full platform overhaul. Turning a product into a service is a strategic decision; the technical choices come after.
This article was originally written in Turkish by Gökhan MERCANOĞLU on June 6, 2011 and has been automatically translated into English and other languages using machine translation.