AI Is Revealing the Limits of Today’s SaaS Stack

Miloš Radić — Wed, 29 Apr 2026 20:12:55 +0000

Most teams in the professional services space already use AI every day. In contained situations, it works very well for them. It can quickly summarize a document, improve a draft, or analyze a clean set of inputs. But when the task at hand requires a bit more context, and the information is spread across disconnected tools, AI just won’t return satisfactory results.
The professional services platform Productive recently surveyed 256 professionals across agency and professional services roles to understand how teams are using AI today. They found that AI is used heavily for writing and summarizing, but much less for tasks that require a broader perspective, such as planning or coordination. This aligns with a familiar AI constraint: the technology only works as well as the data it can access. And when work is split across multiple systems, AI has a harder time getting the information it needs to be genuinely useful.

AI Works Well in Controlled Tasks, Not Across Workflows

AI tends to perform best when the task is clearly defined and the inputs are easy to follow. That is why it has quickly become a reliable tool for writing, summarizing, and basic analysis. The boundaries are clear, the context is contained, and the output is easy to check.
Trouble begins once the work moves beyond a single task. Real workflows are not contained in one place. They span multiple tools, evolve over time, and depend on a mix of data, decisions, and human input. In those conditions, AI is no longer working from a complete picture but piecing together fragments.
Productive’s research data on how teams actually use AI supports this. heavy use in content and summarization, but far less in planning or coordination. It’s not because these are less valuable or less popular tasks; on the contrary. They are simply harder for AI to operate in because they rely on context that spans systems rather than residing in one place.
This creates a clear ceiling for what AI can do for teams. AI can speed up parts of the work, but it cannot easily connect them. A summary might be accurate, but it does not reflect what changed in the project plan. A draft might sound right, but it does not account for the latest client decision. The more the work depends on these moving pieces, the more AI lags behind the actual state of the workflow.

Today’s SaaS Stack Splits Work Across Systems

The way most companies manage work today did not emerge by accident. Over time, SaaS tools were built to solve specific problems: one system for sales, another for project delivery, another for time tracking, another for finance, and a handful more for communication and collaboration. Each tool does its job well, but each one only sees part of the work.
A typical setup makes this clear. Deals live in a CRM, delivery happens in a project tool, hours are tracked elsewhere, financial data sits in accounting software, and key decisions are scattered across chat threads and calendars. Taken individually, these systems are effective. Together, they do not form a complete view of what is actually happening.
That fragmentation is not a failure of any single tool. It is a consequence of how SaaS evolved: products optimized for specific functions, connected through integrations, but not designed to operate as one continuous system. The result is a working environment where information is constantly moving, but rarely fully connected. For people, that means constant context switching and reconstruction; for AI, it means operating with incomplete information.
This is where the friction becomes visible. Teams spend time rechecking outputs, cross-referencing tools, and manually filling in missing pieces. What looks like a small gap at the system level becomes repeated microtasks in day-to-day work. AI does not remove that effort. In many cases, it even amplifies it.

The Direction SaaS Is Starting to Move In

There are early signs of a different pattern emerging. Instead of adding more tools or layering AI on top of existing ones, some platforms are starting to rethink how work data is structured in the first place. The focus is moving from isolated functionality toward a more connected context, where projects, financials, communication, and operations begin to live closer together.
This shift is becoming more relevant as building software gets easier. With AI and rapid development tools lowering the barrier to launching new apps, features are faster to replicate than ever. New tools can be built, copied, and iterated on quickly. What is harder to replicate is the underlying context: how well a system brings together the data that reflects how work actually happens.
Some platforms are already moving in this direction. Productive is one example, built from the start to bring project, financial, and operational data into one place, and now introducing AI capabilities such as AI agents and AI Notetaker to operate within that context.
When there’s a single work context, AI stops being limited to isolated tasks. It can follow how work moves, pick up on changes, and act on information that reflects the full state of a project, not just a single input.

DEV Community: Miloš Radić

AI Is Revealing the Limits of Today’s SaaS Stack

AI Works Well in Controlled Tasks, Not Across Workflows

Today’s SaaS Stack Splits Work Across Systems

The Direction SaaS Is Starting to Move In