Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi
SaaS

Finance operations for growing SMEs

Client
Client name — to be added
Industry
Fintech, B2B SaaS
Services
Product Strategy, SaaS Product Design, Design System
Year
2025
Ledgerly — cover

01Overview

Ledgerly is a placeholder case study illustrating how a B2B finance product could be structured, from discovery through design system. Replace this text with the real project overview: who the client is, what the product does and your role.

02Business challenge

Finance teams at small and mid-sized companies juggle spreadsheets, bank portals and accounting tools. The challenge was to reduce the time spent reconciling transactions while keeping accountants confident in every number.

03Objectives

  1. 01Reduce steps in the reconciliation workflow
  2. 02Make cash position visible at a glance
  3. 03Create a scalable design system for future modules

04Research

Placeholder: describe interviews, workflow shadowing, competitor reviews and the key insights that shaped the product. Example insight format — 'Accountants trusted the tool only when they could trace every number back to its source document.'

05Strategy

Focus the MVP on one painful job — matching payments to invoices — and design every surface around traceability: every figure links to its origin.

06Design process

  1. Step 01

    Discovery

    Mapped the current reconciliation workflow and pain points.

  2. Step 02

    Information architecture

    Organized the product around accounts, transactions and exceptions.

  3. Step 03

    Prototyping

    Tested matching flows with clickable prototypes.

  4. Step 04

    Design system

    Built tokens, tables, filters and data-viz components.

07Final solution

A calm, data-dense workspace with an exceptions-first inbox, explainable matching suggestions and a cash overview that updates in real time.

08Screens & mockups

Exceptions inbox — what needs attention today
Transaction matching with source traceability
Design system — tables, filters and tokens

09Results

Results will be published once verified with the client. No metrics are shown until they're real.

10Key learnings

  • — In financial tools, trust is a feature: explainability beats automation.
  • — Designing tables and empty states early prevents most late-stage rework.

Next step

Tell me where you are and where you want to go. I'll reply within two working days with honest next steps — even if that means I'm not the right fit.