All work

2026

UniBee Customer Portal

SaaSBillingWeb & Mobile

UniBee is a platform for subscription management, billing automation and global payments. As the customer base grew, so did support load: users had no way to change a plan, understand an invoice, or see a limit coming.

9
Core flows, designed from zero
16
Component sets in the UI kit
US · EU · CA
Tax rules supported

context

I worked directly with a product manager who framed the requirements as a written spec, and designed against it from the first flow through to the review after release.

What I owned

  • Designing the core user flows and working through their edge states
  • Building a scalable design system, producing the Figma UI and preparing dev handoff
  • Design review after release, to hold front-end quality against the layouts

problem

As UniBee's customer base grew, support load grew with it. Users were filing tickets for three reasons.

No self-service

No way to change a plan or manage a subscription on their own.

Opaque invoices

Customers couldn't tell how a total was assembled: base plan, extra resources purchased, overage, regional tax.

A blind spot on limits

Users only discovered they had exceeded a limit after the fact.

research

To design a portal that would actually take load off support, I broke the PM's requirements down into real user scenarios using job stories.

When I run out of traffic or API quota in the middle of the night, I want to buy the package I need in two clicks without digging through settings, so my service doesn't go down and my own customers aren't affected.
Emergency top-up
When finance asks me for a monthly report, I want to see clearly how the total was assembled, so I don't have to recalculate by hand and write to UniBee support for an explanation.
Invoice transparency
When I add a corporate card, I want to see the exact amount including tax before I hit Pay, so I avoid surprise charges and mistakes.
Payment safety

Before designing, I looked at how the main players solve this. Stripe offers a rigid design with no customisation, no one-time purchases and no crypto gateways. Chargebee covers the scenarios, but its interface is overloaded and aimed at B2B finance people rather than a technical SaaS audience. Recurly has limited UI customisation and struggles with non-standard billing scenarios.

CriterionStripeChargebeeRecurlyUniBee (target)
One-time purchasesNoYesPartialYes
Crypto gatewaysNoNoNoYes
Hybrid invoice (sub + one-time)NoYesNoYes
Real-time overage monitoringNoPartialNoYes
Proration preview before paymentYesYesYesYes
Gateway-agnosticNoNoNoYes

Competitors cover the standard subscription flow well, but none of them solves the combination of subscription, one-time purchases and multiple gateways in a single interface. That became UniBee's point of differentiation and set my design priorities.

design

Showing the proration math on a plan change

A user switches plans mid-month. Charge them the full price and they leave. Fail to explain how the unused days are credited back and they bury support in tickets.

I designed Subscription Update Preview as a mandatory intermediate step rather than an optional dialog, the way competitors treat it. The screen calculates what is due today on the fly, accounting for the unused remainder of the old plan. The user sees a transparent calculation before the transaction.

Limit monitoring and a seamless top-up

Blowing through a traffic limit is stressful. Users notice the problem when their product is already cut off. The path from spotted it to fixed it has to be as short as possible.

The top-up flow end to end, from the limit warning to the restored progress bar, with the add-on and the bill recorded behind it.

The entry point into the flow is a bright red progress bar on the Overview screen. The Buy More button sits directly in the point of pain, so there is no hunting through menus. The resource-pack purchase flow, from 10GB to 500GB, with a live-updating cart brings the whole path down to a couple of clicks.

Overview carries the plan, the next billing date and a preview of the next invoice, with progress bars tracking consumption in real time. Going over a limit leads straight into package selection and payment.

Dynamic compliance and tax validation

The product operates globally, so the interface has to adapt to customer type (individual or business) and to regional tax: the 5–15% GST/HST logic in Canada, or per-state rules in the US.

Billing Info is designed as an adaptive step-by-step form. Changing the country pulls in custom interactive hints about that region's tax rules in real time.

edge states

When the payment doesn’t go through

Every billing interface gets the successful path right. What separates them is the minute after a card is declined, or the minute when nobody yet knows whether the money moved at all.

States as they shipped. Awaiting payment: what is owed and one way to settle it. Paid: confirmed and gone. Declined: what to do next, not just what broke. Unconfirmed: the gateway has not answered, and the charge may or may not have landed.

scaling

Scaling: UI kit and mobile

I built the portal on a UI kit I had developed for the product: sixteen component sets covering buttons, tabs, icons, inputs, dropdowns and the smaller elements that repeat on every screen. That kept the interface consistent, simplified dev handoff, and roughly halved the time from a layout being started to it being signed off.

The first job story happens in the middle of the night, away from a desk, so the top-up had to work one-handed on a phone. Every two-column form and table restacks vertically, and payment modals become full-height bottom sheets.

results

The portal is live in the UniBee platform.

  • Every request that used to reach support as a billing ticket now has a self-serve path: plan changes, invoice downloads, card updates, tax details, and top-ups when a limit runs out.
  • Time to task: with the end-to-end purchase flow, an emergency resource top-up takes roughly 15 seconds, down from hours of back-and-forth with a manager.

reflection

In the first iteration we split current status (Overview) and detailed subscription management (Subscription & Add-ons) across separate tabs, so as not to overload the user with data. That was a compromise. Looking back, changing a plan costs the user an extra step and a context switch. My next hypothesis, to test in future usability sessions: merge the two screens into a single working dashboard and cut the cognitive load.