Your Next User Might Not Be Human: A PM's Framework for Agent-Ready Products
Software is quietly picking up a second audience — AI agents acting on a human's behalf. Here's a framework for auditing whether your product actually works for both.
For twenty years, "who is the user" had one answer: a person, looking at a screen, making a decision. That assumption is starting to crack.
Across product-led SaaS this year, a growing share of usage isn't a human clicking through your UI — it's an agent, acting on a human's behalf, calling your API, reading your docs, filling in your forms. The PM discipline that grew up entirely around human attention, human comprehension, and human trust now has a second audience it wasn't designed for. Most roadmaps haven't caught up.
The shift is already showing up in the data
This isn't a thought experiment. Three signals converged this week that are worth naming plainly:
- Teams building agent-native tooling are shipping in public right now — background agents that record how you work and turn it into automation, inboxes wired directly into durable agent workflows, sandboxed VMs built specifically so an agent can safely act unsupervised. These aren't demos; they're shipped products with real usage.
- Analysts tracking product-led growth are now describing a "headless" trajectory for software — where the agent, not the human, is the one actually operating the tool, and the human's role shifts from operator to approver.
- On the hiring side, "API PM" and "AI platform PM" are now showing up as distinct functional specializations, separate from the generalist PM role — which only happens when a company has decided a product surface needs dedicated ownership.
None of this means humans are disappearing from your product. It means most products now have to satisfy two different readers of the same information, often on the same screen, and most product decisions are still being made as if there's only one.
Why this breaks quietly, not loudly
The dangerous part of this shift is that it doesn't show up as an outage. It shows up as a slow erosion of trust in your product's own outputs.
A feature built entirely for human judgment optimizes for things agents don't parse well: ambiguous copy that reads fine to a person but has no single correct interpretation, state that lives only in visual layout rather than in the underlying data, confirmations that assume a human will notice if something looks wrong. An agent acting against that same surface doesn't pause to sanity-check the way a person does — it does exactly what the interface told it to do, at whatever speed it's capable of, and it does it whether or not the interface was actually clear.
Keep reading
Most "AI Features" Shouldn't Be AI Features. Here's the Test That Tells You.
Most "AI features" shipped in 2026 are rules engines wearing an AI costume. Here's the four-question test to run before you spec one — and what it looks like when a feature fails all four.
The Product Velocity Illusion: Why Shipping Faster Hasn't Made Your Roadmap Better
AI collapsed the time it takes to build a feature, but not the time it takes to decide what to build or validate that it worked. The Three Clocks framework shows product teams where their real bottleneck moved — and how to stop mistaking build speed for progress.
Can AI replace product managers? What the 2026 data actually says
94% of PMs use AI daily — but only ~6% for strategy, and 43% of startups still fail on product-market fit. Why AI replaces the busywork, not the judgment.