Cash/MONEY

From fragile expense capture to household finance

Cash/MONEY started with a practical household problem: keeping everyday spending visible without maintaining a chain of spreadsheets, Notion forms and automations. The first product replaced that fragile workflow with fast transaction capture and a dedicated API.

The work has since developed into a broader household finance product. Shared ledgers, budgets, cash-flow cycles, planning, goals, notifications and reports connect the daily transaction to the decisions a household needs to make next.

Design around the household, not just the transaction

Couples and shared households do not always earn or spend on the same cycle. A useful operating view needs to show budget pressure, expected cash flow and the effect of a decision over time. Cash/MONEY brings those concepts together instead of treating the ledger as the whole product.

Fast capture remains a key entry point. Defaults and predictions reduce repeated input, while budget context gives the entry a consequence the user can understand. Shared access and family permissions are part of the model, not an assumption that every participant should see everything.

Connected capabilities, deliberate boundaries

The SvelteKit frontend and Flask/PostgreSQL backend support a common finance model. Separate mobile and operational tooling exist alongside the web application. The public showcase uses sanitised examples and describes household scenarios without depending on authenticated financial APIs.

Product direction includes shared-expense acquisition, more capture assistance and mobile workflows. Those are areas for continued validation; this story does not imply that bank integrations or every planned client capability are already available.

What this work demonstrates

Cash/MONEY demonstrates the evolution from a focused personal need into a connected product domain. It combines interaction design, modelling, multi-user permissions and operational concerns around a clear purpose: helping a household understand where it stands and what comes next.

The next phase is to validate adoption and harden the shared-access and recovery paths before broadening acquisition. Measured financial outcomes and user-growth figures are intentionally omitted until supported by evidence.