Data Engineering & Analytics

One model under Tableau and Power BI.

We run Tableau Server and Tableau Online — administration, migration, and the semantic layer underneath the dashboards — alongside Power BI and SQL Server, not instead of them.

company delivery history · founder-asserted ·

not in scope · Tableau or Power BI licence reselling — you hold or buy your own licences directly

The next step

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses


Scorecard pipeline — warehouse to Tableau to KPIs Source systems feed a scheduled extract, which loads a modelled warehouse. Tableau Server, Tableau Online and Power BI read from the warehouse on a refresh cadence and publish scorecards and a KPI set. The BI layer reads the warehouse; it never writes back to source systems. Sourcesystems Extract(scheduled) Warehouse(modelled) BI layer Tableau /Power BI Scorecard+ KPIs Both tools read the warehouse on a refresh cadence and publish scorecards. Never writes back to source systems — read-only into the BI layer. Sourcesystems Extract(scheduled) Warehouse(modelled) BI layer Tableau /Power BI Scorecard+ KPIs Both tools read the warehouse on a refresh cadence and publish scorecards. Never writes back to source systems — read-only into the BI layer.
Source systems feed an extract into a modelled warehouse. Tableau Server, Tableau Online and Power BI read that model on a refresh cadence and publish it as a scorecard and KPI set — the BI layer reads the model; it never writes back to the source systems.Full step-by-step description

What the work covers

Two platforms, run as one estate rather than two separate tool choices:

company delivery history · founder-asserted ·

We are not a Tableau or Power BI reseller. You hold the licences directly, with Tableau and with Microsoft, and we administer, migrate and build on top of what you already have.

Scorecards and KPI reporting

Once a model exists, publishing an agreed set of measures on a schedule is the last mile of this work, not a separate practice. Scorecards, performance metrics and KPI reporting sit on top of the same warehouse and the same definitions as the rest of it.

company delivery history · founder-asserted ·

How a number gets from a source system to a scorecard

The same path, step by step:

  1. Source systems. ERP, POS, inventory, or whatever systems of record the operation runs on — the same sources a reconciliation or a warehouse project reads from.
  2. Extract. A scheduled pull, not a manual export somebody remembers to run.
  3. Modelled warehouse. The same warehouse layer we build for any reporting project — one set of definitions, not a parallel copy built inside the BI tool.
  4. Tableau Server. Reads the model, publishes and refreshes workbooks against it, and enforces permissions and row-level security at the platform level.
  5. Tableau Online. The same administration model, hosted rather than self-managed.
  6. Power BI. Reads the same modelled warehouse, where Power BI is the tool your team already knows — not a second, disagreeing model.
  7. Scorecard and KPI set. Published on a schedule, with the definitions agreed once in the model rather than argued over in the meeting where the number gets shown.

The BI layer — Tableau or Power BI — reads that model. It does not write back to the source systems, and it is not where the definitions live.

Access during the work

Access to your Tableau or Power BI tenant during this work follows the same standard we hold ourselves to everywhere else: named individual accounts, least privilege, and logged, time-bound elevation. See Trust & security.

Continue

Start with a call about the numbers that do not agree.

Book an assessment call

30 minutes · with the engineer who would scope the work

one-page recap within 2 business days of a call that progresses