13 karma · joined December 7, 2015
1. Exclusions. You can exclude any single transaction from the forecast. It stays in your history but no longer counts toward the projection.
2. Streams. You can group a set of transactions into a stream (e.g. your YouTube subscription inside Entertainment), and it gets its own projection on its own schedule instead of being averaged into the category.
3. Plans. If you know a big expense is coming, you can set up a Plan. Plans can add one-off events (like an expensive car repair) or apply a percentage increase/decrease to a category (like Shopping during the holidays).
Finally, once there’s enough history, the forecast also picks up seasonal patterns, like higher spending in Shopping or Travel in December, and will project higher amounts for just that month. Your first December may be underestimated, but it gets more accurate as history builds up.
- Privacy. Stoke is a paid subscription. I’m not selling your data. Caveat: if you connect an agent over MCP, what that agent does with your data is up to you. I can't control that.
- Data. The core product is the projection, and it’s only as good as the data underneath it. Plaid data is imperfect, so there’s always some cleanup to do. ChatGPT and Muse may do a decent job of recategorizing transactions and even remembering those fixes for future ones, but I think direct access to those controls (categories, rules, overrides) is a better experience than asking a chatbot.
- Portability. Everything you’ve modeled lives in Stoke, not in one AI assistant's memory. You can freely switch from ChatGPT to Claude or anything else without losing anything.
- Not mutually exclusive. All the questions you would ask your LLM about your finances, you can still do via the Stoke MCP, so I see it as the best of both worlds.