Telecom operators want to sell transformation, not only connectivity

GSMA reports that 79% of surveyed African mobile operators identify becoming a digital-transformation partner as a primary enterprise objective. The phrase signals a move beyond connectivity toward cloud, security, identity, payments, data and managed services.

An objective is not a revenue line. The operator has to connect a product to a business process, integrate it, support it and accept responsibility when it fails.

The contract exposes the strategy.

Connectivity remains the base contract

Enterprise buyers need coverage, capacity, latency, resilience and service levels. A transformation pitch cannot compensate for an unstable circuit. The operator should expose performance and repair before adding layers.

Business connectivity can include mobile, fibre, fixed wireless, satellite and managed local networks. The right mix depends on sites and workload. Bundling should not hide which provider owns each component.

Service credits are a limited remedy, not the value of lost operations. Buyers should design continuity around consequence. Operators should price the resilience they can verify.

Account management needs access to network operations. A sales representative without incident evidence becomes another message relay.

Product replaces custom project

A managed service needs a defined scope, onboarding, price, service level and support process. If every customer requires unique engineering and contract exceptions, the offer behaves like consulting and can be difficult to scale.

Standardisation does not mean one configuration. It means repeatable modules and controlled variation. Network APIs offer one example: common interfaces can make number verification or device signals available to many developers.

Operators should count time from signed order to usable service. Long internal handoffs consume customer trust and sales capacity. Publish dependencies such as permits, customer data or third-party hardware.

Product margin includes presales engineering, implementation, licences, cloud, support and incident work. Connectivity revenue alone cannot subsidise unlimited customisation invisibly.

Enterprise sales needs industry knowledge

A bank, mine, retailer and public agency buy different outcomes and carry different regulation. The sales team needs enough process knowledge to identify the constraint without pretending to replace the customer's specialist.

Use-case claims should have measured baselines. “Improve efficiency” becomes transaction time, downtime, loss or staff hours under a defined workflow. The customer and operator should agree who measures.

Procurement cycles can exceed consumer product timelines. Security review, data protection, integration and budget approval need evidence early. A pilot that bypasses them can succeed technically and fail to contract.

Reference customers help only when scope and conditions are comparable. Protect confidentiality while sharing architecture and realised results.

Integration creates shared failure

A managed solution can join network, cloud, devices, software and customer systems. Each component has updates, credentials and logs. The customer experiences one service.

Name an incident owner and common identifier. Contracts among suppliers should support the response promised to the customer. An operator cannot guarantee repair it has no right to demand upstream.

Data flows require a map. Identify controller and processor roles under applicable law, locations, retention and subprocessors. Network access does not grant permission to reuse enterprise data.

Change management needs notice and rollback. An operator update that breaks a customer's integration can create operational loss even if the network remains available.

Support becomes part of the product

Enterprise buyers may operate continuously across regions. Support hours, languages, channels and escalation need to match. A premium label without response and restoration definitions is not a service level.

First-line agents need runbooks and access to product status. Escalation should preserve context. Customers should not repeat security-sensitive information to several teams.

Problem management follows restoration. Repeated incidents require root cause and prevention. Report known errors and planned fixes without exposing network security.

Capacity and support staffing should grow with contracts. Revenue booked before operational readiness can degrade every customer.

Partnership changes commercial risk

A connectivity provider bills for access. An outcome-oriented partner may tie price to transactions, savings or availability. That can align incentives and expose the operator to variables it does not control.

Define the measurement source and baseline. A revenue-share product needs audit rights and treatment of refunds. A savings-share arrangement needs agreement on what would have happened without the service.

Long contracts can support investment and lock customers into obsolete technology. Include benchmarking, change and exit. Customers need data and configuration portability.

Credit risk matters when operators finance devices or infrastructure for customers. Separate service margin from lending economics.

Test the 79% objective through operating evidence

Operators can report enterprise product revenue, recurring share, time to activate, service performance, renewal and support cost. A growing pipeline or partnership announcement is earlier evidence.

Cohort reporting prevents mature connectivity contracts from masking weak new products. For each launch period, show customers activated, implementation time, recurring gross margin, incidents and renewals. Preserve cancelled pilots and delayed projects in the denominator. A transformation offer that closes many demonstrations and few durable contracts needs product work before another campaign.

Buyers can assess whether the operator has reference architecture, accountable product management, integration capability, security evidence, support and an exit process. A large network footprint solves one part.

Regulators should distinguish competition in connectivity from adjacent digital services. Bundling can lower transaction cost and can disadvantage independent providers. Market evidence should guide remedies.

The ambition reflects a real change in where value may sit as connectivity matures. Transformation reaches the income statement after the customer's process works under ordinary conditions.

Sources

• GSMA, 16 June 2026: The Mobile Economy Africa 2026