Case study · 03 / 03
MO Finance OS
A personal financial operating system built on a ledger, not a budget sheet.
- Field
- Financial intelligence
- Interface
- Arabic and English
- Built with
- Next.jsTypeScriptTailwind CSSPrismaSQLiteVitest
Figures, names and emails in the screenshots are blurred to protect the people who use them.
01The problem
Bank balances don't tell the whole story. A card statement can mix your own spending with expenses you carried for other people, and a shortfall shows up only when a due date arrives.
02What we built
A ledger-based system that reads bank statements, reconciles them and turns them into one financial picture: what you really owe, what's coming in, and what could hurt you in the next 30 days. It was built in phases, with an automated test suite behind the numbers.
Inside the system
09
- 01Parses CIB and BDC statements: periods, closing balances, due dates, minimum payments
- 02Reconciles the statement balance against your real share and other people's exposure
- 03Alert engine, credit guard, cash-flow guardian and spending-leak detector
- 04A 30-day summary: cash on hand, confirmed income, dues and the gap
- 05A daily spending limit, split by category
- 06Spending analytics with weekly and monthly reviews
- 07Scenario engine, debt strategy engine and close-the-gap planning
- 08Accounts, cards, people, receivables, recurring payments, savings circles and gold
- 09Arabic and English interface
How the data flows
- 01Data
- 02Reconciliation
- 03Analysis
- 04Risk detection
- 05Planning
- 06Action
Your process could be the next system here.
Show us the spreadsheet, the inbox or the habit that holds your work together. We'll tell you honestly what a system would change.