Composable Finance & Ledger Platform for BFIs

Context

Sumo Ledger is a composable finance platform built for Banking and Financial Institutions — mobile wallet providers, neobanks, money-transfer services, multi-sided platforms and traditional banks running ERPs. Its promise is that teams can "build & integrate like legos, to any other software system or data source," assembling financial products from modular pieces instead of rigid, monolithic core systems.

My Role

As Product Designer I owned the end-to-end design of the platform's interface — research, information architecture, interaction and UI through to developer handoff — working closely with the product and engineering teams. The core challenge was making a powerful, low-level ledger and processing engine legible to the operators who configure it.

The Problem

BFIs typically stitch together inflexible core-banking systems, spreadsheets and bespoke scripts to move and reconcile money. Building or changing a financial workflow means waiting on engineering, integrations are brittle, and there's little real-time visibility into balances and transactions across asset types. The result is slow product velocity and operational risk.

What I Did

• Designed the product around six composable modules — Accounts, Process, Tariff, Tasks, Reports and Connect — so an operator can build a workflow by combining blocks rather than commissioning custom code.
• Made the "Process" engine visual — turning business-process and pricing logic into a configurable canvas, with the Tariff rules engine surfaced as something a non-engineer can reason about.
• Tamed complexity in the ledger UI — multi-asset, multi-currency balances and a hierarchical chart of accounts presented so real-time financial state is actually readable.
• Designed the integration layer — the Connect surface for third-party APIs, webhooks and ERP connectors (Tally, Swastik, RIGO), keeping event-driven plumbing understandable.

Outcome

The platform supports high-throughput processing — up to 1,500 transactions per second per ledger account — with real-time webhooks and event-driven notifications, letting institutions automate financial workflows and gain live visibility without manual intervention. The modular, API-first model means new financial products can be composed and integrated far faster than on a traditional core.

Reflection

The hardest design work here was restraint: exposing enough of a deeply technical engine to make it powerful, while hiding enough to keep it usable. Building a shared visual language for "composability" early would have paid off across every module.