The Wallet Transfer Is Real. The Revenue It Creates Isn't ARR.
Buyers are handing AI vendors most of their incremental budget and simultaneously installing the governance that caps it, which makes durability rather than demand the variable your software marks depend on.
The sequencing is the tell
Watch the order in which incumbents moved. Workday, HubSpot, Microsoft and Amazon are running AI discounts and free trials before defections appear in reported numbers. Vendors with real switching costs raise price and absorb some logo loss; pre-emptive discounting is a confession of weak differentiation, and it compresses gross margin and net revenue retention simultaneously. The Information's reporting frames these cuts explicitly as retention moves — which is why a mark built on 2023-era net revenue retention plus contractual escalators is the stalest number in a software book.
The other half of the same playbook contradicts it: migrating those same customers onto metered pricing that raises effective prices. Pegasystems quantifies it. Monthly GitHub Copilot spend went from $20,000 to $260,000 after Microsoft shifted to usage-based billing — roughly $3.1M annualized against a total software budget of $10-15M, meaning one coding tool now consumes 21-31% of all software spend, up from about 2%. CIO David Vidoni did not churn. He installed per-employee spending caps and complained publicly that vendors offload cost optimization onto buyers.
What Microsoft did next matters more than the bill
Microsoft offered one million credits — worth roughly $10,000 — for a month of Copilot Cowork, and Vidoni plans to test Cowork in finance and marketing. A billing dispute became footprint expansion for five figures, with reporting suggesting other customers received materially richer incentives. Two consequences for your book: incumbent switching costs are cheaper to defend than the AI-native displacement narrative assumes, and every portfolio company carrying a Copilot line item should be demanding incentive parity before its next renewal window.
The cost side points the same direction
Two independent signals say unit-price deflation is not reaching gross margin. Token prices have fallen 75% while customer AI bills tripled, because agentic workloads consume tokens far faster than prices fall — that figure traces to a sponsored placement, so treat the precision loosely and the direction as corroborated elsewhere. And xAI shipped Grok 4.7 at exactly Grok 4.6's price with a larger base model and output self-verification. A model that checks its own work before returning it burns more tokens per completed job by construction: flat list price, higher total bill, and app-layer companies will switch without telling finance.
The cleanest version sits in voice. OpenAI's own GPT Voice engineers state plainly that full-duplex serving must be measured in concurrent sessions, not requests, because the model never idles — you rent GPU memory and compute for every second a human talks, thinks or pauses. Text application economics lean on idle-time amortization. Full-duplex has no idle time, so any voice position whose plan is built on per-request cost is overstating margin structurally, not marginally.
ARR is the wrong metric for metered AI revenue. Ask for month-over-month consumption retention, the share of accounts that have imposed internal caps, and revenue concentration in the top consuming decile.
The caveat that keeps this honest
The cohort is dozens of tech-forward companies averaging 2,400 employees — Snowflake, Datadog, Cloudflare, AMD among them — and OpenAI is both a Zip customer and a named beneficiary of the shift it measures. True broad-market AI wallet share is plausibly 2-4%. Use the 8% as a 12-24 month leading indicator, not as market-size evidence in an investment memo. What survives the caveat is still large: in the most sophisticated buying cohort in the economy, legacy software is a mid-single-digit growth business, and the revenue replacing it is consumption the buyer is already governing.
What to do
Demand month-over-month consumption retention and the share of accounts with imposed spend caps from every portfolio company monetizing AI per-unit, before Q3 books close.
Re-run base-case growth on every seat-based software mark at mid-single-digit organic line growth rather than low teens, and flag any mark whose thesis needs more than 10% seat expansion.
Add one question to the AI application diligence checklist this quarter: what is gross margin if the customer caps spend at twice the prior subscription price?