Software in the AI Era: From SaaS to Open Source
- Kannan Palaniswamy

- Jan 17
- 3 min read

For almost two decades, Software-as-a-Service stood at the center of enterprise innovation. It reshaped how organizations approached their core processes—whether in prospecting, sales, contracting, billing, cash collection, customer support, expense management, or accounting. SaaS applications brought modern interfaces, greater accessibility, and faster implementation cycles compared to their on‑premise predecessors. They also introduced shared master data models that became widely adopted across industries, creating a level of standardization that would have been hard to achieve through traditional enterprise software.
Despite this, the early promise of SaaS began to unravel as real-world complexity caught up with the rigid simplicity these platforms were designed around. National legislation in areas like taxation, invoicing, and data privacy repeatedly disrupted the idea of a single global process. Vendors had to introduce country-specific exceptions, and over time, these multiplied. What started as clean, elegant systems became patchworks of regional logic layered on top of globally shared structures.
The pressure intensified when large enterprises—whose requirements rarely fit into standardized templates—became major customers. To win these high-value deals, SaaS companies were forced to allow extensive customizations. The more they adapted their once-rigid systems, the further they moved from the “one version for everyone” vision. Different clients ended up running different configurations, on different versions, often shaped by regulatory limitations that prevented new features from being implemented consistently. As the variations grew, the cost and complexity of maintaining the platforms increased.
Integration created another challenge. As SaaS vendors expanded horizontally, they began competing for ownership of the same business processes. Sales platforms and billing platforms overlapped; customer support platforms fought for the same master customer record; expense tools and HR suites clashed over workflows. This created duplicated features and fractured user journeys. At the same time, niche SaaS products emerged to solve hyper-specific micro-processes. Companies began purchasing dozens of small tools to handle tiny slices of a process. While this created flexibility, it also resulted in greater administrative burden, more application sprawl, and heavier user management workloads—especially in organizations with high employee turnover.
Commercially, SaaS gradually drifted toward a rent-seeking model. Although the subscription model promised pay‑as‑you‑go flexibility, many SaaS companies priced their products much like traditional software licenses, often charging by seats regardless of actual usage (I hope microsoft is listening :)). Scaling down was difficult, and in some cases, increasing consumption led to disproportionately higher costs. When major software giants started acquiring SaaS firms at high valuations, they did so assuming that existing contracts or rather growth would continue indefinitely. To justify these acquisition costs, they frequently raised prices year after year. Larger enterprises had the resources to switch platforms when prices became unreasonable, but small and mid‑sized businesses often found themselves trapped.
The evolution of product updates also reflected deeper structural issues. Capabilities that customers once considered essential—such as real-time APIs, richer integrations, or advanced analytics—were moved behind additional paywalls. Vendors often found it easier to build entirely new product lines than to modernize older versions that were heavily customized. As a result, many SaaS platforms now exist in multiple generations, each tied to different technological eras and regulatory circumstances. Upgrading older versions became so difficult that some organizations preferred rebuilding their system from scratch rather than navigating a complex migration.
SaaS is not failing, but it is showing clear signs of slowing under its own weight. The model that once promised simplicity, lower costs, and rapid innovation now struggles to uphold those principles in the face of its accumulated complexity. While artificial intelligence is often positioned as the next major disruptor in software, I believe the real threat is the ease with which these applications can be replaced.
The more significant challenger, emerging quietly yet steadily, is open source (aided by AI power of course). Open source does not require customers to accept rigid data models, opaque pricing, or vendor lock‑in. It enables organizations to adapt software to their needs without being penalized for customizations. It allows transparent improvements, community-driven innovation, and genuine pay‑for‑value economics. With flexible deployment, self-hosting options, and growing professional support ecosystems, open source presents a level of freedom and sustainability that SaaS increasingly struggles to match.
SaaS changed how the world uses software, and its contributions remain enormous. But as the model matures and its limitations become more visible, open source—aided rather than lead by AI—appears positioned as the more transformative and principled alternative for the next era of digital systems.
