How much does it cost to build an internal dashboard
An internal dashboard runs A$12,000 to A$40,000, and the cost is almost never the charts. It is getting the data somewhere trustworthy and agreeing what the numbers mean, which is a conversation, not a build.
Somebody exports three spreadsheets every Monday and pastes them into a fourth. That is the problem. The dashboard is the answer people reach for, and it is usually the right one, but not for the reason they think.
What it costs
| Typical range | A$12,000 to A$40,000 |
| Our six-week version | A$15,000 fixed, 4 weeks |
| What you get first | The five numbers your leadership actually asks about, refreshed daily, with a definition written next to each one. |
The low end is one data source you already control, daily refresh, and a handful of numbers. The high end is several systems that disagree with each other, near-real-time, and numbers finance will sign off on.
The three things that move the number
1. How many systems disagree. One source is a build. Three sources is a reconciliation project, because they will not match, and deciding which is right is a business decision that gets discovered halfway through the work.
2. Definitions nobody has written down. Does an active customer include someone who paused? Does revenue count the refund in the month of the sale or the refund? Every dashboard project turns into this conversation, and the ones that go well have it in week one.
3. How fresh it has to be. Daily is cheap. Hourly is more. Live is a different architecture. Almost nobody who asks for live needs it, and asking what decision changes because of the difference usually settles it in a sentence.
What to cut for a first version
- Live refresh. Daily is nearly always enough, and it is a fraction of the cost.
- Drill-downs. Ship the top-level numbers and see which one people ask about first.
- Custom charting. A table is often better and it is never ambiguous.
- Access control beyond one internal group, unless there is a real reason.
A dashboard that shows five numbers everyone agrees on beats one showing fifty that get argued about. The second kind stops getting opened after a month, and I have watched that happen more than once.
The line item to read twice
Data integration as one line. Ask how many sources, whether any of them disagree today, and who decides the answer when they do. If nobody has that authority, the project has a problem no developer can fix.
Common questions
Should I use Power BI or Metabase instead of building
If your data is already in one place and reasonably clean, yes, and it will be faster and cheaper. Building makes sense when the numbers need logic those tools cannot express, or when the dashboard is part of a product rather than an internal report.
Why do dashboard projects get abandoned
Because nobody agreed what the numbers meant, so the first time one looks wrong, trust goes and it never comes back. Write the definition next to each number and most of that risk disappears.
How fresh does the data need to be
Ask what decision changes if it is a day old. For most internal reporting the honest answer is none, and that answer saves a large fraction of the budget.
If you want the whole method rather than one answer, it is written up in the book. Five dollars, and it takes an evening: Turn Your Expertise Into a Real Tech Product. If you would rather just ask, book a call and you will get a straight answer on the call, including if the answer is do not build it.