Files

adroit /Ledger· Case study

Free design review

Case study

Ledger

A brokerage customer portal, from sign-up to a funded account

A retail broker's customer portal: sign in, open an account in eleven steps, fund it by bank transfer, and follow balances, transfers, margin calls and statements in one place.

Product designThe people, maps and journeys on this page are who and what we designed for, drawn from the brief and the product. They are assumptions to check with real users.

Web portal for desktop browsers, designed at 1440 wide: a navy customer portal with light forms and drawers

The challenge

Opening and funding a brokerage account is where new customers give up. The portal had to make a long regulated application feel finite, make every transfer clear before and after it is sent, and keep the account's state readable at a glance.

What we did

  • Product design
  • Customer portal
  • Account opening
  • Money movement flows

What changed

  • An account-opening wizard with all eleven steps named on a rail, so the end is always in sight.
  • A transfer drawer that opens over the page, from deposit or withdraw to review to result.
  • Transfer history that writes out both the processor's status and the firm's.
  • A dashboard with the account card, recent activity, margin calls and settlement side by side.
  • One navigation for dashboard, activity, transfers, statements, reports and firm notices, with the account ID always in view.

Overview

Ledger is the customer web portal of a retail brokerage that clears through a larger platform. Customers sign in, open an account, move money in and out by bank transfer, and follow their activity, statements, gains and losses, and margin calls.

The design file holds the customer portal and account opening, with an admin portal, marketing pages and early wireframes beside them. This case study covers the customer side.

The file is a design, not a shipped build, and this page shows the design. Every name, number and account on the rebuilt screens is sample data.

The challenge

A brokerage account asks a lot before it gives anything back: identity, income, risk, experience, disclosures and signatures, then a linked bank and a first deposit that takes days to clear.

Every one of those steps is a place to drop out. Every transfer is money the customer cannot see for a while, so the portal has to say where it is.

The same customers come back to check one thing quickly, such as a balance, a transfer or a margin call. That has to be on the first screen.

The account at a glance

The dashboard greets the customer by name and puts trade search and a period picker in the same bar. The last transaction and the account card sit on the left; transfers by week and margin calls fill the top; recent activity and settlement fill the bottom.

Rebuilt as live HTML and SVG from the design file, with sample data.

Dashboard

The landscape

We compared six retail brokers on what the design file covers, from bank linking to statements and margin calls. Every claim links to its source; claims read from a search summary rather than the page are marked as such.

In the matrix, "unknown" means we could not check it in public sources, and "private" means it sits behind a login. The Ledger column reflects the design file, not a shipped build.

Showing 7 of 7 features

The landscape. Each cell says whether a product has a feature: yes, partly, no, not known, or not public (it may exist but nothing public shows it). Our product is the first column.
FeatureOurs
Bank link with a manual fallbackPartlyYesNot knownPartlyNot knownYesNot known
Deposit and withdraw in one panelYesNot knownNot knownNot knownNot knownNot knownNot known
Review step before a transferYesNot knownNot knownNot knownNot knownNot knownNot known
Transfer status in wordsYesNot publicNot publicNot publicNot publicNot publicNot public
Statements onlineYesYesNot knownNot knownNot knownNot knownPartly
Gain and loss viewYesNot knownPartlyNot knownNot knownNot knownYes
Margin calls in the portalYesNot knownNot knownNot knownPartlyNot knownNot known
  • Yes
  • Partly
  • No
  • Not known
  • Not public

Where we stand out

  • Money movement in one drawer

    Deposit or withdraw, method, bank, amount, consent, review and result all happen in one drawer over the page, so the customer never loses the history behind it.

  • Two statuses, both in words

    Each transfer shows the processor's status and the firm's status as written labels, with the reason beside them. We did not find transfer status described in the public help pages we read.

  • Margin and settlement on the first screen

    Margin calls and the day's settlement sit on the dashboard, next to the balance, instead of in a separate report.

Where they do better

