How to build a Claude dashboard

To build a dashboard in Claude on your own business data: connect your systems to Tugger, create a Claude Project and save your business rules in it, ask Claude to build the dashboard from your Tugger data, then save the finished dashboard back into the project. From then on you refresh it with a single prompt instead of rebuilding it.

Why rebuilding costs more than refreshing

Dashboards built in Claude are brilliant. Rebuilding them every month is the expensive habit this guide breaks.

When you ask Claude to “build me a dashboard”, it re-learns your business rules, re-queries your data and regenerates every line of code from scratch. The result is impressive, which is exactly why people ask again the following week. And the week after. Do that with a full rebuild each time and the tokens add up fast.

The fix isn’t a different tool. It’s not rebuilding. The dashboard itself is cheap. The rebuilds are the cost. Build it once, save it, and from then on you only ever pay for fresh numbers.

First, the bit that makes this work

On its own, Claude can’t see your business data. That’s where Tugger comes in. We pull your systems, your accounts platform, your CRM, your job system, into a secure, managed warehouse and give Claude a safe connection to it. So when your dashboard needs refreshing, Claude reaches into your actual numbers and updates it from them. That connection is the whole trick.

What you’ll need

• A Tugger account with your business systems connected. Xero, HubSpot, Simpro or whatever else you’re running, from a library of 60+ connectors.
• Claude connected to Tugger, so it can query your data in natural language. The walkthrough below covers it if you haven’t done this yet.
• A Claude plan that includes Projects. The paid plans do.

Four steps, once

Everything in this section happens one time. Get these right and every month afterwards is a single prompt.

1. Work inside a Claude Project

Create a Project in Claude and put your business rules in the project instructions. What counts as a sale, how you define margin, which cost centres matter, anything a new financial controller would need explaining on day one. Claude is not a mind reader, but tell it once here and it remembers in every chat.

2. Build the dashboard, once

In a chat inside that project, describe what you want to see. For example:

Using my Tugger data and the rules saved in this project, build an interactive HTML dashboard of monthly job profitability by cost centre. Revenue, costs and margin, with a trend across the last six months.

Or for the finance side:

Build an interactive HTML dashboard of monthly sales and gross margin by customer group from my Xero data, using the definitions saved in this project.

More on what Claude can do with your accounts data in Xero AI Insights.

3. Tweak it with changes, not rebuilds

Get it right by asking for the specific change. “Add a split by region”, “make the variance column red when negative”, “drop the pie chart”. Each tweak edits what’s there rather than starting over.

4. Save it to the project

The dashboard appears alongside the chat as its own panel. Download it from there using the download button at the top of the panel, then upload the file into your project’s knowledge section, the same place your rules live, naming it something obvious like Job Profitability Dashboard.

This is the step that makes everything else work. Every future chat in the project can now see the dashboard and update it, rather than starting from a blank page.

The refresh

Tugger refreshes your data on a schedule, so when you want the latest picture it’s one prompt.

Refresh my Job Profitability Dashboard with the latest data from Tugger.

Claude pulls the fresh figures through Tugger and drops them into the saved dashboard. The layout, the code and your business rules all stay put. Only the numbers move.

And it’s not just dashboards. The same trick works for anything you produce on a rhythm: a monthly reconciliation, a board pack, a set of management accounts. Build the format once, save it to the project, then refresh it each month instead of describing it all over again. Then, each month:

Run the July reconciliation in the saved format.

Rule of thumb: if you’re about to type “build”, try “refresh” or “update” first. It’s nearly always what you actually want, and it costs a fraction of the tokens.

This isn’t theory

Our own CFO runs his month-end this way. Board pack, management accounts, consolidation across entities, all built through Claude on Tugger data and refreshed month after month. The first month took some setting up, teaching Claude the business rules, the same way you’d brief a new financial controller.

But here’s the difference. Train a person and the knowledge walks out the door when they do. Train Claude once, and it stays trained.

Four ways to keep tokens down

• Ask for answers, not data. “July margin by customer group” runs as one aggregated query through Tugger’s semantic layer. “Show me all my data” pulls thousands of rows through the conversation.
• Name the period. A question scoped to one month costs less than one that scans your whole history.
• One saved format per job. A margin dashboard, a recon format, a board-pack layout, each refreshed on its own, beats one giant rebuild that does everything.
• Change it, don’t recreate it. When something needs to look different, ask for that one change. Claude edits the saved version rather than starting from a blank page.
  

Want to build yours with your own data?

Everything in this guide runs on your real numbers. Connect your systems to Tugger and your first dashboard is a conversation away. Setup is managed for you, so there’s nothing to build. Tugger is ISO 27001:2022 certified.

Try Tugger free for 10 days or book a demo

What to do next

• New to Tugger? Book a demo and we’ll build the first dashboard with you, your actual numbers on screen. Or start your free 10 day trial and dive straight in.
• Already using Tugger? Your data’s in the warehouse. Create the project, save your rules, and build, or ask our team to walk through your first one with you.

A quick note on accuracy. AI is a powerful assistant, not a