I bypassed Plaid with a Secured Service Bot + Gemini. Looking for 5 "Founding" critics.
Most people quit budgeting because they don't trust third-party apps with their bank passwords, or they hate the "Plaid tax" on their privacy.
I built Family Budget Tracker to solve this. It is a Zero-Based budgeting tool that runs entirely within your own Google Drive infrastructure.
The Tech: Instead of bank sync, I developed a Secured Service Bot (Python) that uses Gemini to parse PDF and image statements. I call it the "Magic Drop." You drag a statement into your Drive, and the bot handles the math, calculates "Safe to Spend," and links transactions to your goals.
The Deal: I’ve just stabilized the parsing logic and I need people to try and break it.
The Founding 5: The first 5 users to sign up and email me honest feedback (bugs or UX issues) get Free Lifetime Access.
The Beta 20: The next 20 users get 50% off the Yearly Price ($35 Solo / $49 Family) locked in forever.
How to Claim:
Sign up for the 7-day trial (no credit card required): https://family-budget.getdigraw.com/
Test the "Magic Drop" with a statement (or a sample).
Email your feedback to: support@getdigraw.com
I'll manually upgrade you and send your 50% private code if the free spots are gone.
Interesting idea — avoiding bank sync entirely feels like a big trust unlock. Curious whether statement parsing accuracy or UX has been the bigger challenge so far.
Thanks, You hit on the exact tension I’m navigating every day.
To be honest, UX has been the bigger hurdle. The logic is simple: the more friction you add (asking for an upload), the more trust you need.
On the Accuracy side, Gemini’s multimodal (vision) capabilities have actually made parsing surprisingly robus,it handles the spatial layout of a PDF better than traditional OCR.
The real challenge is the 'Time-to-Magic.' Since statement parsing isn't instant (unlike a cached Plaid sync), I’ve had to focus heavily on the UX of that waiting period making sure the user feels the 'Secured Service Bot' is actually working hard for them in the background rather than just staring at a loading spinner.
Are you building anything in the automation space?
Yeah, that “time-to-magic” point really resonates. Even when the backend logic is solid, the moment you ask users to upload something, the burden of trust shifts heavily onto the UX.
What you said about making the waiting period feel intentional instead of dead time is spot on — that’s where a lot of tools quietly lose people. A spinner feels broken; visible progress feels earned.
I’m working on an AI that is more on the decision-support side (inventory forecasting for small businesses), but the same tension shows up there too. I’ve been spending more time on explaining what’s happening and why than on squeezing out marginal model improvements.
The statement parsing angle is smart - Plaid's per-connection pricing doesn't make sense for personal finance tools where users only connect their own accounts.
I'm building in a similar space (statement parsing for accountants/bookkeepers) and the messy part isn't the OCR itself - it's handling the 50+ different PDF formats banks use. Same transaction data, wildly different layouts. Lloyds formats nothing like Barclays, Monzo statements are completely different from high street banks, business accounts have different columns than personal.
Curious how you're handling that variation? Are you fine-tuning prompts per bank, or trying to make Gemini figure it out from scratch each time?
The "Magic Drop" UX sounds nice. Drag-and-drop is underrated - people hate filling out forms when they just want an answer.
You're spot on, Jack. The 'Lloyds vs. Monzo' layout variance is exactly where traditional OCR/RegEx pipelines fall apart.
I found that trying to read the text first and then parse it was too brittle. Switching to a Multimodal (Vision) approach was a game-changer. I treat the document as a spatial map. Gemini is surprisingly good at 'seeing' the column relationships even when the headers are wildly different.
The 'Magic Drop' was my way of keeping that 'Zero-Link' privacy promise while matching the speed of Plaid. your bankreconciler app sounds like a beast to build handling business accounts must be 10 times the data volume!
Congrats on the launch, looks solid. What channels are you experimenting with to get early users?
Thanks, Ajayi! I'm glad you like the direction.
Right now, I'm focusing on high-intent communities like r/ynabalternatives and Indie Hackers to find 'power users' who really care about privacy. I'm prioritizing direct feedback over broad reach for these first 50 users.
Have you found any specific launch strategies that worked well for your projects?
That’s a great approach, starting with high-intent communities and prioritizing feedback over reach is exactly what works early on, especially for privacy-focused tools. What I’ve seen work well is using discussion-first posts in very specific subreddits (like you’re doing) where the focus is on a real problem or workflow, not the product itself. Founders who stay active in the comments tend to attract power users naturally, and those conversations often turn into organic recommendations later.
Are you planning to run those discussions yourself long-term, or would you consider having someone help keep them active while you focus on building?
That’s a great question, Ajayi.
For now, I'm staying in the trenches as a solo founder. My goal for this phase isn't mass scale, it's high-fidelity feedback.
I want to be the one answering every support ticket and reading every bug report myself. It’s the only way to ensure the 'Magic Drop' logic is 100% robust before I even think about bringing on help or scaling the community.
I'll definitely keep your point about long-term management in mind as we grow, but for the 'Founding 20' users, it's just me and the code!
That makes perfect sense. Staying close to the product and your users at this stage is the right decision, especially when it comes to your core logic and trust model. It seems like you're taking a solid foundation-first approach. When you reach a point where feedback stabilizes and visibility becomes a priority, I would be happy to share some lightweight strategies that founders use to maintain community presence while still keeping that hands-on connection. Wishing you all the best with the Founding 20; it's an exciting phase to be in!