All work

2025–2026

UniBee: From Internal Tool to Market-Ready Product

SaaSFinTechB2BWeb

UniBee worked for the people who built it, because they knew how it worked. To sell it to outside SaaS companies, the same product had to make sense without knowing the system and without a call with the team.

30
Tasks across the five admin sections, from sign-up to tax
US · EU
Tax rules in the merchant settings

Product Designer, the only designer on the team. Team: product manager, frontend, backend and QA. Scope: the merchant admin and checkout.

context

UniBee is an open-source platform for subscriptions, invoices and payments: an alternative to Chargebee, Recurly and Paddle for SaaS companies. It started as an internal tool for a group of companies, Multilogin first among them.

When I joined, the product had a working but rough skeleton: the core entities existed, and the interface grew task by task. That was enough for the internal team. The next goal was outside customers: SaaS companies with MRR from €50K, a health app among the first.

The customer portal, where buyers manage things after the purchase, has its own case.

problem

An outside customer doesn't know how the billing works inside

Where knowing the system was enough for the internal team, a new customer ran into four problems.

No way in

After sign-up, customers landed straight in lists and couldn't tell what was already set up or what to do next.

Plans fell behind the business

The plan page and checkout were built for a single phase, while the business needed plans with several.

Payments went international

Several connections to one gateway, US and EU tax, one invoice paid in parts through different gateways: the admin showed none of it.

Data was hard to find

List filters were scattered across the page, and the main actions got lost.

process

The spec as a starting point, not a finished answer

Many tasks started from customer feedback.

1. Spec and breakdown

The product manager wrote the spec, and we refined the scenarios together before any design started.

2. Prototype and states

Flows, errors, empty states, mobile. Many of the decisions were made here.

3. Check

Contested scenarios were tested with the internal team.

4. Handoff and review

A spec for the frontend, and after development, a check of the build against the layouts.

product map

The admin has five sections, and I worked on tasks in all of them: from sign-up and plans to admin permissions, emails and multi-currency. Below are the four hardest stories.

design 1

Finding your way in the product

An outside customer has to get into the product on their own and see right away what to set up next. For that I reworked sign-up and designed Home, which didn't exist before.

Sign-up in two steps

I kept the first step minimal: email, password and confirmation, plus sign-in with Google and GitHub, which a technical audience expects. The details billing needs moved to the second step: name, company and country. The country isn't a formality here: tax and currency depend on it.

A quick way in, with a preview of the product on the left. Errors appear next to the field they belong to.

Home: one page instead of searching through sections

Before Home, customers landed straight in lists after signing in. Now the first page answers two questions: how things are going and what isn't set up yet.

Summary

Active products, customers, successful payments and the success rate.

Setup steps

Action cards that lead straight to the right section: set up plans, connect an integration, look at the metrics.

The summary stays useful after launch, so Home became a permanent section rather than one-off onboarding.

What's happening and what to set up next. Each step shows its status and leads to the right section.

design 2

Plans and checkout

The business moved to plans with several phases: for example a trial, then discounted rates for different periods, then the main rate. That touched both sides: how a merchant sets up a plan and how a buyer pays for it.

Setting up a multi-phase plan

The plan page was built around a single phase. I rebuilt it so each phase became its own block.

Phases separated visually and in order

It's clear which setting belongs to which phase, and editing one doesn't touch another.

Errors on the phase itself

A plan with an empty phase or the wrong order won't save, and the problem is highlighted right in that phase's block.

Older single-phase plans still open and work as before.

Each phase in its own block, with a summary of the plan and its empty fields on the right.
The price of a published plan can't change by accident: to edit the name and price, the plan has to be unpublished first.

Checkout: from one page to three steps

The old checkout was one long form and couldn't show payment by phase. The spec suggested splitting it into four steps.

Internal testing showed that too much information at once confused people. We merged the buyer's details and address into one step and kept three. Fewer steps, each short and about one thing.

