SPLA has been the default licensing program for hosters for a long time, and defaults are sticky. But for a growing number of providers, the program that once fit the business has quietly become a poor match for it. The reasons are rarely a single headline price difference. They accumulate: the reporting overhead, the standing audit exposure, the way the economics have shifted as customer estates move toward subscription models, and the operational cost of getting monthly reporting exactly right across every cycle. This article lays out the commercial case for leaving SPLA so a hoster can assess it on the merits rather than by inertia.
This is a strategic question, not an audit defense one, but the two are connected. For the defensive context, read the SPLA audit defense guide. Here we weigh the case to leave.
The hidden cost of staying
The visible cost of SPLA is the monthly fee for what you consume. The hidden costs are larger and easy to ignore until an audit makes them concrete. SPLA is pay as you consume, verified for every monthly reporting cycle across a 36 month lookback by a Big Four firm under the MBSA audit clause. That structure means three standing costs run in the background whether or not you are currently being audited.
- The operational overhead of accurate monthly reporting: SAL counts, customer mapping, version mapping, and sealed authentication data, every cycle without exception
- The standing audit exposure, where any reporting weakness across three years can surface as back fees plus a penalty uplift of 25 to 125 percent
- The margin quietly lost to over reporting, where a conservative or mistaken count has been paying for more than was delivered
SPLA does not bill you for the overhead and the exposure. It just makes you carry them, month after month, until something forces a reckoning.
What changed in the economics
The market that SPLA was built for has shifted. Customer demand has moved toward subscription and cloud consumption models, and the products customers want are increasingly the ones available through CSP rather than through traditional hosted delivery. For a provider whose estate has drifted in that direction, continuing to run everything through SPLA can mean carrying the heaviest compliance model for workloads that would sit more naturally elsewhere. The economics are no longer just about the per unit rate, they are about whether the licensing model matches the way the business now delivers value.
What CSP offers and what it does not
CSP is a different model with a different shape of obligation. For many subscription oriented workloads it aligns the licensing with how customers actually buy, and it removes some of the monthly reporting burden that SPLA imposes. It is not a universal answer. Some workloads remain better suited to SPLA, and a move to CSP brings its own commercial commitments and operational changes. The honest commercial case is rarely all or nothing. For most providers it is a question of which parts of the estate belong in which program, and what the blended position looks like once the transition costs are accounted for.
| Dimension | SPLA | CSP |
|---|---|---|
| Billing model | Monthly pay as you consume | Subscription aligned to customer |
| Reporting burden | Heavy, monthly, audited on lookback | Lighter for subscription workloads |
| Audit exposure | 36 month lookback, Big Four | Different and generally narrower |
| Best fit | Some hosted and dense workloads | Subscription and cloud aligned demand |
The audit dimension of the decision
There is a specific reason the leaving decision intersects with audit defense. A move away from SPLA does not erase the 36 month lookback on the period you were in the program. If you exit while reporting weaknesses exist in the trailing window, those weaknesses can still surface in a later verification. The commercial case for leaving therefore has to account for cleaning up the SPLA position on the way out, not just the destination economics. A migration planned without that step can trade a known overhead for an unaddressed exposure.
How to frame the decision
The right way to assess the case is to model the full picture rather than the headline price. That means the per unit economics in each program, the operational cost of reporting under SPLA, the standing audit exposure you carry while in it, the transition cost of moving, and the cost of cleaning up the trailing SPLA position. When all of those sit in one model, the decision usually becomes clear, and for some providers it points firmly toward leaving while for others it points toward staying and tightening discipline. Either way, the decision is made on evidence rather than inertia.
Where this leaves you
SPLA is not wrong for every hoster, but it is no longer right for every hoster either, and the cost of assuming it still fits can be high. Weigh the hidden overhead and exposure alongside the headline economics, account for the trailing lookback, and model the blended position across both programs before deciding. The case for leaving is real for some providers and worth taking seriously for all of them.
If you want the full method for assessing your SPLA position, modeling the alternatives, and exiting without leaving audit exposure behind, download our SPLA audit defense guide and work through it against your own estate.
Before you send anything back to the auditor, our SPLA to CSP migration service moves you across without opening new exposure.