Don't forget, AI is slow and expensive! I have to withhold the specifics, but we recently built an application that processes text documents of many different shapes and sizes. It identifies, normalizes, and stores a certain category of information so that it can be used in real-time applications. We started by writing an old fashioned application that could handle the most common shapes and sizes. It's extremely fast and it runs on very cheap infrastructure. There's basically zero incremental cost to process a thousand more documents. For the long tail of documents our old school application can't handle, we've engineered prompts for an LLM that allow it to identify and extract the same data reliably. Whereas our old school application processes a document in under 10ms, the LLM is likely to take half a second. The LLM's incremental cost per document can be a whole penny in some cases, which is a lot! And plus there are rate limits; we have to feed the LLM on a schedule to make sure we don't get shut down. Moral of the story: AI is an order of magnitude slower and more expensive than a regular-ass program. So if you CAN do something the old fashioned way, you SHOULD. And AI will help you write the code for that anyway ;-)
I would also add that in 2024 studies the vast majority of AI implementations fail, According to Gartner, 85% of all AI models/projects fail because of poor data quality or little to no relevant data. I would also stress, having spent a year on an AI project, that some enterprises have unrealistic expectations of what AI can deliver. https://www.river-road-consulting.com/the-shiny-object-syndrome
Co-Founder of Altrosyn and DIrector at CDTECH | Inventor | Manufacturer
1dIt's definitely a balancing act figuring out when traditional methods shine and when LLMs offer unique value. The cost-performance tradeoff you describe is something many of us grapple with, especially when dealing with large document volumes. What strategies have you found most effective for prioritizing which documents get processed by the LLM versus your efficient custom application?