Skip to content

About / the room behind the decisions

A wallet is not a system.

MoneyRoom begins with a simple belief: cards, benefits, points, travel access, and spending become more useful when their decisions can share context.

01

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.

Card termsBenefit periodsProgram balancesAirport accessSpending records

Why one room

Context should survive the handoff.

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.

  1. 01

    Keep the inputs visible.

    A recommendation should show the wallet and category context behind it, not arrive as an unexplained verdict.

  2. 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.

  3. 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.

  4. 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

Product detail is the brand proof.

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.

  1. A

    Wallet context

    Card choice starts with the cards a person actually carries.

  2. B

    Period context

    Benefit usage stays attached to the period that gives it meaning.

  3. C

    Connection context

    Optional read-only account data remains visibly separate from product rules and manual choices.

  4. D

    Decision context

    Spending review can inform the next card decision without erasing uncertainty.

The threshold

See the room. Then inspect its boundary.

The product story matters only if the controls, connection model, and limits are equally legible.