Vijay Raina is a seasoned strategist in the enterprise SaaS landscape, renowned for his deep understanding of software design and his ability to see past the hype of emerging technologies. With years of experience helping companies navigate the shift from legacy systems to cloud-native architectures, he has become a leading voice on how software must evolve to remain indispensable to the modern enterprise. In this conversation, we explore the fundamental shift occurring in the industry—a transition from a feature-heavy “access” model to a lean, outcome-oriented framework where AI acts as the connective tissue between user intent and business results.
SaaS valuations are under pressure even as vendors ship more features and AI tools. Why does adding functionality often fail to drive growth today, and what specific metrics should teams track to ensure their AI layers actually translate into measurable customer success?
For the better part of two decades, the SaaS industry operated under the assumption that more functionality naturally equated to more value, but we are seeing that logic crumble in real-time. The reason adding features fails today is that we’ve reached a point of feature saturation where every new button or module actually increases the cognitive load on the user rather than solving their problems faster. AI is exposing the reality that customers were never truly buying our features; they were buying the outcomes those features supposedly facilitated. Instead of tracking traditional vanity metrics like logins or seat utilization, teams must pivot to tracking “time-to-outcome” and the success rate of specific automated workflows. If your AI layer isn’t tangibly shrinking the gap between a user’s initial intent and the final deliverable, it is just adding more noise to an already cluttered interface.
A significant gap often exists between a user activating a product and achieving sustained business value. How does automation bridge this gap by connecting fragmented features, and what steps can companies take to move from being a navigation-heavy tool to an execution-focused platform?
That gap between activation and value is where most SaaS companies lose their “stickiness” because it usually requires a human to do the heavy lifting of connecting disparate features. Historically, vendors expected users to be power users who knew exactly which menu to click to get a result, but automation changes that by acting as the glue between these fragmented parts. To move from navigation to execution, companies need to stop building “toolkits” and start building “solutions” that handle the hand-offs between different modules automatically. This involves mapping out the recurring workflows that already exist within your most successful customer segments and then hardening those into repeatable, one-click processes. When the product stops being a map the user has to navigate and starts being the vehicle that drives them to their destination, the perceived value of the software skyrockets.
Traditional seat-based and feature-tier pricing models are beginning to break down as automation replaces manual effort. When transitioning to outcome-based pricing, how should vendors define their new unit of value, and how can they manage the risk of revenue fluctuations during this shift?
The breakdown of seat-based pricing is an uncomfortable but necessary evolution because when an AI agent can do the work of ten people, charging by the “head” becomes a race to the bottom. Defining a new unit of value requires a deep dive into what the customer actually gains—whether that’s a processed invoice, a generated lead, or a resolved support ticket—and making that the “metered” event. Managing the risk of revenue fluctuations during this transition is the hardest part, and it often requires a hybrid approach where a base subscription provides access, while the premium is captured through the volume of outcomes delivered. By aligning your revenue directly with the customer’s success, you create a more resilient partnership, though it requires a high degree of transparency in how you measure and report that impact. It’s a shift from being a utility provider to becoming a strategic partner that shares in the efficiency gains of the client.
Expanding a product’s capabilities often adds complexity faster than it creates value in an AI-shaped market. What are the practical trade-offs of collapsing a broad feature set into specific, executable workflows, and how can vendors maintain differentiation when common tasks become commoditized by prompts?
The major trade-off when you collapse features into workflows is that you might alienate the “power users” who enjoyed the granular control of a complex system, but this is a risk you must take to survive. In an AI-shaped market, differentiation no longer comes from having a unique button or a slightly better UI; it comes from the proprietary data and the specific context your software brings to a prompt. If a task can be done by a generic LLM, it is already a commodity, so your job as a vendor is to wrap that task in a workflow that is uniquely tailored to your vertical’s specific needs. You win by being the one who understands the nuance of the industry better than a general-purpose AI, ensuring that your executable workflows are not just fast, but highly accurate and context-aware. Clarity and specificity are the new moats in an era where volume and breadth have become cheap.
Most organizations are currently layering AI on top of existing workflows rather than completely replacing their software stacks. In this environment, how does a vendor prove their software is still worth a premium, and what strategies help turn under-utilized modules into high-impact, repeatable processes?
Proving your worth in a “layered” environment means you have to be the most reliable and integrated part of the customer’s existing ecosystem, rather than an isolated silo. To justify a premium price, you must demonstrate that your software is the “intelligence layer” that makes all their other tools work better, rather than just being another line item in their budget. You can turn under-utilized modules into high-impact processes by using AI to analyze how users are struggling and then proactively offering to automate those specific, neglected tasks. For example, if you have a reporting module that no one uses because it’s too complex, use AI to transform it into an automated weekly insight delivered directly to the user’s inbox. When you take the burden of “learning the software” off the table, those dormant features suddenly become the most valuable parts of the platform.
What is your forecast for the future of SaaS?
I believe we are entering an era of “Invisible SaaS” where the most successful platforms will be those that require the least amount of direct human interaction to produce the highest quality outcomes. The software of the future won’t be a place where people spend eight hours a day clicking around; instead, it will be an autonomous engine that runs in the background, only surfacing to provide critical insights or ask for a final approval. We will see a massive consolidation where the “feature-rich” but “outcome-poor” vendors are replaced by lean, highly specialized agents that charge for the value they create rather than the access they provide. Ultimately, the market will reward clarity over volume, and the winners will be the ones who realized that their job wasn’t to build more software, but to solve more problems with less friction.
