X-StudioCase StudyX-Studio × Morrow · 2025
Morrow answers the question freelancers actually have, which is not what the balance says but how much is safe to spend. Income, invoices, expenses, tax and forecasting in one calm workspace.
What we did
Studio concept. Morrow is an X-Studio exploration rather than client work, so every figure in the interface is illustrative. It is published to show how the studio thinks about financial products, not to claim a shipped result.
01 · The project
Money arrives from different clients on different days. Expenses move unpredictably. Tax sits in the background growing quietly. And the dashboard on the screen answers a question nobody asked, which is what the balance happens to be at this second.
Morrow is a concept for a financial operating system built around the reality of independent work. It brings income, expenses, invoices, taxes, savings and cash-flow forecasting into one workspace that is organised around decisions rather than transactions.
X-Studio ran the whole exploration: product strategy, UX, interface design, brand, the design system and motion direction, as one piece of thinking rather than six handoffs.
02 · The opportunity
For someone working for themselves the mental model is a loop: earn, receive, spend, set aside, plan, repeat. The product's job is to make that loop visible instead of handing over a statement and expecting interpretation.
So we designed the interface around six questions rather than around a chart of accounts. Answer those well and the spreadsheet becomes unnecessary.
How much can I actually spend?
03 · Product principles
The first screen answers the question without asking anyone to do arithmetic. Available to spend, not balance, not revenue, not cash.
Tax, invoices, subscriptions and expenses are tangled underneath. Progressive disclosure and restrained hierarchy keep the surface calm.
A dashboard that only reports the past is a receipt. Morrow is built to show what is likely to happen next.
04 · The signature interaction
The result is safe to spend. The interaction is deliberately small: one figure at the top of the screen, and a tap to reveal exactly how it was reached. The complexity stays available without ever becoming the main experience.
05 · The core experience
A financial overview rather than a statement. Hierarchy runs decision first, then context, then detail.
Incoming and outgoing money in one view: client payments, subscriptions, transfers, pending income and status.
Treated as part of the financial system rather than a separate tool, with expected payment dates tied back to clients.
Morrow estimates what should be reserved and presents it as a normal part of the plan, not as a warning.
Categorised automatically and reviewed on a clean timeline, to answer the only question that gets asked: where did it go?
06 · Responsive design
The environment for overview and deeper analysis.
The environment for a decision made between two meetings.
07 · Visual direction
Large editorial headings against highly legible interface text.
A quiet neutral foundation with a single restrained accent for positive states.
Soft cards, subtle borders, minimal shadow and generous spacing.
Movement communicates financial state rather than decorating the screen.
08 · The design system
The system is built from a compact set of primitives: navigation, metric cards, financial charts, transaction rows, status indicators, invoice cards, amount inputs, date selectors, action buttons and mobile navigation.
Keeping it small is the point. A financial product accumulates features faster than almost anything else, and a sprawling component library is how interfaces become noisy two years after launch.
09 · The takeaway
Morrow let us explore how financial software can move away from dashboards full of numbers and toward interfaces that communicate confidence, context and the next action. For someone whose income is their own responsibility, that difference is the product.
