Subhrajit.
LinkedInGitHubGet in touch
All work

Product Designer · Fintech · Product + Design System

From financial products to financial prescriptions.

Designing Nivex, a wealth platform that diagnoses an investor’s financial situation before recommending what to do next.

Role
Product Designer
Company
Nivex, via Techdome
Year
2026
Built with
  • Figma
  • Claude
  • ChatGPT

The problem

Most investing apps ask: “What do you want to invest in?”

Traditional
Question
Product
  1. Question leads to Product
Nivex
Financial data
Diagnosis
Prescription
Action
  1. Financial data leads to Diagnosis
  2. Diagnosis leads to Prescription
  3. Prescription leads to Action

The problem wasn’t finding another financial product. It was understanding whether the investor’s existing decisions were actually working.

The big idea

Prescription,
not product.

  1. 01

    Examine

    Understand what the investor owns.

  2. 02

    Diagnose

    Find risks, inefficiencies and behavioural patterns.

  3. 03

    Prescribe

    Provide specific, human-reviewed actions.

  4. 04

    Follow up

    Track progress against the prescription.

The product ecosystem

One design language, three role-specific experiences.

User flow · investor
Sign up
Log in
Choose service
Audit My Portfolio
Build My Portfolio
Audit My Trades
Import CAS / PAN
Short questionsno upload
Processing
Dashboard
Prescription
Portfolio
Goals
Trades

Highlighted: the audit path, which is the one most investors arrive on. Build My Portfolio skips the import entirely — it has nothing to upload — and that fork is why the dashboard had to be shaped by the services you own rather than by a fixed menu.

  1. Sign up leads to Choose service
  2. Log in leads to Choose service
  3. Choose service leads to Audit My Portfolio
  4. Choose service leads to Build My Portfolio
  5. Choose service leads to Audit My Trades
  6. Audit My Portfolio leads to Import CAS / PAN
  7. Audit My Trades leads to Import CAS / PAN
  8. Build My Portfolio leads to Short questions
  9. Import CAS / PAN leads to Processing
  10. Short questions leads to Processing
  11. Processing leads to Dashboard
  12. Dashboard leads to Prescription
  13. Dashboard leads to Portfolio
  14. Dashboard leads to Goals
  15. Dashboard leads to Trades
The Nivex investor dashboard: wealth score, XIRR, invested versus current value and holdings

Investor

Choose → Import → Diagnose → Act

  • Service selection
  • PAN / CAS / Tradebook import
  • Processing
  • Dashboard
  • Portfolio
  • Goals
  • Trades
The Nivex advisor client queue: cases by investor, service and status

Advisor

Clients → Analyse → Review → Prescribe

  • Client list
  • Client detail
  • Case documents
  • Financial data
  • Prescription authoring
  • Calls
The Nivex admin overview: platform-wide case and investor operations

Admin

Cases → Investors → Staff → Operations

  • Overview
  • Cases
  • Investors
  • Staff
  • Calls
  • Client preview

Key design decisions

The Nivex entry screen: a restrained split layout with a single primary action

01

Calm over consumer-fintech

Removed pill-heavy and promotional patterns so the experience reads as trusted financial advice rather than a trading app.

The advisor queue showing one investor holding three separate services

Harsh Sharma, three times — Portfolio Audit, Build Portfolio and Trades Audit as separate cases under one investor.

02

One investor ≠ one service

The product moved from assuming one service per investor to supporting several, without fragmenting the experience.

One investor, many services
Investor
Portfolio Auditown case
Trades Auditown case
Build Portfolioown case
One dashboard

The fix was not a second dashboard per service. The nav, the home hero and the cross-sell all read from one seam, so owning three services still gives you one product.

  1. Investor leads to Portfolio Audit
  2. Investor leads to Trades Audit
  3. Investor leads to Build Portfolio
  4. Portfolio Audit leads to One dashboard
  5. Trades Audit leads to One dashboard
  6. Build Portfolio leads to One dashboard
The prescription an investor sees: three advisor-approved steps, each with a reason

What the investor receives has already passed a person.

03

AI proposes. Humans prescribe.

AI can suggest recommendations, but an advisor has to explicitly approve them before they reach the investor.

Human in the loop
Financial signals
AI draftsuggested
Advisor reviewmust approve
Prescription
Investor

Nothing passes the filled step automatically. No bulk accept either — an advisor accepts one draft at a time, which is the feature rather than the friction.

  1. Financial signals leads to AI draft
  2. AI draft leads to Advisor review
  3. Advisor review leads to Prescription
  4. Prescription leads to Investor

The design system

One system. Multiple products.

Tokens to product
Primitives
Semantic
Theme
Components
Investor
Staff
Admin
Marketing

313 tokens resolving in that order, with a lint on every pull request and nothing hardcoded — which is why dark mode was a configuration change rather than a redesign.

  1. Primitives leads to Semantic
  2. Semantic leads to Theme
  3. Theme leads to Components
  4. Components leads to Investor
  5. Components leads to Staff
  6. Components leads to Admin
  7. Components leads to Marketing
Nivex investor surface, built from the shared system
Investor
Nivex staff surface, built from the shared system
Staff
Nivex admin surface, built from the shared system
Admin

The design system wasn’t a standalone library. It was built to ship the product — shared tokens and components keeping every surface consistent in look and in behaviour.

Method

Designing at the speed of implementation.

Workflow
Design constraints
Claude Codeimplementation
Working prototype
Test

Constraints first, implementation second, human judgment throughout. The dashed return is where most of the design actually happened.

  1. Design constraints leads to Claude Code
  2. Claude Code leads to Working prototype
  3. Working prototype leads to Test

I translated the product decisions and the design system into a working React prototype with Claude Code, so I could test real product behaviour instead of relying on static screens.

  • CLAUDE.md
  • 14 ADRs
  • Design tokens
  • Component docs
  • React prototype
  • Storybook

Constraints first, implementation second, human judgment throughout. The rules and architecture decisions existed before the code they governed.

The product

Nivex — Service selection
Service selectionThree ways in, depending on whether you already hold something.
Nivex — Data import
Data importHoldings pulled from a CAS statement, PAN or tradebook — nothing typed twice.
Nivex — Prescription
PrescriptionAnalysis converted into specific, ordered, advisor-approved actions.
Nivex — Portfolio diagnosis
Portfolio diagnosisRaw financial data turned into signals an investor can read.
Nivex — Investor dashboard
Investor dashboardShaped by the services you own, showing progress against the prescription.
Nivex — Goals
GoalsWhat the money is for, and whether anything is actually mapped to it.
Nivex — Trades
TradesHolding period, win rate and capital deployed — the habits behind the tradebook.
Nivex — Advisor workspace
Advisor workspaceThe context an advisor needs to review a case and prescribe against it.
Nivex — Admin operations
Admin operationsEvery case across the platform, by service and status.

Delivered

  • Investor experience
  • Advisor experience
  • Admin experience
  • Shared design system
  • Working product prototype
  • Storybook
  • Marketing website
  • Human-in-the-loop prescription model

The goal wasn’t to build another investment app. It was to make financial advice understandable, actionable and trustworthy.

Nivex changed how I think about AI-assisted product design: the important question isn’t only what AI can automate, but where it should stop.

Next case study

A clearer workspace for working with APIs