Every team has its own figures
We agree shared definitions. The same KPI is simply calculated in several ways.
When sales and finance turn up to the management meeting with two different revenue figures, it is rarely because somebody miscalculated. Each team pulls numbers from its own system and applies its own definition. We tidy up master data, bring the sources together and build reports where a figure needs no footnote.
Each builds on the last: rules for your master data first, then a shared data warehouse, and finally automatic reading of the documents that pour in.
A single register of customers, suppliers, products and departments, with CVR lookups, rules for creating records and a hunt for duplicates. Skip this step and you simply end up processing a mess faster.
Data from e-conomic or Business Central, the webshop, stock control and marketing platforms is consolidated in Microsoft Fabric or Azure in an EU region. On top we build Power BI reports for sales, inventory, finance and production - identical results whoever runs them.
Invoices, delivery notes and contracts arriving as PDFs or scans are read automatically. Numbers, dates and amounts drop into the system, leaving staff to check and approve. OIOUBL invoices via NemHandel are handled natively.
The request often sounds like "we'd like a nice dashboard". Behind it there is almost always one of the issues below, and that is what needs fixing.
We agree shared definitions. The same KPI is simply calculated in several ways.
We cleanse master data and set rules. Duplicates creep in wherever nobody checks at creation.
We build a self-refreshing warehouse. Excel exports and manual copy-paste eat the analyst's week.
We schedule automatic loads. A monthly extract cannot keep pace with the decisions being made.
We add automatic document capture. Invoice lines are still keyed in by hand, one after another.
A polished dashboard on top of poor data is worse than none at all. When a report is compiled by hand, errors tend to get noticed along the way. A tidy chart looks credible, and management acts on it without questioning what lies underneath. That is why we always begin with data quality.
We begin with one department and a small set of KPIs. Trying to cover the whole organisation in one go drags on for months and seldom ends well. All work is done remotely.
What counts as revenue, a shipped order, an active customer? The dullest step and at the same time the most important one.
We find out where data lives, who owns it and how much cleansing is needed. Personal data is mapped with GDPR in mind.
Automatic loading goes live, and the first Power BI report answers the questions management really asks.
Further systems and teams are connected. Each new source costs less than the one before, because the foundation is already in place.
If everything sits in one system and nobody doubts the numbers, you do not need an extra layer. The need arises once data comes from several places: finance, webshop, stock control, Google Ads and Meta. Hooking all of that onto the production database is awkward, and heavy queries slow the system down for everyone else.
With reasonably well-kept data, roughly a month, including agreement on the KPIs. If master data is in poor shape, most of the time goes on clean-up and the timeline shifts. So we look inside the databases before committing to a date.
In an EU region, usually Azure North Europe or West Europe. We sign a data processing agreement, restrict access by role and log who views what. Reports containing personal data get row-level security, so a sales rep sees only their own customers.
Either option works. Under a service agreement we monitor the loads, adapt when a source system changes and add new KPIs on request. Alternatively we hand everything over to your own people with documentation. This is settled at kick-off.
Tell us which reports are built by hand and where the figures disagree. We will review the source systems and suggest where to begin.
Thank you for getting in touch
One of our consultants already has it. Expect a reply within the working day; anything urgent goes straight to an engineer.
That city is not on our list. Check the spelling or pick the nearest larger town.