Agentability Audit

n8n and the Agentability Gap: What 100 SaaS Products Reveal About AI Agent Readiness

A systematic audit of the top 100 SaaS products shows an average agentability score of just 38.3 out of 100, with workflow automation platform n8n among those measured. Two critical weaknesses—transparency and shadow-UI avoidance—are holding nearly the entire industry back.

The promise of AI agents operating software autonomously depends on a prerequisite that few product teams have considered: their applications must be built to support agent interaction in the first place. A recent systematic audit of 100 leading SaaS products, including workflow automation platform n8n, reveals an industry-wide readiness gap that threatens to delay the agent era by years.

The audit measured what we call agentability—the degree to which software can be reliably operated by AI agents—across eight Agent Factors Engineering (AFE) principles. Each product received a score from 0 to 100, and the results were sobering.

The average agentability score across all 100 products was just 38.3 out of 100, placing the typical SaaS product squarely in the "Developing" tier.

The distribution tells a more nuanced story. Only 22 products achieved "Agent-Ready" status with scores of 45 or above. The majority—54 products—fell into the "Developing" tier (35-44 points). Another 17 were classified as "Lagging" (20-34 points), and 7 products scored so poorly they earned the "Agent-Blind" designation with scores under 20.

n8n, a workflow automation platform designed to connect applications and automate processes, was among the products evaluated. Its detailed agentability profile breaks down performance across all eight AFE principles, offering a representative case study of where modern SaaS stands on agent readiness.

Two Critical Weaknesses Across the Industry

While the overall scores reveal a struggling industry, the principle-by-principle breakdown exposes two catastrophic failure points that affect nearly every product audited.

83 of the 100 products scored zero on transparency, averaging just 5 points across the entire dataset.

Transparency, in the AFE framework, measures whether a product exposes its state, capabilities, and constraints in machine-readable formats that agents can query and understand. This includes publishing API schemas, capability catalogs, rate limit information, and semantic descriptions of what operations are possible. Without this information layer, agents must resort to trial-and-error approaches or rely on outdated training data—neither of which produces reliable automation.

The near-universal failure on transparency suggests that product teams have not yet internalized a fundamental shift: in an agent-mediated world, your interface is not just your GUI or even your API documentation. It's the machine-readable metadata that allows an agent to reason about what your product can do before attempting to use it.

The second critical weakness is shadow-UI avoidance, where 80 of 100 products scored under 20, with an average of just 17 points across the dataset. Shadow-UI refers to interface patterns that are invisible or unreliable from an agent's perspective: hover-triggered menus, dynamically loaded content without proper state indicators, tooltip-dependent controls, and actions that require precise timing or cursor positioning.

These patterns emerged from a decade of designing for human users with mice and eyes. They create elegant, space-efficient interfaces. But for agents parsing DOM structures or making API calls, they represent unpredictable failure points that can break automation without warning.

The Eight AFE Principles and Their Scores

The audit evaluated products across eight distinct principles, each scored from 0 to 100:

  • Machine readability (71 average): The extent to which interface elements, content, and state can be parsed and understood by automated systems. This was the highest-scoring principle, suggesting many products have at least basic semantic HTML or API structure.
  • Transparency (5 average): Availability of machine-readable capability descriptions, constraints, and state information.
  • Shadow-UI avoidance (17 average): Elimination of interface patterns that are invisible or unreliable to agents.
  • Defaults (35 average): Smart default values and behaviors that reduce the decision burden on agents.
  • Control (48 average): Granular, programmable control over product behavior and configuration.
  • Chunking (45 average): Breaking complex operations into discrete, resumable steps that agents can execute incrementally.
  • Status (47 average): Clear, queryable status information about ongoing operations and system state.
  • Clean handoffs (40 average): Well-defined points where agent control can transition to human oversight or other agents.

The relatively strong performance on machine readability (71) reveals that the foundation exists. Most modern products use structured data formats and have some API layer. But the dramatic drop-off in transparency and shadow-UI avoidance shows that teams have not yet taken the next step: designing explicitly for agent interaction.

What This Means for Product Teams

The agentability gap is not primarily a technical problem—it's a design and product strategy problem. The products in this audit already have APIs, structured data, and modern architectures. What they lack is intentional design for agent interaction patterns.

Product teams should start by addressing the two universal weak points. For transparency, this means publishing machine-readable capability catalogs. Start simple: a JSON schema describing your API surface area, including rate limits, authentication requirements, and semantic descriptions of endpoints. Tools like OpenAPI specifications are a starting point, but true transparency requires going further to describe business-level capabilities and constraints.

Practical Steps Forward

To improve shadow-UI avoidance scores, audit your interface for patterns that depend on hover states, complex timing, or visual-only cues. Ensure that every action available through your GUI is also available through a programmatic interface with predictable behavior. Where dynamic content is necessary, emit clear state change signals that agents can observe.

The products that scored in the Agent-Ready tier (45+) share common characteristics: they expose state programmatically, minimize hidden interface dependencies, and provide clear documentation of both capabilities and constraints. These are not massive engineering lifts—they are deliberate design decisions.

Teams can assess their own products using run a free audit against the AFE framework. The rubric is open and reproducible. For a broader view of how different product categories perform, the Agentability Index provides comparative context across the 100 audited products.

The agent era will not wait for products to catch up. The 22 products already in the Agent-Ready tier are establishing a competitive advantage in a world where AI agents increasingly mediate software interaction. The 78 that are not yet ready have a clear roadmap in the AFE principles—and a narrowing window to act on it.

How agent-ready is your product?

Run a free agentability audit and get a scored, prioritized fix list in minutes.

Run a free audit