Your Info → Payment → Confirmation

The order summary is pinned on the right and shows the whole subscription path by phase: what to pay today and what comes later. Changing the country or entering a VAT number recalculates the tax and total immediately. The buyer chooses whether they subscribe as an individual or as a company, and on mobile the total and the button move to the bottom of the screen.

The subscription path by phase and today's amount stay visible from the first step to the confirmation.

Checkout is the moment of purchase, and the customer portal is life after it. Together they cover the buyer's whole journey.

design 3

Global payments

UniBee customers sell worldwide: they connect several gateways, pay US tax and take payments in parts. Three tasks made that complexity manageable from the admin.

Gateway connections

A merchant connects many gateways at once: cards, crypto, bank transfer, local methods. Any gateway can be duplicated, and at a customer's request each gateway got a page listing its connections. Before, it wasn't clear how many connections a gateway had or which one was live.

  • A list of connections with their status: ready to use or archived.
  • The main connection marked with a star, search by name and email, and actions in a menu on each row.
  • In a connection's settings: the display name, up to five payment method logos sorted by drag and drop, and the issuing company's details that go on invoices sent through this gateway. That way one merchant can invoice from different legal entities.
Connected gateways, and new ones in one click. A connection's settings hold the method logos and the invoice issuer.

US and EU tax

Tax has to be something you can set up without being a tax consultant, so I split the page into two levels.

Connection

Turn on US tax and choose a provider. If TaxJar isn't connected, the field points to where to do it.

Global default rules

They apply to every product, and a product or plan can set its own tax address and override them.

The European case is covered by VAT: the buyer enters a VAT number at checkout, and the tax and total are recalculated immediately.

Connecting the provider, and the global default rules.

Refunds on invoices paid in parts

One invoice could be paid through different gateways: for example $2,000 through Stripe and $3,000 through Payssion. Compliance requires the money to go back where it came from.

I added a refund method choice to the refund dialog. It lists the invoice's successful transactions with the amount available, such as “Stripe, $2,000 available”. The refund won't start without a method, and the amount is checked against the chosen channel's limit.

The money goes back where it came from.

design 4

Working with data

The user list was the first screen to get the new global filter component. The task was bigger than one page: set the pattern for every list in the admin.

Before: some filters sat in the table header and some at the top of the page. Search took a lot of height, and “Create user” along with import and export were hard to find. After:

One way into filters

The Filter button opens a panel with the fields: name, email, status, date created, subscription plan.

Chips instead of an open panel

Once applied, the panel closes and the chosen conditions stay above the table as chips. You can see what's filtered, and any condition comes off in one click.

A hierarchy of actions

“+ New User” became the primary button at the top right, and import and export moved to secondary actions.

More data on screen

The top area got more compact, so the table shows more rows without scrolling.

The same pattern is meant for subscriptions and refunds, so filters work the same way in every list.

The panel is open. Once applied it closes, and the chosen conditions stay as chips above the table.

edge cases

When something goes wrong

In billing a mistake costs money, so in every story I designed more than the happy path.

SituationWhat the person sees
An error in a checkout stepThe step doesn't advance, errors appear under the fields, and focus goes to the first wrong field
The gateway declined the paymentThe buyer stays on the payment step, sees the reason and can choose another method
Editing a published planThe phases are locked with a hint: to change the name and price, unpublish the plan
Disconnecting TaxJarA confirmation: the integration is removed together with its API key
The session expiredA sign-in window over the page, with the data kept

results

A product an outside customer sets up on their own

After these changes, UniBee started onboarding outside SaaS customers.

  • Customers got one way in: two-step sign-up and a Home that shows what isn't set up yet.
  • The multi-phase model is supported end to end, from a merchant setting up a plan to a buyer paying for it.
  • The admin now handles international cases: several gateway connections, US tax, refunds on invoices paid in parts.
  • The filter with chips became the shared pattern for lists.