GlidePath Money

How it works

One file or a few balances gets your first Money State.

The rest sharpens it. Start with a local file, type two or three current balances, or inspect a clearly labeled fictional demo household that you can exit anytime.

The first useful artifact comes before the long setup guide.

Why this isn't bank-sync

Automation that runs on your machine — not a pipe to your bank.

Aggregator apps feel automatic because a standing connection syncs from outside the app. GlidePath works from files you choose to bring in. You keep the source file, review the preview before it saves, and keep the local result with its receipt.

The loop, end to end

State, change, decision, close, future echo.

Money State is the everyday brief. The Close turns it into an official record. The modeled echo shows how the current path carries forward, with its assumption sentence still visible.

  1. see the state dated, sourced, and local
  2. see what changed anchored to the last close
  3. make one decision or record a dated skip
  4. close and be done the official brief is archived
  5. see the echo modeled with assumptions visible

The receipts behind the loop

Every beat says what supports it.

Freshness, close anchors, source links, archived lines, runway anchors (the months-of-coverage figures each close records), and visible assumptions keep the state inspectable instead of asking you to trust a score.

freshness dated local files close anchor the comparison point assumptions the modeled boundary

Money State starts from the facts

The period and freshness line say which local files support the brief. Missing facts stay visible instead of being guessed away.

Change keeps its close anchor

Changed Since Last Close names the movement, the comparison point, and the source-backed line that produced it.

The decision stays yours

One Decision can surface a choice worth considering. The Close can also record an honest dated skip when nothing needs a call.

The Close keeps the record

The official brief archives changed, quiet, decision, and close facts. Past closes keep each record browsable instead of overwriting it.

Between closes

The everyday workbenches, where the evidence lives.

The loop is the story; these are the rooms it reads from. A transactions workbench shows where every dollar moves, with the records behind it. Budgets are month-native — pick the month, see the actuals, and choose which remainders carry forward. And reports start from the job, not the menu: save the views you come back to, and any number opens the ledger rows behind it. When the Close arrives, these are the receipts it leans on.

The transactions workbench

Search, filter, and inspect the rows behind the rest of the app — each one carrying its source badge and an audit trail.

GlidePath Money transactions workbench on a fictional demo household: a living ledger of 143 rows with a 90/100 ledger-health read, search and filter controls, a filtered income and expense sum, and rows carrying source badges beside each amount.

Fictional demo data.

Reports that name their job

Each card says the question it answers, where the numbers come from, and whether there is enough history to trust the view — and evidence links open the ledger rows behind any number.

GlidePath Money report library on a fictional demo household: job-named cards — what changed this month, where every dollar goes, debt paydown timeline, 0% promo cliff risk, goal progress — each stating its data sources, a Ready badge, and an open link.

Fictional demo data.

See the loop in the real app.

Walk the screenshot tour — or install the app and choose Explore to walk the real thing on a fictional household, no license key, account, or email.