Back

Endl

A regulated stablecoin banking platform for cross-border payments across APAC and the UAE.

For around 1.5+ years I was the only designer: the product, the website, the brand, the motion, the decks. This page is all of it, in the order it happened.

Role

Sole designer & design engineer

Timeline

April 2025 - September 2026

Stack

Figma, Paper, Claude Code, Adobe Creative Suite

Surface

Web & mobile app, marketing assets, investment materials, website

The website

First, people had to trust us.

Nobody moves money through a website that looks unfinished. Before the product could sell, the site had to carry the credibility of a bank. I designed and built it three times from ground up as the company found its footing.

Businesses moving six figures through a regulated corridor do their homework long before they book a call. They want to know who is registered, who holds the money and what happens when something breaks, so I made sure the site answered all of it upfront. Every page I added took one more question off the sales team.

Knowing that features shipped every few weeks and the narrative kept on changing, I constantly created various hero sections for the landing page that would resonate with the marketing content going out. This made sure the same information was conveyed across all channels, building a strong brand image.

Within a week of Claude Code releasing, I started learning how to implement my designs into functional websites. I had built two versions of the site on a no-code platform before that, Framer, but after picking up a bit of new terminology and watching how the developers on the team managed the pipeline, I learnt how to create a branch, make changes, test, ship it and raise a pull request.

In total I have raised 55 pull requests so far, adding up to +118,056 lines of code.

Having worked inside Framer on all the previous projects, I already had the habit of building properly responsive components and testing functionality once they were done, so that process stayed the same.

In total I shipped around 162 pages, bringing in over 152,683+ visitors across the website. I also made a lot of technical SEO fixes, and created automated CMS skills inside Claude for the blogs.

So every raw written blog now goes through a proper SEO check, gets enriched with the right keywords for maximum visibility, and has its thumbnails and infographics generated autonomously, and then a skill creates a new branch and pushes the new set of blogs live.

The fundraise

Then we needed capital.

Early-stage fintech raises on trust and clarity. I designed the pitch deck, the investment memo, and the white-label proposals that went in front of investors and enterprise partners.

I designed investor and sales decks, 50+ iterations throughout, various proposals for the B2B offerings and investment memos, helping the team raise $1.5 million combined so far (as of September 2026).

The product

Then we built the bank.

When I picked up the dashboard revamp, the problems were visible in the first minute. Three different balances competed on one screen, stats sat at the same visual weight as the money itself, primary actions had no clear home, and everything fought for attention at once. The platform was complete and functional, and almost impossible to read.

What I found

The old dashboard, before any of the revamp work.

1. 01Three balances on one screen with no hierarchy between them
2. 02Stats merged visually with the main balance
3. 03Primary actions placed without a clear pattern
4. 04Tables used for every list, on every screen
5. 05No max-width behavior, layouts broke on wide and small displays
6. 06Too much information shown at once, nothing prioritised

Foundations first

Branding, then a system to build on.

I started by applying the updated branding to the existing application, then built the design system underneath it, color variables for both dark and light, a scalable typography library, and a gathered icon and flag set. With the tokens in place I started building components.

Understanding the machine

Mapping how the money actually moved.

I synced with the product team and mapped the internal money-movement architecture, then drew all of it down in flowcharts until I understood how the adjacent features connect, stablecoin token transfers, corporate cards, remittances, deposits, and how money actually moves between them.

These flowcharts contain the research process, understanding the money flows and eliminating unnecessary steps or displays of information, all of which were mandatory in the new mature product design.

Talking to people in the same position

I then spoke with friends who run remote agencies working with global clients, about how they hold their money, how they spend it, and what changes when they travel. Their pain points pointed the same direction the flowcharts did, the product had to become the simplest banking surface possible.

The most overwhelming element

Tables, everywhere.

Recipients, transactions, account activity, every list was rows and columns. It looked fine in design files and fell apart in use, on a 1440px or 1280px display it didn’t fit, and with no max-width behavior a wide curved monitor stretched it into a genuine accessibility problem.

I redesigned the components from scratch into elements that hold at every screen size and read at a glance. The full reasoning lives in its own breakdown.

I made sure that the components are easily understandable, and every important detail stayed in place.

The new dashboard

The face of the app.

The dashboard is the first thing anyone opens, so it carried the most weight. It leads with one balance instead of three, and the stats sit below it now rather than competing at the same size. The primary action is the one people actually came for, opening the deposit details to receive money. Recent transactions use the row component instead of a table, and the whole layout is centered with a max width, so it holds from a 1280px laptop to a wide curved monitor.

