Sources
Pantheon, Minimax, Metakocka, SAOP, Business Central or Odoo; timesheet and attendance tools; a webshop on WooCommerce, Shopify or PrestaShop; Amazon and eBay; Google Ads and Meta; spreadsheets kept in SharePoint or Google Drive.
Service · Data and analytics
Data warehouse
Suppose you run a construction firm in Murska Sobota with eight sites on the go. Materials and subcontractor invoices are in Pantheon, workers' hours in a separate timesheet tool, and estimates and progress claims in Excel files that every site manager keeps in his own style. Management usually discovers that a project has lost money only at final account, when the only thing left to take from it is a lesson. A data warehouse pulls these sources into a single database refreshed overnight. Each morning one dashboard shows how much each project has consumed against its estimate, how many hours went into each phase and which progress claim has not yet been invoiced. Your existing software stays as it is; the warehouse merely reads from it. Because everyone looks at the same figure, the meeting opens with a decision rather than an argument about whose spreadsheet is correct. We set everything up remotely and then hand the working system to your team or keep looking after it.
Overnight refresh
reports ready first thing
One definition
per indicator, written and agreed
Role-based access
site managers see their own projects
Your EU account
the data remains yours
Scope of the service
We shape the warehouse around the questions it has to answer, not around whichever tables happen to be available.
Views by project and channel
Costs for materials, labour, transport, commissions and advertising are assigned to a project, sales channel or product group. You see contribution margin rather than turnover alone.
Glossary of indicators
What counts as revenue, when an order is closed, how credit notes and advances are handled. Each definition lives in one place, and the dashboard displays it beside the figure.
Checks at the door
Every night, dbt transformations test for missing days, negative stock and suspicious jumps. When something fails, the dashboard states clearly up to which date the numbers can be trusted.
Changes over time
If a project passes to a different manager or prices are revised, earlier data stays recorded as it was at the time. Comparisons with last year therefore remain fair.
Access by role
Row-level security in Power BI or Metabase: management sees everything, a site manager his projects, an outside partner only its own orders. Personal data you do not need for analysis is left out or pseudonymised.
Where it runs
PostgreSQL at Hetzner, OVHcloud or IONOS, or a managed database in EU regions of Azure, AWS or Google Cloud. The account belongs to your company, and Apply acts as processor under a data processing agreement.
How the work runs
We only start the next step once the previous one is genuinely being used, so nothing gets built just in case.
01
Three questions from the board
On a video call we pick no more than three questions management cannot get a quick answer to today. Version one serves those alone.
02
First source, reconciled
We connect the business software and reconcile recent months with the books before adding anything else.
03
A dashboard for one meeting
We build a dashboard for a specific monthly meeting and run it alongside the old spreadsheets for a few months.
04
The next source
Once the dashboard is part of the routine, we bring in another source such as timesheets or the webshop and repeat the cycle.
A figure that disagrees with the books is worse than no figure at all. If the first dashboard shows revenue a few per cent away from the financial statements, management will stop believing it, however polished it looks. So before any new dashboard goes out, we reconcile with accounts and document every gap: credit notes raised a month later, advance invoices, exchange differences on sales outside the euro area. Only when the accountant is satisfied does the dashboard reach the board.
Your questions answered
When the same figure is assembled by hand every month from at least two sources. If you run a single business system and its own reports do the job, you do not need a warehouse, and we will tell you so.
Either your team, to whom we hand over documentation and code, or us within a plan or by the hour. Since transformations are written in dbt and stored in your own repository, you are not tied to us.
Yes, both Power BI and Metabase offer a mobile layout. We design the phone version separately, with fewer figures and larger type, because people open it on site or on the move.
It should not. Data is read overnight or in small batches, preferably via the software's interfaces or from a database copy. Reports then query the warehouse, never the live system.
Set-up is billed at €50 per hour plus VAT against an estimate agreed in advance, or at a fixed price where the scope is clear. Hosting and Power BI licences are paid by you straight to the provider.
More services in this area
Settle on a single set of figures
Tell us which questions get no quick answer in meetings and which systems the numbers come from. Your first dashboard will be built around those questions.
When we work
Weekdays 9:00-17:00 CET, answers the same or next working day
Weekdays 9:00-17:00 CET, answers the same or next working day
Calls
Video meetings, Teams and Meet both welcome
Video meetings, Teams and Meet both welcome
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
- Questions first. If something is missing before we can estimate, we email you or set up a brief video chat.
- A written quote. It spells out the work, a euro figure excluding VAT and a sensible start date. No fine print, no surprise line items down the road.
- You choose. It lands in your mailbox. Read it at your own pace, query anything that seems vague, and only then make up your mind.