Walk the real workflow with sample data. Anchor to a balance, place income and commitments on a timeline, and watch the lowest point ahead move as each piece lands, before creating an account.
The guided demo starts where you would: with the balance you actually have. It anchors at $6,200 in checking, typed in rather than synced, because there is no bank connection to sync from.
From there it adds the things that make a balance misleading. Payday of $4,200 arrives on the 9th. The card payment of $1,250 leaves on the 2nd. Same month, same money, and the order is the entire problem.
Once rent, an auto-invest, the car, groceries and a weekend trip are all on the timeline, the projected balance dips to roughly $730 before payday lands.
That is the point of the whole exercise. The bank says $6,200. The genuinely free figure, with every commitment and the investing already covered, is around $730. One of those numbers is safe to make a decision against and the other is not.
The walkthrough then shows the states an entry moves through, because they answer different questions. Marking something processed records that the money has genuinely left the account, which is what stops a projection drifting from reality while a payment is pending.
Disabling an entry tests a possibility without deleting it, so you can ask what happens if the trip does not go ahead and put it straight back. Marking it done closes the loop and takes it out of the forecast entirely.
The last step resets to today so the method is yours rather than the sample data’s: anchor to a real balance, place what you know is coming, and read the lowest point rather than the highest.
Every figure in the walkthrough is computed by the same engine the real app uses. Nothing is illustrated or approximated for the demo.