Claude can chart it.
Can you trust it?

I can usually make a chart look convincing before I can prove it answers the right question. That gap is where this launch gets interesting.

On October 8, Anthropic introduced Claude Dashboards and Claude Motion in beta. Dashboards brings connected data into an inspectable visual workspace. Motion turns supplied material into editable animated explainers. Docs, Slides and Design also left beta and became available on Free. [1]

My read: the useful opportunity is fewer handoffs between figuring something out and explaining it. The risk is that a polished output gets approved faster than its reasoning.

Dashboards: the query is part of the product.

Anthropic names Redshift, BigQuery, ClickHouse, Databricks and Snowflake as data sources, alongside connected apps such as Salesforce. You can request filters or a different time grouping in chat. Dashboards start private and count against plan usage. Enterprise owners must enable the feature. [2]

For Claude data visualization, the most valuable habit is opening the query before sharing the chart. “New customers” might count accounts created, subscriptions started, or invoices paid. Those can produce three perfectly plausible charts with three different answers.

I would start with a question whose answer I already know. Check one period against the source. Then try a refund, a duplicate account and a timezone boundary. If the totals disagree, fix the definition before asking for nicer colors.

What remains unverified: the reviewed documentation does not specify a guaranteed refresh interval, maximum dataset size or a full permissions model for every connector. A visible refresh timestamp is useful; “live” should not be read as a real-time service-level guarantee. Confirm those requirements in your environment.

Motion: revision is the selling point.

A wrong number halfway through a video is an expensive little discovery. An animation built from editable elements has an obvious appeal: correct the number, adjust the timing, keep working.

Claude Motion accepts your reports, data or images as source material. Specify the audience, destination and approximate duration. The editor and chat support revisions; MP4 is a documented export. Longer, more complex animations consume more usage than a typical message. Motion is enabled by default on Team and disabled by default on Enterprise. [3]

I would use it first for an explanation with a narrow job: show the three setup steps a new customer keeps missing. Give each step enough screen time to read. Watch without narration. If the sequence still needs a presenter to explain it, the animation has more work to do.

The reviewed docs do not establish export resolution, maximum duration, audio controls or detailed brand-management features. Test your required format before building a campaign around it. A 30-second prompt example is not a published duration limit.

Three workflows I would actually try.

For marketers: investigate the conversion gap.

Ask for signups by channel, then activation by the same channel and period. Define activation and attribution first. A channel bringing cheap signups may produce very few customers who get started. Review the query with whoever owns the tracking. Only then turn the finding into a short team update. This is a proposed workflow, not a measured conversion improvement.

For founders: make the weekly update reproducible.

Choose three numbers that affect a decision. Specify their definitions once, check the underlying records, and record the refresh time when you share. If you animate the update, include the period on screen. An exported video is a snapshot even when the dashboard behind it changes.

For business teams: explain one recurring exception.

Use approved source material to storyboard what happens when an import fails or an opportunity stalls. Ask a colleague unfamiliar with the process to follow it. Measure whether they understand the next action. The number of animations produced is a much less useful success metric.

Keep exploring.

For another look at connecting signals to business decisions, read my Nectar Social Field Note. For turning an explanation into a useful presentation, see Gamma and the partnership pitch.