"How do this week's signups compare with last month?" "Which region's revenue is growing?" Even when you want to see numbers like these at work, building tables and charts from company data often means asking someone who knows how. It takes days from asking to receiving, and by the time it arrives, the numbers are out of date.
On top of that, you can't tell how the numbers in the finished chart were calculated without asking the person who made it.
"Claude Dashboards," announced by Anthropic on October 8, 2026, is a feature for handling this flow through conversation. Let's look at what changed, who it helps and how, and how to ask first.
Contents
What changed: just ask, and you get a screen of up-to-date numbers
According to Anthropic's announcement, Claude Dashboards is a feature that builds a dashboard when you ask a question in everyday words. A dashboard is a single screen that lays out important numbers as charts and tables. When the underlying data changes, the numbers on the screen update too.
It connects to the large stores where companies keep their data (Amazon Redshift, BigQuery, ClickHouse, Databricks, Snowflake) and to sales management tools like Salesforce. Your team and Claude can edit the screen you made together.
It's a trial release (beta) for paid plans, and on the Enterprise plan for companies, it can't be used until an administrator turns it on. People connected to company data can now have an "always up-to-date screen of numbers" from a single question.
Who it helps, and how: you can check where the numbers come from
This feature helps people who use company data stores or sales management tools and are in a position to make decisions from numbers. If you use Claude personally without a connection to a data store, it doesn't directly affect you.
The biggest benefit for people starting from zero is that you can check where any number comes from. According to the announcement, clicking a number on the screen shows the query that pulled it from the data, and you can have Claude explain it. Each chart also shows how current its data is.
Using numbers in a meeting without knowing how they were calculated is worrying, but here you can ask on the spot, "How did you get this number?" Instead of taking numbers at face value, you can have Claude explain where they come from before using them.
How to ask first: explain what you want to decide before having it built
The announcement gives "Build a dashboard of this quarter's revenue by region" as an example request. That will produce a screen, but if you first explain what decision the screen is for, it's easier to discuss with Claude which numbers to lay out.
For example, the exchange looks like this.
You: At next month's sales meeting, I want to decide which region to add people to. I'd like a screen showing this quarter's revenue by region. Can you picture what the screen would look like? Claude: For example, this quarter's revenue by region at the top, a comparison with last month below that, and the month-by-month trend at the bottom. You: Nice. Since it's about deciding whether to add people, also show the growth rate. Once it's built, explain how you got the growth rate numbers too.
Rather than asking with just "build a revenue dashboard," talking from what you want to decide, with "I want to decide which region to add people to," makes it easier to get the numbers you need. Explain first what the screen is for deciding, and once it's built, ask how the numbers were calculated.
Summary
With Claude Dashboards, you can now get a screen of up-to-date numbers just by asking, and have Claude explain where any number comes from. The wait for someone who knows how and the worry of not knowing how things were calculated both shrink, so you can move from seeing numbers to making decisions right away.
Before laying out the numbers you want to see, explain what you're looking at them to decide. This idea comes up not only with dashboards, but every time you have Claude put something together, whether a table or a document.
Next time you have numbers put together, try starting with "here's what I want to decide from this".