The Product Desk

The Subsidy Is Ending, Not the Feature

A staff engineer ran Claude through Cline for three months and watched her team's per-developer cost stay roughly flat. Starting June 15, that line item moves. Anthropic announced that Claude usage through third-party tools (Conductor, Zed, OpenClaw, T3 Code, Cline) gets a separate credit pool equal to the plan's dollar value, and once that pool is burned, the meter switches to API rates. The 50% rate limit increase for two months is a grace period. For teams whose workflows were quietly running on 70-90% implicit discounts through harness-mediated access, the per-developer cost just rose by roughly an order of magnitude.

The timing reads like finance, not product. Anthropic hired a CFO and is likely aiming at an October 2026 IPO. Power-user subsidies do not produce the revenue-per-user a public market wants to see. Expect at least one more pricing adjustment before the S-1 narrative settles.

ServiceNow Is the Canary

ServiceNow's CDIO Kellie Romack watched her team's full-year Anthropic budget get consumed before mid-2026. She cannot say which users or which workloads drove it, because the telemetry to answer that question does not ship in the box. PagerDuty and National Life Group describe the same gap. National Life Group's Nimesh Mehta puts it directly: Anthropic is "great for consumer usage but not great for companies."

The signal is not that AI is expensive. The signal is that AI costs are structurally unpredictable and the model providers have not built the instrumentation customers need to govern them.

Two product categories are being pulled into existence by that gap. One is AI cost governance, which is what ServiceNow built internally as an AI Control Tower and now sells. The other is the multi-model abstraction layer, which stops being an engineering convenience and starts being strategic infrastructure the moment a provider can raise prices without SLAs or usage transparency.

OpenAI's Displacement Play Has a 30-Day Clock

Sam Altman offered 2 months of free Codex to enterprise customers who switch within 30 days, timed to Anthropic's moment of developer frustration. The Ramp data showing Anthropic at 34.4% against OpenAI's 32.3% explains the hurry: OpenAI lost the business adoption lead for the first time and wants it back inside a quarter. That is a forcing function with an expiration date.

The 2x2 for This Sprint

Duolingo's 20% Validates the Quality Constraint

Duolingo's CEO acknowledged publicly that mandating AI usage across all roles produced performative adoption without productivity gains and roughly 20% unusable output. They reversed the policy. The lesson for teams setting AI adoption goals is to measure cycle time and output quality, not tool logins, and to plan human-in-the-loop capacity against a 20% rework assumption until your own data says otherwise.

Three Platforms, One Week, Same Architecture

SAP, ServiceNow, and Salesforce all shipped autonomous agent architectures this week and landed in the same place at the execution layer: headless workflows callable over MCP. SAP added a €100M partner fund and a Knowledge Graph for agent context. ServiceNow's Action Fabric pulled workflow logic out from behind the UI and exposed it for any third-party agent to call. Vendors do not stand up hundred-million-euro funds for features. They stand them up for platform bets they plan to defend for years.

A Fortune 500 procurement lead opened three enterprise demos this week and asked the same question in each: 'Can our agents call this directly, or do my people have to click through your UI?' Two vendors didn't have an answer. The third did. Guess which one moved to the next stage.

The Distribution Change Is Already in RFPs

Here is what buyers are actually doing: writing RFPs that assume every connected tool exposes an agent-callable surface. Tools that don't are quietly dropped from the shortlist. That signal shows up in renewal conversations a quarter before it shows up in win rates, which is why most teams will see it late. Legacy bot detection has an 81% AI agent bypass rate, so the security assumption about who is calling the API is stale at the same time the procurement assumption is.

The build is smaller than the strategy talk suggests. For most teams: a week of scoping, 2-4 weeks of build, assuming the underlying API is not a mess. The harder decision is the second one. Restructuring the core UI around the assumption that an agent is the first-touch user is a roadmap question, not a sprint question, and it is the one product decks keep skipping.

Apple's Agent App Store Adds the Consumer Dimension

Apple is building AI agent governance into the App Store, with a likely reveal at WWDC June 2026. They are solving three problems at once: an approval process for agents, the 'agent spawns unauthorized sub-apps' bypass, and making sure agents cannot route around App Store fees. If the agent roadmap involves dynamic UI generation or open-ended tool use on iOS, architect for constraints now. Retrofitting after review guidance lands is the expensive path.

The Forcing Function

Pull the last 20 support tickets and feature requests from top-decile accounts. Count how many assume a human in the seat versus an agent doing the work. If the ratio moved even 10 points toward agents in the last two quarters, the headless layer is a retention bet on the next renewal cycle, not a platform bet on a future board meeting. Read the tickets before picking the sprint.

One Person Shipped What Used to Take a Team

Elena Verna — former head of growth at Amplitude, Miro, and Dropbox — opened a Linear ticket, wrote the copy, designed the layout, and pushed Lovable's enterprise pricing page to production alone. No PM scoping the requirements. No designer on mocks. No engineer on build. In a conventional org that work needs all three plus about a week of calendar time to keep them aligned. Verna now spends 90% of her time building and almost none of it in meetings.

Lovable has zero product managers. Engineers talk to users, write the specs, ship the code, and read the feedback themselves. The company is growing fast enough that this is not an oversight. It is the operating model. They are hiring Growth PMs parallel to Verna rather than under her, which is not a growth team in the org-chart sense. It is a roster of autonomous operators.

The Unbundling Framework

Decompose the PM role into four jobs: user research, prioritization, spec-writing, and cross-functional coordination. Lovable's bet is that the first three collapse into the engineer once the engineer is the one talking to users, and the fourth evaporates when the org stays small. At their current headcount the bet pays out. Where it breaks is the question nobody at Lovable has had to answer yet.

AI does not make a PM world-class at design or engineering. It makes them average-to-good at everything at once. For a PM who already thinks across functions, that is an opening — but only if the time goes into shipping rather than coordinating other people shipping.

The Diagnostic for Monday

The Risk Is Real and Asymmetric

Senior builders who can get autonomy and impact density at a Lovable-style flat org will leave to get it. Companies that ungate information access will pull disproportionate talent. The ones that protect management layers end up staffed with coordinators and no builders. Some leaders hear the HI-C pitch and answer "Absolutely not. I need another VP title", which is fine. The model appeals to a specific archetype, not universally.

The survival test for PMs is narrow. Of the work shipped last quarter, how much of the PM contribution was judgment about what to build versus coordination of people building it? If the coordination half goes to zero tomorrow, does the judgment half justify the role on its own? If yes, the job gets better. If no, the job gets done by someone like Verna.