A dashboard can look simple while depending on difficult work underneath it. A chart built from a clean table is a different project from a report that reconciles several systems and controls access by department.

A useful estimate explains those differences. It also separates the cost of the Microsoft platform from the cost of designing, building, and supporting the reporting.

Separate the main costs

There are three categories to consider:

  • Project work: discovery, data preparation, modelling, report design, testing, deployment, and agreed training.
  • Platform costs: the Microsoft licences and capacity required for the proposed audience and sharing model.
  • Ongoing ownership: monitoring, maintenance, changes, and the internal time needed to keep definitions and source data reliable.

A quoted build price is only part of that picture. Before comparing proposals, check whether they cover the same work and identify the same dependencies.

Data condition changes the estimate

The important questions start before anyone chooses chart colours. Are dates consistent? Do systems use the same asset and customer identifiers? Can the source owner explain how a total is calculated?

If different teams define the same measure differently, the project needs a decision about the definition. Software cannot settle that disagreement on its own.

Ask what source access is available and whether sample data represents normal operations. An estimate based on a tidy sample can change when missing history, duplicate records, or unusual transactions appear.

Audience and reliability matter

A report for one small group has different requirements from reporting shared across departments or with external users. Access rules, sensitive fields, and testing with realistic user accounts all affect the work.

Freshness also needs a definition. “Up to date” might mean ready for the morning meeting or available soon after a transaction. Different storage modes and refresh arrangements have different dependencies. Microsoft's Power BI refresh guidance explains why refreshing data, a model, and a report are not always the same operation.

Plan who notices a failed refresh and who can repair it.

Confirm licensing before finalising the design

Use Microsoft's Canadian Power BI pricing page for current plans. The appropriate arrangement depends on creators, viewers, distribution, and existing capacity. Do not assume every Microsoft 365 user can view every Power BI report without additional licensing.

A proposal should identify platform costs separately and state its currency, taxes, exclusions, and assumptions.

Make the first paid step clear

At Northern Analytics, the initial 30-minute consultation is free. It is a high-level conversation about the problem and whether further work makes sense.

Follow-on discovery, analysis, scoping, design, and implementation are paid services. We agree on the scope and fee for that work before it begins. A consultation is not a promise of a detailed assessment or a fixed build quote without investigation.

To prepare, list the report's users, source systems, important measures, access restrictions, and the manual work it replaces. Use anonymised examples until an appropriate information-sharing arrangement is in place.

Read about choosing between Excel and Power BI, or request the initial consultation to discuss where to start.