Launching today
Jupid
File your taxes with Claude Code
643 followers
File your taxes with Claude Code
643 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.
Spiritme
What about using an LLM with a vector database for persistent context? Seems like that would solve the memory problem without a new product.
@nikita_bogdanov1 Great technical question. Vector search helps with recall but doesn't solve the categorization consistency problem. You need structured vendor-to-category mappings that update deterministically, not probabilistic retrieval. We tried the RAG approach early on - it hallucinates categories at scale. The data layer we built is more like a traditional database with LLM-powered onboarding, not a vector search.
Skala
This solves a pain I've been feeling for a while. I dumped my bank CSV into Claude last month and it was great at first, but by the 200th transaction it was categorizing Uber rides as 'Office Supplies.' How does Jupid keep accuracy high across thousands of transactions?
@danilakropotkin Great question! Our innovation is that we don't work with transactions directly — we work with your counterparties. When we understand the background and context of who you're doing business with, assigning the correct category becomes straightforward, because the relationship between your company and the counterparty IS the economic essence of the transaction. That's how we maintain high accuracy across thousands of transactions.
The vendor relationship memory approach is clever. I've hit the exact context drift problem — paste 6 months of transactions into Claude, works great until it starts re-categorizing the same coffee shop three different ways. Modeling context around counterparties instead of individual rows is a much smarter data structure for this.
@letian_wang3 Yes, that’s exactly the point. Transactions alone are not enough for proper categorization or stable memory. That’s why we took a completely different approach and work with counterparties and relationship memory.
Documentation.AI
Hey @slavaakulov Congratulations on the launch. Is Jupid available for c-corps as well?
@roopreddy Thanks, Roop! Yes, it works for C-Corps as well. If you use pass-through filing, it doesn't matter what corporate structure you have — we support it.
Venture Roof
The 'Works in Claude Code' angle is interesting. What does that actually look like in practice?
@dimakim You open Claude Code in your project, and you can ask things like 'what were my top 5 expenses last month?' or 'am I on track for quarterly estimated taxes?' - using your real bank data, not hypotheticals. It's your financial data available as context wherever you code. For founders who live in the terminal, it means never switching to a separate accounting app.
I already use claude code a lot for my tax calculation, but looking forward to close the gap and solve it end to end with agents. Best of luck!
@arseny_info Would love to have you as one of our first users, Arseny! Unfortunately, for now we only connect to US banks via Plaid. However, we work perfectly with any CSV exports — you can just drop your bank statements and we'll process them as if it were a regular bank connection.
Pulse App
Congrats with the launch - great product!
Does it handle estimated quarterly taxes?
@esmentoza Yes, we do estimated taxes — both monthly and quarterly, no problem!