Dashboards and reports
Built around the questions each team asks every week, with a path from the summary down to the row behind it.
Power BI consulting for teams leaving Excel or Tableau, or with an estate nobody owns. We built one model over 10 review sources for a hotel chain.


WHAT IT IS
A Power BI consultant builds the reporting layer on top of your data and gets people to trust it. That means connecting the sources, designing the semantic model with its measures in DAX, building the dashboards and reports, rebuilding old reports from Excel or Tableau, and setting up workspaces, security and who owns what.
Most of that work sits below the report. When two dashboards disagree on revenue, the fix is rarely on the page people look at. It is in the model, where the measure was defined twice. Where we start depends on which of three situations you are in.
The logic sits in formulas and calculated fields that one or two people understand, and someone pastes in new data by hand each month. Moving it into one Power BI model is the migration work. If Tableau or Excel will stay in use beside Power BI, the work becomes analytics that spans several BI tools.
Here the tool works and the trust doesn't. Workspaces multiply, the same dataset lives in five slightly different copies, and nobody can say which copy the finance report reads from. Governance and rollout is the work that fixes it.
The model comes before the first dashboard, because changing it later means reworking every report built on it. We start from the questions the reports must answer and the systems that hold the answers. If those systems need pipelines or a warehouse before Power BI can read them, that is the data engineering behind Power BI, and we take it on as well.


SERVICES
A team whose model already works may only need new reports. A team leaving Tableau needs the migration first and, soon after, the governance that stops the new estate drifting back into the state of the old one.
Built around the questions each team asks every week, with a path from the summary down to the row behind it.
The BI data model every report relies on, usually a star schema, with fact tables such as bookings joined to dimensions such as date and hotel.
Measures are written once in DAX, and Power Query cleans and shapes the source data before it reaches the model.
From Tableau, Excel or another BI tool. We decide with you which reports to rebuild, which to retire and how each calculation carries over.
Calculated fields and formulas become DAX measures, and old and new numbers are reconciled before the old report is switched off.
Who publishes, who views and who owns each dataset, set out in workspaces and access rules, with a plan for how people learn the new reports.
Development and production run in separate workspaces, with endorsed semantic models. At handover your team gets a walkthrough of each report and the data dictionary behind it.
CASE STUDY
A hotel chain in Europe had guest reviews and ratings spread across booking sites, maps and social networks. The client wanted them in one place, with a view for each hotel and one for the whole chain.
We built a Power BI dashboard that aggregates guest reviews and ratings from 10 sources, including Google Maps, TripAdvisor, Booking.com and Facebook. Review text is sorted by keyword, so the dashboard shows which topic, such as price, staff or cleanliness, pulls a hotel's score down, with no need to read each site.
We put one data model over all 10 sources. A review from TripAdvisor and one from Booking.com are sorted by the same keywords and parameters, and that is what lets one hotel be compared directly with another.
Our client's guest rating was 4.40 before the launch and 4.85 after.


Tell us where its numbers come from, who reads it and what it is supposed to show. We take the first conversation from there.
FOUNDATIONS
Power BI reads from databases, cloud storage, spreadsheets and business applications. Once more than a few systems feed the same reports, a warehouse or lakehouse beats a folder of exports: Microsoft Fabric with OneLake, ADLS Gen2 with Azure Synapse, Snowflake or Databricks. Building the warehouse that feeds Power BI is a service of its own.
The model holds the tables, relationships and DAX measures every report reuses, and each table gets a storage mode. Import copies the data into the model and is quick to query. DirectQuery leaves the data at the source and queries it when a visual loads, which is usually slower. Direct Lake reads Delta tables in OneLake without a separate import copy, at speeds close to Import. We choose the mode table by table, since it sets how fresh the numbers are.
You buy the Power BI or Fabric licenses from Microsoft, and that bill sits outside our fee.
Each dataset refreshes as often as its source changes and its readers need. Row-level security decides who sees which rows, so a regional manager sees their own region and finance sees the whole company.


