Product & Strategy

The Product Desk

The Signal

Gemini 4 Argon's per-task cost doubles to about $4 after Nov 30, passing GPT-6 Astra.

The $1.99 a task that puts it level on the Intelligence Index is calculated at $2/$10 per million tokens. After the cutoff that rate becomes $4/$20, and at the same token mix the cheaper option ends up costing more per task than the rival at roughly $3.30. A model-swap case built this month rests on a price that lasts about six weeks, so the comparison you take to finance should be run at both rates.

In Play

  1. Argon's Promotional Price Window

    Artificial Analysis rates Gemini 4 Argon, generally available since Oct 14, level with GPT-6 Astra on its Intelligence Index at $1.99 per task. That figure uses $2/$10 per million tokens, a rate that doubles to $4/$20 after Nov 30. Any model-swap case your team builds this month uses prices that expire in about six weeks. Reviewers also disagree on quality. Cursor puts Argon on par with Opus 5.5, while one tester logged a false-claim rate above 50% on codebase analysis.

  2. Decision Models Split Off the Frontier

    Microsoft launched Decision-1 on Oct 13 for routing, classification and verification. Computerworld reports AWS, OpenAI and Cloudflare are adopting the same bounded-decision layer. These models return a choice plus a probability, which makes them cheap gates for agent actions. One test agent built by Claude Code shows the risk: all 46 of its tests passed, yet a fallback misattributed confidence in a way that could authorize a tool call. Microsoft has published no benchmarks for its efficiency claim.

  3. AI ROI Still Measured in Hours Saved

    A Wharton and GBK Collective survey of 1,400 managers finds only about 27% of firms track revenue from customer-facing AI, while 40% measure hours saved. The share expecting AI budgets to rise substantially next year fell to 10% from 19% in 2025. Your 2027 funding will follow features that can show growth. Raw usage dashboards won't make that case, because Visier finds 48% of workers exaggerate their AI use.

  4. Agents Meet Locked Doors and Echo Attacks

    The Information reports JPMorgan said on its Oct 13 earnings call that it will not let 'just any outside agent' into client accounts. CSO Online separately reports researchers bypassed six agent frameworks with a 'Repeat-After-Me' prompt and verified 253 bugs across 118 open-source MCP servers. If your agents act inside customers' systems, they now need a permission model a risk committee will accept. Sublime also ties part of a roughly 33,000% rise in calendar-invite phishing to agents that auto-accept invites.

  5. AI Vendors Look Less Durable

    Character.AI filed for Chapter 11 on Oct 12 with Disney as first bidder at $20M. Its owner warns the platform shuts down if no buyer keeps it running by the sale's late November or early December close. The Pragmatic Engineer's excerpt of Sam Newman's new book offers Cursor as the warning case: when Anthropic changed its pricing in 2025, Cursor passed a significant cost increase on to its customers. Fallback models and degraded modes now belong in your plan. Capacity is tight too, with The Information counting $531B of Anthropic compute deals in 11 months.

Deep Dives

Argon's Lead Is Real, but Its Price Expires on Nov 30

On paper Argon is the cheapest frontier-class option, but that may not hold at December prices. Its weakest skill is also the one most AI features rely on: stating facts.

What the price change does to the ranking

The per-task numbers move once the price increase is applied. Artificial Analysis measures $1.99 per task at the $2/$10 rate. If the token mix holds, $4/$20 puts Argon near $4 per task, by AINews' own back-of-envelope estimate rather than any published figure. GPT-6 Astra works out to roughly $3.30 per task at the same ratio, so Argon would cost more. The estimate ignores the 95% cached-input discount. Workloads with long, stable prompts may keep much of the advantage.

Cache-hit rate decides which side of that line a team lands on. Artificial Analysis now publishes measured cache-hit rates because they dominate real cost. A swap proposal should carry the team's own measured hit rate and name the provider it was measured on. List price alone is not enough. The provider matters more than it looks: GLM-5.3 Max runs from $0.92 to $8.68 per task depending on who serves it.


Strong at building, weak at stating facts

The independent results split by type of work. Cursor reports 52.8% on CursorBench, on par with Opus 5.5. Roboflow measures Argon High at 84.7% versus Astra's 76.8% on text localization and recognition, at about a quarter of the cost. Arena, meanwhile, ranks Argon only fifth on its agent leaderboard, behind Opus 5.5, GPT-6.1 Sol, Fable 5.1 and GPT-6 Astra at max effort.

