Until yesterday the order was fixed. Curious about data? File a ticket or write SQL. Need an explainer video? Flip slides or outsource it.

On October 8, Anthropic put Claude Dashboards and Claude Motion into beta to change that order. Dashboards turn plain-language questions into live dashboards. Motion turns text and charts into code-based animations. The point is not that they look good. It is that every chart shows its query and refresh time.

Dashboards: ask, and a dashboard appears

The structure is simple. Connect a data platform, ask in plain language.

Connect: Amazon Redshift, BigQuery, ClickHouse, Databricks, Snowflake
         + business connectors like Salesforce

Ask: "How do this week's signups compare with last month?"
  → Claude pulls the data and builds the dashboard
  → The dashboard stays current as the data changes

What matters is not the pretty chart but verifiability. Click any number to see the query behind it, or ask Claude to explain it. Each chart shows when its data was last refreshed. That is what AI-made numbers owe you.

The use cases are practical. Quick exploratory questions like "which sales region slipped last quarter?" When deeper analysis is needed, send the dashboard straight to Amplitude, Grafana, Hex, Mixpanel, Omni, Perplexity, PostHog, or Sigma. Looker, monday.com, and Tableau integrations are coming soon.

This may look like the RAG chatbot from the internal-docs chatbot post, but the job differs. A RAG chatbot finds answers in documents. Dashboards pin a number's source and freshness on screen.

Motion: animation without a video-generation model

Motion looks like an AI video tool at first glance, but it is built the opposite way. Instead of generating footage with a video model, Claude writes code that animates your text, charts, shapes, and images.

Input: a quarterly report, a board-deck chart, a product walkthrough
  → Claude writes animation code (plays like a short video)
  → Adjust it in the editor or ask Claude to change it
  → Download as an MP4 file

Property: no generated footage, no AI-generated people.
          Every word, number, and timing stays editable.

Type /motion in the message box to bring up the option. Turn a quarterly report into a 30-second all-hands explainer, add motion to a chart, or make onboarding walkthroughs. To take it further, open the result in Adobe, Descript, HeyGen, Higgsfield, invideo, Luma AI, or Runway. Canva and Captions support is coming soon.

This matches the principle from the generative AI content post. With an original idea and editing standards, AI adds speed. Without them, only plausible-looking output remains. Motion guarantees editability as code.

Check the beta scope first: this is not for everyone yet

Clear up the biggest likely misunderstanding first.

Claude Dashboards: beta on paid plans
Claude Motion: beta on Team and Enterprise plans
Enterprise: both off by default → enable in Organization settings > Artifacts

Graduated with this launch: Docs, Slides, Design (all plans incl. Free)
  → 45M+ docs, decks, and designs created so far
  → Enterprise: on by default October 15 (or turn on today)

Standalone Claude Design (claude.ai/design): runs until December 14 only
  → Migrate via "Migrate team design systems" on the Artifacts page

So not every reader can try this today. Enterprise admins start by enabling it. Individual users can start with the graduated Docs, Slides, and Design improvements (external sharing, PowerPoint and PDF exports, editable Google Slides files, mobile editing).

A flow from verification to visualization to explanation

What really changes is not the tool but the sequence. Reporting, data analysis, and content creation join one flow.

Step 1 verify: pick 3 operating metrics and fix their definitions
  e.g. weekly signups, paid conversion, churn
  → Check each query and refresh time in Dashboards

Step 2 visualize: question → dashboard → deepen in BI tools
  → Light exploration in Claude, deep analysis in existing tools

Step 3 explain: turn one dashboard scene into Motion
  → A 30-second explainer for all-hands or onboarding

As AI makes more artifacts, human work moves earlier, not away. Fixing metric definitions, reading queries, checking numbers before sharing. Like the Excel automation post shows, cutting repetitive work and making numbers trustworthy are two sides of one job.

CodeBridge Mini Lab: spec three metrics today

Even without beta access, you can prepare now.

1. Pick 3 metrics:
   - Three numbers you check every week
   - One-line definition each (e.g. "signup = email-verified account")

2. Write 3 verification questions:
   - What query stands behind this number?
   - When was it last refreshed?
   - Which tool takes the deep-dive analysis?

3. Draft a 30-second explainer script:
   - One number + one reason + one next action
   - Paste-ready when Motion arrives

With this spec, you can ask "how do this week's signups compare with last month?" the day Dashboards opens. Workflows can be designed before tools arrive.

Conclusion: artifacts from AI need provenance first

One line to summarize.

When AI moves from answers to artifacts, trust comes from provenance.

Dashboards ship queries and refresh times. Motion ships editable code. Both say "check how this was made," not "trust it because AI made it." Some readers cannot use the betas yet, but metric definitions and verification flows can be set up today. That is the minimum preparation for the dashboard era.

Further reading

References

Go deeper with a course

If you want to start by automating repetitive metric cleanup and report work with AI, the Cursor AI flow from Excel cleanup to web apps connects directly to this post's dashboard workflow.