PROJECT OR PEOPLE
A project fits when you can describe the result, a set of finance dashboards or a move off Tableau, and have nobody on your side to direct the work. Our team runs it from discovery to handover.
People fit when you already have a data lead and a backlog and need more hands. Through staff augmentation we add analysts who build Power BI reports or Power BI developers to your team, and we present matched candidates within 7 days of your request. They work in your process and your tools, and your lead sets the priorities.


PROCESS
Four steps take a Power BI project from discovery to rollout, whether it starts from Excel, from Tableau or from a blank workspace. Discovery sets the plan and the milestones, and you accept each milestone before the next one starts.
STEP 1
We review your sources, your current reports and who uses them, then hand over requirements, an architecture, an estimate, a delivery plan and the risks.
STEP 2
We agree with you which reports and which parts of the model each milestone delivers, in the order your teams need them.
STEP 3
We build the model, the DAX measures and the reports, and test the numbers against the source system before each release. A demo follows each sprint.
STEP 4
We release the reports to your users and hand the work over to the team that will run it.
HOW WE WORK
We deliver an agreed scope end to end: plan, team, milestones, QA and release. You make the product decisions and accept each milestone.
Fixed price per milestone after discovery, or time and materials against an estimate.
A short phase before a build: requirements and backlog, architecture, an estimate and a delivery plan.
Fixed price, usually 2–4 weeks.
Our engineers join your team and work in your process and tools. You manage them; we source, vet and contract them.
Hourly rate per engineer by role and seniority, invoiced monthly.
WHY OCTALANCE


80%+ of our engineers and analysts are senior-level or above, with 7 years' experience on average. On Power BI, that seniority goes into the data model, the part hardest to change later.
Every candidate passes three steps: a technical assessment, a soft-skills evaluation and a check of their job history. For BI roles the assessment includes a DAX and data-model task.
On a project we choose and vet the team and answer for the delivery. You can still interview the key roles, the people who will design your model, before work starts.
We build in Tableau as well as Power BI, and we have no reason to move a report that works. A Tableau workbook that a few people read and trust may be cheaper to leave where it is.
Name the situation, the sources and when your users need the reports. We can sign an NDA before you share anything about the project.
FAQ
Yes. Power BI is part of Microsoft Fabric now, and it is where Fabric's reports are built and read. What Fabric changes is the ground under the reports. The data can sit in OneLake, and capacity can be bought once for the whole organization. The skills that make a report trustworthy, a clean semantic model and well-written DAX, carry over, so a model built well today is not work you will redo.
With Pro, the people who publish and the people who view shared reports each need a license, so it fits a modest number of users. Premium Per User is also bought per person and adds larger models and more frequent refresh, and everyone who views Premium Per User content needs that license too, unless the content sits in a capacity that allows it. A Fabric capacity is bought for the organization, and on the larger capacities people who only view reports don't each need a paid license. The answer turns on how many of your users only read, how big the models are and whether you will keep your data in Fabric too. Check Microsoft's current terms before you buy.
Yes. Our team built Tableau dashboards for a professional education company on an Amazon Redshift warehouse, so we know what calculated fields do on the Tableau side as well as in DAX. Each report is compared with its old version until the figures agree. Where they differ, the cause is usually a business rule buried in a formula, and that is worth settling with whoever owns the number before anyone builds on it. There is no published case for a migration to Power BI.
No. Octalance is not a Microsoft partner and works as an independent team. What you can check instead is the work and the people. Every BI candidate passes a DAX and data-model task before reaching a shortlist, and you can read the hotel chain case, ask us about its data model and meet the engineers who would design yours.
Scope sets it: how many sources you connect, how large the model grows, how many reports you need and how much governance and rollout comes with them. We start with a fixed-price discovery phase, then build at a fixed price per milestone or on time and materials against the estimate. The licenses you buy from Microsoft come on top of our fee. The models sit side by side under Engagement models and terms on this page.
You do. They are built in your own Power BI tenant, so nothing has to be exported or moved over to you at the end. Our engineers work in it through named accounts you issue, each with only the access its role needs, and all of that access is removed when the engagement ends. Your team keeps the reports in its own workspaces and goes on editing them after we leave. Where we handle your data, a data processing agreement is part of the engagement.