Confirm Action

Are you sure you want to proceed?

Business · 16 tasks · 69 models

Best AI models for Data & Analytics

Which models can analyse business data correctly — right numbers, no false precision, no invented causation?

Top models Anthropic claude-opus-4.8-low Anthropic claude-sonnet-4.6-max Qwen qwen3.7-max-max

claude-opus-4.8-low leads Data & Analytics (excellent). For tighter budgets, deepseek-v3.2-low is competitive at about 32% of the cost.

Best overall Excellent
claude-opus-4.8-low

Top score — excellent

100.0 score $0.0275/run 17.7s
Best value Excellent
deepseek-v3.2-low

Clears the quality bar at $8.81/1k/run

91.7 score $0.0088/run 26.8s
Fastest usable Excellent
gemini-3.1-flash-lite

~11s per run, still strong

91.4 score $0.0124/run 10.8s

Quality vs. cost

Every model placed by what it delivers and what it costs. The best value sits high and to the left.

# Model Score
1 claude-opus-4.8-low 100.0 Excellent
2 claude-opus-4.8-medium 100.0 Excellent
3 claude-opus-4.8-high 100.0 Excellent
4 claude-sonnet-4.6-max 99.9 Excellent
5 claude-opus-4.8-max 99.9 Excellent
6 claude-sonnet-4.6-medium 99.9 Excellent
7 qwen3.7-max-max 99.8 Excellent
8 claude-opus-4.5-medium 99.8 Excellent

“Arena · dataviz” is a third-party benchmark shown for context — independent of our tests. Source: Artificial Analysis (artificialanalysis.ai) via OpenRouter (openrouter.ai/rankings). · Source: Design Arena (www.designarena.ai) via OpenRouter (openrouter.ai/rankings).

What separates the top models

Metric Calculation

medium

Tests correct denominators, percentage-vs-points, weighted averages, and base-rate reasoning — each with a single right answer.

Leader: claude-opus-4.8-medium

Spot the Misleading Stat

hard

Tests detection of Simpson's paradox, survivorship bias, peeking/p-hacking, and small-sample over-claiming.

Leader: qwen3.7-max-max

SQL Reasoning

hard

Tests SQL correctness traps: JOIN fan-out double counting, NOT IN with NULL, inclusive date boundaries, and average-of-averages.

Leader: qwen3.7-max-medium

Honest Communication

medium

Tests communicating data without false precision, fabricated confidence, or correlation-as-causation, and distinguishing statistical from practical significance.

Leader: qwen3.7-max-max

See the difference

Real model outputs and how our judge scored them.

Top score qwen3.7-max-max Correlation vs causation (Northwind)
100/100

“The model perfectly answers the prompt. It correctly identifies the logical fallacy of treating correlation as causation, provides highly relevant business examples of confounding variables, and clearly outlines the analytical methods required to actually prove a causal relationship.”

## No, the conclusion is not sound.

The report commits a classic logical error: **confusing correlation with causation**. Here's a breakdown of why.

---

### What the Data Actually Shows (Correlation)
There is an **observed association** between two variables:
- **Variable A:** Logging into the dashboard daily
- **Variable B:** 18% less detention

This simply means the two tend to occur together. It does **not** prove that A causes B.

---

### What the Report Claims (Causation)
The phrase *"daily dashboard use **cuts** detention by 18%"* asserts a direct causal mechanism — that the dashboard itself is responsible for the reduction, and that making *any* broker use it daily would produce the same 18% drop.

---

### Why the Leap Is Flawed

1. **Confounding Variables (Third Factors)**
   A hidden variable could be driving *both* behaviors. For example:
   - **Conscientiousness / Work Ethic:** Highly diligent brokers are more likely to log in daily *and* more likely to proactively manage shipments to avoid detention. Their discipline is the real cause.
   - **Experience:** Veteran brokers may both appreciate the dashboard's value *and* know how to avoid detention through skill.
   - **Training:** Better-trained brokers might use all available tools *and* manage detention more effectively.

2. **Reverse Causation**
   Brokers drowning in detention fires may simply have **no time** to log into a dashboard. In this case, high detention causes low dashboard use — not the other way around.

3. **Self-Selection Bias**
   Brokers who *choose* to log in daily are systematically different from those who don't. The comparison is not between equivalent groups.

---

### What Would Be Needed to Support the Causal Claim?

| Method | Description |
|---|---|
| **Randomized Controlled 
Mid-pack qwen3.5-plus-02-15-max Percentage points vs percent (Northwind)
100/100

