E-commerce
Platform ROAS, store revenue and bank deposits that never agree.
One revenue definition, net of returns and COD failures, with spend joined against it by channel.
Every business past a certain size has the same meeting: marketing's number, sales' number and finance's number, none of which agree, and an hour spent reconciling instead of deciding. The fix is not a better spreadsheet. It is one place where the definitions are agreed and applied consistently.
Business intelligence work consolidates data from ad platforms, CRM, your product and your accounting system into one warehouse, with agreed metric definitions, and presents it as dashboards. The purpose is that everyone in the meeting is looking at the same number.
Written down, agreed, and applied everywhere. Most reporting disputes are definition disputes in disguise.
Dashboards refresh themselves. A report that needs a person to build it is a report that arrives late.
Ad platforms, CRM, product or store, and accounting — the minimum to see spend through to revenue.
Daily refresh for most businesses. Real-time is rarely needed and always more expensive.
Decision and metric list
Metric dictionary
Running data pipelines
Modelled warehouse layer
Live dashboards
Dashboards in weekly use
Marketing reports leads from the ad platform. Sales reports opportunities from the CRM. Finance reports revenue from the accounting system. All three are correct within their own system and none of them can be joined, so the meeting becomes an argument about arithmetic.
The value is not the chart. It is the meeting that stops being about the data.
Platform ROAS, store revenue and bank deposits that never agree.
One revenue definition, net of returns and COD failures, with spend joined against it by channel.
Cost per lead reported by marketing and closed revenue reported by sales, never in the same table.
Attribution carried through the CRM to closed revenue, reported by campaign and creative.
MRR, churn and CAC calculated differently by every person who has ever produced a board deck.
Agreed definitions in the warehouse, with cohort retention and payback computed the same way every month.
Branch performance in eleven separate systems with no comparison.
Consolidated reporting per location, normalised so branches are genuinely comparable.
Client reporting assembled by hand across dozens of accounts every month.
Automated client dashboards from one pipeline, branded per client.
Production, inventory and sales data in an ERP nobody can report from usefully.
A warehouse alongside the ERP, with dashboards that do not require an ERP consultant to change.
Dashboard projects fail on governance rather than on technology. The tooling is largely solved; the agreement is not.
What counts as a lead, when revenue is recognised, whether returns are netted. Most disagreements about numbers are disagreements about definitions that nobody has articulated.
Transformations belong in the warehouse, not in each dashboard. Otherwise every chart implements its own slightly different version of the same calculation.
A dashboard that requires someone to update it is a report. Reports are late by construction; dashboards are not.
Start from the decisions the business makes weekly and build the smallest thing that informs them. Dashboards built to display everything get looked at once.
Every metric that matters, defined in a sentence, agreed by the people who use it. The most valuable and least exciting deliverable here.
Automated extraction from ad platforms, CRM, store, product and accounting systems, with failure alerting.
A modelled layer where the joins and transformations live once, so every dashboard reads the same numbers.
Executive, marketing, sales and operations views, each built around the decisions that audience actually makes.
Spend joined to leads joined to closed revenue, with the model's limitations stated rather than hidden.
Scheduled summaries to email or Slack, so the numbers reach people who will not open a dashboard.
Thresholds on the metrics that matter, so a problem announces itself rather than waiting for the monthly review.
How the data flows, what each metric means, and how to add a chart without breaking anything.
Every business past a certain size has the same meeting: marketing's number, sales' number and finance's number, none of which agree, and an hour spent reconciling instead of deciding.
Dashboard projects fail on governance rather than technology. What counts as a lead, when revenue is recognised, whether returns are netted — most disagreements about numbers are disagreements about definitions nobody has articulated. Write the definitions down before building anything, and get the people who use them to agree.
Start from the decisions the business makes weekly and build the smallest thing that informs them. Dashboards built to display everything get opened once, admired, and never used to decide anything. The structure that works is in marketing dashboard setup.
For almost every business, a daily refresh matches the decisions anyone actually makes. Hourly encourages reacting to noise and real-time is considerably more expensive — worth it far less often than people expect when they ask for it.
A dashboard cannot fix a conversion event that counts page views. If the underlying measurement is wrong, a BI project produces a faster, prettier route to the wrong conclusion — which is why we usually do Conversion & Analytics first and the dashboard afterwards.
Every stage ends in something you can hold — a document, a build, a live account. If a stage cannot name its output, it is a meeting, not a stage.
What decisions are made weekly and monthly, and what would need to be visible to make them well.
Agree definitions across departments and write them down before building anything.
Automated extraction from each source, with monitoring and failure alerts.
Joins and transformations in the warehouse, tested against known figures from each source system.
Dashboards per audience, built around decisions rather than around available fields.
Training, scheduled distribution and a review after a month of real use.
Everything here is part of the engagement at no extra cost. We do not itemise them on an invoice and we do not withhold them if you leave.
Every metric that matters, defined in a sentence and agreed across departments. The least exciting and most valuable thing we produce, and it is yours.
No one assembles a report by hand. A report that needs a person is late by construction.
The top numbers with their comparisons, pushed to people who will never open a dashboard link.
So a problem announces itself instead of waiting for the monthly review to discover it.
What comes from where, what each metric means, and how to add a chart without breaking anything.
Longer answers to the questions people ask before they hire anyone for data & bi dashboards.
Built by us, free, no signup, nothing uploaded to a server. Take them whether or not you ever become a client.
A marketing dashboard joining ad platforms, GA4 and your CRM is a defined project. A warehouse-backed build across marketing, sales, product and finance is larger, and is only worth it once you are joining four or more sources. Ongoing analysis is monthly. The metric dictionary comes with all of them.
Tell us what you have now and what you are trying to reach. We will audit it and tell you what we would do, what it would cost and whether you need us at all. The audit is free and yours to keep.