The sharpest warning comes from developer Theo. Argon got a perfect score on his Skatebench-private test, and its false-claim rate topped 50% on his codebase-analysis benchmark. Ethan Mollick praises its writing and agentic behavior but flags overconfidence. Artificial Analysis' 15% hallucination rate on its Omniscience test is the lowest among models scoring at least 45. The test rewards abstaining, so that figure is not an overall error rate.

The pitch is a model that builds well. Whether the weakness matters depends on what the user does with the output. Sorting each backlog feature on one axis, draft versus assertion, shows where Argon can go first. A user who gets a draft and edits it absorbs a confident wrong answer at little cost. A user who is told something is true about their own data acts on it, and a wrong claim there does real harm.

Feature typeExamplesSurvives a confident error?Control needed before Argon
GenerateDrafts, code scaffolds, creative copyYes, the user editsStandard eval on your tasks
AssertAudit summaries, compliance checks, code review commentsNoGrounding, citations, an abstention path
Route or classifyTriage, extractionPartlyBake-off against a decision model

Google already uses model tier as a paywall

Google's own packaging points the same direction. Computerworld reports Gemini Pro is reserved for paying users, while free users get Gemini Flash Lite. That is a public reference point for any free-versus-paid tiering decision. Argon also shipped on day one inside Cursor, Devin and GitHub Copilot, so engineers may already be using it before anyone has priced it. The other date to know is Oct 27, when Cognition's 75% Devin discount ends.

We think Argon deserves a serious bench test. Its lead belongs in the plan only at the price the team will pay in December.

What to do

  1. Re-bench your top three production workloads on Argon against your incumbent model this week. Report cost per successful task at both $2/$10 and $4/$20, alongside your measured cache-hit rate.

  2. Add grounding, citations and an abstention path to every feature that makes factual claims about user data before it moves to Argon, and measure its false-claim rate on an internal eval set this sprint.

  3. Trial Argon-backed Devin on your own tickets before Oct 27 if coding agents are on your evaluation list. Measure rework, not completion.

Cheap Decision Models Hand You a Probability, and Your Code Turns It Into Permission

Moving routing and classification off the frontier model saves money, but authorization then sits in fallback code that tests rarely exercise.

How a missing action got a 0.90 confidence

An incident agent pages the team on a number that belonged to another action. Daily Dose of Data Science had Claude Code build the agent from one prompt: 30 files and 3,383 lines. It sends Jev, a choice-selecting model, six questions in one request. One is next_action, with six allowed values. A policy gate reads the chosen action's probability. At 0.80 or above, the action runs. From 0.55 to 0.79, the agent gathers more evidence. Below 0.55, a human takes over.

The bug sat in one fallback. When the chosen action was missing from the returned probability map, the code borrowed the largest probability of any option. In the example, the model chose page_team, page_team had no probability, and inspect_logs came back at 0.90, so page_team inherited 0.90 and cleared the gate. Fixtures and live responses always included the chosen option's probability, so the path never ran in testing. CodeRabbit's review rated merge risk High and found stored XSS and a fixture mode that could fall through to live requests. The CodeRabbit portion is sponsored, though its findings are specific and checkable.


Why this pattern is about to spread

Vendors are selling decision models as their own tier, and each one returns a probability that downstream code will act on. Computerworld reports Microsoft's Decision-1, launched Oct 13, and says AWS, OpenAI and Cloudflare are adopting the same layer. Artificial Analysis launched a Decision Index covering knowledge, reasoning, tool calling and safety classification, where Jev 1.13 leads at 58. Jev reportedly reached nearly 13% of paid teams on Vercel AI Gateway in its first 24 hours, a figure with no citation and no retention data.

The economics are tempting. ScaleDown charges $0.05 per million input tokens with free output. A lower-confidence comparison has Haiku 5.5 Low at 61 to Jev's 58, at $184 versus $42 per million tasks and 1.4 versus 0.13 seconds per task. Every figure here comes from a vendor or a single evaluator.


Where the sources disagree

Microsoft calls Decision-1 more efficient than general-purpose LLMs and has published no accuracy, latency or price figures. Computerworld lists governance, calibration and operational overhead as open questions. AINews adds that decision models are weaker, and often overconfident, on knowledge and reasoning. The sources agree only that these models suit routing, classification and extraction.

Call typeFit for a decision modelTypical failureGate rule
Route or triageStrongRequest sent to the wrong laneLog and sample outcomes
Classify or extractStrongSilent mislabelCalibrate on labeled outcomes
Authorize an actionOnly with an external gateConfidence attached to the wrong optionMissing or unpaired means zero and a human
Open-ended judgmentWeakOverconfident wrong answerKeep on a frontier model