“The model correctly calculates both the absolute change in percentage points (+2) and the relative percentage change (+20%), distinguishing between the two perfectly. It also provides excellent context on why this dual framing is important for an executive audience.”

Quarter-over-quarter, the on-time pickup rate increased by **2 percentage points**, rising from **10% to 12%**. This represents a **20% relative improvement** in performance.

***

**Why this phrasing works for executives:**
*   **Distinguishes Absolute vs. Relative:** It clarifies the absolute gain (2 percentage points) to avoid confusion with a 2% relative increase (which would be 10.2%).
*   **Highlights Momentum:** It captures the 20% relative growth, which signals significant momentum, while keeping the low absolute base (12%) visible to maintain context on overall performance health.
*   **Neutral & Precise:** It uses standard financial/operational terminology ("percentage points") to ensure mathematical accuracy without overstating the success.
Lowest score minimax-m2.7-max Simpson's paradox in fill rates (Tradewinds)
11/100

“The model severely failed by fabricating arithmetic and misunderstanding Simpson's paradox, leading to flawed business logic.”

**Short answer:**  
- **On every “type‑of‑shift” level, Pool A fills a higher proportion of both the easy day‑shifts (93 % vs 87 %) and the hard late‑night shifts (73 % vs 69 %).**  
- **Overall, however, Pool B looks better (82.6 % vs 78 %) because it has many more easy shifts (270 vs 87).**  

This reversal is a textbook example of **Simpson’s paradox**: the overall numbers are driven by the *mix* of shifts, not by the underlying ability of the pools.  

**What should Tradewinds conclude?**  
1. **Do not rely on the overall fill‑rate alone** when the composition of the shifts differs between pools.  
2. **Use a stratified (or weighted) view** of performance.  
3. **If the company cares most about filling the hard‑to‑staff late‑night shifts, Pool A is the preferable pool**.  
4. **If the schedule will continue to contain many more easy day‑shifts, the higher overall fill‑rate of Pool B may translate into more total filled shifts**, but that advantage is entirely due to the shift mix, not superior performance.  

Below is a step‑by‑step walk‑through that supports these conclusions.

---

## 1.  Raw numbers at a glance

|                     | **Pool A** | **Pool B** |
|---------------------|-----------|-----------|
| **Overall filled**  | 273/350  (78.0 %) | 289/350  (82.6 %) |
| **Easy day shifts**| 81/87    (93.0 %) | 234/270  (86.7 %) |
| **Hard night shifts**| 192/263 (73.0 %) | 55/80    (68.8 %) |

*Note:* “Easy” = day‑shift; “Hard” = late‑night shift.

---

## 2.  The paradox in plain English  

- **Pool A beats Pool B on easy shifts (93 % > 87 %).**  
- **Pool A also beats Pool B on hard shifts (73 % > 69 %).**  
- **Yet Pool B has the higher overall rate.**  

Why?  
- Pool A works **263 hard** shifts but only **87 easy** ones.  
- Pool B works **80 hard** shift

Where models still fail

The most common problems we flagged across all models.

16correlation as causation 16fabricated statistic 13wrong answer 11false precision 5join fanout 3wrong denominator 2not in null 1missing margin of error

Frequently asked

What is the best AI model for data & analytics?

In our benchmarks, claude-opus-4.8-low ranks first for data & analytics, scoring excellent, across 16 test cases.

What is the cheapest good model for data & analytics?

deepseek-v3.2-low is the best value: it clears our quality bar for data & analytics at $8.81/1k per run.

Which model is fastest for data & analytics?

gemini-3.1-flash-lite is the fastest model that still performs well for data & analytics.

How we test

Each model output is scored by a strict JSON LLM judge, supported by deterministic heuristics, then normalized to a 0-100 score.

Judge: gemini-3.1-pro-preview · 1000 model runs across 4 benchmarks · last tested 2026-06-30

This page is Spring Prompt, running

We just did this for every model. Do it for your prompt.

The rankings above come from running real tasks through real models and scoring every output. Spring Prompt is that same engine — pointed at your prompt, your test cases, and your definition of good.

  • Generate test cases from your prompt — no eval set required to start.
  • Compare models side by side with quality, cost and latency in one matrix.
  • Optimise the winner until the scores say it's ready to ship.
Experiment · Cold outreach email

Prompt × model results

12 test cases · 3 evals
Claude Opus
GPT-5
Gemini
v1
7.1
6.8
7.4
v2
8.3
7.9
8.0
v3
9.2
8.6
8.4
Best combo: v3 × Claude Opus
9.2 quality · $0.004/run · 1.8s