Why we built JamCash
By Michael Sanford · Published · Updated
JamCash started life as the finance module inside Aiden, a personal operations app Michael Sanford built for himself. It grew until it was the part he used every day, so in October 2026 it moved out and became its own product, published by Sanford Labs.
What was the problem?
Most finance apps guess. They guess your categories, guess which charges repeat, and guess what a transfer is, and when they guess wrong you fix it again next month. JamCash takes the opposite view: your rules and your edits are the source of truth, and the bank feed fills in around them.
What does that look like in practice?
- Rules you write. A rule matches a description by text, prefix or pattern and files the transaction. Rules run on every sync.
- Edits that stick. If you change a transaction and the bank later sends a different version, JamCash keeps yours and queues the bank’s for review.
- Suggestions, not decisions. Recurring charges are detected and suggested; you confirm or dismiss each one.
Why an MCP server?
Because asking “am I on budget this month?” should be a sentence, not a report. JamCash’s MCP server gives an assistant like Claude the same answers the web app shows, through the same code, so the two can never disagree.