Show HN: Invoice Detector – All your invoices in one place, every month

This is a compelling use case for AI, and a solution that was sorely needed.

- If you refer to it as '(payables) bills' not '(receivables) invoices' it will tie in more neatly with your customers' payables departments, and employees will be less likely to confuse it with receivables. It also future proofs your dictionary for when you scale. It also opens you up to B2C (Individuals refer to their bills as bills, not invoices).

- This is too small in scope for the long term (presumably preaching to the choir). Businesses can't have one integration per entity class. I.e.: If a business installs this, then they will also need another LLM agent scanning for customer tickets, another for sales, etc. Having 100s of integrations is a security problem, on top of cost and complexity considerations.

- Thus, presumably your plan is to introduce more integrations for more entity classes over time, a single agent scanning and each routing different entities into their respective bucket. The low hanging fruit is probably: Other supplier comms/tickets, Customer leads/sales/rfqs, Customer tickets/support, Customer complaints, Outgoing invoices (detect when a recurring invoice has not been issued, for example), RMM augmentation (e.g. warranty/domain expiry warning emails), Marketing notifications to correct campaigns.

- The pricing is interesting, as the lower tier is in a range that will be very price elastic for 'small businesses that are not particularly profitable'. I.e., tiny water-treading companies tend to quibble over $20/month (despite it preventing >$100 in equivalent labour) as they will assume that it is one of many necessary other integrations. Adjusting price down would bring in many more customers, but they would arguably not be 'ideal' customers (less of a problem since this is a subscription pay-in-advance system, though).

- I like the clear simple copy (a neat springboard for target audience to think 'this will save me so much effort'). I suppose some people would argue that you should go harder on the 'This will save you lots of employee time and prevent catastrophes' message.

- Far more transparency please - Website sparse on details (inc. privacy, data storage). You can't really onboard EU customers until then.

- Upcoming integrations with Xero, MYOB et al?

Great entry point into what can evolve into an 'IFTTT-v2' business routing system. If you're getting <0.1% false negatives then well done, you're onto something.