Product daily

Synthesized by Clarity (Claude) from 36 sources · May contain errors — spot one? mail@promitb.dev · Methodology →

Anthropic Ends 90% Harness Discount June 15, OpenAI Bids

Sources
36
Words
1,724
Read
9min

Topics Agentic AI LLM Inference AI Capital

◆ The signal

Anthropic kills the 70-90% implicit discount for third-party harness users on June 15 — if your team uses Claude through Cursor, Cline, or OpenCode, your per-developer cost assumption is wrong by roughly an order of magnitude starting in 30 days. OpenAI is counter-offering 2 months free Codex to enterprise switchers within a 30-day window. Model your actual exposure this week, not next month, because both offers expire before most planning cycles complete.

◆ INTELLIGENCE MAP

Intelligence map

  1. 01

    Anthropic's June 15 Pricing Restructure Forces Vendor Decision

    act now

    Anthropic is collapsing arbitrage: third-party tool usage gets separate credit pools equal to plan value, then API rates. OpenAI immediately offered 2 months free Codex for switchers. Anthropic leads business adoption at 34.4% vs OpenAI's 32.3% per Ramp — this is an IPO-preparation margin play, not a product feature.

    70-90%
    implicit discount eliminated
    8
    sources
    • Anthropic biz share
    • OpenAI biz share
    • Pricing change date
    • OpenAI switch offer
    1. Anthropic34.4%+4x YoY
    2. OpenAI32.3%+0.3%
  2. 02

    AI Cost Governance Crisis: ServiceNow Blows Full-Year Budget by May

    act now

    ServiceNow burned its entire annual Anthropic budget before mid-2026 with no per-user telemetry to explain why. 'Tokenmaxxing' — employees over-consuming AI tools — is emerging as a real cost management problem. Anthropic lacks enterprise-standard SLAs, usage monitoring, and per-feature attribution that buyers need.

    5 months
    to burn 12-month budget
    4
    sources
    • Budget consumed by
    • Anthropic rev growth
    • Activation w/o FDEs
    • AI spend switchable
    1. Budget consumed in 5 of 12 months100
  3. 03

    Enterprise Agent Infrastructure: SAP, ServiceNow, and Salesforce Ship Headless Workflows

    monitor

    SAP committed €100M to an Autonomous Enterprise partner fund. ServiceNow's Action Fabric decouples workflow logic from UI for third-party agents via MCP. Vercel production data confirms 59% of all token volume is now agentic. Enterprise buyers are asking 'can our agents call this directly?' — products without agent-callable APIs are being dropped from shortlists.

    59%
    token volume is agentic
    5
    sources
    • SAP partner fund
    • Agentic token share
    • RFP window
    • Bot detection bypass
    1. Agentic workloads59
    2. Traditional AI41
  4. 04

    PM Role Compression: Single-Operator Shipping Validated at Scale

    background

    Elena Verna shipped Lovable's enterprise pricing page alone — work that traditionally required PM + designer + engineer + a week. Lovable has zero PMs; the company hires autonomous operators who spend 90% of time building with almost no meetings. The coordination half of the PM role is collapsing; the judgment half is the defensible skill.

    90%
    time spent building
    2
    sources
    • Verna build time
    • Meeting time
    • Traditional PM split
    • Lovable PM count
    1. HI-C: Building90%
    2. Traditional PM: Building20%
  5. 05

    AI Cyber Capability Crosses Full Network Takeover Threshold

    monitor

    Anthropic's Mythos is the first model to clear both UK AISI simulated attack ranges — jumping from 'advanced persistence' to 'full network takeover' in one generation. PraisonAI auth bypass was weaponized in 4 hours post-disclosure. Vulnerability management SLAs written for human-speed attackers are now structurally inadequate.

    4 hours
    disclosure to exploit
    5
    sources
    • Mythos AISI clearance
    • PraisonAI exploit time
    • Identity fraud TAM
    • Palo Alto vulns found
    1. Previous gen50persistence only
    2. Current gen100full takeover

