News / Mobile
Mobile industry forecasts for 2008 focused on thinner margins
A January 2008 outlook argued that mature mobile markets faced pressure on average revenue per user and would seek more value from data services.
What the report described
Analysts expected enterprise data packages, outsourcing and network sharing to receive more attention as operators tried to reduce costs. The article also placed roaming regulation and the limits of voice growth among the pressures on the business model.
How to read the claim
These are forecasts and assessments made at the start of 2008, not a present market forecast.
Margin pressure changes the operating model
The forecast is clearer when margin pressure is treated as a design constraint. Voice use could not be assumed to lift revenue alone, so an operator had to decide which activities deserved its capital and which could be shared or outsourced. Enterprise data packages offered a different relationship: they connected a business customer to devices, support and usage rather than a single voice price. The article points to a search for a more resilient revenue mix, not simply a search for more subscribers.
Sharing and outsourcing solve different problems
Network sharing can spread the burden of infrastructure that competing operators each need. Outsourcing can move a function to a specialist supplier. Neither automatically improves service; each changes who controls daily decisions, fault handling and the pace of changes. In the 2008 forecast, these were answers to price competition and roaming regulation that could narrow the room left to recover investment. The choice was not only what to cut, but which capabilities the operator still needed to direct.
A business-package decision
A small company considering mobile data for staff had to look beyond included minutes. Would the bundle make routine work more predictable without creating a price structure it could not understand? For the operator, that bundle made sense only if support, capacity and the offer itself could be supplied below the value created. This two-sided calculation explains why the forecast tied data services to operational efficiency: the service had to be useful to the business while also improving the economics of serving it.
That makes the forecast a question about service architecture: retain control where it affects customers, and change the cost base where duplicated infrastructure contributes little distinction.