Ask most owners how the business did last week and they will need a day and a few spreadsheets to answer. A business dashboard answers that question on one screen, using live data, so you can act while there is still time to change the outcome.
This guide covers what a good dashboard does, how to choose the numbers it shows, why data quality matters more than design, and when to use a standard reporting tool or build something custom.
What a business dashboard is, and is not
A business dashboard is a screen that pulls key figures from your systems and shows them in a form people can read in seconds. Sales pipeline, cash position, overdue work, customer issues: whatever drives your decisions.
It is not a report with every number you can find. It is not a wall of charts for a meeting room. A useful dashboard answers a small number of specific questions for a specific person, and shows them when something needs attention.
A sales manager, a finance lead and an operations manager usually need different views. Trying to serve all three on one screen is how dashboards become cluttered.
The hidden cost of manual reporting
In many businesses, reporting looks like this: someone exports data from three systems, pastes it into a spreadsheet, fixes the formats, builds charts and emails the result. It happens every week or month, and it quietly eats hours.
The time is only part of the problem:
- The numbers are old by the time anyone reads them, so problems are spotted late.
- Copying introduces errors, and nobody can easily trace where a figure came from.
- Different teams build their own versions, so meetings start with arguments about whose numbers are right.
- It depends on one person. When they are away, the report does not happen.
A dashboard connected directly to your systems removes the copying, so the people who used to build reports can spend that time acting on them.
Signs your business is ready for a dashboard
- You regularly ask the same questions and wait for someone to compile the answer.
- Key information lives in several tools: CRM, accounting, project management, support.
- Problems such as overdue invoices or delayed jobs are found by customers before your team notices.
- Managers spend part of every week building spreadsheets.
- You have grown past the point where the owner can see everything by walking round.
If your systems are not connected yet, that work often comes first. Our guide on how software integrations connect business systems explains the groundwork.
How to choose the right KPIs
The hardest part of a dashboard is deciding what to leave out. Work through these steps for each person or team who will use it.
- Start with decisions, not data. List the decisions this person makes weekly. Hiring, chasing payment, moving staff between jobs, adjusting marketing spend.
- Ask what they need to know to make each decision. That gives you the questions the dashboard must answer.
- Turn each question into one measure. "Are we going to hit the month?" might become pipeline value expected to close this month against target.
- Define it precisely. What counts as a lead? When is a job complete? Which date is used: order, invoice or payment?
- Set a threshold or comparison. A number alone means little. Show it against target, last period or a warning level.
- Agree what happens when it turns red. If nobody would act on a change, the measure probably does not belong on the screen.
Aim for five to eight measures per view. More detail can sit behind a click.
Starter KPIs for a growing business
Every business is different, but these are common starting points:
Sales
New inquiries by source, conversion rate from inquiry to sale, pipeline value by stage and average order or project value.
Cash
Invoices raised, overdue invoices by age, expected receipts this month and cash against forecast.
Operations
Work in progress, jobs overdue, average turnaround time and capacity booked for the coming weeks.
Customers
Open support issues, time to first response, complaints and repeat business.
Choose the handful that would change what you do this week. Leave the rest for a monthly review.
Data quality decides whether anyone trusts it
A dashboard built on messy data is confidently wrong, and once people catch it being wrong they stop looking. Before building, check the basics:
- Consistent entry. Are statuses, categories and dates filled in the same way by everyone?
- No duplicates. The same customer in three forms will distort every count.
- Shared definitions. Sales and finance must mean the same thing by "revenue".
- Required fields. If a measure depends on a field, make that field required at the point of entry.
- A named owner for each data source who fixes problems when they appear.
Fixing the processes that feed the data is often the most valuable part of a dashboard project. Our data migration and management work frequently starts here.
Standard reporting tools or a custom dashboard?
Many tools you already use have built-in reports. Check those first; they may be enough for one team. Beyond that there are two main routes.
Business intelligence tools
Products such as Power BI and Looker Studio connect to many data sources and suit people who like exploring data. They work well when you have someone comfortable building and maintaining reports, and when your data sources are supported.
A custom dashboard
A custom dashboard is designed for a specific audience and sits inside your own systems or portal. It makes sense when users are not technical, when data comes from sources that standard tools do not support well, when you need to act from the dashboard (approve, assign, chase) rather than only view, or when clients also need to see their own figures. This is the core of our dashboards and business systems work.
AI is starting to help here too. A dashboard can include a plain-language summary of what changed this week, or let a manager ask a question about the data in ordinary words. These features are useful when the underlying data is clean; they cannot fix data that is not. For more ideas, see our guide to practical AI use cases.
Rolling it out so people actually use it
A dashboard that nobody opens is just another report. Adoption takes a little planning.
- Build it with its users. Show early drafts to the people who will rely on it and ask what they would do differently after seeing each number.
- Replace something. Retire the old spreadsheet report when the dashboard goes live. Running both keeps the arguments about which is right.
- Use it in meetings. Open the dashboard at the start of the weekly review instead of a slide deck. People take the numbers seriously when leaders do.
- Set up alerts for the important thresholds, so people do not need to check constantly. An email or message when overdue invoices pass a level is often more useful than another chart.
- Review it every quarter. Remove measures nobody uses and add ones that new questions require.
Small changes based on real use tend to matter more than getting the first version perfect.
Common dashboard mistakes
- Too many charts. If everything is highlighted, nothing is.
- Vanity measures. Website visits feel good but may not drive any decision.
- No targets or comparisons, so people cannot tell if a number is good or bad.
- Building before agreeing definitions, which leads to rework and arguments.
- Nobody owns it. Dashboards need someone to keep measures relevant as the business changes.
- Ignoring mobile. Managers often check figures on a phone between meetings.
Frequently asked questions
What should a business dashboard show?
It should show the small set of measures that drive decisions for a specific person or team, compared against a target or previous period, with detail available behind a click.
Can a dashboard combine data from accounting and our CRM?
Yes. Dashboards commonly combine accounting tools such as Xero or QuickBooks with CRM, operations and support data, as long as each system offers access to its data.
Should we use Power BI or build a custom dashboard?
Business intelligence tools suit teams with someone who enjoys building reports. A custom dashboard suits non-technical users, unusual data sources, or when people need to act from the screen.
How often should dashboard data update?
As often as you act on it. Sales and operations figures often benefit from updates through the day, while financial summaries may only need a daily refresh.
What if our data is messy?
Fix the most important sources first. Agree definitions, remove duplicates and make key fields required. A dashboard built on unreliable data will lose trust quickly.
Start with Monday morning
Write down the five things you would want to know first thing on a Monday, before your first meeting. Then find where each one lives today and how long it takes to get. That list is the specification for your first business dashboard.
Start small, get people using it, and add views as new questions come up.