Short answer: If the management dashboard serves internal staff and the data already sits in a database, spreadsheet or ERP, start with a BI tool such as Power BI, Google's Data Studio (named Looker Studio until April 2026) or Metabase. Build a custom dashboard inside the product when customers will see it, when it must trigger actions, or when it has to follow the product's own permissions. Either way, the hard part is picking the few numbers that matter.
Key takeaways
- Data Studio is free: Google calls it a no-cost tool; paid Pro adds team workspaces and company-owned content.
- Power BI has refresh quotas: shared capacity allows eight scheduled refreshes a day per semantic model; Premium, PPU or Fabric allow 48.
- Metabase is open source: its Open Source Edition is free to self-host under the AGPL license.
- Customer-facing embedding costs extra: production Power BI embedding for external users needs a purchased capacity.
When a BI tool is enough, and when to build
A BI tool fits when the audience is internal, questions change often and an analyst maintains the reports. Microsoft's pricing page for the United States lists Power BI Pro at $14 per user per month, paid yearly. A custom build fits when customers pay for the dashboard, when clicking a number should open the record behind it, or when each customer may see only its own data.
| Option | Fits | Watch for |
|---|---|---|
| Power BI | Microsoft 365 companies, finance reporting | Refresh quotas on shared capacity; external embedding needs a capacity |
| Data Studio | Marketing teams working with Google data sources | Pro needed for team workspaces and company-owned reports |
| Metabase | Self-hosting teams with a SQL database | SSO-based embedding requires a Pro or Enterprise plan |
| Custom, inside the product | Customer-facing analytics, actions from the screen | Every new chart is development work |
Many dashboards begin as an overgrown spreadsheet, as in replacing Excel with a custom system. When the product already has user roles and permissions, a built-in dashboard reuses them instead of a second permission model in the BI tool.
Choosing KPIs, data sources and refresh
Start from decisions. For every KPI, write down who looks at it, how often, and what they do when it moves. In 2004 Stephen Few defined a dashboard as the most important information needed to reach one or more objectives, arranged on a single screen and monitored at a glance. That screen is a useful cap on the KPI list.
Next, name each KPI's source. Many Israeli companies pull from Priority ERP or from a CRM like the ones in custom CRM cost breakdowns. Agree on one definition per metric, for example whether revenue includes VAT, and match refresh to the decision: a morning sales meeting needs that morning's data; a monthly board review can live with a daily load.
