Logo

The main AxiomLens dashboard brings together core cashflow metrics, trends, and insights.

AxiomLens – Cashflow Analytics for Small Businesses

Turning scattered numbers into an actionable overview

This self-initiated concept shows how a SaaS dashboard might help small and medium-sized businesses and freelancers get a clear view of their cash flow and leverage AI-powered predictions to act before problems arise. I focused on structuring data-heavy UI, making key metrics glanceable, and designing flows that feel calm and reliable at all times.


Project in a Nutshell

My role

Product concept, UX/UI design, (UX) research, interaction patterns, dashboard IA, microcopy, visual design system basics

Timeline

~2 weeks of evening work (from first sketches to polished hi-fi screens)

Tools

Figma, Google Sheets & Docs, Notion, ChatGPT, UX Pilot

Dashboard UX Data-heavy UI Research Branding Financial SaaS Design System Foundations Microcopy (EN)

Challenge

Freelancers and small business owners rely on a patchwork of banking apps, invoicing tools, and spreadsheets. They see numbers, but rarely get a clear, at-a-glance view of how money moves over time, when a cashflow gap is coming, or which clients are slowing payments down. Existing dashboards either overwhelm with noisy charts or stay too high-level, and AI helpers are rarely implemented in a clear, trustworthy way.

Objective

Design a graphical concept of cash flow analytics – AxiomLens – an all-in-one service that unites income, expenses, and invoices with readable AI insights on top. Focus on data-heavy UI that stays glanceable, with clear flows between main overview, invoice management, and detailed history – so users have a single, reliable view of their financial health.

Highlights

  • Dark, calm dashboard UI with clear hierarchy for key metrics and trends
  • Reusable cards for income, expenses, taxes, and AI insights
  • Invoice table and detail views optimized for status, due dates, and actions
  • Consistent component system for payment states and more
  • Copy and labels written with localization in mind from day one

Outcome

  • A coherent set of 4 hi-fi screens ready for hand-off or prototyping
  • Information architecture that clearly links cashflow, invoices, and AI insights
  • A solid design system baseline (typography, layout, cards, badges, styles)
  • A case study on problem framing, design decisions, and business value

Problem & Context

The starting point

Instead of designing yet another finance app, I focused on a very specific scenario: a founder or freelancer opening a dashboard for a quick check-in before starting work. They don't have time for deep analysis; they just want to know whether anything needs attention today.

In reality, their data sits in different places and on different timelines: daily bank movements, monthly subscriptions, irregular invoices, and taxes due monthly, quarterly, or annually. AxiomLens began as an experiment in bringing these timelines together into one working view: what has already happened, what is scheduled, and what might become a problem if nothing changes.

Key challenges

  • Aligning information that lives on different time scales (per invoice, per month, per quarter).
  • Showing overdue and "almost overdue" items in a way that feels urgent but not alarmist..
  • Translating AI-generated insights into short, readable comments instead of opaque "predictions".
  • Keeping the UI approachable for non-accountants while still exposing enough detail for real decisions.

Success criteria for the UI

  • The main screen should answer three simple questions:
    - "How are we doing right now?";
    - "What needs attention today or this week?";
    - "Is anything risky coming up soon?"
  • Risks – cash dips, overdue invoices, upcoming large expenses – live in clearly defined areas, not hidden behind filters.
  • Dense tables and charts stay scannable through consistent layout, restrained color, and predictable patterns.

Concept constraints

  • Single-owner view only in the MVP version – no multi-user roles or collaboration tools in this iteration.
  • Scope limited to cashflow and invoices, not full accounting or tax preparation.
  • Data import from banking and invoicing tools is assumed to exist; the project focuses on display and decision support, not integration flows (a lot of job for the devs to do here).

Users & Goals

I designed this tool not only as an all-in-one way to keep track of things, but also as a way to improve your overall situation. It is supposed to use AI analytics and insights to highlight patterns and events a human eye might miss, helping you steer your financial flow with a smarter, more attentive system.

Busy Small-Business Owner

Guy avatar

Frank, 33

Owner of a small creative studio

Runs a small business with a couple of employees and contractors. Between client calls, chats, and production work, he only has a few minutes to check finances and make quick decisions.

Needs at a glance

  • Whether the next 2-4 weeks are covered (rent, payroll, core expenses).
  • Which invoices are late, by how much, and how that impacts this month.
  • A single "now + next" view without rebuilding spreadsheets every week.

