Business

Intelligence

Business Intelligence consulting for your company.

Your company already has the data. What it lacks is a number everyone trusts.

We build the dashboard that management accepts as the single source of truth, with the tools you already use.

Business Intelligence

What Business Intelligence actually does

Turning the data your company already produces into a single version of the truth, visible every morning with no spreadsheets in between.

A Business Intelligence system collects the data from your ERP, invoicing, production and sales software, then cleans it and joins it up in a central data warehouse. From there it feeds dashboards that answer specific questions: how much we sold, at what margin, where the budget is drifting.

What sets it apart from a hand-built report is not the chart, it is the reliability. Every figure has an agreed definition, a traceable source and a refresh date. When management and finance look at the same number, it is because it really is the same number.

1definition per metric, agreed with the business
24 hmaximum delay between the data and the dashboard
0spreadsheets between the source and the decision

Three quick questions

The first three, answered in two lines each.

What it is

How is it different from the reports I already have?

Nobody has to build them. The data loads itself, each metric is defined once and the dashboard is up to date whenever you open it.

Who it is for

Does it make sense for my company?

Yes, if you already have an ERP and someone spends hours every week putting reports together. From there, the system pays for itself in that time.

When

How long until it is up and running?

The first useful dashboard takes 4 to 8 weeks. We start with the question that hurts most, not by integrating everything at once.

How to tell you need it

Hardly anyone comes to Business Intelligence out of conviction. They come after the third meeting spent arguing about which figure is the right one.

The figures do not match between departments

Sales says one thing, finance says another, and the management meeting is spent arguing over which is right instead of making decisions.

Reports are assembled by hand every month

Someone exports, copies, pastes and checks. Two days of skilled work for a document that is out of date the moment it is sent.

You find out too late what is going wrong

A project's margin is discovered when the project closes. A stock-out, when the customer has already called.

Every system keeps its own version

ERP, CRM, production and Excel do not talk to each other. Joining them up becomes a new project every time someone needs it.

What we build

Six separate pieces that can be commissioned together or on their own, depending on what your company really needs.

Mockup: Leadership · dashboard
01

Dashboards by role

Management, finance and operations do not need the same view. Each opens their own and sees their five numbers in under a minute, with the detail there if they need to drill down.

Mockup: Metrics dictionary · v3 approved
02

Metrics dictionary

What 'margin' means, when a sale counts, what is left out. One definition per metric, signed off with the business, and the same calculation in every dashboard.

Mockup: Scheduled reports
03

Reports that send themselves

The monthly report, the weekly sales report, the production report. They are generated and distributed without anyone touching them. This is usually the part that pays for the project first.

Mockup: Architecture · source integration
04

Source integration

ERP, CRM, production, spreadsheets and bank feeds, loaded every night into a data warehouse that is the only source for every dashboard.

Mockup: Performance · before and after
05

Optimising what you already have

When the problem is a dashboard that takes a minute to open, the work lies in the data model and performance. It is usually fixed in a matter of weeks, without rebuilding everything.

Mockup: Adoption · 12 weeks
06

Adoption and training

A dashboard nobody opens does not exist. We train each team on its own dashboard and track usage until it becomes part of the routine.

What changes in the first six months

−80% less time spent putting together the monthly report From two days to two hours, at a distribution client
1 definition for each metric, shared by every department
24h maximum delay between the data and the dashboard
6weeks to the first dashboard in production Median across our most recent projects

How we work

Five steps, and the first one is not technical.

  1. 1

    A business question

    'I want to know which products are losing me money' works. 'I want a dashboard' does not say which decision it is going to change.

  2. 2

    The real state of your data

    Sources, quality and access. This is where the timeline and the budget come from, not from a project template.

  3. 3

    A first useful dashboard

    Within weeks, with a tight scope and real data, so the team can use it and tell us what is missing.

  4. 4

    Iterate and train

    Nobody learns a dashboard from a presentation: they learn it by using it. We adjust it with the team in the room.

  5. 5

    Handover and independence

    Documented, and with your team able to maintain it. If you would rather we maintained it, we agree that; we do not work to make you dependent on us.

We work with the technology you already have

BI puts the data in order; AI puts it to work

BI calculates, AI decides. Business Intelligence gives you the validated figure and displays it. An AI system reasons over that information, runs processes and makes decisions within the limits you set.

One does not replace the other, and the order is not negotiable. An automation that rests on a metric nobody has agreed on inherits the argument instead of settling it.

In practice, many projects start with BI and carry on into AI workflow automation. The dashboard shows that an order ought to be placed; the next step is for the order to place itself.

Your systems

  • Sales
  • Stock
  • Hours
  • Customers
  • Purchasing
  • Collections

Business Intelligence

  • Sales
  • Stock
  • Hours
  • Customers
  • Purchasing
  • Collections

AI acts

  • StockOrders
  • SalesMargin
  • HoursCost

Where it applies

01 Real margins
02 Financial close
03 Inventory
04 Sales and customers
05 Operations
01 Real margins
Line illustration: price bars split into cost and margin
01

Real margins

Margin by product, customer and channel, with overheads allocated properly. This is where a product being sold at a loss, without anyone knowing, turns up most often.

02 Financial close
Line illustration: calendar with the last day closed and a double total line
02

Financial close

Profit and loss and budget variances without waiting for the manual month-end close. The finance team stops working two weeks behind.

03 Inventory
Line illustration: warehouse shelving with empty slots
03

Inventory

Stock-outs, overstock and real turnover by item, with alerts before the problem reaches the customer.

04 Sales and customers
Line illustration: portfolio split ring and performance bars
04

Sales and customers

Customer concentration, falling orders spotted in time, and performance by sales rep and by territory.

05 Operations
Line illustration: conveyor belt with boxes and a gauge
05

Operations

Plant performance, waste and downtime, set against what they cost. This is where operations data becomes a financial decision.

Frequently asked questions

The ones that come up before a project is approved. If yours is missing, write to us.

Let's talk about your project
How much does a Business Intelligence project cost?

It depends almost entirely on the state of your data, not on the number of reports. What drives the work is how many sources need integrating and what shape they are in. We fix the price after a one-hour session looking at your systems.

Power BI or Tableau?

If your company already works with Microsoft 365, Power BI is usually the sensible choice on cost and integration. Tableau has the edge when the main use is visual exploration. Your environment makes the decision, not our preference.

Do I need a data warehouse first?

No. We build it as part of the project, sized to what you need today. A BI project without a warehouse ends up with dashboards querying the ERP directly, and that breaks as soon as volumes grow or the software changes.

Does it work for a small company?

Yes, and the return often comes sooner than in a large one, because there are not ten departments to bring into line on a single definition.

What happens when the project ends?

The system is yours: the code, the model and the documentation are handed over. If you like, we carry on with monthly maintenance covering incidents, changes to the sources and new dashboards. But the option of depending on nobody has to be on the table.

And what does this have to do with AI?

Everything. An AI agent that answers 'how is the margin looking this month?' needs the same things as a dashboard: clean data, defined metrics and a warehouse to query. BI is the foundation that lets AI say something true.

Which industries usually start here?

Manufacturing and food, because the plant already records stoppages, consumption and waste, and all that is missing is the cost alongside them. And yachting and marine, where calculating minimum and ideal stock levels (case study in Spanish) cut stock-outs by 85%. In healthcare it comes second, on financial data.