The request for a business dashboard is always reasonable and always the same. One screen. Our actual numbers. Updated automatically. Then the quote arrives talking about pipelines and warehouses and modelling, and it costs five times what a chart ought to cost, and it feels like being sold complexity.
It is not. The chart genuinely is cheap. Everything that has to be true before the chart can exist is the project, and that is most of the cost. Understanding this before you buy is the difference between commissioning the right thing and paying for a screen that nobody trusts.
Why the chart is the cheap part
Take a simple ask: revenue this month against last month, by product line.
Drawing that, once the data exists in a clean table, is an afternoon. Getting to that clean table means reaching into your accounting system and your sales system, discovering that product lines are named differently in each, finding that one of them has no way to export on a schedule, deciding what counts as revenue given the credit notes, working out what happens to refunds, handling the three months where somebody typed the product name by hand, and agreeing whether a sale counts on the order date or the invoice date.
None of that is visible in the finished dashboard. All of it has to be right, and none of it can be skipped, which is why a proposal that is all chart and no plumbing should worry you rather than please you.
Business dashboard cost: the short answer
| Scope | What it involves | Illustrative cost |
|---|---|---|
| One system, clean data | Everything already lives in one place and is tidy. Connect, model lightly, build the views. | $5,000 to $15,000 |
| Two or three systems | Connecting each, reconciling how they name things, agreeing definitions, a scheduled refresh. | $15,000 to $45,000 |
| Several systems, some messy | The above plus real cleaning, handling history, a proper place for the combined data to live. | $45,000 to $120,000 |
| Company-wide, many users and roles | The above plus permissions, self-service, documentation, and a maintained set of agreed definitions. | $100,000 to $300,000 and up |
Illustrative ranges from the kind of work we quote, not a price list. As a rough split: about a fifth of the effort is the dashboard, and the rest is connecting, cleaning and agreeing. Budget ongoing cost too, since sources change their interfaces and someone has to notice.
The five things that move the price
- How many systems. Each one is a connection, credentials, a schedule, and a thing that will change without telling you. The jump from one system to two is bigger than the jump from two to three.
- Whether the data is any good. Free-text fields where a list should be. Customers entered three times with slightly different names. Dates in two formats. Nothing wrong with any of it operationally; all of it must be resolved before a number can be trusted.
- Whether anyone agrees what the numbers mean. The genuine hard part, and it is not technical. More on this below.
- How fresh it has to be. Daily is straightforward. Hourly is more. Live is a different architecture and costs accordingly. Almost nobody who asks for live needs live, and asking why usually saves a large sum.
- Who needs access and to what. One screen for three directors is simple. Fifty people who must each see only their own region is a permissions model, and permissions models are real work.
The argument nobody warns you about
This is the part that delays dashboard projects, and it is never in the plan. You will end up in a meeting about what counts as a sale.
Is it a sale when the order is placed, when it is invoiced, when it is paid, or when it is delivered? Sales say the first, finance say the third, operations say the fourth, and each of them is right for their own purposes. Same for what counts as an active customer, what a lead is, whether returns come off this month or the month of the original order, and whether an internal transfer counts at all.
Nobody has had to write these down before, because each department has quietly used its own definition and it has never mattered until one screen tried to show a single number to everyone. Expect this to take longer than the technical work and to need someone with authority to decide. The dashboard cannot resolve it, and a dashboard built before it is resolved will be argued with rather than used, which is the most common way these projects fail.
Tools, honestly
The tool matters far less than anybody selling one will suggest. All the mainstream options draw a competent chart. Choose on fit, not on features.
- What your team already has. If your business runs on one of the big office suites, the dashboard tool that comes with it is capable, already licensed, and already familiar. Starting anywhere else needs a reason.
- Whether people will use it. A tool people already know beats a better tool they will not open.
- How it is licensed. Per user adds up quickly at scale. Check the arithmetic at the number of viewers you will actually have in two years.
- Whether you can leave. Definitions and logic locked inside one vendor's format are expensive to move later.
- Whether your existing systems already do it. Genuinely check first. Accounting packages, CRMs and e-commerce platforms all ship reporting that is better than people assume, and if your data lives in one system, that reporting may be the entire answer for nothing.
Start with three numbers, not thirty
The most reliable way to waste money here is to ask for everything. It feels efficient to gather every metric while someone is already connecting the systems, and it produces a screen so dense that nobody reads it, which fails in exactly the same way as having no dashboard at all.
A better brief is uncomfortably small. Pick the three numbers you would want if you could only see three, and be strict: a number belongs on the list only if seeing it would change something you do. Most metrics fail that test. They are interesting rather than useful, and interesting numbers are what fill up dashboards nobody opens.
- Write the three questions first, in plain words, before anyone mentions a tool. Not revenue, but is revenue ahead of where it was this time last year.
- Say what you would do differently if each number were bad. If there is no answer, take it off the list.
- Build only those, and use them for a month before adding anything.
- Let the next questions come from use. The fourth and fifth numbers you actually want are almost never the ones you would have specified at the start, which is the strongest argument for building small.
This also cuts the cost substantially, because three numbers frequently need fewer systems connected than thirty do, and the connections are the expensive part. Starting narrow is not a compromise here; it is a cheaper route to something people use.
A dashboard will not fix messy data
Worth saying plainly, because it is the most expensive misunderstanding in this area. A dashboard is a window. If what is behind the window is inconsistent, the dashboard shows you inconsistency, faster and in colour.
The pattern is familiar: the dashboard launches, someone notices a number looks wrong, it is wrong, everybody loses confidence, and within two months nobody opens it. Meanwhile the underlying problem, which was that half the team does not fill in the customer type field, is exactly where it was.
Sometimes the honest answer is to fix the process before building anything, and the visible cost of a dashboard is what finally makes that worth doing. If most of the work turns out to be moving and cleaning data between systems, that is data pipelines rather than a dashboard project. If what you actually want is a reliable number sent to you every Monday rather than a screen you visit, reporting is cheaper and often more useful.
What you get for the money
- Connections to your systems, running on a schedule, with someone alerted when one breaks. They do break.
- A place the combined data lives, so the dashboard is not repeatedly interrogating your live systems and slowing them down.
- Cleaning and matching rules, so the same customer is one customer.
- Written definitions, agreed and recorded, so the argument above happens once rather than every quarter.
- The dashboard itself, which is the small, visible, satisfying part.
- A handover, so your team can add a view without ringing anyone.
Not for you if
Two questions worth asking any supplier: what proportion of this quote is the dashboard itself, and who decides what a sale means? If the first answer is most of it, they have not understood the work. If they have no answer to the second, they have not done this before.