About
We built the statement-credit tracker we couldn't find.
Annual-fee cards promise credits, and they're easy to lose track of. MoneyRoom exists to track them — plainly, privately, and without selling your data.
What the product observes
The useful facts live in different places.
An earn rate sits in issuer terms. A credit resets on its own clock. Points live inside separate programs. Lounge access changes by card, airport, and rule. A transaction arrives after the choice that created it.
Why one room
One workspace, because card decisions overlap.
MoneyRoom is organized as one workspace because the decision rarely ends at one feature. The card you choose can affect a benefit, a points balance, a lounge visit, and the spending pattern you review later.
Product principles
Rules for a room that handles financial context.
- 01
Keep the inputs visible.
A recommendation should show the wallet and category context behind it, not arrive as an unexplained verdict.
- 02
Make connection a choice.
Manual tracking remains a real product path. Connected account context is optional, and its boundary should be understandable before it is enabled.
- 03
Treat periods as product structure.
Benefits reset on different clocks. The interface should preserve each period, its usage, and its history instead of flattening them into one total.
- 04
Design the exit with the entrance.
Export, disconnect, notification controls, and account deletion belong in the product model—not in an afterthought.
The craft ledger
The details are the product.
MoneyRoom can be used manually. Its optional connected path uses Plaid, and the product exposes export, institution-disconnect, notification, and account-deletion controls in Settings.
- A
Wallet context
Card choice starts with the cards a person actually carries.
- B
Period context
Benefit usage stays attached to the period that gives it meaning.
- C
Connection context
Optional read-only account data remains visibly separate from product rules and manual choices.
- D
Decision context
Spending review can inform the next card decision without erasing uncertainty.
The threshold
See what it does. Then check what it can't do.
The product story matters only if the controls, connection model, and limits are equally legible.