Competitive Brief: Call Sheet
Researched: OpenAI · for Anthropic reps
Focus: enterprise coding/developers
Today's angle
GitHub Copilot's first full token-billing cycle closed on June 30, 2026, and the invoices confirmed the damage developers feared. On Reddit, X and GitHub's own forum, agentic users report costs 10x to 50x their old flat rate: one developer's roughly $29 plan projected to nearly $750 a month, another's $50 to about $3,000. GitHub concedes intense agentic users will pay more and has not reversed course. That turns the flat-rate contrast with Claude Code (Pro $20, Max 5x/20x at $100/$200) into a confirmed cost argument rather than a projection.
Top 3 plays
PLAY 01
Developers prefer Claude Code, and they're the ones who'll live in the tool.
JetBrains' January 2026 survey of 10,000+ professional developers gives Claude Code the market's highest loyalty (CSAT 91, NPS 54) alongside ~6x adoption growth in nine months to 18% (24% in the US/Canada). Strongest with hands-on engineering teams who get a real vote in the tool choice.
"JetBrains' own survey of 10,000 engineers shows Claude Code has the highest satisfaction and recommend scores of any AI coding tool. Adoption follows preference."
PLAY 02
Independent spend data now ranks Anthropic the most-adopted AI vendor among businesses.
Ramp's expense index across 50,000+ companies shows 34.4% paying for Anthropic vs 32.3% for OpenAI as of spring 2026, the first time Anthropic has led. It's drawn from actual corporate card spend rather than a vendor survey, which makes it hard for an OpenAI rep to dismiss. Best deployed against the "OpenAI is the safe default" reflex.
"Anthropic just passed OpenAI as the #1 AI vendor in business spend, based on Ramp's corporate-card data across 50,000 companies. Anthropic is becoming the default."
PLAY 03
On the hardest, least-gameable coding benchmark, Claude leads.
SWE-bench Verified is increasingly saturated and contamination-prone; SWE-bench Pro uses harder, non-public tasks. There, Claude Opus 4.7 leads at 64.3% vs GPT-5.4's 59.1%. For engineering leaders who care about messy real-world tickets rather than leaderboard optics, that's the number that matters.
"GPT wins the saturated benchmark by a point; Claude wins the hard one, SWE-bench Pro with real tasks, by five. Ask which one looks like your codebase."
Objection handling
"I heard Microsoft is pulling Claude Code from its own engineers. Why should we adopt it?"
Counter: Microsoft is protecting its own SKU. Their engineers liked Claude Code enough that it threatened Copilot, and you can still run Claude through Copilot today.
"Uber blew through its AI budget on Claude Code and capped spend. How do we avoid that?"
Counter: Set seat-level budgets and a clear ROI metric before rollout, and you get the productivity without Uber's bill shock.
"Claude has had multiple outages this month. Can it handle our production load?"
Counter: Deploy production workloads via Bedrock or Vertex with an enterprise SLA rather than the consumer endpoint or direct API. That tier was insulated from the June 2 outage, and with the API now hit directly too, it is the right choice for any workload that cannot tolerate disruption.
"Didn't Claude Code get worse, and doesn't Veracode say it writes insecure code?"
Counter: Concede the 4.7 period, then move to 4.8 and a security eval on the prospect's own code, where the self-verification improvements show up.
"The federal government banned Anthropic. Is it a risky vendor to standardize on?"
Counter: If they have federal compliance needs, have the conversation honestly. For commercial enterprise, the dispute is about military red lines, and your cloud procurement path is unaffected.
"Anthropic keeps changing its pricing. How do I budget against a moving target?"
Counter: Put production usage on the pay-as-you-go API with committed-use terms: metered, SLA-backed, and now locked at $2/$10 for Sonnet 5 with the planned increase canceled.
"The government forced Anthropic to disable two of its models overnight for every customer. How do we know the same won't happen to what we're building on?"
Counter: Anchor cloud-marketplace customers on Sonnet 4.6 or Opus 4.8 until Fable 5 re-enables there. If government risk still worries the buyer, note that OpenAI's GPT-5.6 launched under the same gate: an industry-wide condition, not an Anthropic defect.
"International buyers are moving to Mistral and Cohere because of the export ban. Is Anthropic losing ground internationally?"
Counter: Acknowledge the defections as a real cost of the ban, then move the conversation back to workload results: offer to benchmark the buyer's specific coding workload head-to-head against the alternative they are evaluating.
"Wasn't Claude trained on pirated books? Isn't that a legal risk for us?"
Counter: Tell the buyer the exposure is capped and resolved, not open-ended: a fixed payout, destroyed copies and a court finding that training on lawfully acquired text is fair use. That's a closed legal question, not a reason to slow down a Claude deal.
"Your own models broke out of a test environment and accessed real systems. How do we know an agent won't do that to us?"
Counter: Meet it head on. Frame the scope honestly: this surfaced in a cybersecurity evaluation, and Anthropic's detect-and-disclose speed is the point worth naming. Offer to walk the buyer through the published incident report and Anthropic's evaluation-safety practices.
Agent Scout · every claim verified against its source · 84 claims tracked