On 13 May 2026, Ramp published its April 2026 AI Index — a measure of business AI adoption built from the corporate-card spend of more than 50,000 companies on the Ramp network — and for the first time in the index’s history, Anthropic surpassed OpenAI in business adoption. Anthropic’s share climbed 3.8 points in April to 34.4%; OpenAI’s fell 2.9 points to 32.3%. A year earlier the picture was inverted — Anthropic under 8%, OpenAI roughly 32%. Over twelve months, Anthropic has roughly quadrupled its business adoption while OpenAI’s grew by 0.3 points. The engine of the swing is a single product: Claude Code, Anthropic’s agentic coding tool, now the fastest-growing product in Anthropic’s history. Adjacent reporting from the same week put Anthropic’s annualised revenue run-rate at $30B in April 2026, up from $9B at the end of 2025, with a reported $950B funding round in discussion. This is the first procurement-grade signal that the consumer-AI narrative and the enterprise-AI narrative have decoupled. ChatGPT still dominates the consumer surface. The corporate card moved somewhere else. The four-year vendor-lock playbook your procurement team is still running has just been outdated by twelve months of data.
The Ramp AI Index is the cleanest public picture of enterprise AI procurement that exists today. The methodology is direct: 50,000+ companies on the Ramp corporate-card network, actual dollars paid, monthly rebase. Not survey intent. Not press-release adoption. The April 2026 release, published 13 May, is the first time the index has crossed: Anthropic 34.4%, OpenAI 32.3%, with Anthropic gaining 3.8 points in a single month and OpenAI losing 2.9. Twelve months earlier Anthropic was under 8% and OpenAI was around 32% — OpenAI has essentially held its absolute share while Anthropic has roughly quadrupled. The engine is not the general-purpose chatbot. It is Claude Code, the agentic coding tool, now the fastest-growing product in Anthropic’s history. Adjacent reporting from the same week landed Anthropic’s annualised revenue run-rate at $30B in April, up from $9B at the end of 2025, with a reported $950B funding round in discussion (not yet closed; treat as context rather than evidence). The Ramp Economics Lab flagged three risks against the milestone, fairly: a structural incentive for Anthropic to steer customers toward more expensive models, exposure to Microsoft / GitHub Copilot’s distribution advantage, and a thinning differentiation gap as OpenAI moves on coding agents. The directional signal survives the caveats. Three procurement implications follow, each more uncomfortable than the last for any team running a 2024-vintage vendor strategy. The next paragraphs cover why this is a procurement-grade signal, what the “Claude Code is the engine” finding actually means for budget allocation, and the four moves every engineering lead should make before the next renewal cycle.
Most AI adoption data in 2026 has one of two failure modes. Vendor case studies are marketing. Survey data is intent rather than commitment. The Ramp index avoids both because it is dollar-denominated and observed, not stated. Three things specifically make this read different from the noise around it.
First, the dataset is dollars paid. 50,000+ companies on a single corporate-card network, monthly, against the same merchant categorisation logic. The signal is what got charged to the card, not what got promised in a procurement deck. Spend ahead of usage is rare; usage ahead of spend is rare. The two converge over enough months that the spend pattern is a clean read on what enterprises are choosing in production.
Second, the timeframe is the change, not the snapshot. Anthropic at 34.4% in a single month is a number; Anthropic moving from under 8% to 34.4% over twelve months is the structural fact. OpenAI essentially held its absolute share (32% to 32.3%) while the market grew around it; Anthropic took the growth. Procurement decisions made on a 2024 vendor landscape now sit on data that did not yet exist.
Third, the sample bias is documented and the direction is robust to it. Ramp’s customer base over-indexes on growth-stage and SMB companies, not on Fortune 500 procurement. The honest reading is that the index is the cleanest signal we have for the demotoprod-shaped buyer (founder, CTO, engineering lead in a 50–5,000-person company) and a weaker signal for the largest enterprises. For most readers of this post, that bias is in their favour: the data is from companies that look more like theirs than the Fortune 500 surveys do.
The differentiator that pulled 50,000 finance teams was not the headline benchmark. It was not the model-card MMLU score. It was a single product category — agentic coding inside the firewall — and a single product, Claude Code, that has been the structural driver of Anthropic’s $9B-to-$30B revenue ramp in four months. The implication runs well beyond Anthropic.
Most enterprise AI strategies in 2026 still have “general-purpose chatbot for the company” as the headline use case and developer tooling as a side note. The Ramp data is direct evidence that the budget has already moved in the opposite direction. Coding agents are the wedge. They are where the spend is converting from pilot to renewal, from a single seat to a team licence, from a team licence to an org-wide rollout. The general-purpose chatbot has become table stakes; the coding agent has become the line item that grows.
The strategic correction for engineering leadership: re-prioritise the AI roadmap to put coding-agent enablement near the top, not as the “developer tools” afterthought. The productivity numbers attached to coding agents in 2026 (10–20% PR throughput, sometimes higher in specific stacks) are higher than the productivity numbers attached to most other AI categories, and they accrue to a function (engineering) that is already the most expensive headcount line in most software companies. The ROI math favours the coding-agent line in a way that is becoming hard to argue against.
The Ramp signal carries three procurement implications. Each is more structurally awkward than the one before it for any team running a single-vendor 2024 playbook.
One — consumer usage is no longer a proxy for enterprise spend. ChatGPT still dominates the consumer surface, and that is unlikely to change in 2026. But the CTO who is using “how many of my friends use ChatGPT” as evidence for the company-standard vendor is using a leading indicator that has demonstrably stopped predicting the procurement outcome. The decoupling is not partial; it is the first crossover in the index’s history. Treat the two surfaces as separate markets with separate purchase decisions, evaluated against separate criteria.
Two — coding agents are moving real enterprise budget, before the vendor strategy has caught up. Most 2026 AI strategy decks I review still treat coding agents as a developer-tools rounding error. The Ramp data is direct evidence that the budget has already shifted. The procurement-correct response is to bring the coding-agent decision up to the same review tier as the general-purpose model decision: same vendor scorecard, same SLA expectations, same fallback-path analysis. Lumping coding agents into “developer tools” means the most consequential 2026 AI procurement decision is being made by a sub-budget that is not reviewed at the right altitude.
Three — the “lock vendor in 2024, review in 2028” playbook is now untenable. A 3.3× revenue jump in four months and a reported $950B funding round in discussion is the kind of magnitude swing that breaks the four-year procurement horizon most enterprises are still running. Annual re-evaluation is no longer disciplined hygiene; it is the only defensible cadence. Write annual re-evaluation into the procurement calendar before the next pricing or capability dislocation forces the conversation under deadline pressure. The CFO who pushes back at annual cadence on the grounds of “we just renegotiated” needs to read the Ramp index. The category is moving faster than the playbook the procurement team learned in 2022.
Reading the data is the easy part. Translating it into a vendor strategy that survives the next twelve months is the work. Four moves, in order. Each is engineering-time-affordable; none is glamorous.
Move 1 — Inventory the AI vendor surface and the budget against each. One row per vendor per use case. Capture the contract length, renewal date, monthly spend, the use case the vendor supports, the criticality (Tier 1 production, Tier 2 internal, Tier 3 experiment), and whether the vendor is single-point-of-failure for that use case. Most teams discover during this audit that they have three to five more AI vendors than they expected, and that one or two are on contracts written before the market reshaped.
Move 2 — Build the portable abstraction layer. A vendor-agnostic prompt and tool layer, a model-routing abstraction, a tested fallback path to a second provider for at least the Tier 1 use cases. The work is mid-engineering effort, not a full platform rewrite; libraries and patterns are mature enough in 2026 to make this a sprint or two rather than a quarter. Without it, every vendor capability or pricing dislocation lands as a multi-month migration. With it, the dislocation lands as a routing change.
Move 3 — Run an annual vendor re-evaluation against a written scorecard. One scorecard. The dimensions are familiar: capability fit, price, reliability, governance, exit cost, vendor concentration. Score every active AI vendor annually. Document the rationale for renewal in writing. The discipline is not the score itself; it is forcing the conversation onto the calendar before market pressure does. The renewal that comes up under emergency pressure is the renewal that gets the worst terms.
Move 4 — Bring the coding-agent decision up to a board-visible review tier. If coding agents are now the highest-ROI AI line item in the budget — and the Ramp data suggests they are for most software-shaped buyers — the procurement decision should sit at the altitude of an infrastructure line, not a developer-tools line. Document the productivity baseline before rollout, the target after rollout, the security and IP-leakage posture, the SLA, the on-call rotation. Coding-agent decisions made in the engineering manager’s discretionary line will be the most-regretted procurement choices of 2027.
Three caveats worth holding alongside the headline. None of them invalidate the signal; each of them refines how to act on it.
The Ramp dataset over-indexes on growth-stage and SMB. The signal is strongest for the demotoprod-shaped buyer and weaker for the Fortune 500. If your procurement context is large-enterprise, treat the Ramp number as a leading indicator that the same shift is on the way, rather than a description of the Fortune 500’s current state.
The token-price incentive is real. The Ramp Economics Lab flagged that Anthropic has a structural incentive to steer customers toward more expensive models. Watch the actual cost-per-task on your highest-volume workflows, not the cost-per-token. The procurement scorecard should track end-to-end cost on a representative workload, not the headline price.
The Microsoft / Copilot distribution moat has not closed. GitHub Copilot rides on top of Microsoft 365 distribution; for buyers heavily invested in the Microsoft stack, the distribution advantage is meaningful and not visible in the Ramp data, which measures direct-to-vendor spend. Account for it in the procurement scorecard if your buyer is Microsoft-anchored.
Don’t over-react to a single month. April 2026 is one data point. The twelve-month direction (Anthropic 8% → 34.4%, OpenAI ~32% → 32.3%) is the structural finding. Switch every vendor on the basis of one month’s index and you will spend the next year migrating again. Read the trend; act on the trend.
Don’t treat the swing as a single-vendor story. The structural finding is that the AI procurement landscape is moving faster than the procurement playbook. The fix is the portable abstraction layer and the annual re-evaluation, not switching from OpenAI to Anthropic. The next swing — in either direction — is already on the way.
Don’t conflate the consumer market with the enterprise market. Reasoning from your own ChatGPT usage to a procurement decision is the cleanest example of this category error. The two markets have decoupled. Use enterprise data for enterprise decisions.
Don’t defer the abstraction layer because “we’re happy with our current vendor.” The abstraction is not a vendor migration tool; it is a discontinuity insurance policy. The cost of building it is bounded and known. The cost of needing it without having it is unbounded and discovered under deadline pressure.
The AI vendor inventory is a single document with renewal dates, monthly spend, criticality tier, and single-point-of-failure flag per use case. A portable prompt and tool layer is in production for every Tier 1 service, with a tested fallback path to a second provider documented and rehearsed. The procurement scorecard is written, signed off by the CTO and the CFO, and scheduled into the annual calendar. The coding-agent decision sits at the same review tier as the general-purpose model decision; the productivity baseline and target are documented. Engineering leadership can answer, in writing, the question “what happens to our AI operating model if our primary vendor doubles its price, halves its rate limit, or is acquired,” in two paragraphs. Most cannot today. The ones who can are the ones whose 2027 procurement cycle is a one-meeting renewal, not a quarter-long crisis.
The April 2026 Ramp index is not a story about which vendor won. It is a story about a market that is moving faster than the procurement discipline most enterprises are using to navigate it. The vendor at the top of the league table will move again. The market structure underneath — coding agents as the wedge, annual re-evaluation as the cadence, portable abstractions as the insurance — is the durable artefact. The engineering leaders who treat the OpenAI-by-default policy as a settled question are defending it against a vendor that quadrupled in a year. The engineering leaders who treat the Anthropic-by-default policy as the new settled question will be defending the same posture against the next entrant in twelve months. The procurement-correct move is the same in both cases: build the abstraction layer, write the scorecard, schedule the re-evaluation, and let the data move the decision next time too. The vendor changes. The discipline does not.
Indica Tech’s two-week AI vendor portfolio audit inventories every active AI vendor with renewal dates and criticality tiers, scores each against a written scorecard, identifies single-point-of-failure exposure across Tier 1 services, drafts the portable prompt-and-tool layer against your stack, and gives you a 90-day plan to bring the coding-agent decision up to the right review tier. Fixed price £3,500. Written report. Whether you hire us for the remediation or not.
See the audit engagement →