Launching today

Jupid
File your taxes with Claude Code
346 followers
File your taxes with Claude Code
346 followers
No matter how powerful LLMs get, they are objectively bad at financial transactions. Context loss, inconsistent categories, no memory between sessions. Jupid fixes the data layer. Connect your bank — it learns your business and every vendor relationship once, then remembers forever. Transactions mapped to IRS Schedule C categories (~96% accuracy). Missed deductions found: $1,249/year average. File your Schedule C in 5 minutes. Works with Claude Code. Free trial + 50% off first 3 months.









@slavaakulov How does Jupid "remember" that context long-term without constant retraining, especially for solopreneurs like me juggling multiple clients?
@swati_paliwal Great question, Swati! We don't work with transactions — we work with your counterparties. We build context around your connections with partners, clients, and vendors. So the context is stored around your relationships, not around individual transactions. This keeps the context window very efficient — no need to store thousands of transactions in a single context window.
Sidekick Browser for Teams
@slavaakulov
This is fantastic, after years of IRS fines, missed deadlines and accounting mess (there's always something more important to do in a startup than accounting) having something like is a godsend :) I only wish you guys launched a decade ago )
@dmitry_pushkarev Dmitry, thank you so much for the kind words! Really means a lot. I hope Jupid saves you from those IRS fines going forward
Tobira.ai
@vlad_shipilov Vlad, thank you for the kind words! Hope we'll be useful — give it a try and let us know how it goes!
Nice launch! I run a single-member US LLC. Most of my expenses are SaaS subscriptions, a few contractor payments, and the occasional travel. Pretty clean Schedule C. Two questions: (1) How does Jupid handle the personal vs. business split on a single bank account — does it learn which recurring charges are business over time, or do I have to tag everything manually upfront? (2) For a low-volume consulting LLC (~50-100 transactions/month), is there enough signal for the categorization engine to be useful, or does this shine more at higher transaction volumes?
@sergey_kalachev Our topmost goal is eventually make it so you don't need to tag anything manually!
think of working with a real human accountant: sometimes he'll have to ask you questions ("Did you fuel your car here for personal needs or business travel?"), but often, knowing you, your company operations, your history and preferences, he can make this assumption on his own.
That's our target: Jupid should become well-versed in your operations so it'll bother you only when it's necessary and just once.
@sergey_kalachev Great questions, Sergey! First, on personal vs. business — we start with the bank account type. Generally, the account itself sets the pattern for how we treat transactions: business expense or personal. You can always override and mark any personal transaction as business. As for transaction volume — it's really just a matter of tokens our system consumes. The categorization question is most relevant during onboarding, when you're just starting out. After that, transactions naturally become more predictable and typed, and volume doesn't matter much.
AgentQL
If our company already considers using one of the alternatives, like Fondo, how are you different from them? Any highlights/number differences?
@colriot Fondo is a great company. But they still rely heavily on manual work for bookkeeping. Where we excel is the technology — you practically don't need manual work anymore. Out of the box, you get high-quality categorization. Plus you always have instant communication with our AI accountant through any messenger.
I did all my taxes this year with Claude walking me through the whole process. It was honestly perfect. So seeing someone build a dedicated product around this makes total sense. The messy part was always the data, not the AI itself. Curious how Jupid handles bank connections for EU accounts?
@thenomadcode Great to hear you've been using Claude for taxes! You're right — the messy part was always the data, not the AI itself. For EU bank connections — we work with any CSV exports, so you can just drop your bank statements and we'll handle them. Direct EU bank integrations are on our roadmap.
Hey, Slava, congratulations with the Jupid launch!
Just for understanding, about ~96% auto-mapping to Schedule C categories, where does liability sit for the remaining 4% — and more importantly, for incorrect classifications within that 96%?
Is there a verification layer, or are users implicitly trusting a black-box financial brain?
@michael_batuev Thank you for the support, Michael! Great question about the 4%. Yes, that 4% always needs additional context from the client — because we can extract everything that's in the data, but not everything IS in the data. Sometimes you need extra context. That's why we built convenient access through any messenger — WhatsApp, iMessage. Our system can simply ask the client about missing information on the go. Once we get a response in any free form via iMessage or SMS, we turn it into proper accounting records.
Banyan AI Lite
Good luck and happy launch! Question: whoch countries do you cover and how do you make sure results are deterministic, no hallucinations or wrong calculation. You know, you better not fool around with tax authorities 😀
@davitausberlin Great question, Davit! Right now we cover the US for tax filing. As for hallucinations — yes, you have to fight them. We've built a multi-layer supervision system with cross-validation between different models, plus manual review checkpoints. You definitely don't want to mess around with tax authorities 😄