Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Even modern, API-first tools like Brex and QuickBooks don't expose all necessary data programmatically. Daytona's CEO had to give an agent a virtual machine with read-only logins to scrape web UIs and export data to build a complete board deck, proving GUI automation remains critical.

Related Insights

When building AI-driven workflows, the primary interface becomes the API, not the GUI. A tool's value is determined by its programmatic control. Consequently, a clunky UI with a strong API like Salesforce can be superior for AI integration than a tool with a slick UI but a weak API.

The next generation of software may lack traditional user interfaces. Instead, they will be 'API-first' or 'agent-first,' integrating directly into existing workflows like Slack or email. Software will increasingly 'visit the user' rather than requiring the user to visit a dashboard.

AI agents often default to "build it yourself" because SaaS products aren't designed for them. To stay relevant, SaaS companies must create agent-friendly CLIs, APIs, and even add hints in help text to guide agents through complex workflows.

When a key software tool like Gong lacked a direct data feed, a workaround was created by identifying URL patterns. A scraping tool was used to grab a unique Call ID, which was then appended to a base URL to access and scrape the full transcript, unblocking a complex automation workflow.

Counterintuitively, the path to full automation isn't just analyzing conversation transcripts. Cresta's CEO found that you must first observe and instrument what human agents are doing on their desktops—navigating legacy systems and UIs—to truly understand and automate the complete workflow.

The usefulness of AI agents is severely hampered because most web services lack robust, accessible APIs. This forces agents to rely on unstable methods like web scraping, which are easily blocked, limiting their reliability and potential integration into complex workflows.

While headless APIs are ideal, many websites and apps actively block headless browsers to prevent scraping. This forces AI agents to interact with the standard graphical user interface to complete tasks, just as a human would, rather than relying on APIs.

As companies integrate AI agents into their workflows, unrestricted API access to their own data is non-negotiable. SaaS providers that paywall or limit API access will be abandoned for more open platforms that don't hold customer data "ransom."

In a world where AI agents perform tasks, the value of a SaaS product is no longer its user-friendly interface but the robustness of its APIs. The core differentiator becomes the proprietary business logic, security, and data governance embedded within the API layer.

Contrary to being overhyped, AI agent browsers are actually underrated for a small but growing set of complex tasks like data scraping, research consolidation, and form automation. For these use cases, their value is immense and time-saving.