August 2026
When businesses negotiate connectivity contracts, the conversation often starts with price. What does the data cost? What is the rate per megabyte? Can we negotiate a better deal if we commit to more volume?
These are reasonable questions, but they don’t tell you the whole story.
A competitive rate starts looking very different when it comes with a 36-month contract, a significant minimum monthly spend, and a technical environment that becomes increasingly difficult to change once everything is up and running.
This is particularly relevant for businesses using APN services and reverse billing at scale. The numbers are bigger, the infrastructure is more important, and the consequences of getting the commercial model wrong can follow you around for years.
So perhaps there is a better question to start with: who really controls the connectivity behind your business?
The rate is only part of the cost
Most of us are already familiar with paying for connectivity capacity we never use.
Think about your home fibre connection. You may have a 50 Mbps or 100 Mbps service, but how often does your household consume everything available to it? Two people can browse, work from home, and watch Netflix without coming close to using the full capacity.
The difference between what is purchased and what is actually consumed is known in telecommunications as breakage. At home, it probably doesn’t matter much. Take the same principle into a large business environment, and things become more interesting.
A company negotiating an APN agreement for hundreds or thousands of connected devices may be offered an attractive cents-per-megabyte rate. Perhaps it comes in at 9c/MB, and procurement walks away feeling like it has done a good job.
Look under the hood, though, and there may be a substantial monthly minimum spend attached to that price, together with a long-term commitment. The cold, hard truth is that the headline rate may have very little to do with what the service ultimately costs your business.
You aren’t only buying data. You’re committing to a commercial structure and carrying the risk if true usage doesn’t behave the way everyone expected it to.
When redundancy creates another problem
Businesses understandably want resilient connectivity, particularly where mobile data supports important services, devices or employees.
One way of spreading that risk is to work across multiple mobile networks. On paper, this makes perfect sense. If one network has a problem, you have alternatives. The difficulty starts when every network comes with its own agreement, APN integration, technical team, and change-control process.
Something as simple as an IP address change can suddenly mean opening three tickets with three engineering teams, then trying to get everyone aligned to implement the same update. Anyone who has managed multiple large providers knows how quickly a “simple change” can stop being simple.
This becomes a hidden tax on the business. Your technical team spends time managing suppliers and processes instead of doing the work you employ them to do. More suppliers can give you resilience, but more contracts and operational touchpoints don’t automatically reduce risk. If the environment hasn’t been designed properly, you may simply introduce a different kind of risk.
What sits behind your reverse-billing provider?
Reverse billing introduces another layer that businesses should understand. The concept itself is straightforward: a reverse-billing service allows someone to use your website, app, or digital platform without paying for the mobile data required to access it. Your organisation carries the data cost instead.
For businesses that need customers, employees or communities to access important digital services, this can be incredibly useful. Backspace provides this through its Zero-byte reverse-billing platform.
Where things become less straightforward is the commercial structure behind the service.
You might ask three companies to quote and receive three proposals carrying three different brands. It is natural to assume you are comparing three completely independent options. That isn’t always the case.
When you look under the hood, there can be another provider or aggregator sitting behind the business you are dealing with. Sometimes there may be several commercial layers before you reach the mobile network that’s carrying your traffic.
There is nothing inherently wrong with using an upstream provider. The problem comes when you don’t know that dependency exists.
If that upstream provider changes its pricing, alters its strategy or experiences a service problem, the impact can flow straight through to your organisation. Yet you may have no relationship with that business and very little influence over what happens next. You signed with the company you know. Someone else may still control an important part of the service you depend on.
For businesses relying on connectivity to deliver services to customers, staff or partners, that is worth understanding before the contract is signed.
A simpler way to manage APN connectivity
Aggregation can solve many of these problems when the model has been built with simplicity in mind.
At Backspace, our approach is to remove as much unnecessary complexity as possible.
Our APN environment provides access across South Africa’s four major mobile network operators through a single management platform. Instead of forcing customers into minimum billing commitments to unlock a particular rate, the current model is usage-based, with no minimum bill and no minimum contract term required to secure the rate.
It means a business can get the network diversity it needs without recreating the same commercial and technical relationship several times over. One environment. One relationship. One place to manage the service.
That sounds obvious, but in telecommunications the obvious solution is often buried beneath years of legacy processes and commercial structures. There’s enough complexity out there already.
Commercial agility matters when things change
No business knows exactly what its connectivity requirement will look like three years from now.
You may be moving thousands of devices onto a new platform. You may be launching a service where customer adoption is difficult to predict. Usage could grow far faster than expected, or a project could move in an entirely different direction after six months.
This is where rigid contracts become painful. If your connectivity model relies on high minimum spends and long-term volume assumptions, your business carries much of the risk when those assumptions change.
A usage-based model gives you room to move.
That doesn’t mean businesses should avoid contracts or commitments altogether. It means the commercial structure should make sense for what has effectively become a business utility.
Connectivity needs to grow with you without every increase in usage triggering another round of contracts, negotiations, and risk. That is what commercial agility should look like.
Your infrastructure should support the direction of your business rather than anchor it to decisions made years earlier.
One less layer can make a big difference
In a fragmented APN environment, your people may be managing several suppliers, several contracts, separate technical integrations, and different change processes.
Someone must manage all of that.
Finance needs visibility over costs. Procurement manages the contracts. Technical teams manage integrations and support tickets. Management wants to know why a change is taking so long when, from the outside, it looks relatively straightforward.
Reducing those relationships into one environment removes a great deal of friction.
This becomes especially valuable when something goes wrong. You don’t want your team spending the first few hours of an incident trying to establish who owns the problem.
Seven questions to ask before signing your next agreement
Businesses reviewing an APN or reverse-billing provider would do well to look beyond the rate card and ask a few simple questions.
- Who owns the network commercials behind my service? You should know who your provider relies on to deliver what it is selling to you.
- How many contractual layers sit between my business and the mobile networks? Understand whether you are dealing directly with the organisation that controls the important commercial relationships.
- What happens if an upstream agreement changes or fails? If someone else’s commercial decision could affect your service, you need to know about it.
- How easy are the commercial terms to understand? Look at minimum spends, bundles and contractual terms, not only the cents-per-megabyte figure on the front page.
- How easily can the service scale? Growth shouldn’t automatically mean another major contractual commitment.
- How complicated is it to make a technical change? Ask how many tickets, providers, and engineering teams need to become involved when something needs updating.
- How easy is it to leave if the relationship no longer works? A provider should want to keep your business because the service works, not because a contract makes it difficult for you to go elsewhere.
Good service should create stickiness
There will always be contracts in business, and there will always be commercial commitments. That isn’t the problem.
The problem is when complexity and lock-in become the reason a customer stays.
We think the real contract should be the service itself. Customers should stay because their connectivity works, because someone answers when there’s a problem, and because changes can be made without disappearing into months of corporate process. They should stay because the commercial model still makes sense as the business grows.
With something as fundamental as connectivity, clarity, control, and aligned incentives should be the rule, not the exception.
If you are reviewing your APN or reverse-billing environment, look beyond the rate card. Understand who owns the relationships behind the service, what you are committing to, and what happens when your business needs to change.
If the answers are difficult to get, that probably tells you something too.
Contact the Backspace team about your APN or reverse-billing requirements.
