01 · Reality check
What Claude actually does well here
Good at
- Turning an uploaded spreadsheet into an interactive artifact quickly
- Choosing which chart actually answers the question you are asking
- Writing dashboard code you can deploy for live data
- Producing real spreadsheet and chart files you can share
- Cleaning and reshaping messy data before it ever reaches a chart
Not the right tool for
- Connecting to a live database on its own from an artifact
- Guaranteeing its calculations are right, so verify the numbers
- Knowing which metrics matter to your business unless you say
- Replacing a proper BI tool for governed, org-wide reporting
- Handling data volumes beyond its file limits
02 · The method
Step by step
- 1
Decide: snapshot or live
A one-off analysis becomes an artifact in minutes. Something that must refresh from a live source needs code you deploy. Choosing wrong wastes the most time here.
- 2
Start with the question, not the chart
Tell it the decision the dashboard should support. Dashboards built from questions are useful; dashboards built from available columns are noise.
- 3
Clean the data first
Upload the file and ask it to identify problems: missing values, inconsistent formats, duplicates. Charting dirty data produces confident, wrong pictures.
- 4
Ask for an artifact for the fast version
Request an interactive dashboard as an artifact. You get something you can click and share right away, which is usually enough to learn whether the design is right.
- 5
Verify the numbers against the source
Check a few figures by hand against the raw data. Calculation errors in a well-designed dashboard are especially dangerous because they look authoritative.
- 6
Graduate to deployed code if it needs to live
Once the design is proven, have Claude write it as a real application connected to your data source, and deploy that.
03 · Use this now
Copy-paste prompt for a dashboard artifact
Here is my data file. The decision this dashboard needs to support is: [what you actually want to decide or monitor]. The people using it are [who] and they care most about [metrics]. First, inspect the data and tell me what is wrong with it: missing values, inconsistent formats, duplicates, anything that would distort a chart. Then propose the four or five views that genuinely answer the question, explaining why each one and which chart type fits. After I approve, build it as an interactive artifact. Show me the calculation behind each headline number so I can verify it against the source.
04 · Avoid these
Common mistakes
- Charting before cleaning, which produces confident and wrong pictures.
- Building every chart the data allows instead of the few that answer the question.
- Trusting headline numbers without checking the calculation against the raw data.
- Expecting an artifact to refresh from a live database, which it does not do on its own.
- Publishing an artifact containing sensitive data, since publishing creates a public link.
05 · Questions
Frequently asked questions
Can Claude build an interactive dashboard?
Yes, using artifacts, which give you an interactive view you can use and share straight away. Anthropic makes artifacts available on all plans, provided code execution is enabled. For a dashboard that updates from a live data source, have Claude write the code and deploy it yourself instead.
Can Claude connect to my live database?
Not from an artifact, which works from the data you supplied. For live data you have two routes: have Claude write an application you deploy against your database, or use a connector through MCP if one exists for your system. The artifact route is for analysis, not live monitoring.
Can Claude create Excel files and charts?
Yes. Its code execution and file creation feature produces real .xlsx files, charts and other documents, and Anthropic makes this available on all plans including Free. Created files are capped at 30 MB, and it can save output to Google Drive.
How do I share a Claude dashboard?
Artifacts can be shared, and the mechanism differs by plan: Free, Pro and Max can publish an artifact to a public link, while Team and Enterprise share within the organisation. Be careful publishing anything containing sensitive or personal data, since publishing creates a public link.