Making money-in obvious

With the primary action settled, I built the deposit page around the one thing people actually do there, which is copy details. Every field copies on its own for anyone filling a form line by line, and the whole set copies in one go for anyone pasting into their bank. For stablecoins the network and token are chosen before any of it renders, so the address on screen is always the right one and nobody sends funds to a chain the account is not watching.

Calming the accounts screen

The previous accounts screen was overwhelming, cluttered information, and yes, more tables. I optimised it significantly. At the bottom sits the default fund destination the person selects, and if they want, they can set a preferred network and token so deposits land and convert into stablecoins directly.

Every money flow, one shape

Then I revamped all the money flows, sending to a wallet address or a bank account, depositing fiat or stablecoins, whether from yourself or from someone else. Each flow sits centered with a clear stepper and unambiguous actions, so wherever money moves, the screen behaves the same way.

The recipients library

Solving the repetitive payment problem.

Most clients send money to the same set of people every time, and they hold their own bank details for withdrawing earnings into local accounts. So I introduced a library where recipients are stored and managed, distinguished as individuals or businesses.

Adding a recipient works from its own dashboard with a stepper that asks for everything up front, bank details or crypto wallet address, and the same flow can be entered from inside send money.

Next time, the person just selects the recipient and sends. The B2B customers gave a lot of positive feedback on this one.

Transactions in one place

All transactions live in a single dashboard, accounts and cards together, with ample filter options so anything can be traced properly. Whatever the row doesn’t say, the transaction details page does.

Stablecoin corporate cards

Then came the corporate cards. Organisations create multiple cards per department, set limits, control every card in detail, and track their entire expenses. The person spends in any local currency while the amount deducts only from the stable fund balance the owner deposited. A very handy product.

I also designed the physical card itself and got the stakeholders aligned on it. VISA later approved the design, and it now shows up directly inside Apple Wallet when added.

Two balances, one screen

Then a real problem arrived. The primary balance already existed, the account balance, and now card funds had to join it, because the card money lives in a separate contract on the backend.

That was infrastructure, not a design choice, so the job became finding an intuitive way to clearly distinguish the two balances without overwhelming the user. I ran an in-depth study of how other fintech applications convey the same message, because the underlying model is actually ideal, a separate balance for your entire team’s card spend. The whole investigation has its own page.

Invoicing without the friction

I also worked on invoicing and kept sending an invoice as simple as it can be. All the receiving details sit ready inside dropdowns, so the person just selects the account they want to receive funds in and sends.

Invoice creation is usually tedious and feels overwhelming most of the time, so I turned the entire process into a three step form. The person only fills the form and never has to get into design or any other creation ops. The invoice was ready once the form and the receiving details were in, sitting in the dashboard with the receiving currency, amount, due date, invoice number and vendor name all placed intuitively.

Through all of it I kept the application as simple as I could, leaning on one visual principle, a faded background with pure white foreground elements, so what matters lifts off the page and the user never has to work out what they’re looking at.

The product, running

I motion designed multiple demo videos that guided users through the entire process behind various features of the web application. This reduced the effort the operations team spent solving the same queries for multiple customers.

Here are a couple of them ~

Creating cards process

Sending money to a wallet address

Going live

The app launched on Product Hunt, where it held #1 Product of the Day for a good part of the day and closed at #3 globally. I made the motion video for the launch, and the App Store and Play Store carousels as well.

Then came the animations

I worked on a bunch of motion graphic videos. I liked expressing the vision of the product through animation, and explaining what it does.

The systems

AI was advancing fast, and I wanted to catch up with it beyond the eight hours of work.

So I learned how to create systems, and how image generation workflows could be implemented on the marketing side. I set up mockup generation and graphic generation systems inside Magnific AI, and generated assets for multiple video paid ads, social media graphics, and card mockups.

The emails

I worked on 50+ different HTML files for both the marketing and product teams, developed them, and made them HubSpot friendly. Those went out for cold outreach, customer communication, and promotions.

Conclusion

There were several creative projects I worked on during my time here that I could not list down. Being a Swiss Army knife for a very lean startup, with little time to achieve everything, I learned a lot.

I have always been oriented towards owning a project and completing it with absolute precision. And since I browsed an enormous amount of inspiration throughout, I developed a strong taste for modern global design, and learned a lot about the industry, marketing, its distribution channels, and how the entire product moves.