Pain points

  • Data scattered across banking apps, Excel, and invoicing tools.
  • Evenings spent reconciling numbers instead of running the business.

Freelance Consultant

Max avatar

Jing, 29

Consultant with multiple retainers

Works with several clients on retainers and project-based contracts. Payment terms differ wildly, so her income is irregular and easy to misjudge.

Needs at a glance

  • Track recurring invoices; spot gaps in future income.
  • A client/project breakdown to see who really drives revenue.
  • Gentle prompts to send invoices or follow up before delays become awkward.

Pain points

  • No single place to see all upcoming payments and manage the cashflow.
  • Gets surprised by slow months because issues only become visible when the balance is already low.
  • Regular "Did I send that invoice?" checks that show up late at night and create low-grade anxiety.

Dashboard & Design Goals

User Goals

  • See today's cash position and the coming 30-45 days in one place.
  • Spot late or risky invoices without hunting through emails or spreadsheets.
  • Understand what's driving the trend up or down (specific clients, months, or invoices).
  • Decide quickly whether to invest, save, postpone, or chase payments.
  • Share a simple, exportable overview with an accountant, co-founder, or partner.

Product & UX Principles

  • Turn scattered financial data into one trustworthy working view, not a wall of charts.
  • Highlight risk with clean, readable visuals.
  • Keep navigation intentionally shallow: from dashboard to details in 1-2 clicks.
  • Design patterns that can later stretch to taxes, subscriptions, and deeper AI insights without redesigning the core.

Key Screens

A closer look at the core AxiomLens flow: starting from the main dashboard, moving through a deeper cashflow overview, and then into invoice management. Together, these screens show how dense financial data is structured into a simple loop: understand the situation, spot an issue, open the details, and take action.

Main Dashboard. High-level cashflow overview with key metrics, trends, and AI insights surfaced in a single, focused view.
01 · Main Dashboard

Everyday check-in screen – meet the Product!

The Main Dashboard is the screen Frank, Jing, and any other user would see most often. It combines topline numbers, trends, AI insights, and the latest invoices into a single working view, so a quick glance is enough to decide whether anything needs attention today.

Because this is the first screen anyone sees, it had to strike a careful balance between information density, visual calm, and clear next steps. It also set the visual language for the whole product, so it went through the most iterations: from early wireframes to several high-fidelity versions, documented in the Design Process & Iterations section.

Key Decisions:

  • Metric cards for income, expenses, net profit, and tax due give a quick snapshot of where things stand, plus small trend notes compared to last month.
  • The cashflow overview shows how you got here over the chosen period, with a simple path to the full view.
  • AI Insights panel surfaces risks and opportunities in plain language with direct links to relevant views.
  • Recent invoices table grounds the high-level picture in specific clients and amounts, with clear status badges and one-click actions.
  • Dark, calm UI with a tight grid and restrained color keeps dense data readable without feeling like a trading terminal. And it also looks cool.
Cashflow Overview. Detailed inflow vs. outflow chart with filters and insight cards that explain what changed and why.
02 · Cashflow Overview

Read the trends without losing the story

This screen is where a user would zoom out from the dashboard and look at how money actually moves over a chosen period – by account, year, and quarter. Instead of a static balance, they see how inflow and outflow stack up week by week (in this scenario).

Key Decisions:

  • Focused chart layout compares cash inflow vs. outflow with a shared scale and subtle grid, so trends and gaps are easy to spot.
  • Period & account filters (account, year, quarter/month) let users answer concrete questions like "How did Q4 go on the main account?" without changing screens.
  • Key Financial Drivers & Insights cards underneath translate patterns into plain language: seasonal spikes, potential savings, or invoices that are starting to skew the quarter.
  • Minimal chrome around the graph keeps attention on the data itself, with secondary actions like "Export report" tucked away but available.
Invoices List. Dense but scannable table with status badges, quick actions, and insight cards for working through long billing histories.
03 · Invoices

Day-to-day billing workhorse

This is where Frank and Jing actually manage the money coming in. The screen combines high-level invoicing metrics with a dense but readable table, so they can move from “How much is stuck in invoices?” to “Which ones do I deal with first?” in a few seconds.

