From installed software to SaaS: what Salesforce really changed
The phrase “No Software” was one of Salesforce's best-known early messages. It works as a provocation, but it can obscure the most interesting part of the case: software did not disappear. What changed was the operating contract between supplier and customer.
The complete analysis of this transformation, along with positioning, community, and Agentforce, is in the main Salesforce analysis.
Before SaaS, buying software meant taking on more infrastructure
In the traditional enterprise software model, an organization had to deal with installation, servers, updates, compatibility, implementation projects, and local maintenance at multiple levels.
The supplier delivered the application, but a significant share of the operation remained with the customer and its technology partners.
That model was not necessarily bad. It reflected the technical possibilities, control requirements, and market structure of the period. The problem emerged when the internet, connectivity, and software architecture made another form of distribution possible.
Salesforce turned access into a continuous service
By delivering CRM through the browser and charging by subscription, Salesforce changed several components at once.
The customer began accessing an application operated by the supplier. Updates could be distributed centrally. The infrastructure required to maintain the service became more concentrated on the platform. The commercial relationship became recurring.
These changes altered the buyer experience and the supplier's economics. Recurring revenue, retention, and expansion within an account became increasingly important.
SaaS is a relationship model, not just hosting
Reducing SaaS to “software in the cloud” misses part of the transformation. The model connects product and operations over time.
When the supplier continuously updates the application, it needs to pay closer attention to usage, support, adoption, and renewal. The initial sale remains important, but economic value depends on the customer staying.
This logic influences the company's own organization. Customer success, usage metrics, account expansion, and continuous product evolution take on a larger role.
A new category changes what customers consider normal
As SaaS matured, behaviors that once seemed novel became expected. Remote access, recurring updates, and subscription purchasing became common reference points across different categories.
When that happens, disruption stops being an exclusive advantage. It becomes basic market infrastructure.
This process appears in other cases of digital transformation. The analysis of Canva and disruption in Brazil shows how changes in access and experience can expand a category to audiences that previously depended on more specialized processes.
Technical change needs a comprehensible narrative
Multi-tenant architecture, provisioning, and centralized operations are important concepts, but they do not create attention on their own. Salesforce translated a technical transformation into a simple contrast between the old model and a lighter alternative.
This movement also appears in Red Bull's strategy, in a different context: the company connects the product to a field of meaning larger than its basic function.
In Salesforce's case, the narrative organized an operational change. Its strength came from the combination of symbol and experience.
SaaS also created new dependencies
Every simplification shifts responsibilities. Less local infrastructure can mean greater dependence on the supplier, connectivity, integrations, and platform policies.
Companies need to assess availability, security, data portability, governance, and accumulated cost. The model reduces some types of complexity and creates others.
For that reason, the evolution of SaaS should not be told as a linear passage from a bad model to a good one. It is a reorganization of responsibilities and incentives.
What this teaches companies trying to change a category
A meaningful transformation usually changes more than one layer.
How the product is accessed.
How operational responsibilities are distributed.
The billing model.
The speed of updates.
The relationship between supplier and customer.
When only the vocabulary changes, the category tends to remain the same. When several of these layers are reorganized, the market may need new language to understand what is happening.
From the cloud to agents
Salesforce is trying to repeat part of this logic with artificial intelligence. The current thesis is that agents can transform software from a tool used by people into a layer capable of executing work more autonomously.
The analysis of four mistakes in the use of artificial intelligence helps distinguish real capability from superficial use. The same discipline is required to evaluate enterprise agents: value needs to show up in operations, not just in the label.
Continue exploring EuAlan
See also Canva and disruption, Red Bull Marketing Strategy and How to use AI without making your text generic.
Comments