An honest read: these are the places the others are ahead today.

  • Speed of funding: tastytrade and Robinhood can make part of a deposit tradable right away. The design file makes no such promise.
  • Reach: Robinhood and tastytrade document their flows in mobile apps as well as on the web. The file is desktop web only.
  • Depth of profit and loss: Interactive Brokers and Webull document richer performance tooling than the gain and loss pages in the file.

Sources

The landscape

Robinhood

First-time and casual retail investors.

Audience
First-time and casual retail investors.
Website
robinhood.com/us/en/support/articles/link-your-bank-account (opens in a new tab)

Strengths

  • Link a bank by signing in to it, or by account and routing numbers with two microdeposits; the same steps on the web and in the app.
  • Monthly statements on the web under Account, then Reports and statements, about two weeks after the month ends.
  • Instant Deposits let customers trade with part of a pending transfer (search snippet).

Gaps

  • Margin-call messaging and a realized gain and loss view were not verified.
The landscape

Webull

Active retail traders.

Audience
Active retail traders.
Website
webull.com/help/faq/10988-All-About-Overnight-Trading (opens in a new tab)

Strengths

  • Trading from 4:00 AM to 8:00 PM ET, plus an overnight session for selected symbols.
  • Profit and loss help covers cumulative and realized P&L (search snippet).

Gaps

  • Bank linking, statements and margin-call messaging were not verified.
The landscape

Firstrade

Cost-conscious long-term investors.

Audience
Cost-conscious long-term investors.
Website
help.firstrade.info/en/articles/9253196-how-do-i-link-a-bank-account-for-ach-transfer (opens in a new tab)

Strengths

  • Link a bank by signing in to it, with an optional nickname and first deposit in the same form.
  • A bank profile on the web under Accounts, Deposit/Transfer.

Gaps

  • The first ACH deposit can take up to four business days to clear (search snippet).
  • Account-opening steps, margin calls and gain and loss views were not verified.
The landscape

Public

Retail investors across stocks, options, bonds and crypto.

Audience
Retail investors across stocks, options, bonds and crypto.
Website
help.public.com/en/articles/9773751-what-are-day-trade-money-due-and-equity-maintenance-calls (opens in a new tab)

Strengths

  • Help pages name each kind of margin call and how to meet it, for example a deposit within four business days.
  • Notifications when a portfolio nears a maintenance call (search snippet).

Gaps

  • The margin-call article does not say how customers are told.
  • Bank linking and statements were not verified.
The landscape

tastytrade

Options-first active traders.

Audience
Options-first active traders.
Website
tastytrade.com/how-to-fund (opens in a new tab)

Strengths

  • Instant bank link gives up to $10,000 of an ACH deposit as buying power right away, once a day.
  • Banks without instant link can use micro-deposits on the website.

Gaps

  • Statements and margin-call views were not verified; one help article returned an error.
The landscape

Interactive Brokers

Active and international investors.

Audience
Active and international investors.
Website
interactivebrokers.com/en/general/education/pdfnotes/PDF-TWS_Statements.php (opens in a new tab)

Strengths

  • A realized and unrealized performance summary under Reports, Statements in the web Client Portal (search snippet).
  • Tax-lot methods beyond first-in, first-out (search snippet).

Gaps

  • The help site did not resolve for us, so every claim is secondhand.
  • Bank linking and margin-call views were not verified.

Who we designed for

Someone we designed for, drawn from the brief and the product. Not a real person, and not yet checked with real users.
  • Opening a first brokerage account

    “Tell me how many steps are left and I'll finish it.”

    Goals
    3
    Frustrations
    3
  • Checks the account a few times a week

    “Is my money there yet, and do I owe anything?”

    Goals
    3
    Frustrations
    3
Who we designed for
Someone we designed for, drawn from the brief and the product. Not a real person, and not yet checked with real users.

The new investor

Opening a first brokerage account

“Tell me how many steps are left and I'll finish it.”
Illustrative line, not a recorded quote

Context

Signs up on a laptop in the evening, with an ID card and a bank login to hand.

