Made a bank's tools into one product

What I walked into

Corporate clients ran their working day across four interfaces, each shipped by a different team, each with its own idea of what a payment looks like. Design was a service desk taking screen requests.

My job was to set the rules the product runs on. Not to draw the screens.

Operations

Payments, statements and currency control lived in three separate places with three ways to filter, sign and track the same document.

We merged them into one surface with a single model underneath. Signing a payment went from [X] steps to [Y].

Extended mode

The new interface tested well with owners and managers. Accountants hated it.

They work in volume. The density they had wasn't the obstacle — it was the tool. So we shipped extended mode: the old table logic, rebuilt on the new system. Two ways to use one product, on purpose.

Accountants are the segment that keeps the platform alive.

Across the product

Transfers were rewritten to speak like a person. The home screen was rebuilt around what people actually open the app to do. Foreign trade, deposits and lending followed the same rules.

Five surfaces, four designers, one system. I owned the rules and the review.

The assistant

Then I built one myself.

Business owners ask it questions in plain language and get answers pulled from their own accounts — no menu diving, no learning where things live. I designed it and coded the working product.