Key Decisions:

  • Summary cards at the top give a quick health check: total invoiced, paid, overdue, plus average payment delay.
  • Status/account/year filters let users slice the list down fast without leaving the page.
  • Clean invoice table supports scanning and sorting over long histories.
  • Inline actions keep common tasks one click away instead of hiding them in menus.
Invoice Details. Focused overlay with client info, line-item breakdown, totals, and a visual payment timeline.
04 · Invoice Details

All invoice context, without breaking your flow

Opening an invoice should feel smooth and native. The detail view appears as an overlay on top of the list, so users can check details, send a reminder, review history, or download a PDF – then close it and stay exactly where they were.

Key Decisions:

  • Overlay pattern keeps users anchored in the invoices view.
  • Client block (contact data + billing address) is grouped at the top for quick verification or follow-up.
  • Money block separates subtotal, VAT, and total clearly to avoid misreading amounts.
  • History timeline shows created, sent, seen, and paid states, putting "we never got that invoice" conversations out of question – assuming both the client and the professional use AxiomLens.

Logo & Branding

For a finance product, trust often starts with the logo. A solid identity can smooth a lot of rough edges in early versions; a clumsy one can make a good concept look amateur before anyone even tries it. With AxiomLens I needed something that felt analytical and modern, hinted at "smart" AI help, but still read first and foremost as a financial tool. The name already pointed in that direction: Axiom as a reliable truth, Lens as a way to inspect data. The explorations below show how I moved from a generic "AI + aperture" mark to a more grounded, chart-based symbol that fits the product better (though it's still far from perfect).

What the brand stands for

  • Financial clarity only. Serious enough to handle money, without looking like a speculative trading app or a crypto platform.
  • Smart, but not Sci-Fi. A subtle nod to AI and automation, without turning the logo into a tech gadget icon.
  • Stable and grounded. Clear geometry and an underlying grid to suggest structure, reliability, and long-term use.

Naming logic

  • Axiom – a core truth: the stable, reliable foundation for making decisions.
  • Lens – focus and clarity: a direct metaphor for understanding what's ahead.
  • Together, AxiomLens AxiomLens suggests "reliable numbers, seen clearly."

Logo evolution

A camera-style aperture combined with circuit lines, trying to merge the lens metaphor with a "smart system" feel
Iteration 2: The same symbol with a horizontal wordmark. This worked better in headers and on white backgrounds
A chart-based icon on a dark background: the financial metaphor became clear, but felt a bit aggressive
Electrolize-font wordmark keeps a slightly technical character, the palette is less agressive now

Design Process & Iterations

I approached AxiomLens the same way I'd tackle a real-world product: start with flows and information architecture, move from lo-fi exploration to focused hi-fi iterations, validate them with usability tests, and only then lock the final visual system. The goal was to prove the logic first – what screens exist, what each of them needs to show, and how easily people can move through them – and only after that refine the data-to-UI ratio, hierarchy, and colour decisions.

From flows to final dashboard

  1. Flow map & wireframe logic. First, I mapped the key areas – cashflow, invoices, clients, expenses, taxes, insights, settings, and mobile – into a single wireframe flow. This captured which screens should exist, how they connect, and which questions each one answers.
  2. Lo-fi AI-assisted layout. Using the flow as a brief, I generated a rough lo-fi version of the main dashboard to stress-test information density: which metrics earn a place above the fold, what can be secondary, and how much content reasonably fits on one screen without feeling cramped.
  3. Hi-fi iterations on hierarchy. Several high-fidelity passes explored different approaches to the quick overview, invoice area, and graph treatments. Some options leaned into gradients and depth; others pushed flatter, more editorial layouts to keep the product feeling calm and premium.
  4. Usability testing & feedback. I ran ten remotely moderated usability sessions with German freelancers using an interactive prototype. The goal was to see how naturally they could complete core tasks and to spot any confusing areas, navigation dead ends, or information overload before settling on a final direction. Their feedback led to adjustments in the placement of AI insights, the contrast of status states, and a softer colour palette.
  5. Converging on the final layout. The final dashboard combines the strongest parts of each iteration: clearer invoice visuals, a more informative summary strip, consistent colour roles, and a tighter rhythm between cards, charts, and tables.

In the end, the main view works in a simple, predictable way: nothing is there for the sake of being, navigation stays short, and the same structure can support future screens.

From flow map to final dashboard

First iteration: wireframe flow for all main AxiomLens areas, used as the backbone for the first lo-fi dashboard and navigation decisions.

Design System Foundations

I set up a small design system early so the dashboard could stay dense and readable as it evolved. The focus was on typography that holds up next to numbers, a calm dark theme, and simple patterns that are easy to reuse across new screens.

Typography

  • Readable under pressure. Type sizes chosen to stay legible next to busy tables and charts.
  • Two-level hierarchy. Headlines guide scanning; labels and helper text stay quiet.
  • Monospace accents. Used sparingly for aligned financial values and code-like details.

Colors & Surface

  • Dark canvas. Modern, trendy, comfortable for long sessions and makes chart lines stand out. Though the light theme is also planned!
  • Soft blues. Accents that feel analytical and calm, not "growth-hack" hype.
  • Borders over shadows. Elevation is minimal to keep focus on data.

Spacing & Layout Rhythm

  • Consistent scale. A unified system across sections and components creates a cohesive product feel.
  • Card-first structure. Dense data broken into clear, breathable modules.
  • Edge discipline. Strong outer margins to prevent dashboard clutter and keep the layout feeling intentional.

Core components

These four component families do most of the heavy lifting. Reusing them across screens keeps the product consistent without needing a huge design system.

Metric cards. Used for income, expenses, net profit, tax, and invoicing KPIs. Single pattern: label, main value, small trend line or delta, and an icon.
Status pills. Labels for payment and insight states. The palette is shared between tables and cards, so users learn quickly which colours signal good news, warnings, or neutral info.
AI Insights cards. Richer cards that bundle an icon, short title, explanation, and a clear action. They turn raw analysis into small, focused suggestions instead of another chart.
Icon set. Great for navigation, KPIs, and actions. Line weight and corner radius match the overall UI, so icons support the hierarchy without competing with the numbers.

Next Steps

AxiomLens is but a concept project. Turning it into a real tool would require a full team of engineers, data and AI specialists, security and compliance experts, tax lawyers and proper customer support. That said, thinking about "what next?" helps sharpen the direction. If I were to evolve AxiomLens further, I'd focus on:

  • Light & dark themes. Dark mode would stay the default, but there'd also be a light theme and system-theme auto switching. Modern browsers support this out of the box, so the layout and colours would need to hold up in both modes without breaking.
  • Multi-currency & VAT handling. Essential for freelancers and studios working across borders: one view that normalizes currencies, VAT rates, and tax rules for the countries they operate in.
  • Team mode. Roles and permissions for cases where more than one person needs to keep an eye on cashflow – founders, assistants, or external accountants sharing the same workspace.
  • Deeper banking & invoicing integrations. Start with simple, in-house import options for bank statements and invoices, then work towards direct integrations with major EU providers (Stripe, PayPal, SEPA, local banks) so users don't have to manually reconcile numbers.
  • Different account types. A "business owner" view for entrepreneurs, and a lighter "client" view just for communication, checking and paying invoices.
  • Tax hub. A dedicated area that tracks which taxes apply, estimates rates based on available data, and shows key deadlines and reminders per country or region.

Learnings

Working on AxiomLens was less about drawing a fancy dashboard and more about understanding what it really takes to make financial tools feel usable and trustworthy. Here are a few things that stuck with me:

  • Questions first, screens second. Once I stopped thinking in "features" and instead asked, What do people want to know in the first 30 seconds?, a lot of UI fell away. That shift made it much easier to decide what deserved the top row and what could quietly move into details.

  • AI is only useful if it lands in the right place. I knew from the start that AI insights needed a dedicated place, but it was hard to position them in such a data-heavy product. Usability sessions helped me find a layout where people actually noticed the insights without finding them distracting.

  • Density costs more than one might think. On paper, it looked like I could fit "just one more chart" into the main view. In practice, every extra block made real numbers harder to read. I ended up cutting several ideas and learned to prefer fewer, stronger components over a wall of "useful" widgets.

  • Brand and product have to agree. The early "aperture + circuits" logo looked clever, but read as a generic AI tool. Switching to a more obviously financial symbol instantly aligned expectations: people understood what kind of product they were looking at before reading a single word.

  • Concept work still reveals real complexity. Sketching "next steps" – tax logic, multi-currency handling, integrations, roles – was a useful dose of humility. Even a polished concept sits on top of a huge amount of engineering, compliance, and data work. It's a good reminder to respect the depth behind "simple" finance products.