◆ DEEP DIVES

Deep dives

  1. 01

    June 15: Anthropic's Pricing Bomb and the 30-Day Vendor Decision Window

    act now

    The Arbitrage Is Closing

    A developer opened her Cursor billing page this week and saw the same number she has seen for months. Next month she will see a number roughly ten times larger. Anthropic announced that every Claude subscription now includes API credits equal to the plan's dollar amount — the $200 plan gets $200 in credits. The pitch is generosity. What it actually does, for the large cohort using Claude through third-party harnesses like Cursor, Cline, OpenCode, and Aider at effective 70-90% discounts to direct API pricing, is end the implicit subsidy. Starting June 15, third-party tool usage gets a separate credit pool. Once that pool is burned, the meter runs at full API rates.

    The timing is not a coincidence. Anthropic hired a CFO and is targeting an October 2026 IPO. Power users absorbing enormous implicit discounts do not produce the revenue-per-user numbers public investors want to see on the S-1. Plan for at least one more pricing adjustment before that filing.

    OpenAI's Displacement Counter

    Sam Altman responded within hours with 2 months of free Codex for enterprise customers who switch within 30 days. This is displacement pricing aimed at the exact week developer frustration peaks. The Ramp data showing Anthropic at 34.4% versus OpenAI's 32.3% — the first time Anthropic has led in business adoption — explains why the counter shipped on the same news cycle.

    The interesting question is not whether Codex is as good as Claude for a given workflow. It's what the real switching cost looks like once the harness discount is gone on one side and two months of runway is on the table on the other.

    The Decision Framework

    Two axes this sprint. First: is the Claude usage load-bearing for a specific production workflow, or exploratory? Second: is the harness replaceable with Anthropic-native tooling at similar quality, or not?

    • Load-bearing and replaceable: renegotiate with Anthropic inside the 30-day window while the leverage is real.
    • Load-bearing and not replaceable: pilot Codex on the 2-month-free offer this week, not next month.
    • Exploratory in either cell: stop paying metered rates for exploration. Move to whichever vendor is currently subsidizing it.

    Sources Disagree on Duration

    One read frames this as IPO preparation, which implies pricing stabilizes after October 2026. Another reads the same facts and points out that Anthropic's ARR grew from $9B to $30B in roughly 4 months and customers are absorbing price increases without churning, which implies the pricing power outlasts any IPO calendar. The conservative plan models at least one more adjustment before October regardless.

    Action items

    • Model the cost impact of Anthropic's new $-for-$ API credit structure on all third-party Claude usage by May 23
    • Evaluate OpenAI's 2-month free Codex offer for your highest-volume Claude workflow this sprint
    • Add model abstraction layer to technical debt backlog with P1 priority

    Sources:AINews pricing analysis · ben's bites Vercel data · Techpresso B2B analysis · TLDR AI model market · The Pragmatic Engineer capacity crisis

  2. 02

    Your AI Feature P&L Has a Telemetry Gap — ServiceNow Proved It

    act now

    The Budget Blow Nobody Saw Coming

    Kellie Romack, ServiceNow's CDIO, opened her finance dashboard one morning and saw her team's full-year Anthropic budget get consumed before the middle of 2026. She cannot tell you which users drove it, or which workloads, because Anthropic does not ship the telemetry to answer those questions. PagerDuty and National Life Group describe the same problem. National Life's Nimesh Mehta called Anthropic 'great for consumer usage but not great for companies.'

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

    Tokenmaxxing: The Goodhart's Law Problem

    Here is what teams tell themselves users do: adopt AI tools, get more productive, generate value. Here is what users actually do when usage becomes a metric. Amazon mandated 80%+ weekly AI tool usage and staff are gaming leaderboards. Duolingo's CEO publicly acknowledged their blanket 'evaluate all employees on AI usage' policy failed. AI content at scale produces approximately 20% unusable output, and mandating usage produced performative adoption. They reversed the policy.

    The cost model is now the product risk. Token spend sat in a finance spreadsheet and got reviewed quarterly. That arrangement worked when AI features were pilots with capped traffic. It does not work when the feature is embedded in the workflow and usage scales with customer success.

    The Missing Infrastructure Layer

    ServiceNow built an AI Control Tower internally and staffed it with a dedicated person to watch Anthropic consumption. It now sells the tool to its own customers. That is the tell. Two product categories are being pulled into existence by this gap:

    1. AI cost governance: usage monitoring and cost attribution has moved from nice-to-have to procurement blocker
    2. Multi-model abstraction: strategic infrastructure the moment a provider can raise prices without SLAs or usage transparency

    The Stable Cell

    One forcing function resolves the sprint question. On one axis: is inference cost fixed per seat or variable per call. On the other: does the customer pay per seat or per outcome. The only stable cell is variable cost matched to variable pricing. Every other cell is a bet that usage will not grow, which is a strange bet to place on a feature the same deck tells the board is working.

    Action items

    • Audit whether you can break down LLM API costs per customer, per feature, per use case by end of this sprint
    • Implement per-endpoint spend caps and automated alerts before any new AI feature launch
    • Replace AI usage frequency metrics with outcome metrics (task completion, time saved, accuracy) in next executive review
    • Pressure-test AI feature pricing model: if your heaviest user 5x their consumption next quarter, does margin hold?

    Sources:Laura Bratton enterprise AI costs · The Pragmatic Engineer capacity · TLDR Dev tokenmaxxing · TLDR Marketing Duolingo mandate · TLDR AI cost curves

  3. 03

    SAP and ServiceNow Just Made 'Can Your Agents Call This?' a Procurement Question

    monitor

    SAP, ServiceNow, and Salesforce Converged on Headless Execution

    SAP shipped a Knowledge Graph for agent context alongside a €100M partner fund for Autonomous Enterprise. ServiceNow's Action Fabric decoupled workflow logic from UI and exposed it to any third-party agent over MCP. Salesforce added native WhatsApp voice to Agentforce Contact Center. The shipping notes look unrelated. The architecture underneath is identical: headless, API-first execution addressable through MCP servers.

    Vendors do not stand up hundred-million-euro partner funds for features. They stand them up for platform bets they intend to defend for years.

    The Procurement Question Has Already Changed

    A Fortune 500 procurement manager is now asking in demos: 'Can our agents call this directly, or do my people have to click through your UI?' Two vendors did not have an answer. The third did, and moved to the next stage. That is the question RFP language will calcify around inside two to three quarters.

    If your APIs are not agent-consumable, agents will route around you to a competitor whose APIs are. The window before this shows up in RFPs is two to three quarters.

    What 59% of Token Volume Actually Says

    Vercel's AI Gateway production data across 200,000+ teams shows 59% of all token volume is now agentic workloads. Anthropic captures 61% of AI spend, driven by Opus for heavy reasoning. Google captures 38% of token volume, driven by Flash for cheap, fast tasks. Most large teams route across multiple providers rather than committing to one. That is what buyers are doing, not what the vendor decks claim they will do.

    The Forcing Function for Product Teams

    The decision is narrower than 'build an agent strategy.' It is whether the workflows a product owns can be invoked by an agent that is not yours, without a human clicking through the UI, by Q4. If not, the agent living in the buyer's stack will route around the product to one whose surface is callable.

    Has stable API surfaceNo documented API
    Requires human approvalSurvives the shiftSprint work: API layer
    Fully automatableGets bypassed by agentsGets replaced entirely

    The honest scope is a week of design and two to four weeks of build for an MCP server against existing APIs — assuming the underlying API is not already a mess. That is the estimate from teams who have actually shipped it.

    Action items

    • Audit your product's API surface for agent-consumability: can a third-party AI agent discover, authenticate, and execute core workflows without UI?
    • Scope an MCP-compatible headless layer against your top 3 workflows by end of quarter
    • Evaluate SAP's €100M Autonomous Enterprise partner fund for strategic fit
    • Instrument what happens when an agent fulfills your top user intents without opening the app — track repeat-task depth, not session count

    Sources:TLDR IT SAP/ServiceNow · TLDR agentic volume · ben's bites Vercel data · Simplifying AI Gemini agents · a16z GTM thesis

  4. 04

    The PM Coordination Tax Is Collapsing — What Survives Is Judgment

    background

    Lovable Has Zero Product Managers

    Elena Verna — former head of growth at Amplitude, Miro, and Dropbox — took a pure IC seat at Lovable in December 2025. She now spends 90% of her time building, has almost no meetings, and personally shipped Lovable's enterprise pricing page to production. In a traditional org, that project needed a PM, a designer, engineers, and a week of calendar time. She did it in hours.

    Lovable is not a thought experiment. It is growing fast enough that the missing PM function is not an oversight. It is the operating model. Engineers talk to users, write specs, ship code, and read feedback directly.

    What's Actually Being Unbundled

    The PM role decomposes into four jobs: user research, prioritization, spec-writing, and cross-functional coordination. AI tools collapse the first three into a single high-context operator when that operator talks to users directly. The fourth disappears when the org is small enough or flat enough that coordination lives in a shared channel.

    AI doesn't 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 instead of coordinating other people shipping.

    The Diagnostic

    Two questions to carry into Monday:

    1. Of the work shipped last quarter, how much of the PM contribution was judgment about what to build versus coordination of people building it?
    2. If the coordination half went to zero tomorrow, does the judgment half justify the role?

    If the second answer is yes, the job gets better. If no, the job gets done by someone like Verna.

    The Structural Risk for Established Companies

    Senior builders who can get autonomy and impact density at a flat org will leave to get it. The companies that ungate information access, the blocker Verna names explicitly, will pull disproportionate talent. The ones that protect management layers end up with coordinators and no builders. Not every PM role disappears. The roles that survive look less like project managers and more like mini-GMs who happen to prototype and iterate directly.


    Caveat: this model works at Lovable's current size. It breaks at a different size, and nobody knows exactly where. Teams with regulatory requirements, complex multi-team dependencies, or enterprise sales motions still need coordination. The real question is whether that coordination is creating value or just filling a calendar.

    Action items

    • Calculate your personal build-vs-coordinate ratio this week — track hours spent creating vs. aligning
    • Ship one small project end-to-end using AI tools without engaging your cross-functional team within 2 weeks
    • Identify 1-2 senior ICs who might be more productive with full autonomy and fewer reports — propose a pilot
    • Rewrite your PM career positioning around judgment and strategy rather than coordination

    Sources:Lenny's Newsletter HI-C role · Lenny's Newsletter Lovable model

