Investor Dashboard
Year
2025
Project Type
Product Design | Freelance Project
Skills
UI/UX Design | Mobile-First Design | Responsive Web | Financial Data Visualization | Design System Integration (ShadCN)
Qeratech’s Investor Dashboard is a mobile-first web app designed to give crypto investors a clear, accessible view of their Bitcoin performance - without the complexity of trading platforms like Binance. This case study showcases how I translated backend metrics into a calm, user-friendly dashboard that empowers clients to check their investments with confidence and ease.
Project Overview
My Role
What I Was Hired To Do & By Whom
Qeratech is a third-party service managing Bitcoin investments on Binance for clients who want a hands-off trading experience. The company had backend functionality and internal processes but no user-facing or centralized operational interfaces.
I was brought on as a freelance product designer to design three responsive platforms from scratch:
-
An investor dashboard for clients
-
A trader interface for internal portfolio oversight
-
An accountant platform for financial tracking (in progress)
Who are the target users?
Everyday investors, not traders
The users of this interface are individual investors who prefer to outsource the trading and portfolio management to someone else. While they typically understand basic financial terms, they don’t want to manage the intricacies of trading. What they do want is a quick, trustworthy overview of how their investments are doing.
Though I didn’t have direct access to the users, I gathered insights through:
-
Conversations with the founder (who regularly interacts with clients)
-
Quick reviews of competitor dashboards
-
Informal chats with crypto-investing peers
Users check their investments often - usually from mobile - but feel overwhelmed by the default Binance dashboards. The goal was to replace that with a calmer, clearer experience.
The starting point
Designing from the data up
The company already had backend infrastructure to manage trades and track performance, but no interface for clients to view their own investment status. My task was to create the full UX and UI from scratch.
I received backend metrics and worked closely with the founder to determine what mattered most:
-
Which data points to display (and which to leave out)
-
How to name and organize data so it made sense to non-experts
-
How to visually prioritize the most important insights
Since most users would check the dashboard on their phones, I took a mobile-first approach, while ensuring full responsiveness for desktop. The final design needed to feel simple, professional, and easy to check at a glance.
The interface was intentionally minimal, offering only essential user actions: log in, update password, change currency, and log out.
The scope of the design
A dashboard for the Investors
The goal was to design a focused dashboard that would give clients exactly what they need, and nothing they don’t. No trading tools, no data overload, just a clean, reliable view of performance.
The dashboard aimed to:
-
Help clients understand their profit and overall portfolio status
-
Remove noise and technical language
-
Reinforce trust in the service by showing information clearly and transparently
This wasn’t about teaching users to trade, it was about helping them feel informed and confident without having to dig.
Key Challenges & Solutions
1. What data should we show & what should we leave out?
The challenge
Clients didn’t need access to every backend metric available in the system - only what was relevant, clear, and meaningful. The core question was: how much is too much to show? Showing too little could feel vague; showing too much could overwhelm and confuse.
Process & exploration
I received a raw list of metrics used by the trading team, including BTC/USDT values, monthly/daily PnL, account start dates, and more.
I received a raw list of metrics used by the trading team, including BTC/USDT values, monthly/daily PnL, account start dates, and more. Using ChatGPT and domain research, I built up my own understanding of each metric’s role. I then assessed which were directly useful to clients, and which might create noise or confusion.
I grouped related metrics into categories like "Investment Summary" and "Profit Over Time," and noted those most frequently checked by users (e.g., Total BTC, Daily/Monthly Average PnL). I also consulted the founder and several casual Bitcoin investors to validate these assumptions. There were no disagreements, though the founder requested I include the account onboarding date - which I added to the user profile section.
The solution
I presented high-priority values like Total BTC, Daily and Monthly PnL at the top of the interface, using visual hierarchy and grouping to organize the rest. To avoid constant number shifts tied to real-time BTC conversion, we chose to display values primarily in BTC, with a converted currency value below for user-selected currencies.
2. How do we present profit/loss in a way that's clear and intuitive?
The challenge
Bitcoin dashboards deal with large numbers, variable formats, and multiple currencies. Without standardization, it’s easy for profit/loss values to become unreadable or emotionally unclear.
Process & exploration
I created a matrix comparing several display options -signs, color-coding, full-sentence labels, symbols, rounding, iconography, and combinations thereof. I also reviewed how other platforms handled this and found there was no consistent standard.
In Figma, I visually tested combinations across use cases to evaluate scannability and visual balance. I also considered the need for tooltips and format adjustments for non-expert users, though the founder confirmed that clients were already comfortable with most financial symbols and terms.
The solution
I implemented signed, color-coded values with BTC as the primary unit and a converted USD/selected currency value underneath. I used consistent formatting and alignment across all views. This struck a balance between emotional clarity and practical detail - especially important on mobile, where space is tight.
3. How can we stay transparent about losses without making users feel anxious?
The challenge
Unlike demo data, real dashboards include losses. The challenge here was emotional tone: how to show dips transparently without making the interface feel negative, risky, or untrustworthy - especially since losses are common in trading.
Process & exploration
I began by mocking up screens showing ideal performance - but then stress-tested the interface using negative-value data to see how the tone shifted. Color intensity, terminology, and layout all played a role. I also thought carefully about how to introduce the company’s 20% fee without making it feel like a hidden cost or a focal point.
The solution
I adjusted color hues to be softer and used “Earnings” instead of “PnL” or “Profit,” which helped frame losses more neutrally. Negative numbers were styled gently but clearly. I moved the 20% fee disclosure into the terms section with an (i) icon - accessible but not emphasized. All labels were revised to be transparent without feeling harsh.
4. Designing a graph visualizing investment growth (for mobile)
The challenge
The founder wanted a line graph showing investment progression over time - including top-up moments. But this needed to work without hover interactions on mobile, and with a wide range of BTC values.
Process & exploration
I was given relevant metrics and constraints. I explored how to plot BTC over time (X = BTC/Currency of choice, Y = time, updated daily) while clearly marking top-ups. I suggested adding a filter (7 days, 30 days, 3 months) and limiting the timeline view for new clients. I also anticipated readability concerns - large numeric ranges, no hover on mobile, and multiple units to visualize.
The solution
I used a line chart from the ShadCN design system for consistency and speed. I represented top-ups with visible jumps in the graph line and color transitions at those points. For added clarity, users could explore their full investment history in a dedicated section, while the chart focused on high-level trends. All design choices were responsive-first and documented in Figma for developer reference.
Final Design
