You want a grip on your numbers. Revenue, stock, outstanding invoices, capacity: right now it is scattered across separate reports, exports and spreadsheets, and you rebuild the same overview by hand every Monday. A dashboard solves that. But “having a dashboard built” means two very different things, and most providers tell you only one half of the story. This guide explains the difference, names real prices and helps you choose which route fits your question. Without the sales pitch.
What is a dashboard?
A dashboard is a single screen that brings your most important figures and information together, so you see at a glance where you stand. It pulls data from different sources, turns it into charts, tables and numbers, and refreshes automatically. Instead of clicking open ten separate reports, you look at one place.
So far everyone agrees. But under that one term sit two kinds of dashboard that are built differently, cost differently and serve a different purpose. Anyone who misses that distinction often buys the wrong thing. That is why every good decision starts here.
Reporting dashboard or custom application dashboard?
This is the most important question in the whole guide. A reporting dashboard makes existing data visible and is read-only: you look, filter and analyze, but you change nothing. A custom application dashboard is a screen inside your own software where you not only look but also act: approving an order, changing a status, assigning a customer.
The entire search results page for “have a dashboard built” is almost exclusively about the first kind: Power BI studios that visualize your existing figures nicely. That is fine work, but it is not the only answer. If your dashboard is part of how you work, and not just a view of how things are going, then you need custom. Choose based on what the user has to do with the dashboard.
| Reporting dashboard | Custom application dashboard | |
|---|---|---|
| Purpose | Look, analyze, decide | Work: look and act |
| Example | Revenue KPIs, sales report, board overview | Order screen, planning, customer management |
| Action possible? | No, read-only | Yes: edit, approve, assign |
| Typical tool | Power BI, Looker Studio, Tableau | Custom web application |
| Part of | Your BI layer | Your own software or portal |
| Price indication | €2,500 to €7,500 | €5,000 to €50,000+ |
Not sure whether you actually need a whole platform instead of just a dashboard? Read the difference between a web app, a SaaS and a custom platform. And if the dashboard becomes part of an environment where customers or staff log in, look at customer portal examples.
What does it cost to have a dashboard built?
Having a reporting dashboard built costs roughly €2,500 to €7,500. A custom dashboard inside an existing application ranges from €5,000 to €15,000, and a full custom platform with a dashboard, roles and actions from €20,000 to €50,000 or more. The price almost never turns on the charts themselves, but on the number of data sources, the quality of that data and the connections between them.
| Type of dashboard | What you get | Indication |
|---|---|---|
| Reporting dashboard (Power BI, Looker Studio) | Existing data visualized, read-only insight | €2,500 to €7,500 |
| Custom dashboard in an existing app | Custom screen in your own web application | €5,000 to €15,000 |
| Full custom platform with dashboard | Dashboard plus actions, roles and connections | €20,000 to €50,000+ |
Do not forget the running costs. A Power BI dashboard needs a license per user per month (see Power BI pricing from Microsoft), plus maintenance when your data sources change. For custom, budget 10 to 20 percent of the build price per year for hosting and maintenance. Poor data quality makes both more expensive than needed: Gartner estimates that organizations lose an average of $12.9 million per year to it, mainly through decisions based on outdated or conflicting figures (Gartner). A dashboard on top of messy data only shows that mess faster.
The full breakdown of a custom dashboard as part of an application is in our web application cost guide. Want the broader custom prices side by side? They live in custom software costs and prices.
Build it yourself or have it built?
Building a dashboard yourself or having it built is a classic make-or-buy choice. For a simple read-only overview you can get far yourself: Power BI and Looker Studio are accessible, and Looker Studio is free on top of that. Connect your sources, drag in the charts and share the result. That works fine as long as the data is clean and the logic stays manageable.
The tipping point comes at three moments. When you have to combine data sources that do not work together on their own. When you want to manage permissions, so not everyone sees everything. And when you want to act in the dashboard instead of only looking. The tools for building it yourself are maturing fast, by the way: Gartner expected that by 2025 around 70 percent of new business applications would be built with low-code or no-code, up from less than 25 percent in 2020 (Gartner). Even so, that line does not move endlessly.
Torn between a no-code solution and real custom software for an operational dashboard? Weigh it explicitly, for instance against Airtable or Notion as a platform. Custom only pays off once you hit a real limit, not before.
What tools are dashboards built with?
For a reporting dashboard, Power BI, Looker Studio and Tableau are the default choices. Power BI is the most used in the Netherlands and connects easily to Microsoft data, Looker Studio is free and strong around Google sources, and Tableau is powerful for heavy visualizations. A custom application dashboard is built with the same web technology as any modern application.
| Tool | Strong at | Watch out for | Fits |
|---|---|---|---|
| Power BI | Microsoft data, broad adoption, sharing | License per user | Reporting in a Microsoft environment |
| Looker Studio | Free, Google sources, quick to start | Less powerful on heavy data | Small to mid-size reporting dashboard |
| Tableau | Heavy visualizations, analysis | Higher rate, steeper learning curve | Data-intensive organizations |
| Custom web application | Acting, roles, connections, ownership | Larger investment | Operational dashboard in your own process |
If you build custom, focus less on the exact brand names and more on two things. A modern, widely used stack, so you can easily find developers later who will take it over. And speed, because a slow dashboard goes unused. The probability that someone bounces rises by 32 percent as a page goes from 1 to 3 seconds of load time, according to Think with Google (Think with Google). For a dashboard you open daily, every second counts double.
The journey from data to dashboard
Having a dashboard built runs in four steps: opening up data sources, designing what you want to see, building and connecting, and delivering with maintenance agreements. Most of the work is not in drawing charts, but in getting the data underneath clean and reliable. A pretty dashboard on the wrong figures is more dangerous than no dashboard.
- Map the data sources (a few days to 1 week). Which systems hold the figures you want to see: accounting, CRM, webshop, Analytics, a database? And are those sources reliable and current?
- Design: what question does this dashboard answer? (a few days). Not “show everything”, but the three to five decisions you make with this screen every week. The KPIs follow from that, not the other way around.
- Build and connect (1 to a few weeks). Setting up the connections, cleaning the data and building the visualization or custom screen. For custom this happens in short sprints with a demo, so you steer early.
- Deliver and maintain. Go-live, explanation for the users and agreements on who keeps it current when a data source changes.
That preparation is not a luxury. According to McKinsey, 45 percent of large IT projects run over budget (McKinsey), and the biggest lever against that is getting sharp on what you build before anything is built. For a custom dashboard you follow much the same route as having a web application built, because the dashboard is part of that application.
What should you watch out for? The five pitfalls
Most disappointments around dashboards come not from the technology, but from choices around it. Five pitfalls come back most often, and all five are avoidable upfront.
- Wanting to show everything. A dashboard with fifty numbers gets ignored. Start with the few figures you actually steer on and expand only afterward.
- Building on dirty data. A dashboard does not make bad data better, only more visible. Clean the source first, or connect the systems that do not work together.
- Demanding real-time you do not need. Refreshing every second costs far more than every hour or overnight. Ask which decision truly cannot wait.
- No code ownership on custom. Without ownership you pay the same party for every change. Read why that matters in code ownership and vendor lock-in.
- No maintenance agreement. Data sources change, KPIs shift. Agree who keeps the dashboard alive, otherwise it stalls within half a year.
Where should you have a dashboard built?
For a pure reporting dashboard, choose a BI or Power BI studio: that is their specialism and for read-only insight often the fastest and cheapest route. For a custom application dashboard, one you also act in, choose a software studio that builds the whole application. More important than the type of party is what you agree on upfront.
Ask every provider three things. Do I get a fixed price for a clear scope? Do I get the code in ownership on custom? And how do you handle my data sources and connections? A good partner answers those without dodging. More on that choice is in software studio vs freelance developer and in our complete guide to having custom software built.
How do you start, concretely?
Start with the question, not the tool. Write down the three decisions you make every week and for which you now gather data by hand. Then look at which sources hold those figures and how clean they are. Only then does the choice between a reporting dashboard and custom become obvious, and you compare every quote on the same scope instead of on a hunch.
Want to validate quickly without starting a big project? Begin with one screen or one report and expand once it works. How to phase that is covered in building an MVP: approach and phases. Book a free intake call if you would like to look together at which route fits. No sales pressure, just grounded advice.
TopDevs is a Dutch software agency that builds custom software, AI integrations and automations.