◆ QUICK HITS

Quick hits

  • Update: Anthropic capacity — Colossus 1 lease (220K GPUs from xAI) confirmed; committed to doubling Claude Code's 5-hour limits and removing peak-hour throttling within 2-4 weeks

    The Pragmatic Engineer capacity analysis

  • AI persona drift quantified: significant degradation occurs within 8 dialogue rounds due to attention decay — embed 'canary phrases' in system prompts as lightweight monitoring

    Brian Ardinger innovation research

  • Microsoft's agent memory architecture stabilizes at 400-500 memories with 97.2% retention precision using consolidation + forgetting — first benchmarkable spec for persistent agent features

    TLDR Data agent architecture

  • Gemini leaking private phone numbers from training data — users receiving unsolicited calls as a direct result of chatbot outputs; audit your AI features for PII output-layer filtering

    MIT Technology Review AI safety

  • Google's Universal Commerce Protocol embeds BNPL (Affirm + Klarna) directly into AI shopping via Gemini — new commerce infrastructure layer for agent-mediated purchasing

    TLDR Fintech commerce infrastructure

  • Abridge case study: $5.3B valuation by picking one workflow (clinical documentation) that clinicians hated, compressing 11 minutes to 2, then expanding to prior auth and clinical decision support only after earning distribution

    Latent.Space Abridge deep-dive

  • Only 15% of organizations have data foundation for agentic AI — nearly half cite data quality as primary blocker; add readiness assessment to enterprise onboarding before contract signing

    TLDR Data enterprise readiness

  • NGINX unauthenticated RCE (18 years undetected) affects both Plus and Open Source — confirm with infra team and patch internet-facing instances today

    The Hacker News vulnerability analysis

  • Claude Code ships /goal command: fully unattended multi-turn coding sessions with separate evaluator model judging completion — reference architecture for any autonomous AI workflow

    Daily Dose of DS autonomous coding

  • Design systems need machine-readable semantic metadata — Claude Code writes to Figma via MCP but ignores tokens and governance; one developer built 4 custom Skills to fix this gap

    TLDR Design agent infrastructure

