You Inc

Case snapshot

Problem

Create one auditable view of assets, liabilities, cashflow, and runway from fragmented personal-finance data.

My role

Solo product engineer responsible for product direction, data model, integrations, security posture, and delivery.

What I changed

Converted read-only bank feeds into balanced journal entries.
Held uncertain classifications in suspense instead of silently guessing.
Derived dashboard views from the ledger with tenant-isolated data.

Result

A working live system with signup and a clearly labeled sample dashboard; it is not currently operated as a business.

Budgeting was not the model I needed

I wanted a coherent view of what I own, owe, earn, and spend—not another set of envelopes or a spreadsheet that depended on manual upkeep.

Financial data needs explicit uncertainty

Read-only Akahu data enters a ledger where every posting balances. Rules route known transactions, while anything uncertain is held in suspense for review rather than guessed.

The ledger became the product boundary

Net worth, runway, cashflow, and action prompts are derived from the same accounting model. Bank tokens stay server-side and row-level security isolates each account.

The public evidence uses sample data

The live site exposes signup, security details, the bank-to-board pipeline, and a sample company dashboard. Its concierge commission examples are illustrative and are not client outcomes.

The useful lesson was that a trustworthy financial product begins with auditable entries and clear exceptions. Dashboard variety is secondary to getting that foundation right.