I want our financial system to be penny-perfect and instantly accessible.
As end users, my wife and I have both regularly scheduled and ad hoc needs. On a regular cadence, we review budgets, assess goal progress, and plan our expected financial behaviors into the foreseeable future. At unpredictable moments, we also need to conversationally assess everything from this week's budget and spend-anomaly alerts to net-worth modeling for retirement. Anything related to money should feel easy and intuitive.
Underneath that experience, the data stays secure, scheduled loops are hardened, and the system runs proactively, nudging us toward better planning and saving.
Our ultimate goal is financial freedom. Getting there requires a better way to track and manage our family finances: one that makes progress visible, helps us act sooner, and lets us celebrate milestones along the way.
Design intents
- Positive reinforcement with negative alerts - celebrate progress during every review ritual, and alert us proactively if we're veering off track
- Tech independence - the family record stays local, portable, and rebuildable, with vendors treated as swappable inputs
- Secure by construction - credentials stay outside model context, statements are masked before parsing, and shared web access must be authenticated and least-privilege
- Pristine provenance - every record, change, and decision traces back to its source
- Trust is earned - regular human reviews continue until alignment is consistently very high
- Works for both of us - outputs make sense, remain easy and secure to access, and inform decisions for both of us
- Close the loop - every decision and target is proactively tracked and reported against
Status (2026-09-01)
The operating loop now exists. Since the July audit, the ledger reached 99% categorization, fourteen expected-transaction lines grew into a dated forecast, and the forecast, budget, and compare loop went live across the monthly review, the quest home, and the forecast page. The first forecast covered September through December and matched the hand-built rollup to the cent. My wife and I committed the first monthly budget against it. October is the first month where drift and discipline can be measured, so the quest is now about proving the routine, not building it. It's still a little too manual, and I need to land the surfaces for us to collaborate. I'm overall pleased with the progress and, most importantly, it's already impacting our financial decisions.
What's working
- The philosophy is specific - family freedom, a stress shield, lifestyle bounds, and re-design triggers are written down
- The raw materials are owned - statements and bank feeds land in a local database with source provenance
- Trust is a design constraint - rules are meant to earn automation through approvals and continuing samples
- The family ritual has a surface - goals, watched categories, balances, and commitments can share one monthly view
- The database is rebuildable - independent source layers feed one stable query surface
- The loop has vocabulary - forecast, budget, and actuals are distinct objects, and every deliberate deviation carries a written reason
- Guardrails live in the database - a forecast with blocking issues cannot be frozen, and every schema change ships with a receipt
What's not (yet)
- Historical categories are close but not fully settled, and that gap still nags at me
- The forecasting logic was close in some months and off in others; outliers had to be corrected by hand
- Short, medium, and long-term savings targets are not yet visible on the screens, so the savings picture gets lost
- The review surface handles hundreds of line items awkwardly; the review logic and the review screen are still tangled
- No month has closed with a committed budget yet, so drift and discipline remain unmeasured
- The shared family surface needs more hardening before it feels like a product we both reach for
Stabilization sequence
- Make input health explicit - freshness, account coverage, statement coverage, and sync failures become visible gates
- Make gold deterministic - one matching contract, durable overrides in source/config, reconciliation tests, reproducible rebuilds
- Finish the categorization loop - executable rules, confidence state for every category, a durable review queue, and coverage metrics
- Prove the family routines - harden access, run each ritual on its intended cadence for three months, carry commitments forward, and remove anything that doesn't aid a decision
- Add proactive guidance - specific recommendations and probability models only after the descriptive loop stays trustworthy