Data & Technology

Sales and finance bring the same number to the meeting

Finance, sales and inventory data is loaded automatically into a data warehouse that is reconciled against the books. Every report calculates the same way, from the monthly report to the group management report, and nobody has to build them by hand.

Data warehouseData integrationdbtSnowflake and Fabric

The business logic is written once

The business logic, such as how margin is calculated, is written once in the data warehouse. Reports, dashboards and AI solutions then draw from the same place, and revenue, customer and margin mean the same thing everywhere. The logic is tested and documented, and it does not depend on any one person.

From source system to report: how a data warehouse is built
Architecture
SOURCESSTAGINGSEMANTIC MODELSUSED BYAIERPCRMPAYROLLGRIDMAPstg_orderstg_kundstg_lonFinanceACCOUNT · PERIODfact_transaktiondim_kontodim_perioddim_kundLogisticsORDER LINE · DAYfact_leveransdim_artikeldim_lagerdim_kundsame definitionAI ASSISTANTBI REPORTSDATA APIEXPORT / EXCEL
Nightly run
04:00 EXTRACT
04:06 TEST
04:11 MODEL
04:19 PUBLISH
04:24 DONE
Every night, data from the source systems and the mappings in Gridmap are loaded. dbt then tests and models the data and publishes it to a finance model and a logistics model. Both use the same customer dimension, so a customer is the same customer in both. Reports, APIs and AI assistants read from the models.
“Stormyran plays an invaluable role for us in handling and processing complex data for our B2B clients. Their expertise and reliability make them an important partner in our business.”

Mårten Brandt

CFO, Klarsynt

Book a review of your monthly report

We look at how the monthly report is produced today and sketch the path to a data warehouse, with a timeline and what a first stage would deliver.

Who it is for

We build data warehouses for everything from companies with a couple of source systems to listed groups with hundreds of report users.

Companies with data in a few systems

A finance system, a CRM and a number of Excel files. We bring them into one warehouse and build the first reports on top.

  • Start with the most important sources
  • The monthly report is automated
  • Extend as needs change

Companies with their own BI or IT team

We build or clean up the warehouse together with your team, so you can maintain it yourselves afterwards.

  • Code review of what is already there
  • Tests and documentation in dbt
  • The code in your Git

Groups and listed companies

Many source systems, hundreds of users and reporting at several levels. The architecture, permissions and models have to hold as more companies and systems are added.

  • Architecture for several companies
  • Row-level security
  • Shared definitions across the group

Signs that you need a data warehouse

The monthly report is built by hand in Excel from several systems

Different departments report different figures for the same KPI

Business logic lives in individual reports or with individual people

Every new question from management turns into a new development project

The data is not good enough to try AI or machine learning

What we build

  • Data flows from ERP, CRM, payroll, e-commerce and other sources
  • Transformations and business logic in dbt, with tests and documentation
  • Semantic models with shared definitions for things like customer and revenue
  • Row-level security, so each user sees the right data
  • Mappings and reference data the business maintains itself in Gridmap
  • Connections to Power BI, Qlik, Excel and APIs
  • Maintenance and further development once the warehouse is live

What you get

  • The same numbers in every report
  • Reports that update automatically, with no manual steps
  • Business logic that is tested and documented
  • Code and a warehouse that you own, in your own environment
  • A foundation for AI and machine learning

How it works

Most projects are done in 6–12 weeks. Larger warehouses with many sources are built in stages, where the first stage is often the finance system and one or two other sources, so the monthly report can run on the warehouse before everything is finished.
  1. 01

    Current-state review

    We go through which decisions the data should support, which source systems there are and how reporting works today.

    From you
    Time with the people who own the reporting
  2. 02

    Architecture and platform

    We propose a platform and architecture based on the licences you already have, your security requirements and your budget.

  3. 03

    First sources and models

    We connect the most important source systems and build the first models in dbt, with tests for the things that have to be right.

    From you
    Access to the source systems and someone who knows the business definitions
  4. 04

    Reports on the warehouse

    Existing reports are moved across or rebuilt on the warehouse, and we check the figures against the finance system.

  5. 05

    Handover or maintenance

    You get the documentation and the code in your Git. Either you maintain the warehouse yourselves, or we keep maintaining and extending it.

Examples from our work

Listed industrial group

A data warehouse for the group's reporting

We built a data warehouse in Snowflake that brings together data from more than 20 source systems.

The warehouse is the foundation for the group's reporting in Power BI and is used by more than 250 people.

source systems
20+
source systems
users
250+
users
Power BI reports
500+
Power BI reports

Automotive retail group

From architecture advice to a finished warehouse

We have worked with the group for several years, from advice on the data architecture to building the warehouse, the integrations and the BI solutions.

The warehouse is built in Snowflake with dbt, and reporting runs in Qlik.

The report only one person knows how to build

In many companies, important decisions are made from Excel sheets where nobody is quite sure the numbers are current. The knowledge of how reports are produced sits with a few people, and a new report takes days to build.

With a data warehouse the numbers update automatically, and everyone who needs them can get to them without going through the few people who know how the report is built.

The team has worked on group reporting, production planning, inventory optimisation and sales follow-up across many industries.

Technology and platforms

These are the platforms and tools we work with. We make the choice in the architecture step, based on what you already have.

Platforms

Snowflake, Microsoft Fabric, Azure, AWS, Google BigQuery or your own data centre.

Data flows and transformation

dbt, Azure Data Factory, Python and Spark, Fabric and TimeXtender.

Security

Encryption, role-based access, row-level security and logging in line with GDPR and other regulations.
dbtSnowflakeMicrosoft FabricTimeXtender

Latest news in Data Warehousing

Articles and news from us in this area

Consolidate the 30 Excel sheets controlling your analytics environment

Multiple versions of the same file, hard-coded lookup tables and key-person dependencies steal time and erode confidence in the numbers. Gridmap brings every mapping, registry and business rule into one auditable place, with optional rule-based AI that suggests the right value in real time.

Read more

Chat with your code base, get better techinical specifications

An AI assistant that mirrors your codebase as a living markdown knowledge base. End users describe new features, get realistic time estimates grounded in the actual code, and approve development on the spot.

Read more

Frequently asked questions

Contact Us

Fill out the form and we will get back to you within 24 hours.

Data Warehousing | Stormyran