Business Dashboard for Owners: The Numbers Worth Watching

Most business owners have data, but it's scattered: sales in a point-of-sale app or payment gateway, leads in WhatsApp and spreadsheets, subscriptions in an admin's notes. As a result, big decisions often get made on gut feeling. A business dashboard pulls those numbers into one place. But a dashboard is only useful when the numbers are right and their meaning is clear to everyone who reads them.

This article covers which numbers an owner should watch, how to write metric definitions, and why 'not available' beats a misleading zero.

Start with questions, not charts

A common mistake is to put every available data point on the dashboard. You end up with a screen full of charts that nobody opens. It's better to start with the questions you genuinely ask every week, such as:

• How many new leads came in this week, and from where?
• How many of them ended up paying?
• What is revenue this month compared with last month?
• Are existing customers coming back or renewing?
• Are there complaints or technical problems still waiting to be handled?

Every chart on the dashboard should answer one of those questions. If a chart never changes a decision, it can go.

Four groups of numbers to watch

• Funnel. How many people sit at each stage, from visitor or lead to paying customer. The funnel shows where prospects drop off most.
• Revenue. Total sales per period, split by product or service. For subscription businesses, also track monthly recurring revenue (MRR).
• Retention. What share of customers from a given month are still active or buying again in later months. Cohort analysis makes it easy to compare groups of customers.
• Issues. The number of open complaints, bug reports, or problem orders. This one is often forgotten, yet it's the fastest signal that something is broken.

For a small business, these four groups are usually enough to begin with. More detailed operational numbers can be added once the habit of reading the dashboard has formed.

Write a definition for every metric

'New leads' sounds obvious until two people count it differently. Does someone who submitted the form twice count as two? Do the team's test entries count? That's why every metric needs a written definition that includes:

• The metric's name and the question it answers.
• How it's calculated, in plain language.
• The data source, such as the payments table or the lead list in your CRM.
• The period and time zone, for example per calendar day in Western Indonesian Time.
• What's excluded, such as test transactions, cancelled orders, or refunds.

Ideally these definitions can be read straight from the dashboard, for instance through an info icon next to each number. That way new staff and your accountant read the figures the same way.

'Not available' is more honest than a fake zero

Imagine the dashboard shows zero revenue for today. Were there really no sales, or has the payment data simply not synced yet? For an owner, those are very different situations: one is a sales problem, the other a technical one. A good dashboard tells them apart.

The rule is simple: if the data hasn't arrived, the source isn't connected, or the period hasn't finished calculating, show 'not available' rather than zero. A zero only appears when the answer really is zero. This small rule prevents needless panic and decisions pointed in the wrong direction.

The same goes for percentages. A 0% conversion rate from zero leads tells you nothing. It's more honest to say there isn't enough data to calculate it yet, and wait until the numbers are large enough.

A real example: Numekara's seven dashboards

At Numekara (numekara.com), the education business we run ourselves, the owner monitors seven dashboards covering leads, users and subscriptions, revenue, product usage, issue reports, and system health. Website, payment, and subscription data is summarised daily into readable charts and figures, and every metric has a written definition.

They include a funnel from lead to enrolment, revenue and subscription MRR, and customer cohort retention. When data is missing, the dashboard says 'not available' instead of zero. The charts are kept lightweight, with no extra charting library, and the data can be exported to CSV when it needs further work.

What's worth copying isn't the number of dashboards but the habits behind them: every figure has a definition, missing data is admitted openly, and any number can be traced back to the raw data when something looks off.

Next steps

1. Write down the five business questions you ask most often.
2. For each question, choose one metric and write its definition.
3. Check whether the data is already recorded in one place. If not, tidy up the record-keeping before building a dashboard.
4. Start with something simple, even a spreadsheet, and move to an automated dashboard once the metrics prove useful.
5. Review your metric list every quarter and drop the ones that never inform a decision.