Goals

  • Finish the application in one sitting.
  • Know what each step is for before giving personal details.
  • Put money in and see it arrive.

Frustrations

  • Long forms with no end in sight.
  • Being asked for the same thing twice.
  • Transfers that disappear for days with no status.
Who we designed for
Someone we designed for, drawn from the brief and the product. Not a real person, and not yet checked with real users.

The returning customer

Checks the account a few times a week

“Is my money there yet, and do I owe anything?”
Illustrative line, not a recorded quote

Context

Comes in for one answer and leaves; reads the dashboard more than any other screen.

Goals

  • See the balance and anything that needs attention first.
  • Check a pending transfer without calling support.
  • Download a statement at tax time.

Frustrations

  • Status codes that mean nothing to them.
  • Margin messages that arrive only by email.
  • Hunting for the account number.

What they think and feel: The new investor

What we designed for, drawn from the brief and the product. An assumption to check with real users.

Out loud, in meetings and messages

  • “How long will this take?”
  • “Why do you need my income?”

What goes unsaid

  • This is a lot of personal information.
  • I hope I can stop and come back.

Observable behaviour

  • Reads each step's name before filling it.
  • Keeps the bank app open in another tab.

The emotional undertow

  • Cautious with an unfamiliar firm.
  • Relieved when the end is visible.

Pains

  • Not knowing how many steps remain.
  • Not knowing when a deposit will clear.

Gains

  • Every step named from the start.
  • A clear result after each transfer.

What they think and feel: The returning customer

What we designed for, drawn from the brief and the product. An assumption to check with real users.

Out loud, in meetings and messages

  • “Did my deposit go through?”
  • “Where's last month's statement?”

What goes unsaid

  • Declined means something went wrong, but what?
  • I should not need support for this.

Observable behaviour

  • Opens the dashboard, then transfers.
  • Scans the status column first.

The emotional undertow

  • Impatient when the answer is not on the first screen.
  • Reassured by a status in plain words.

Pains

  • Codes instead of words.
  • Margin calls hidden in reports.

Gains

  • Both statuses written out, with a reason.
  • Margin calls next to the balance.

Opening and funding an account

What we designed for, drawn from the brief and the product. An assumption to check with real users.

The journey we designed for: The new investor5 stages

  1. Start an application.

    Feeling today: Neutral (0)After the redesign: Pleased (+1)

  2. Get through eleven regulated steps.

    Feeling today: Frustrated (−1)After the redesign: Pleased (+1)

  3. Prove identity and agree to the terms.

    Feeling today: Frustrated (−1)After the redesign: Neutral (0)

  4. Move the first money in.

    Feeling today: Frustrated (−1)After the redesign: Pleased (+1)

  5. See the money arrive.

    Feeling today: Frustrated (−1)After the redesign: Delighted (+2)

Key design decisions

  1. Every step named from the start

    Problem
    An account application has eleven regulated parts, and an unknown length is the main reason to quit.
    Choice
    A rail lists all eleven steps by name with a short line each; the current step is filled and the title area says "Step 1 of 11". Next sits in a fixed bar at the bottom.
  2. Money moves in a drawer

    Problem
    Transfers sent from a separate page lose the context the customer came from.
    Choice
    The transfer opens as a drawer over the page, topped by the balance, with deposit or withdraw as a toggle and ACH as the method; after that the choice stays on screen as one line, Deposit as ACH fund transfer.
  3. Review before anything is sent

    Problem
    A wrong amount or bank is costly and slow to undo.
    Choice
    The amount step carries the electronic-signature consent; a review step then repeats the linked bank, what is available in it and the amount before Continue with deposit.
  4. Two statuses, in words

    Problem
    A transfer passes through the bank's processor and the firm, and either can stop it.
    Choice
    The history shows the processor's status and the firm's status as written labels, with the processor's transaction ID, the reason and the last update.
  5. The account ID is always in view

    Problem
    Customers need their account number for support and transfers, and it is usually buried in settings.
    Choice
    The sub navigation carries the account ID on the right of every portal page; the account card repeats it with the balance.

