Maiwey

A 30-year financial group that had never spoken to a retail customer. I built their brand and two products from zero.

Client
A&G
Role
Product Designer
Team
3 designers · 1 PM
Year
2025
Scroll ↓
Maiwey product ecosystem - browser, mobile, and laptop
Overview

The challenge

A&G had decades of B2B financial experience but had never spoken to retail customers. They needed a brand, a marketing website, an investment platform, and a mobile app. My job was to design all of it.

Problem
Zero digital presence, zero brand, competing against established fintechs
My role
Research, brand, product UI, and documentation across the full scope
Outcome
2 products shipped: a public marketing site and a private investment platform, both mobile-first
Discovery

They didn't distrust fintech.

The assumption was that people distrusted fintech. They didn't. They distrusted complexity: jargon, hidden fees, interfaces that assumed financial literacy. That finding shaped every design decision.

Product 01 · Public marketing site
01 The landing experience

The brand had to sell itself before users ever logged in.

No branches, no ads at launch. The website was the only way in. I put the savings simulator above the fold, before any brand messaging. Users engaged with the calculator before scrolling.

Maiwey public marketing website - three-page spread showing landing page with savings simulator, product explainers, and investment fund comparison
Product 02 · Private investment platform
02 Savings + deposits

Users needed to feel their money growing.

The balance doesn't change day to day. The interest does. Testing showed users kept checking the balance, seeing no change, and disengaging. I flipped the hierarchy, making interest earned the largest element on screen.

Savings and deposits - mobile renewal screen, web deposit form, and iPhone deposit detail showing interest earned
03 Investment dashboard

Users couldn't tell if their money was doing well or not.

Testing showed users needed to compare across funds, not view them one at a time. I redesigned it as a multi-fund overview. A glance on any screen should answer "am I up or down?"

Key decision

I adapted data density per breakpoint. Desktop shows the full chart with granular data points. Mobile keeps only the trend line and key numbers. Same data, different depth, because context changes with screen size.

Investment dashboard - mobile fund detail with performance chart alongside desktop portfolio overview with multi-fund comparison
04 Risk profile

Regulators required a suitability test. Users hated forms.

Most platforms bury this in a 30-field form. I broke it into three sections, one question at a time.

Key decision

I added "why are we asking this?" to every question. Legal pushed back because they worried plain-language explanations might create liability. I sat with the compliance team and we wrote each explanation together, keeping it accurate but plain. Drop-off fell by a third.

Suitability test - desktop form with progressive questions and 'why are we asking this' explanations, alongside mobile risk profile result
Brand identity

The arrow in the "a".

I modified the typeface Nohemi in three places: the "a" became an upward arrow, the "m" flipped into a "w", the "i" lost its dot. That arrow became the app icon, the favicon, and the one element users recognize at any size.

Maiwey brand identity - the arrow in the 'a' letterform, app icon, favicon, and brand mark at multiple sizes
Impact

What I shipped.

Engagement
85% suitability test completion
Progressive disclosure and plain-language copy cut drop-off by a third.
Delivery
2 products shipped in 4 months
Marketing site + investment platform, both mobile-first.
Autonomy
Client scaling brand independently
40-page brand manual built to outlast the engagement.
Takeaways

What this project taught me.

Build brand and product at the same time, not in sequence.

Every visual decision had to survive a 320px screen. I now test identity work at the smallest breakpoint before presenting it at full scale.

In fintech, clarity is the feature.

The suitability test taught me that explaining why you're asking is more effective than simplifying the question. I now write interface copy that justifies itself.

Next project
MiSIP

Hi there,
say hello :)

Message sent!

Thanks for reaching out, I'll get back to you soon.