Dual-currency wallet for B2B consulting teams
Project Type
B2B, IT Consulting, Web Design
Team
1 UX Researcher/Designer (Me), 2 Engineers, 1 Project Manager, 1 CEO
My Role
UX Research & Design Intern
Timeline
3 months (Jun–Sep 2025)
Overview
Marketeq Wallet is a 0→1 desktop web wallet built for clients who manage service payments across multiple IT consulting projects. When returning clients couldn't see their remaining balance spread across projects, states, and currencies, they paid again instead of reusing existing funds, creating unnecessary refunds and operational overhead.
What I did
I led end-to-end UX research and design, reframing the problem from refund delays to balance visibility. The result is a centralized wallet that surfaces usable funds by currency and project state, with inline USD–TEQ conversion transparency to support confident payment decisions.
my Impact
From “Wait… do I still have money?” to confident decisions.
+45%
Clearer balance visibility
-62%
Fewer duplicate payment attempts
0→1
Ｗallet built from scratch
Final Design Preview
Key Feature 1/3
Balance breakdown across project states
Key Feature 2/3
USD–TEQ conversion preview
Key Feature 3/3
Project allocations and insights
Quick Context (for non-fintech readers)
Who are the users?
Operations leads or finance contacts who manage budgets and authorize payments across multiple consulting projects on the platform.
What is TEQ?
TEQ is an internal balance that clients can use to pay for services on the platform, similar to stored credit rather than a public currency.
Why dual-currency?
Due to business and accounting constraints, payments are made in USD while value can be stored and reused as TEQ for future projects.
The Problem
30% of returning clients paid again instead of reusing existing balances, leading to unnecessary refunds and operational overhead.
What we initially got wrong
We assumed the problem was refund speed, but wait…
How I changed the strategy
Research revealed the real problem was visibility, not refunds.
Through 5 client interviews and competitive analysis across 20+ platforms, I identified key patterns across user behavior and system workflows. The findings reframed the problem from refund delays to balance visibility, uncovering its impact on decision confidence and repeated payment behavior. I brought this evidence to the PM and CEO to shift the project direction.
Design Goal
How might we help clients confidently decide whether to pay again by clearly surfacing usable balances across currencies and project states?
Defining MVP
Working with the CEO and PM, we prioritized balance visibility as the core problem to solve. TEQ incentive features were deferred to a later phase, with the business planning to introduce TEQ adoption once the core wallet experience was stable.
Unified balance overview
USD and TEQ balances in one place, broken down by account state.
USD-TEQ conversion preview
See conversion outcomes before moving funds, reducing dual-currency uncertainty.
Project allocations and insights
Per-project balance status with health indicators that flag issues before they escalate.
FEATURE 01 — UNIFIED BALANCE OVERVIEW
Decision 1: How to display dual-currency balances
To make each balance type clear at a glance, USD, TEQ, and the combined total are displayed as separate cards. This prevents clients from confusing the total with what is actually available to spend in each currency.
Decision 2: How to make USD and TEQ visible through project states
Defining 4 balance states gave clients a shared vocabulary for where their funds were. Visualizing the breakdown as proportions made it easier to read allocation at a glance, without calculating the numbers manually.
FEATURE 02 — USD-TEQ conversion preview
Decision 3: How to surface conversion transparency
Clients needed confidence in the TEQ rate before committing to a conversion. Surfacing the live rate and historical trend inline gave them the context to make the decision without leaving the page.
FEATURE 03 — Project allocations and insights
Decision 4: How to surface project health without manual checking
Clients needed to know which projects required attention without checking each one individually. Three layers of visibility work together: balance state cards at the top, health badges per project, and a portfolio summary at the bottom.
Final Solution
Design 1/2
A unified wallet dashboard designed to centralize balances, conversion tracking, and payment actions.
Design 2/2
Managing project allocation, pending usage, and balance health in one workspace.
Before
Balances were scattered across project pages, emails, and invoices
Clients couldn't tell how much was still usable before checkout
Internal teams handled frequent refund requests and manual adjustments
After
Remaining balances are centralized and visible in one place
Clients see what's available before deciding to pay again
Balance clarity reduces confusion across currencies and projects
Impact & Takeaways
The design improved balance visibility across currencies and project states, reducing the mental effort clients needed to make confident payment decisions.
I ran a comparative usability study with 8 returning clients, testing identical tasks across the existing workflow and the redesigned prototype.
+45% Clearer balance visibility
-62% Fewer duplicate payment attempts
My biggest takeaway: The most impactful decision was how to present and visualize the information users already needed, making balance states readable at a glance rather than something to calculate.
Reflection
Clarity reduces 0→1 ambiguity.
Designing a 0→1 product was initially uncomfortable because many assumptions were unproven. I learned that clarity doesn't come from having all the answers, it comes from asking better questions and staying aligned with the people around you. Working closely with the CEO, PM, and engineer taught me how business priorities and technical constraints shape design scope, and how early alignment makes iteration faster.
If I had more time…
I would track post-launch metrics such as repeat payment rate, refund volume, and funding time to validate long-term impact. I would also run more usability testing rounds to iterate and confirm whether the design truly matches what users need. And I would explore predictive prompts that proactively surface remaining balances before checkout.