Design targets

What the portal was designed to make true, written as figures to test it against.

Targets the design was built to reach, not measured results.

  1. Design target

    ≥ 70%

    Applications started that get submitted

    All eleven steps are named up front so nobody gives up not knowing how much is left.

  2. Design target

    ≤ 12 min

    Median time to finish the application

    A visible end only helps if each step is quick, so every step asks one thing.

  3. Design target

    < 2 per 100

    Support contacts about transfer status

    Every transfer state and its reason is written out in words, not codes.

  4. Design target

    ≥ 60%

    New accounts funded within 7 days of approval

    Funding is the next step after opening, so the transfer drawer is one click from the dashboard.

Getting in

The sign-in page pairs the offer with a navy card, and the way into account opening sits right under the form.

Account opening runs in eleven named steps on a light canvas. The first asks for personal details, address and contact, and whether to add a trusted contact.

Sign in
Account opening, step 1 of 11

Moving money

Transfers open as a drawer over the history. Each row in the history writes out both statuses and the reason.

A deposit takes three states of the same drawer, the amount from the linked bank, a review, and the result with its transaction ID.

Transfers, with the drawer open
Deposit: amount, review, done

The portal is deep navy, with one bright blue for actions and links. Green and red are kept for status and change, and a pale blue tint marks anything the customer is about to confirm.

Forms and drawers switch to white, so data entry reads as a separate, careful task.

Brand: colour

  • Portal page background and table dividers

  • Cards, sub navigation and the welcome bar

  • Header navigation; top of the sign-in card gradient

  • Primary buttons and the selected toggle

  • Links on navy

  • Avatars and chart bars

  • Review boxes, step pill, soft buttons

  • Titles and text on the confirm tint

  • Successful transfers and gains

  • Declined transfers and alerts

  • Falling candles on the margin chart

  • Rising candles on the margin chart

Brand: type

  • Spline Sans

    Interface and data: 14/20 regular and medium, titles 18 to 24 semibold

    $ 500 · Execution Successful

    • 400
    • 500
    • 600
  • Inter

    Welcome line and the large metric: 24 medium, 36 semibold

    Welcome back · 2,420

    • 500
    • 600
  • Lato

    Header navigation and some inputs: semibold in the file (web Lato has no 600, so it is shown at 700)

    Home · Platforms · Pricing

    • 400
    • 700

Brand: logo notes

  • The client's logo is not shown, because the client is anonymised. The mark on the rebuilt screens is a neutral codename wordmark drawn for this case study.
  • The file's photo background on sign-in is replaced by a drawn gradient, and the platform credit under the sign-in card is left out.
  • Colour and type values come from the design file's variables; a few surfaces were read from the rendered frames.

What the file covers

29 parts in 6 groups

The design file sits on one page, with the customer portal, account opening, an admin portal and marketing pages side by side, plus earlier wireframes.

The groups below are its parts and the states inside them.

    • Sign in
    • Forgot and reset password
    • Email verification
    • Admin sign in
    • Eleven-step wizard
    • Two wizard layouts
    • Identification upload
    • Disclosures and signatures
    • Dashboard
    • Activity
    • Transfers
    • Statements and PDF view
    • Gain and loss
    • Margin calls
    • Firm notifications
    • Deposit and withdraw drawer
    • ACH and wire
    • Linked bank
    • Review, success and failure
    • Applications and details
    • User management
    • Audit log
    • Announcements
    • Header and sub navigation
    • Account card
    • Status badges
    • Charts and metrics
    • Inputs, dropdowns and uploads
    • Animated icons

Reflection

The hard part of a brokerage portal is not the charts; it is the waiting. Most of the design is about telling people where their application and their money are.

Next, the assumptions need testing with people opening their first account, and the transfer states need checking against what the processor actually returns.

The open question is mobile. The portal is designed for desktop browsers, and the customers it serves will expect the same answers on a phone.

Want something like this?