Pitches to would-be cloud partners usually begin with a number. A market size with a great many zeros. A revenue line that could be yours. A projection that curves steeply upwards in year three.
This article does not have one. Nobody can honestly tell you what your cloud business will earn; that depends on your market, your customers, your prices and how well you run it. What can be described precisely is how a cloud business worth owning is put together, and why most partners are never offered the chance to own one.
Reseller or owner
For most MSPs, telecom operators, data centre operators, system integrators and technology entrepreneurs, the cloud industry has offered one role: resell a global provider’s services. It is fast, it needs no platform, and it is called a partnership.
Look at what the partner actually holds. The provider sets the catalogue, the list prices and the roadmap. The provider owns the console the customer logs into. The partner holds the relationship and a margin someone else decided, which can change at the next renewal.
Underneath sits an assumption: that owning a cloud needs engineering teams, capital and years of development only a handful of companies can afford. So partners are offered the same trade as everyone else. You can have a cloud that works, or a cloud that is yours.
A reseller holds the relationship. An owner holds the business.
Where the value sits
It is tempting to assume the valuable part of a cloud business is the infrastructure. The racks are the most visible part, and the most expensive. But infrastructure is increasingly a comparison exercise, and comparison exercises are won on price.
What makes a cloud business valuable is structural: revenue that renews, customers who buy more than one thing, services you sell without building them, reach beyond what you run, and prices you control. A business with those properties compounds. A business without them has to be won again every quarter. There are five to get right.
1. Revenue that renews
Project work ends. A migration is delivered, an invoice is paid, and the next project has to be sold. Cloud services are consumed every month for as long as the workload runs, which changes what a sale is worth and what a customer relationship is worth.
It also changes how the business grows. A managed service business adds revenue by adding engineers. A platform adds revenue through automation, so growth no longer has to track headcount.
2. A catalogue, not a product
A partner selling one service gives the customer one reason to stay. A partner selling compute, Kubernetes, managed databases, backup and recovery, security and GPU capacity gives many. Each additional service is a new line on the same invoice, sold to a customer who already trusts you, with no new acquisition cost. The catalogue is how an owner grows the value of each customer rather than merely counting customers.
3. A marketplace for what you do not build
No partner builds everything, and none should try. A marketplace lets you sell software and services made by others, from security vendors and ISVs to other service providers, through your own storefront, under your own brand, on your own invoice. The customer gets one place to buy. You earn on services you did not have to build or run.
4. Federation for what you cannot run
The weakness of any local cloud is breadth. One operator can only run so much, and customers measure every catalogue against the largest in the world.
Federation changes that without changing who owns what. Independently owned clouds publish and consume services by explicit agreement. You can offer a service another cloud runs, somewhere else, while your customers, your data and your operations stay with you, and customer data never moves automatically. The reach is borrowed. The business is not.
5. Margins you set
The last property is the one most often given away. If the platform under your business takes a percentage of everything you sell, then every price you raise and every customer you win is shared with someone who carried none of the risk.
That is why the commercial model matters as much as the technology. With Oasis Stack, the platform is a flat fee per deployment, banded by scale, and federation is a flat participation fee. What you charge your customers is yours to decide and yours to keep. The platform does not take a share of your growth.
Who is positioned to do this
The organisations best placed to build a cloud business already hold something a global provider cannot easily copy. MSPs hold day-to-day relationships and operational trust. Data centre operators hold the facilities and the customers inside them. Telecom operators hold connectivity, national reach and enterprise accounts. System integrators know their customers’ estates better than anyone. Entrepreneurs, for the first time, can start without a multi-year platform programme in front of them.
What none of them should have to do is build a cloud platform first. That is the part Oasis Stack provides: a platform that runs above infrastructure you already own, launches in 90 days, and can be operated by you or by CloudHost. The business on top of it is yours.
The question to ask instead
So when a cloud partnership arrives with a revenue projection attached, set the number aside and ask a different question: whose business is it? Who owns the customer? Who sets the price? Who decides what goes in the catalogue? Who keeps the margin when you succeed?
If the answer is someone else, the size of the number matters less than it seems. If the answer is you, the structure will do more for you than any projection could.