You have questions about your own money that can be difficult to answer.
Not “how much did I spend on coffee.” The real ones: how much of your pay is surplus? Can you use that profit to pay off a credit card? How much of last year’s surplus made it into retirement? What your position looks like if you stop working in March. mini‑me is built so you can just ask.
What asking actually looks like.
An income statement over any period, with transfers between your own accounts netted out instead of counted twice. Because business-grade books sit underneath it, the number ties.
A projection built from your own recurring flows, not a generic model, and you can change the assumptions and run it again.
Your pay stub broken down line by line: withholding, the match, the HSA, the FSA, and where each piece landed.
The answers come from your books. Claude is how you reach them, connected to your instance over MCP, on your say-so.
The app is where the answers come from.
You link your accounts in mini‑me and work in mini‑me: reviewing transactions, fixing a category, checking a balance, opening a statement. All of that runs on the accounting engine inside the app, which keeps your books current as things sync.
Claude is reading that same engine. It isn’t a separate brain with an opinion about your money; it’s another way into the books the app already keeps, for the questions no screen has been built for yet.
Plaid where it works, an uploaded statement where it doesn’t. Same books either way.
Reviewing and recategorising is a button. No prompt to write, nothing to remember.
Balance sheet, income statement, cash flow, over any period. The app and Claude read the same numbers.
Forward views you can change an assumption in and re-run.
Spouse or CPA, scoped to what you choose, plus an LLC you own kept on its own books.
Plainly, before you connect a single account.
One instance per person, open formats, full export, open-source core. If this went away, your books would still open.
Bank links see transactions and nothing else. mini‑me never touches a payment.
Drop in the statement and mini‑me works out which account it belongs to, then books it like any other. Nothing gets left out because Plaid doesn’t cover it.
The app is fully usable without it, and the numbers always come from the ledger rather than the model.
Everything exports. Run both for a quarter and keep whichever one you actually open. Start with two accounts, not eleven.
Questions people actually ask.
Upload the statement instead. mini‑me reads it, works out which of your accounts it belongs to, and books the transactions exactly as it would for a linked one. Some accounts here work that way permanently.
No. Transactions categorise themselves, and correcting one is a button rather than a form. The correction sticks.
As far back as you have statements. Linked accounts bring their available history, and anything older you can upload, so you can close out a year that’s already finished.
Not at all. The statements are already built and everything is labelled in plain words. The accounting is why the answers are right, not something you have to operate.
An hour or so with me, mostly logins. Start with the two or three accounts most of your money runs through; the picture is useful well before everything is in.
Start with the question that’s been bothering you.
Instances go out gradually, because each one is a real database I stand up and support with you. What early users keep asking is what gets built into the app next.