It’s the Monday forecast call, and your CRO asks why mid-market win rates dropped last quarter. Nobody on the call knows. Somebody says they’ll pull it. The request lands in an analyst’s queue that’s already full, and the answer shows up the following week, after the decision it was supposed to inform.
I spent years as an SVP in Revenue Operations, and I lived inside the gap between a good question and an answer people trust. Anthropic launched Claude Dashboards on October 8, and it’s aimed straight at that gap. I think it’s one of the most useful things they’ve shipped this year for anyone running a B2B company. It also makes it easy to build a wrong number that refreshes itself and can be shared with anyone. You need a plan for both.
What Anthropic launched
Claude Dashboards turns a plain-English question about your company’s data into a dashboard that stays current as the data changes. You connect Claude to your data warehouse, whether that’s Snowflake, BigQuery, Databricks, Amazon Redshift, or ClickHouse. It also pulls from apps you’ve connected to Claude, and Salesforce is the one Anthropic calls out. Ask for open opportunities by stage and close date, and Claude writes and runs a SQL query for each chart, then lays out the page.
Two design choices matter more to me than the charts. Click any number to see the query behind it, or ask Claude to explain it. And every chart shows when its data was last refreshed. If you’ve ever had a board member pick apart a pipeline number you couldn’t defend, you know why that matters.
The other launch, Claude Motion, turns your own charts and text into a short animated video you can download as an MP4. It animates your content with code, so there’s no generated footage and no fake people, and you can change any number afterward. Fewer people will care about Motion. I’ll come back to it.
Both are in beta, so expect some rough edges. Dashboards is available on Pro, Max, Team, and Enterprise plans, and Motion on Team and Enterprise. On Enterprise accounts, they stay off until an admin turns them on. Dashboards also counts against your plan’s usage limits.
Where it pays off in a B2B company
Your warehouse already holds years of bookings, renewals, product usage, and support history. In most companies I know, only two or three people can write the SQL to query it, and everyone else’s questions wait in their queue.
If I were running sales at a $60 million software company, the first thing I’d test is whether deals that finish a technical evaluation in the first 30 days close faster and bigger. That used to take a ticket and a week of waiting. Now you ask Claude to compare deal cycle and deal size with and without an early evaluation, split by segment, and you get a first answer in the same sitting. It might be wrong. Fine. Ask Claude to explain the query, notice that it counted closed-lost deals, and fix it before your coffee gets cold.
Renewals, same story. Your head of customer success wants one page with every account renewing in the next 120 days, its contract value, its usage trend, and its open support tickets. That data starts in three systems, so the page usually ends up as somebody’s spreadsheet, stale by Wednesday. If all three already feed your warehouse, Claude can build that page once and keep it current. Then the renewal meeting can start with which accounts to save.
Motion is smaller, but it helps with the other half of the job, which is getting people to understand the numbers. Take the commission plan. Every year it goes out as a PDF, and every year reps skim it and then spend the first quarter disputing their payouts. A 30-second video that walks through one example deal won’t end the disputes. It might cut them down. And when finance changes an accelerator two days before kickoff, RevOps can fix the number in the video without calling an agency.
The risks I’d watch
Metric definitions worry me most. If I had to bet on what sinks a rollout like this, it’s two VPs walking into the same meeting with two different churn numbers, both from Claude, both looking official. Every B2B company has at least two versions of “pipeline” and three versions of “churn.” Say a sales manager asks Claude for net revenue retention, and Claude picks a definition your finance team doesn’t use. Now you’ve got the wrong number I warned about at the top, and someone has already shared it. The visible query only helps if someone checks it. Most sales managers will take the chart at face value. I’d have RevOps or finance own a short written list of official definitions and check the first round of dashboards against it.
Access worries me next. A dashboard is private by default, but you can share it, and with admin approval it can go outside the company. Revenue data includes what every customer pays, and I wouldn’t let anyone connect Salesforce with their own admin login just because it’s quicker. Decide who can connect the warehouse and Salesforce, and with what permissions, before anybody builds anything. Enterprise admins can limit Dashboards to specific groups, and I’d start narrow.
Then there’s sprawl. When dashboards get cheap to make, people make a lot of them. Six months from now you could have forty pages that disagree with each other and with your BI tool. Anthropic pitches Dashboards for quick, exploratory questions. For deeper work, you can send a dashboard on to tools like Hex, Sigma, Mixpanel, or Grafana, with Tableau and Looker coming. I think that’s the right split, and I’d be blunt about it internally. Use Claude to answer the question fast, then move anything that becomes a standing company metric into the system your team already governs.
A head of data could fairly object that they spent two years building clean metric definitions into a governed BI tool, and this looks like a way around all that work. But the warehouse is still the source, and every query is visible. Today’s alternative is a sales leader exporting a CSV and doing the math in a spreadsheet nobody else can check. I’d take the visible query.
What to do Monday
Have your Claude admin turn on Dashboards for a small group (the toggle is in the Artifacts section), say RevOps and finance, and connect your warehouse and Salesforce with read-only access.
Write down your official definitions for pipeline, bookings, churn, and net revenue retention. Then build the five dashboards your forecast call asks for most and check every query against that list.
Set one sprawl rule and name the person who enforces it. Mine would be that anything people ask for twice moves into your governed BI tool.
Once the numbers hold up, try Motion on the one chart your board always asks about. The companies that answer their own questions in the meeting will make better decisions than the ones still waiting on a ticket.
Thank you for reading. If you enjoyed this article, please share it with others.
We were supposed to get rain here these last two days in Los Angeles and I was excited to take Magnus walking in it (he LOVES walking in the rain). Alas, we didn’t get anything. Nothing at all. So - here are two photos of him waiting patiently to go on a walk. And yes - he still really needs a bath. ;)
