Concept project · Dashboard · SaaS B2B · Fintech
Liquid
A B2B liquidity dashboard that helps finance teams read their cash flow, understand risk and make decisions with confidence.
Role
Product Designer
Year
2026
Overview
Liquid helps finance teams understand how much cash they really have, how exposed they are and what is coming up in the short term. The design turns raw financial data into a clear picture of available cash, risk and future obligations.

Problem
Finance teams struggle with a few critical questions. How much cash is actually available? How much is already committed? How long can we operate? Which payments are coming up? The data is fragmented and hard to read, which creates uncertainty and slows decisions down.
Core structure
Dashboard
Answers four key questions about the current position: available liquidity, risk exposure, runway and upcoming obligations.
Cash flow
Shows how liquidity changes over time, separating inflows, outflows and net result, so it is clear whether the business generates or consumes cash.
Obligations
Lists every upcoming payment by date, with its impact level and filters for type and risk.
Reports
A higher level view with aggregated inflows and outflows, a monthly breakdown and the net result, made for reflection and communication.


Key design decisions
Total versus usable liquidity
Not all available cash is free to use, and the design makes that difference visible immediately.
One shared time horizon
Every view follows the same time range, so users can change perspective without losing context.
Separate layers of data
KPIs, charts and tables each have a different job and a different level of detail.
A consistent data model
Tables share the same structure across views, which lowers the effort of moving between sections.
Dense on purpose
Built for finance professionals who need depth, not simplification.

Outcome
The result is a tool that takes finance teams from scattered data to clear answers about cash, risk and runway. Most of the work is in how the information is framed and structured, not in visual polish alone.
How I'd measure success
I'd test whether users answer the four core questions faster and with fewer mistakes than in their current tools, and whether they move between time horizons without losing context. The first study would focus on how well people understand the difference between total and usable liquidity.
Learnings
Designing for finance is not only about visual clarity. The real challenge is framing: the way information is structured directly shapes how people interpret it and act on it.