Recipient Revamp

2025

Building new recipient management system

Revamp of Aspire’s recipient management system; a core feature that enables businesses to manage who they send funds to.

Role and responsibility

Led end-to-end UX design from research to final solution.
Partnered with CX team to translate customer pain points into actionable improvements
Collaborated closely with PMs, engineers, and QA to define scope, MVP flows and quality.

Skills

UX audit, competitor research, feature requirement, flow diagrams, wireframing, user interface design, rapid prototyping

TL;DR Version

~2 minutes read

Context

Aspire’s recipient system was outdated; only accessible during transfers, lacked management options, and caused friction for users handling large volumes.

Goal

Build a scalable, reliable recipient management system to simplify workflows, reduce duplicates, and support multi-currency and multi-account setups.

Research & Process

Research: UX audit of existing flows, internal user interviews, competitor study, CX team insights
Define: MVP focused on reliability & scalability
Design: Wireframes → refined flows → high-fidelity UI
Deliver: Phased rollout aligned with new design system

Solution Highlight

Centralized recipient directory
Multi-account & multi-currency support
Edit, filter, and status controls for clarity
Scalable structure for future integrations

Impact

Expected 25–30% fewer duplicate entries and 20% faster recipient creation, improving efficiency and scalability across Aspire’s ecosystem

Detailed Case study

About Aspire

Aspire is an all-in-one finance platform for modern businesses.
It helps companies send, receive, and manage money easily in one place. Transfers are much cheaper compared to traditional banks.
Offers tools for cards, payments, expenses, budgets, and reports.

Aspire’s upcoming home page; part of the upgraded UI to be rolled out by Q4 2025. The Recipient Revamp design will align with this new design system, while current analysis is based on the existing interface.

Who is this for?

Designed for founders, finance teams, and business owners managing company finances. Used by startups and SMEs across Southeast Asia.

Why revamp the recipient system?

The current recipient screen is limited to basic selection and lacks management features like view or edit. It also does not include essential utilities such as sorting and filtering, making it difficult for users to manage multiple recipients efficiently.

Aspire needed a scalable in-house system to support flexible partner integrations and future product growth.
A revamp was essential to enable scale across product areas like payroll and bills and improve reliability.
The existing recipient system is outdated and limited; only accessible during the transfer flow.
Enhance feature during UI upgrade

What process did I follow?

1. Research
1. Business requirements
2. UX audit - Current experience
3. User interviews: Internal finance users+ CX teams
4. Competitor analysis

2. Define
1. Synthesized insights to identify core user needs and system gaps.
2. Defined MVP scope focused on reliability and scalability.
3. Mapped user journeys and flows for core tasks like add, edit, delete and make transfer.

3. Design
1. Low-fidelity wireframes to explore layouts and interactions.
2. Developed high-fidelity UI designs
3. Roundtable sessions for feedback
4. Validate technical feasibility.

4. Deliver
1. Delivered final design specs and prototypes
2. Documented guidelines
3. Supported handoff and QA

UX Audit & User Interviews insights

No view, edit capabilities for existing recipients
Duplicate entries for single recipients with multiple accounts
No sort, filter capabilities
Payroll and Bills require recipients integration
CX tickets - Recipients are hard to find in the product
No error handling
No clear status communication
Additional information asked constantly

Competitor Analysis

I conducted a competitive analysis of major players including Revolut, Brex, Mercury, and Wise, examining their end-to-end user flows and feature offerings. The analysis revealed that all of them offer advanced account and fund management capabilities.

All competitors provide a centralized recipient directory
View, edit, filter, sort and update capabilities are common
Major ones provide multi account capability
All of them provide clear status communication

Defining Goals

Provide recipient directory with management capabilities and for scale across product.
Support multi-account and multi-currency scenarios.
Simplify and reduce friction when creating/updating recipient details
Create universal recipient form for each currency
Enable better discovery and control for power users.
Enhance error handling & status communication

Design concepts & flows

Early design explorations

Various recipient creation and editing flows, evaluating their alignment with the transfer journey and integration across related product areas.

Low fidelity Wireframes

After aligning on the overall direction, I developed low-fidelity wireframes to outline and detail the key user interactions.

High fidelity Designs

Translated the low-fidelity wireframes into high-fidelity designs using the new Design System 2.0, and further refined them based on stakeholder feedback.

Final Design

Challenges

