(stoke.money)
This is more or less how I already set up GNUCash. Couple dozen scheduled transactions created 90 days into the future, with the "Future Minimum Balance" field enabled on the homescreen.
For me, the time sinks are interrelated:
1. Monthly reconciliation. Every month I sit down and compare the scheduled transactions with what actually happened in statements, for approximately thirty different accounts. Many don't have APIs, certainly none GNUCash would speak. This takes a lot of time and I wish I could just have this automated. Just give me exception handling on the edge cases like a new transaction category, or a forecasted negative checking balance.
2. CC transaction import. This is a structural failing of banking closing down formerly open APIs. Only thing left on my BofA accounts is CSV exports. Which thankfully works with a bit of setup but the writing is on the wall and even that may soon vanish in the name of banks defending their core business.
3. Stock transactions, equity grants & price tracking. This one is even harder since CSV feels structurally not up to the task of representing the "sell to cover taxes" split of RSU grants, and I never really got it working in OFX anyways. Plus I have a pretty weird collection of accounts including a pension IAP that updates once a year (and that update is retroactive to 6 months ago) and a 457b invested in restricted custom funds with no ticker symbols.
Even a SOC type 1 would show you're on the journey.
You need to spam growth and marketing. Your landing page is horrible (too boilerplate, too vibe coded, no graphics. Some pages have horizontal overflows on mobile. https://stoke.money/compare/simplifi). Redo it. Run ads and pay Tiktok influencers and YouTubers.
Standard consumer SaaS security is more than enough for this sort of product. Your users won't know the difference between end-to-end encryption and encryption at rest and while you are nitpicking based on hacker news power user feedback others would eat your lunch already.
If you are a US fintech, monetizing consumer user data is par for the course. Do what you will with that information but just know that your competitors don't simply make money from subscriptions alone.
The governing terms are California's. I checked CA business registry and found no 'VoidHQ' or 'Void HQ'. Not sure who I would be trusting with my data.
in my world, there is no such things as "registering", and I say that because I've seen many people get caught up on this process for actual years. Picking the wrong state, or getting hung up on name, and things like that. Can you shift liability and process payments or not. there is a blueprint that works for this country and international access, but nearly infinite permutations that may take you a lifetime to figure out, or cost you more than it should by copy pasting Delaware for everything.
- 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.