Fintech

Lever - One financial decision a week

A behavior-first fintech experience that replaces passive dashboards with a focused weekly commitment.

Service

Product Design

Industry

Fintech

Year

2026

Reclaim weekly financial decision engine showing subscription commitment, weekly spending, and financial overview screens.
Reclaim weekly financial decision engine showing subscription commitment, weekly spending, and financial overview screens.

Overview

One financial decision a week.

I conceived, designed, and built LEVER to help people carrying credit-card balances choose one financial action each week, set a measurable target, and check in on their progress.

My Role & Scope

As Product Owner and UX Designer, I owned the product strategy, UX architecture, interaction design, high-fidelity UI, prototyping, and implementation across Home, Spending, Goals, AI Coach, and debt experiences. I took the product from concept to a working experience in September 2026.


—PROBLEM & APPROACH

The starting hypothesis

01 The starting hypothesis

  • A financial dashboard can show someone where their money went while leaving the next decision unresolved.

  • LEVER explores a narrower proposition: could choosing one financial action—and keeping it visible through a weekly check-in—make the next step clearer?

02 The intended audience

  • The intended audience includes people carrying revolving credit-card balances who want practical direction without maintaining a detailed budget.

  • This audience definition and the behavioral premise remain hypotheses to validate.

03 The design challenge

The design challenge was to provide focus while preserving enough context and choice for someone to judge whether a recommendation suited their circumstances.


— MY OWNERSHIP

My role in LEVER

I conceived, designed, and implemented LEVER, connecting the product direction with its information architecture, interfaces, recommendation logic, and commitment lifecycle.

The core experience spans opportunity selection, an active commitment, progress logging, cycle completion, and selection of another priority. Spending, cards and loans, recurring expenses, goals, and coaching provide supporting information and tools.

Building the experience let me examine how the design behaved across states, beyond individual screen layouts.

SCOPE

+Product strategy

+Information architecture

+Interaction design

+Interface design

+Implementation

Three interactions connect the experience

The central product decision: organize around a commitment

  • I organized LEVER around a commitment lifecycle:

    Review opportunities → Choose a focus → Take action → Check in → Complete → Review the next priority.

  • Home gives the active commitment visual priority. Supporting financial information remains available, but the main card brings together the target, current amount, next action, and check-in.

  • The tradeoff is deliberate: one active focus makes the experience more concentrated, while increasing the importance of choosing a suitable action. A prominent recommendation is only useful if the user can understand it and realistically act on it.

Recommend a priority, preserve the choice

LEVER presents three ranked opportunities before asking the user to commit.

In the reviewed example, these were credit utilization, Food & Dining, and Shopping. The user could select an alternative, inspect supporting information, or choose “Set as my focus.”

This separates the system’s recommendation from the user’s commitment. The highest-ranked opportunity is a starting point for a decision.

The interface demonstrates that choice, but its clarity and usefulness have not yet been tested with participants.

Rules select the priority; AI supports the experience

A clear boundary for AI

AI extracts transactions and credit-report fields from uploaded documents. It also generates coach responses, narrative insights, and goal-feasibility tips.

It does not select the weekly priority. Financial targets, payoff scenarios, spending-spike nudges, and the dashboard’s financial persona use coded logic.

This architecture creates two design responsibilities: explain the calculation clearly, and make the reliability of its input data understandable. Consistent calculations can still produce unsuitable recommendations when the data or assumptions are incomplete.

Where the experience needs to earn more trust

The next iteration

The next design priority is to make the recommendation easier to judge before asking for commitment.

That means connecting the ranked opportunity to its evidence, clarifying the target’s time period, and helping the user choose a realistic action. Check-ins should communicate a lasting status, while completion feedback should separate recorded activity from measured financial change.

Document extraction also needs evaluation: users should be able to understand and verify the numbers that influence recommendations. That verification experience has not yet been established in this case study.

I would test whether participants can explain why an opportunity was recommended, choose a feasible commitment, interpret progress, and recognize when outdated or missing information limits the recommendation.













BASED

Dublin, California

Open to Bay Area + Remote


SOCIAL

CONTACT

Dublin, California

© 2026 Sangeeta Pareek

BASED

Dublin, California

Open to Bay Area + Remote


SOCIAL

CONTACT

Dublin, California

© 2026 Sangeeta Pareek

BASED

Dublin, California

Open to Bay Area + Remote


SOCIAL

CONTACT

Dublin, California

© 2026 Sangeeta Pareek