Blix case study — Paulina Dera, Product Designer

Intro

Blix is an aggregator of leaflets and promotions that helps people save time and money in stores — already an outstanding performer at 2M monthly active users.

To enrich that experience, I designed an MVP expense-manager feature: a way to photograph receipts and instantly see where the money actually went.

Context

Blix has a lot of dedicated users doing everyday grocery shopping with the app — they look for the best promotions on their favourite products and build shopping lists. To round out that experience, we needed to think about the post-shopping moment too.

We decided to build an MVP of a new feature: an expenses manager.

Define

Our users already enjoyed the shopping list. To make the shopping experience even more complete, we looked at adding the ability to collect and analyse receipts.

The primary business need was to test the feature in a way that could later enable cashback: build and publish an uncomplicated version that would teach us to read and correctly interpret real receipts.

The instant value for the user:

🧐 Instant analysis of the receipt as a chart, so users know exactly what they spent their money on (using OCR).
📈 A month-to-month statement, in this MVP version.
📦 A single place to store all receipts.

The OKR: correct and complete reading of 90% of the information on the receipt.

Research

Before designing the flow, I mapped how existing tools in the category stacked up — a receipt-scanning app (Pan Paragon), a budgeting app (Billy), and bank-native expense tracking (ING) — scored against what users actually valued, using the Kano model.

Competitor analysis of Pan Paragon, Billy, and ING bank expenses, scored against user needs using the Kano model — Competitor analysis summary, scored against user needs with the Kano model.

I also tested the categorisation logic against real receipts from users, manually tagging line items to see how cleanly they'd map onto spending categories before any OCR was involved.

Two real receipts with line items manually categorised into spending categories — Analysing real receipts from users against our proposed categories.

Solution

Moving forward, we decided to show receipts and expenses as two separate, simple surfaces rather than one complex screen — matching the MVP's goal of testing the core idea, not shipping every feature at once. Below is the empty state of the expenses view, and the process of adding the first receipt.

Submitting the first receipt.

We added a simplified divider between this month's and last month's expenses as an MVP version — a quick way to compare spending across months.

Switching between this month and the previous month.

Put together, the whole flow goes from an empty receipts list to a categorised, chart-based expenses summary.