Balancing scalability vs. simplicity
Working around legacy system (partners/tech) constraints
Aligning with engineering, compliance, and product
Improving discoverability without adding clutter

Key Learnings

Balance flexibility and clarity in complex systems
Early cross-functional collaboration avoids rework
Focus on JTBD to translate information hierarchy
Phased rollout = smoother adoption & reliability

More projects

Redefining design system for Aspire's rebrand

Translating new brand identity into product UI

2025

Enable users to remove duplicate records from database

Manual person data merge - Data hygiene

2022

2025

Building new recipient management system

Revamp of Aspire’s recipient management system; a core feature that enables businesses to manage who they send funds to.

Role and responsibility

Led end-to-end UX design from research to final solution.

Partnered with CX team to translate customer pain points into actionable improvements

Collaborated closely with PMs, engineers, and QA to define scope, MVP flows and quality.

Skills

UX audit, competitor research, feature requirement, flow diagrams, wireframing, user interface design, rapid prototyping

TL;DR Version

~2 minutes read

Context

Aspire’s recipient system was outdated; only accessible during transfers, lacked management options, and caused friction for users handling large volumes.

Goal

Build a scalable, reliable recipient management system to simplify workflows, reduce duplicates, and support multi-currency and multi-account setups.

Research & Process

Research: UX audit of existing flows, internal user interviews, competitor study, CX team insights

Define: MVP focused on reliability & scalability

Design: Wireframes → refined flows → high-fidelity UI

Deliver: Phased rollout aligned with new design system

Solution Highlight

Centralized recipient directory

Multi-account & multi-currency support

Edit, filter, and status controls for clarity

Scalable structure for future integrations

Impact

Expected 25–30% fewer duplicate entries and 20% faster recipient creation, improving efficiency and scalability across Aspire’s ecosystem

Detailed Case study

About Aspire

Aspire is an all-in-one finance platform for modern businesses.

It helps companies send, receive, and manage money easily in one place. Transfers are much cheaper compared to traditional banks.

Offers tools for cards, payments, expenses, budgets, and reports.

Aspire’s upcoming home page; part of the upgraded UI to be rolled out by Q4 2025. The Recipient Revamp design will align with this new design system, while current analysis is based on the existing interface.

Who is this for?

Designed for founders, finance teams, and business owners managing company finances. Used by startups and SMEs across Southeast Asia.

Why revamp the recipient system?

The current recipient screen is limited to basic selection and lacks management features like view or edit. It also does not include essential utilities such as sorting and filtering, making it difficult for users to manage multiple recipients efficiently.

Aspire needed a scalable in-house system to support flexible partner integrations and future product growth.

A revamp was essential to enable scale across product areas like payroll and bills and improve reliability.

The existing recipient system is outdated and limited; only accessible during the transfer flow.

Enhance feature during UI upgrade

What process did I follow?

UX Audit & User Interviews insights

No view, edit capabilities for existing recipients

Duplicate entries for single recipients with multiple accounts

No sort, filter capabilities

Payroll and Bills require recipients integration

CX tickets - Recipients are hard to find in the product

No error handling

No clear status communication

Additional information asked constantly

Competitor Analysis

I conducted a competitive analysis of major players including Revolut, Brex, Mercury, and Wise, examining their end-to-end user flows and feature offerings. The analysis revealed that all of them offer advanced account and fund management capabilities.

All competitors provide a centralized recipient directory

View, edit, filter, sort and update capabilities are common

Major ones provide multi account capability

All of them provide clear status communication

Defining Goals

Provide recipient directory with management capabilities and for scale across product.

Support multi-account and multi-currency scenarios.

Simplify and reduce friction when creating/updating recipient details

Create universal recipient form for each currency

Enable better discovery and control for power users.

Enhance error handling & status communication

Design concepts & flows

Early design explorations

Various recipient creation and editing flows, evaluating their alignment with the transfer journey and integration across related product areas.

Low fidelity Wireframes

After aligning on the overall direction, I developed low-fidelity wireframes to outline and detail the key user interactions.

High fidelity Designs

Translated the low-fidelity wireframes into high-fidelity designs using the new Design System 2.0, and further refined them based on stakeholder feedback.

Final Design

Challenges

Balancing scalability vs. simplicity

Working around legacy system (partners/tech) constraints

Aligning with engineering, compliance, and product

Improving discoverability without adding clutter

Key Learnings

Balance flexibility and clarity in complex systems

Early cross-functional collaboration avoids rework