Business Dashboard Development Cost: From Reports to Live Data
What drives dashboard development cost: data sources, cleaning, users and refresh. Compare a custom build with Power BI and free Google tools.
Dashboard development cost depends far more on your data than on the charts. Connecting to each system, cleaning and joining the data, deciding the definitions behind every number, and controlling who sees what usually take most of the effort. A dashboard built in an off-the-shelf tool such as Power BI or Google's free reporting tool can be cheap to start if your data is already tidy; a custom dashboard costs more up front but makes sense when it needs to live inside your own software, show live operational data or serve customers and many staff without per-user fees.
Key takeaways
- Most of the cost is data work: connections, cleaning, joining and agreeing what each number means.
- Power BI Pro is listed at £10.80 per user per month paid yearly, and a free Power BI user must upgrade to Pro or Premium to share reports.
- Google's dashboard tool, which its documentation now calls Data Studio, is no-cost, with a paid Pro tier for enterprise collaboration and administration.
- Custom dashboards suit live operational data, customer-facing reporting and actions inside the same screen.
- Start with five numbers you currently compile by hand and build those first.
What are you actually paying for in a dashboard?
A dashboard looks like a page of charts, so people expect to pay for chart design. In practice the work breaks down like this:
| Part of the job | What it involves | Why it can grow |
|---|---|---|
| Discovery and definitions | Deciding what each metric means: what counts as a sale, a lead, an active customer, a late job | Different teams often define the same number differently |
| Data connections | Pulling data from your CRM, accounts, ecommerce, booking or job system, spreadsheets | Each system has its own API, limits and quirks; some have no API |
| Cleaning and joining | Matching customers across systems, fixing duplicates, handling missing values | Messy source data is the biggest single cost driver |
| Storage and refresh | Keeping a copy of the data and updating it on a schedule or live | Live data costs more than a nightly refresh |
| Visual design | Charts, tables, filters, drill-downs, mobile layout | More views and filters mean more testing |
| Access control | Who sees which branch, team, client or figures | Row-level permissions add design and testing |
| Support | Fixing broken connections when a source system changes, adding metrics | Every connected system can change without notice |
If a quote does not mention data cleaning, definitions or ongoing support, ask about them before comparing prices. Those are where budgets usually go.
Power BI, Google's free tool or a custom dashboard?
These are not really competitors for every job. Each suits a different situation.
Power BI
Microsoft's Power BI pricing page lists a free tier for creating reports, Power BI Pro at £10.80 per user per month paid yearly for publishing and sharing, and Premium Per User at £18.50 per user per month paid yearly, which adds larger model sizes and more frequent refreshes. Prices are shown excluding VAT. The page says free users must upgrade to Pro or Premium to share, and that with larger Fabric capacities (P1 and above, F64 and above) viewers can consume content without a per-user licence. Power BI suits firms already on Microsoft 365 that want internal reporting from several sources and have, or will pay for, someone who can build and maintain the reports.
Google's free reporting tool
Google's documentation now calls the tool Data Studio; many people know it by its previous name, Looker Studio. Google's product documentation describes it as a no-cost tool that turns data into dashboards and reports, with a Pro version offering enterprise-grade collaboration and administration features. It is a natural fit for marketing reporting from Google Analytics, Search Console and Google Ads, and for simple reports from Google Sheets.
Custom dashboard
A custom dashboard is built as part of a web application, with its own database, logins and screens. It costs more to build because nothing is pre-made, but you control what it does and you do not pay per viewer.
| Question | Off-the-shelf BI tool | Custom dashboard |
|---|---|---|
| Up-front cost | Lower, especially if data is tidy | Higher: design, build and data work |
| Ongoing cost | Licences per user or capacity, plus someone to maintain reports | Hosting and a support plan; no per-viewer fees |
| Who builds and changes it | An analyst inside or outside the business | A development team |
| Live operational data | Possible, but refresh limits depend on plan | Designed in from the start |
| Actions from the dashboard | Mostly view-only | Can include buttons: assign a job, chase an invoice, approve an order |
| Customer or client access | Possible, but licensing and branding need care | Built into your portal with your branding |
| Best for | Internal analysis and management reporting | Operational screens, client reporting, dashboards inside your own system |
When is a custom dashboard worth the extra cost?
We would usually suggest trying an off-the-shelf tool first. A custom dashboard earns its cost in a few clear situations:
- It is part of a system you are already building, such as a CRM, booking platform or portal. The data is already in your database, so the dashboard is a set of screens, not an integration project.
- Your customers need to see it. A client portal showing each customer their orders, service levels or project progress is usually better as part of your own product.
- Staff need to act on what they see, not just view it: reassign a late job, chase an overdue invoice, reorder stock.
- Many viewers would make per-user licences expensive, for example every site manager and supervisor across a multi-site business.
- Your data needs logic that is awkward to express in a BI tool, such as your own pricing rules or job stages.
Our custom web apps service builds this kind of system. Version one typically takes 6 to 12 weeks, starting with discovery and a clickable prototype in the first two weeks, then building in two-week sprints with a demo at the end of each, followed by integration and a pilot with a small group. The code and data are yours. If your reporting is really a symptom of running the business on spreadsheets, read our guide to signs you have outgrown spreadsheets first.
Seven questions that set the price of a dashboard project
We do not publish dashboard price bands, because two projects with the same number of charts can differ hugely in data work. These are the questions that decide where yours will land:
- How many data sources? One clean database is quick. Five systems, two of them spreadsheets, is a different job.
- Do the sources have APIs? Systems with a documented API are straightforward; exports by email or screen-scraping are slow and fragile.
- How clean is the data? Duplicate customers, free-text fields and inconsistent product codes all need sorting.
- How fresh must it be? Yesterday's figures each morning are simpler than live numbers updated every minute.
- Who sees what? One management view is simple; per-branch, per-team or per-client access needs permission design.
- How many views and filters? Each extra page and filter combination needs building and testing.
- Is it standalone or inside an existing system? Adding screens to a system that already holds the data is cheaper than building a reporting system from scratch.
A good supplier should be able to give you a fixed price for a first version once these are answered in a discovery stage.
Hidden costs to budget for
- Licences for every person who needs to view or share reports in a BI tool, and how that changes as you grow.
- Maintenance when a source system changes its API or export format.
- Someone to own the definitions, so "revenue" means the same thing next year.
- Training so managers use filters and drill-downs, not screenshots.
- Data storage if historic data is kept outside the source systems.
- New requests. Once a dashboard is useful, people ask for more. Plan a small budget for version two.
How to scope a dashboard so the quote is accurate
- List the reports you make by hand now, who uses them and how long they take.
- Pick five to eight numbers that matter most and write a one-line definition for each.
- Name the source of each number: which system, which field.
- Say how fresh each needs to be and who should see it.
- Note decisions or actions people take from each number.
- Share sample exports so the supplier can see the state of the data.
That one page lets any supplier, whether a BI consultant or a development team, quote properly. It also often reveals that the real problem is a missing system rather than a missing dashboard, which is the theme of our post on internal business tools.
Frequently asked questions
Is Power BI cheaper than a custom dashboard?
Usually at the start, yes, if your data is already in good shape and an internal analyst can build the reports. Microsoft lists Pro at £10.80 per user per month paid yearly. Over time, licences for many viewers and the cost of maintaining reports can add up, so compare total cost over three years, not just the first month.
Can I build a dashboard myself for free?
Often, yes. Google's no-cost reporting tool works well for marketing data from Google Analytics, Search Console and Ads, and Power BI's free tier lets you create reports, though sharing needs a paid licence. Free tools work best when the data already sits in one clean place, such as a well-kept spreadsheet.
How long does it take to build a business dashboard?
A simple dashboard in an off-the-shelf tool from one clean source can be quick. A custom dashboard as part of a web application usually comes with the wider build; our version-one timeline for custom web apps is 6 to 12 weeks. Data cleaning and agreeing definitions are what most often extend timelines.
What should be on a business dashboard?
Only the numbers someone will act on. Typical examples are sales or revenue against target, new enquiries and conversion, jobs or orders by status, overdue invoices and stock levels. Start with five to eight clearly defined metrics, check that people use them, and add more only when a decision needs them.
Can customers see a dashboard on my website?
Yes, inside a secure client portal. Each customer logs in and sees only their own data, such as orders, service reports or project progress. This is usually better as part of a custom portal than a BI tool, because you control branding and permissions and do not pay a licence for each customer.
Next steps
Write down the five reports you build by hand each month and how long they take. If the data already lives in one or two tidy systems, try Power BI or Google's free tool first. If it is scattered, needs to be live, or should sit inside your own system or client portal, a custom dashboard is worth scoping.
To talk through your reporting and get a fixed-price first version, start a project or contact us.
