Skip to content
CV
WorkxChange Financial Services5 min read01 · Overview

Product Design Case Study · Fintech

Making financial logic clear, limiting credit risk

Container xChange is a B2B marketplace for shipping containers. Its wallet brought together credits, income, invoices and credit limits, and every month 150–200 support requests came in about not understanding it. As Lead Designer, I reorganised the financial overview and connected payments to risk limits across two projects.

Read the case
Key facts
  • around 80%

    fewer finance support requests

  • +72%

    wallet payouts

  • Seven figures

    recovered outstanding customer receivables, joint initiative

Role
Lead Designer, Financial Services
Collaboration
Product, Engineering, CFO, Account Management
Projects
Wallet 1.5 · Credit Limit

In short ~1 min

  1. 01 · Problem

    150–200 requests a month

    The wallet held credits, income, invoices and credit limits, and hardly anyone understood it.

  2. 02 · Intervention

    Reordered, tied to risk

    Wallet 1.5 reordered the financial overview, Credit Limit tied payments to risk limits.

  3. 03 · Outcome

    Foundation for 2.0

    Meant as a stopgap, Wallet 1.5 became the base for the next version.

Financial logic has to be readable. I ordered the wallet so customers understand it, and tied payments to risk limits.

xChange Financial Services

At a glance

  • −80%

    finance support requests, the goal was −15%

    −80%finance support requests, the goal was −15%Wallet 1.5
  • +72%

    wallet payouts, the goal was +20%

    +72%wallet payouts, the goal was +20%Wallet 1.5
  • Seven figures

    recovered receivables

    Seven figuresrecovered receivablesCredit Limit, a joint initiative
  1. Problem

    150–200 requests a month

    The wallet held credits, income, invoices and credit limits, and hardly anyone understood it.

  2. Intervention

    Reordered, tied to risk

    Wallet 1.5 reordered the financial overview, Credit Limit tied payments to risk limits.

  3. Outcome

    Foundation for 2.0

    Meant as a stopgap, Wallet 1.5 became the base for the next version.

02 · Wallet 1.5

Making financial logic traceable

More than 20 interviews and hundreds of support calls showed the same pattern: users did not understand their invoices or the categories and statuses of their transactions. Balances and open amounts were hard to follow, and there were no direct payment actions.

The overview beside the details

A two-column system: a compact financial overview on the left, transaction details on the right. Invoices and statements have their own tabs, and explanation patterns show, for example, how the available payout is made up.

Wallet 1.0 with balance and recent invoices above the transaction history
Wallet 1.0: balance and recent invoices above the transaction history.
Wallet 1.5 with the financial overview on the left and transaction details on the right
Wallet 1.5: financial overview on the left, transaction details on the right.

In the invoice table we deliberately accepted higher density: status, amounts, due date and deal reference sit together with the payment action, so everything needed to handle an invoice is in one place.

Wallet 1.5 went live in stages, built with shared UI components and tokens. We tracked support requests and feedback through Zendesk, DataDog and Account Management.

Outcome

Finance support requestsGoal: −15%
around −80%Goal exceeded
Wallet payoutsGoal: +20%
+72%Goal exceeded

Interviews also confirmed that users understood their credit limits better.

03 · Credit Limit

Connecting payments to risk limits

At the end of 2023, high negative customer balances became visible. Credit limits were poorly defined, and customers could exceed them before Operations could step in. I initiated the project and designed the payment flow and the warning logic.

For Credit Limit we were a team of seven: the PM, the tech lead, me in design and four developers; later the same team for all of Financial Services. When our PM was out, I carried the role for a while. The PM and I proposed the credit limits for the launch; the CFO and Account Management set them.

Open invoices: please mind your credit limit

Level 1 · Notice

Dismissible. Points to open invoices and the credit limit.

Credit limit exceeded: payment required

Level 2 · Payment request

Stays in place, with restrictions until payment.

Schematic view of the two warning levels.
Payment flow model with internal and external paths
Flow model: internal product steps (“On Platform”) and external payment paths (“Off Platform”), shown for best-case scenarios. Click to enlarge.
Compact checkout with payment method and payment overview
Compact: payment method and amount.
Extended checkout with top-up, invoice selection and payment method
Extended, the same module: top-up, invoice selection and payment method.

Outcome

First solution liveTeam delivery
4 weeks
Recovered outstanding receivablessix figures first, later
seven figuresjoint initiative
04 · Outcome and reflection

What it achieved and what I would do differently

Finance support requestsGoal: −15% · Wallet 1.5
around −80%
Wallet payoutsGoal: +20% · Wallet 1.5
+72%
Recovered receivablesCredit Limit · joint initiative
seven figures

Wallet 1.5 was meant as a stopgap and became the foundation for 2.0. Credit Limit reduced financial risk quickly and created building blocks that carried further payment flows.

What I would do differently today

  1. A smaller stakeholder group

    Too many participants slowed Credit Limit down. A more selective group would have been faster.

  2. Protect focus

    Wallet 1.5 could have shipped in half the time. Side projects with higher priority stretched the plan.

  3. Refine earlier

    The first warning UI needed adjustments after launch to become clearer.

CV · Maximilian Dahl
In plain words

What do you actually do, Max?

My parents and family have nothing to do with tech or my profession. They told me they did not understand my website. This is for them. And for anyone who would like an explanation without the jargon.

I make software easier to work with.

When someone spends ages searching for a button or has to enter the same information three times, I want to know why. I watch how people work, talk to them and design a better way through the task. Then we try it together.

My title is Principal Designer. That means I also make decisions about how whole products fit together and help the team build on them. I still design and write code myself.

Here is a simple example.

At zvoove, I designed an assistant called zAIn. This simplified example shows the idea:

  1. Someone asks

    “How much holiday do I have left?”

  2. The assistant looks it up

    It finds the information and explains the answer.

  3. The person decides

    If they want to book time off, they review the details before anything is sent.

My job is to work out what people need to see, how the answer should be explained and when the program needs their approval.

A design system is a bit like LEGO.

Imagine every team inventing its own bricks. Nothing fits. With a shared kit, the pieces connect, even when people build different things.

Shared pieces. Different things you can build.
Book time offReview an invoice

In software, those pieces are things like buttons, input fields and messages, plus rules for how they work together. I built this kind of kit at Container xChange. It is called Compass.

What has come out of my work?

One starting point
At zvoove, I designed the shared starting point for several programs and tried it out in code. It became Launchpad, which has been live since August 2026.
Built, too
I built the visible part of the notification centre myself. A backend engineer built the part behind it, and we shipped it together.
A team that can build on the work
At Container xChange, I grew the design team from 4 to 14 together with Niclas. Compass gave designers and developers a shared kit to work with.

What am I particularly good at?

I look beyond the screen in front of me. When several teams run into the same problem, I look for a solution they can share. That is how Compass came about.

And I like making an idea tangible early. I can build a working version myself, put it in front of someone and find out where it falls short. I would rather learn that from using it than from a long discussion about a picture.

What would I like to do next?

I want to help decide what a product should become, support a team and keep building myself. I am looking for a role as a Principal Designer, Team Lead or AI Product Builder, in a team that builds with artificial intelligence.

In plain words: I want to take responsibility for the whole thing, without giving up the part I enjoy most — trying things out and making them work.