◆ Bottom line

The take.

Your AI cost model has a 30-day fuse: Anthropic kills third-party harness discounts on June 15, OpenAI's counter-offer expires in the same window, and ServiceNow just proved that production AI features can burn an entire annual budget in five months without anyone noticing until finance calls. Simultaneously, SAP and ServiceNow committed nine figures to making 'can agents call your API directly?' a procurement requirement — and 59% of all AI token volume is already agentic. The PM who spends this sprint modeling actual inference costs, scoping an MCP-compatible API layer, and measuring their own build-vs-coordinate ratio will ship a materially different product in Q4 than the one still debating vendor strategy in Slack.

— Promit, reading as Product ·

Frequently asked

How much will Claude usage through Cursor or Cline actually cost after June 15?
Third-party harness usage will run at roughly 10x current effective rates once the implicit 70-90% discount ends. Anthropic is moving to a $-for-$ API credit model where the $200 plan gets $200 in credits, with a separate credit pool for third-party tools. Once burned, the meter runs at full API rates.
Is switching to OpenAI's Codex offer worth it for a load-bearing Claude workflow?
Pilot it this sprint if the workflow is load-bearing and the current Claude harness isn't easily replaceable with Anthropic-native tooling. The 2-month free enterprise offer expires in 30 days, and real switching cost is only knowable from a pilot. If the workflow is replaceable, use the offer as leverage to renegotiate directly with Anthropic instead.
What telemetry should we demand from model providers before shipping more AI features?
Per-user, per-feature, and per-workload cost attribution, plus per-endpoint spend caps with automated alerts. ServiceNow burned a full-year Anthropic budget by mid-year because that instrumentation didn't exist. If you can't answer 'which customer drove this spend' from the provider dashboard, you need a control-tower layer before scaling any AI feature.
How do I know if my product will get bypassed by agents in enterprise deals?
Ask whether a third-party agent can discover, authenticate, and execute your core workflows without a human clicking through your UI. Procurement is already asking this in demos, and SAP's €100M Autonomous Enterprise fund plus ServiceNow's Action Fabric signal it becomes standard RFP language within 2-3 quarters. If the answer is no, scope an MCP-compatible headless layer against your top 3 workflows this quarter.
Does the Lovable no-PM model mean I should worry about my job?
Worry about the coordination half of the job, not the judgment half. Audit your last quarter: if most of your contribution was aligning people rather than deciding what to build, that portion is compressing fast as AI tools let senior ICs ship end-to-end. Roles that survive look like mini-GMs who prototype directly, not project managers who route work between functions.

◆ Same day, different angle

Read this day as…

◆ Recent in product

Keep reading.

Spot an error? mail@promitb.dev