ENLV

Case studyPower BI Development

Power BI for a Nordic Loyalty-Tech SaaS

Elvijs Veide3 July 2026 · 6 min readLast reviewed 3 July 2026
Power BI ARR Dashboard visual
Results
  • 2connected reports1 shared model
  • 5currenciesconsolidated
  • 6departments1 live KPI board

The company's product sits behind loyalty apps you've used without thinking about it - the coffee stamp card on your phone, the “10th one free,” the offer that lands on the morning you'd skip. For a subscription business, recurring revenue is the whole scoreboard. And when it's booked in five currencies, “how are we doing?” stops being one question: versus last month, versus target, versus last year, in local currency or converted, counted from when a deal closed or when it starts billing. Answer those from spreadsheets and you'll get a slightly different number each time.

The ChallengePower BI for a Nordic Loyalty-Tech SaaS

The raw material was never the problem - deals in the CRM, invoices in the finance system, monthly exchange rates from the central bank. It fell apart the moment anyone tried to turn that into one agreed number without rebuilding it from scratch each month.

ARR is harder than it looks. A customer in Sweden pays in SEK, head office reports in NOK, and the rate that bridges the two is only published after the month has closed. Miss that and the measure doesn't throw an error - it quietly drops the row and reports less revenue than the company actually has. Do that three ways in three spreadsheets, and you get three “official” ARR numbers, each one defensible, none of them matching.

The KPIs had a different problem: they already existed, but they cost people. Pipeline, retention, burn and more were pulled together manually every cycle, so a finished board was already a little out of date - with small inconsistencies between whoever built it this month and last.

The Mission

Settle the definitions once and reuse them everywhere: one way to convert a currency, one ARR structure, one calendar. Then put the two views the business runs on - recurring revenue and operational KPIs - on top of that shared foundation, refreshed automatically. The goal: ARR trustworthy enough that people stop rebuilding it, and a KPI board that maintains itself instead of being built by hand each month.

Our Approach

We started with the basics everything else depends on: one calendar, one currency table, and a single source of ARR changes. Get those right and the two reports stop being separate projects and become one shared foundation, read two ways. The discipline that held it together:

- One shared calendar behind every time comparison - year-to-date, last twelve months, month-over-month, prior-year - so "this year so far" means the same thing everywhere you see it.

- Exchange rates applied to each amount individually, with a fallback. Every amount converts using the rate for its own currency and month. If this month's official rate isn't published yet, the model uses the most recent rate available instead of leaving the amount out. Five currencies in, one consistent number out - nothing gets silently missed.

- Both dates kept on the same underlying records, so the sold-date view and the effective-date view can never drift apart from each other.

Report one - Annual Recurring Revenue

What ARR is, and why it runs the businessPower BI for a Nordic Loyalty-Tech SaaS

Annual Recurring Revenue is the yearly value of every active subscription the company holds - the revenue it keeps earning as long as customers stay. It's what growth is measured against, what planning and hiring are sized against, and what the company is valued on.

What actually makes up ARR

ARR doesn't move for no reason - each month's change has a cause: new customers, existing ones buying more, contracts growing or shrinking, price changes, or customers leaving. Currency swings are shown separately, so a weaker krone is never mistaken for lost customers. Leadership sees why ARR changed, not just that it did.

Why this beats the old spreadsheet

Because the numbers update automatically, ARR can be checked any day, not just at month-end - so a churn spike or a growth jump shows up that week, early enough to respond. And where the old total shifted with whoever built the spreadsheet, the automated version applies the same rules every time, exchange-rate safety net included: the same figure whether you check it today or after close, with no rebuild.

Report two - Company-wide KPIs

From a manual monthly build to a live board

Automating this put every department's KPIs in one place, refreshed on its own, each shown as actual versus target. What used to be a monthly copy-and-check scramble across separate sources - real hours before anyone could even look at a trend - is now a single refresh.

What the board now tracksPower BI for a Nordic Loyalty-Tech SaaS

Sales sees pipeline value, sales-cycle length, cost of acquisition, and quota coverage. Marketing tracks qualified leads, cost per lead, meetings booked, and email performance. Customer success watches churn, renewals, NPS, and retention. Operations covers uptime, cost of goods, and support load. Finance and leadership see ARR per employee, burn rate, runway, and R&D spend - with US and Europe tracked separately wherever revenue is involved, since the two markets work differently.

Why these KPIs matter to them