Product should own these thresholds. The example's were picked by hand. When the gate halts a run and no tool executes, someone decides what the user sees and who owns the next step. A workable test for tomorrow: any gated action that lacks data behind its threshold or a named owner for stopped cases stays with a human.

A model's confidence score is untrusted input: if the code can't prove which action it belongs to, treat it as zero and send the case to a human.

What to do

  1. Tag every LLM call in your product as generate, route, classify or verify this sprint, and baseline the cost, latency and error rate of each.

  2. Add a fail-closed rule this sprint to every spec where model confidence triggers an action: missing, malformed or unpaired confidence counts as zero and goes to human review. Add invariant tests for that rule to the definition of done for AI-generated PRs.

  3. Bake off your top two or three routing and classification calls against a decision model this quarter. Set acceptance thresholds before the test, and calibrate gate thresholds from labeled outcomes.

Workday Will Bill for Agent Actions Before Buyers Can Measure What They Return

Metered agent pricing makes every action a line item for finance teams. Those teams still judge AI by hours saved and by usage numbers that workers admit they pad.

The bill arrives before the proof

Picture a finance analyst at a Workday customer opening an invoice with a new line for agent actions. That line traces to Workday's Oct 13 announcement, the clearest sign of where enterprise AI pricing is heading. Customers can now run agents from Anthropic, Microsoft and OpenAI inside their Workday accounts. From February 2027, after a no-fee grace period, Workday will charge by usage when those agents tap connectors and take actions. Salesforce offers a similar headless option, now called SIforce. CEO Aneel Bhusri calls it giving customers choice. Employees and investors worry both firms become “dumb” infrastructure underneath someone else's agent.

We saw this when software moved from seats to consumption. The first metered invoice gets read line by line. The Wharton evidence suggests the finance teams reading these lines cannot yet say what an agent action returns.


What buyers measure today

Study author Jeremy Korst describes current AI measurement as “vibes” and managers' “perception.” Most firms count efficiency: 40% track hours saved per employee and 37% track error reduction. Only 8% expect new revenue or products to be AI's main role over the next one to two years. Productivity gets 44%. The 28% of managers reporting “strongly positive” returns are more likely to work at firms that measure growth outcomes. The survey shows the two travel together. It cannot show which drives the other.

Usage data is noisier still. Visier surveyed 1,000 full-time US workers and found 48% exaggerate their AI use or expertise at least some of the time, often to protect their jobs. So a mandated rollout's usage dashboard overstates adoption. Computerworld reports tech executives shifting from cost to value, tying AI projects to financial and non-financial outcomes.


Where the evidence conflicts

The surveys disagree on returns. About 80% of Wharton's managers report positive returns. The Information's own subscriber survey finds 52%. The samples differ, and a 28-point gap tells us the metric is soft. Proof points are thin too. Walmart's CEO said users of its Sparky assistant spend 40% more per order. That was a conference claim with no control group, and high-intent shoppers may be the ones who opt in. If so, the 40% mostly measures who opted in.

The Information's coverage of Ithaca's Bumble deal shows AI framing without numbers. Ithaca calls the purchase an AI-driven bet. Bumble's revenue fell 10% last year and 15% in the first half.

PressureEvidenceWhat it means for your feature
Metered pricingWorkday from February 2027; Salesforce SIforceEach action needs a return story
Padded usage48% of workers exaggerate AI useRaw usage stops counting as value
Soft ROIAbout 27% track customer AI revenueRevenue-linked features stand out at budget time

In our view, the features that survive 2027 planning will show an outcome for every metered action. A two-by-two helps. One axis is metered versus bundled. The other is whether the action maps to an outcome the buyer already tracks, like hours saved or error reduction. Metered with no tracked outcome is the cell CFOs cut first. B2B vendors should expect their own customers' CFOs to run the same test.

What to do

  1. Give every shipped or planned AI feature a named outcome metric and a baseline this sprint. Split its usage into mandated and voluntary cohorts so performative use stops inflating your dashboard.

  2. Set up a holdout or matched-cohort test this quarter on your flagship customer-facing AI feature, to measure incremental revenue or retention lift.

  3. If you sell B2B software, draft a metering hypothesis and a CFO-ready one-pager per agent action this quarter. Treat Workday's February 2027 switch as the live test of buyer tolerance.

The bottom line

These stories share one weakness: the numbers teams use to approve AI work are on loan. Introductory prices expire. Usage counts include people performing adoption. A single fallback line can attach a probability to the wrong action. That breaks the assumption that AI unit economics improve on their own, because buyers and finance teams are about to reprice every feature at its real cost and real outcome. Rebuild your AI business case this week on post-promotion prices, voluntary usage and measured outcomes. Cut any feature that only clears the bar on borrowed numbers.