Comment by arjie

I understand why this is a good idea. I have Claude Code hooked up to my mail synced via IMAP, my Mercury read-only token, and beancount, and it gets almost all of my invoices and categorizes them. The tedious portion for a lot of this is:

* find invoice I_E for expense E

* associate and categorize E based on I_E and transaction field

These things are annoying but Claude Code is great at it and it leaves a much smaller set I have to manually resolve. This is a class of problems that are tractable and checkable, which I happily use LLMs on. If it miscategorizes it, I'm going to see it because I'm looking over the accounts. In fact, I was previously using a different accounting app which had poor API support, so I dumped it so I could use Claude and it's incredible how much this helps me.

There is an enormous number of use-cases that Claude/GPT are good for and the hard part is market penetration here. As an example, my dad was looking at some statistical health survey data in India and working out what things you could glean from it. Claude identified the things that would complicate his analysis in no time. He's 70 years old, and he'd done it all manually until he asked me (I've got a Mathematics degree) if something made statistical sense to do. I told him what it likely was and then asked him to try Claude. Knocked out his work and mine in moments. But he didn't think to use it. Now I have to get him a ChatGPT/Claude subscription.

It's like how if you go to the Datadog pricing page they don't list a feature set. They have all these use-case lists with prices. You can build things using their base metrics functionality and logs functionality but showing the use-cases must have more adoption.