Each metric is an early warning for a specific risk: cost of acquisition and quota coverage show whether sales spending works; churn and retention, whether growth leaks out faster than it comes in; burn and runway, how much time is left to fix things; uptime and support load,

whether the product can take more customers. Together they let leadership adjust course weekly, not just at quarter-end.
Power BI for a Nordic Loyalty-Tech SaaS

What Changed

The two reports agree with each other now - which sounds obvious until you've lived without it. The ARR in the revenue report and the ARR shown on the KPI board are the same number, same logic, same calendar. Nobody asks why the two don't match anymore, because they do.

The KPI board is a refresh now, not a monthly assembly job, so the hours that went into building it go somewhere more useful. And “how are we doing this year” is a click away, not an afternoon of exports and stitching.

Last Words

Growing companies are good at breaking their own spreadsheets - a new currency, a new deal type, a new team structure, something the old setup never planned for. This one is built to absorb that: shared definitions, a safety net for missing exchange rates, and one revenue structure that reads however each team needs. It didn't make the dashboards prettier; it made ARR something people trust without double-checking, and turned the KPI board from a monthly chore into one that keeps itself current.

If your own revenue numbers start slipping the moment a new currency or team enters the picture, or your KPIs still live in a spreadsheet someone rebuilds every month, let's talk.

Frequently asked questions

We already have spreadsheets. Why change?

Spreadsheets have to be rebuilt by hand each period, and the answer tends to shift with whoever built them that month. Small inconsistencies creep in, and a finished report is often already a little out of date. The reporting stack applies the same rules automatically every time, so the numbers hold up and nobody loses hours reassembling them.

Which KPIs does the board track?

Sales (pipeline, sales-cycle length, cost of acquisition, quota coverage), marketing (qualified leads, cost per lead, meetings, email performance), customer success (churn, renewals, NPS, retention), operations (uptime, cost of goods, support load), and finance and leadership (ARR per employee, burn, runway, R&D spend). US and Europe are tracked separately wherever revenue is involved, since the two markets behave differently and shouldn't be averaged together.

How "live" is a live report, really - is it real-time?

Not to the second, and it doesn't need to be. ARR and company KPIs move in deals and contracts, not in milliseconds, so the reports refresh on a schedule - usually overnight - against the current state of the source systems. "Live" here means you never wait for a month-end rebuild to see where you stand, not that a number ticks up the instant a contract is signed.

  • Power BI

Published · Updated · Last reviewed

By Elvijs Veide, Co-founder

More case studies

All case studies
  • Case 01Power BI Development

    CCLM SIA (DigiMart)

    A Power BI Stack for DigiMart

    A Power BI semantic model built by Codnity Data for CCLM SIA - the company behind DigiMart, a Baltic e-commerce and wholesale operator selling Samsung, Bosch, Philips, Xiaomi, Heinner and other appliance brands across Latvia, Lithuania and the Nordics. The model pulls live data from their Moneo accounting system via API, replaces a stack of spreadsheet exports, and gives the team one place to look at sales, gross profit, purchases, unpaid invoices and stock availability - including a custom "Provision of Goods" engine that tracks how many days each SKU sat with no stock.

    5 fact tablessales, purchases, etc
    32business measures
    Read the case
  • Case 02CRM Development

    Eco Baltia Vide

    From Chaos to Clarity: A CRM That Actually Works

    A 12-month custom CRM build by Codnity Dev for EcoBaltia after two previous vendors couldn't deliver. Sprint-based delivery across ~20 sprints, replacing disconnected sales, support, and logistics tools with one unified platform. Built on tight collaboration and regular feedback loops — the EcoBaltia team called communication out as one of the most valued parts of the engagement.

    3 departmentssales, support, logistic
    2 prior vendorscouldn't deliver
    Read the case
  • Case 03Web Development

    Green Space

    Green Space - Custom Website

    Green Space is a Latvian housing company building sustainable solid-wood homes with an 8-month build promise. Codnity Dev built the custom website: digital brochure plus interactive experience - 3D visualisations, day/night animations, model configurator, booking system.

    3D + day/nightinteractive renders
    Configuratoracross all house models
    Read the case

Want results like these?

Tell us where you are stuck. We share the case studies closest to your project in full and reply within one working day.

  • Discovery call, no pitch deck
  • Relevant case studies shared in full
  • A clear scope before you commit
  • A reply within one working day
Or write directlyhello@codnity.comRiga · London · US East Coast

What is it about? (pick any that apply)

We reply within one working day.
Thanks. It's with the team.We reply within one working day.

Cody