PROJECTS

Quanta - Product Redesign

Client:

Quanta Finance Inc.

Year:

2025

Location:

US-based, remote

Service:

UI/UX Redesign

Project Overview


Category: Fintech SaaS/B2B Finance Ops

Deliverables: UX strategy, dashboard architecture, UI system, component library, high-fidelity screens

Timeline: 3 weeks

DAR Design role: UX/UI design team


Quanta Finance is a B2B platform designed to help startups and SMBs manage cash position, corporate cards, and outgoing payments in one place. The product targets operators who need fast answers to daily finance questions:


  • “How much runway do we have right now?”

  • “What spending is trending up?”

  • “Which vendors did we pay recently?”

  • “Are there any approvals or security risks?”


The project goal was to redesign Quanta’s dashboard experience to feel enterprise-grade, reduce cognitive load, and support fast decision-making without sacrificing data density.


The Problem


The previous experience (pre-redesign) had three core issues common to finance tools:


  1. No clear first-screen story.

  2. Users couldn’t quickly understand the cash position, spending direction, or what required attention right now.

  3. Actions were disconnected from insights.

  4. The product showed numbers, but operational actions (send/receive money, manage cards, review payees) lived in separate, hard-to-find areas.

  5. Trust & safety signals were weak.

  6. Finance products must prove reliability. Missing risk indicators, approvals, and security cues reduced confidence.


Goals & Success Criteria


We aligned on measurable outcomes and UX KPIs:


  • Time-to-answer key questions (cash position, spending trend, recent transactions) under 10–20 seconds

  • Increase discoverability of cards & limits, recent payees, and exports

  • Reduce “where do I click?” friction via clearer hierarchy and progressive disclosure

  • Introduce clear health signals: cash flow stability, approvals, unusual access/security


Target Users


Primary: Founder/COO/Finance Manager

  • Needs a daily “finance control room”: runway, spending anomalies, vendor payments, and quick exports.


Secondary: Accountant/Ops

  • Needs statements, categorization, traceability, and predictable workflows.


Tertiary: Admin /IT/Security-minded stakeholder

  • Needs access controls, location anomalies, and approval thresholds.


UX Strategy: The Dashboard as a “Control Room”


We designed the dashboard around one principle:


One screen should answer 80% of daily finance questions. Deep dives are a click away, but the first view must feel complete.


Information Architecture


The dashboard is structured into three zones:


  1. Cash & treasury overview (left)

  2. Real-time spendable balance + trend line + primary actions (initiate/receive).

  3. Operational control (center)

  4. Corporate cards + recent activity, optimized for “what changed today”.

  5. Performance & direction (right)

  6. Expenses/income trends + recent payees for fast vendor workflows.


This layout supports a natural scanning pattern: left > center > right, moving from state > activity > analysis.


Why: Users need both “where we are” and “are we drifting?” in seconds.


Key UX Decisions (and why they exist)


1) Treasury balance gets the strongest visual weight


In finance tools, cash position is the emotional core. We made it the largest card with:

  • clear available balance

  • a readable trend line

  • contextual tooltip for precise points in time


Why: Users need both “where we are” and “are we drifting?” in seconds.


2) Actions sit next to insight (Initiate / Receive)


Primary actions appear inside the treasury card rather than buried in navigation.


Why: Finance workflows are repetitive. Reducing navigation steps reduces errors and speeds up operations.


3) Corporate cards are “front-and-center”


Card visibility includes:


  • card identity

  • current balance

  • quick access for adding a new card


Why: Card management is one of the highest-frequency control tasks in modern finance ops.


4) Health signals are explicit, not implied


The Account health module summarizes:


  • cash flow state

  • approvals needing review

  • security confidence


Why: Trust is a feature. A financial product must show that it protects the business.


5) Analytics on the right uses simple, scannable charts


Expenses and income are shown as monthly bars with trend deltas.


Why: On dashboards, complexity kills clarity. Bars support instant comparison; deeper analytics belong in drilldowns.


6) Recent payees are optimized for fast repeat actions


Payees are shown as avatars + last payment delta, with “New payment” and “Manage payees”.


Why: Vendor payments repeat. The UI should support muscle memory.


7) Progressive disclosure prevents overload


The dashboard gives answers first, details second:


  • summary cards → “See all” links → full pages (Statements / Payments / Reports)


Why: Users don’t want “everything”; they want “what matters now.”


UI System & Visual Direction


We aimed for “quiet confidence” — enterprise clarity without sterile emptiness.


  • Neutral surfaces with consistent elevation

  • Accent colors used for meaning (income/expense) and brand personality (card highlight)

  • Clear typography hierarchy for fast scanning

  • Micro-status pills to turn complexity into readable signals


Accessibility note: status meaning is designed to be supported by labels and icons (not only color).

Risks & How We Mitigated Them


Risk 1: Overloading the first screen


  • Mitigated via strict hierarchy + modular cards + progressive disclosure.


Risk 2: Misinterpretation of financial data


  • Clear labels (“outflows across cards and transfers”), consistent number formatting, conservative chart design.


Risk 3: Trust loss due to weak security cues


  • “Account health” + approvals + security indicators designed as first-class UX elements.


Outcome


The redesign created a dashboard that:


  • answers daily finance questions fast

  • keeps high-frequency actions close to insights

  • reinforces trust with health/security signals

  • looks premium enough to justify enterprise pricing


Next Steps (what we ship after the dashboard)


  • Card details (limits, freezes, merchants, receipts)

  • Approval flows (threshold rules, audit logs)

  • Export presets (per accounting system)

  • Role-based dashboards (Founder vs Accountant)

  • Custom widgets & saved views for different workflows