Category Archives: rants

How AI Enhances 10 Common Procurement Challenges Part II

A recent CIO article drew my ire because it claimed that AI Overcomes 10 Common Procurement Challenges as it oversimplified the problems and overstated the benefits of AI. Let’s finish them one-by-one.

Legacy Systems Complicate the Adoption of New Technology: The article claims AI streamlines integration by assessing system compatibility, automating migration, and reducing downtime. While two out of three ain’t bad, it ain’t good when the critical requirement of assessing system compatibility cannot be met by AI — since simple text matching isn’t helpful if the interface of a legacy system isn’t specified in a standard format (as otherwise it’s essentially field-name matching, which is no different than human guesswork). The reality is that humans still have to define/verify the mappings before the AI can take over.

Letting AI do the mappings is fraught with errors. And its even worse when you let it automatically connect systems, pull and push data, replicate incorrectly mapped and bad data across systems, and “fix” data that was actually correct on system integration because the “bad” data in one system is used to overwrite the good data in another system just because it appeared to be more recent. Because it’s automated, AI can propagate and exacerbate errors at an unprecedented rate and in a matter of seconds make a mess that can take months to repair.

Managing Supplier Risks is a Growing Concern: AI can continuously monitor supplier performance, predict risks, and ensure compliance. This is one situation where they were almost perfectly correct, but, when they say vendor evaluation can be time intensive and imply that AI can speed it up, they overlook the fact that evaluations still have to be done by humans and tech can’t speed that up.

Moreover, if you think you can augment your data with third party data to speed up the evaluations, you’re just fooling yourself. You just make bad decisions faster.

Manual Procurement Process Drain Resources: AI can definitely automate repetitive tasks, reduce human error, increase efficiency, and free your team to focus on strategic initiatives, but only for tasks that are well defined, typically free from exception, and capable of being processed by standard rules. However, this can’t be done until the repetitive tasks are identified, processing rules defined, standard exceptions identified, and additional rules defined. Only then can the AI automate enough to be useful.

Moreover, using a next-gen LLM with chain-of-compute to try to break the requirements of a task down into subtasks, execute those subtasks automatically, and automate a process without any human intervention is just as likely to go wrong as it is to go right.

Demand Forecasting is Often Inaccurate : AI can improve demand forecasting, but only if you have the right data — it’s not a magic box, just a black box that you need to understand.

It’s not just demand trend based on utilization / point of sale data, its also market conditions which can sharply change a demand curve overnight … traditional curve fitting / machine learning that most “AI” is based on cannot detect a change in market conditions or a political situation that can cause a rapid change in demand.

Procurement Remains Transactional Rather Than Strategic: AI DOES NOT transform procurement into a strategic function that optimizes spend, improves supplier collaboration, and aligns purchasing decisions with your business! Only people-powered Human Intelligence (HI!) can do that. Remember — transforming Procurement requires defining a strategy, defining appropriate processes, identifying the right people to transform it, and then, and only then, identifying the right technologies.

Assuming that you can slap in AI and transform a tactical function into a strategic one is worse than a pipe dream, it’s a recipe for disaster. Running fast and hard doesn’t get you any closer to the finish line if it’s not in the right direction. For more details, see the dozens of posts about AI in the archives.

Again, we’re not saying that AI is bad. Technology is neither good nor bad. But, like any technology, it has to be ready for prime time, correctly identified, correctly implemented, and correctly used — and that requires a lot of Human Intelligence (HI!) and planning, and the right processes put in place. Shoving it in and expecting a miracle is dangerous. And this is yet another article that implies you can just shove it in and get results. And you can’t. Especially if it’s the wrong technology, which can enhance your problem instead of shrinking it. That’s the problem. This article, like many others, doesn’t tell you about the dangers and downfalls and what you have to do to avoid them.

How AI Enhances 10 Common Procurement Challenges Part I

A recent CIO article drew my ire because it claimed that AI Overcomes 10 Common Procurement Challenges as it oversimplified the problems and overstated the benefits of AI. Let’s take them one-by-one.

Procurement Takes Too Long, Slowing Innovation: According to the article, AI-driven platforms can generate RFPs, accelerate sourcing, automate approvals, and reduce cycle times … which is mostly true. Properly applied, AI can accelerate sourcing, reduce cycle times, and automate approvals … but not all approvals. As for RFP generation, that’s very limited — LLMs can generate RFPs with a simple prompt, but not necessarily a good RFP. The best RFPs are designed by humans (and then automation, which may or may not use AI, can pull in data from supporting documents as needed), and as for acceleration, it depends on the project — it can’t speed up supplier qualification where humans need to inspect the products and verify the requirements.

Moreover, a rush to AI can make things worse, and not better. Letting AI generate an RFP that misses a key requirement in terms of required certifications, performance criteria, production capacity, etc. can entirely invalidate an RFP process and lead to months of wasted effort if no human realizes that this key requirement was missed until an award is offered and a request for the certification, capacity, etc. is delivered and a “sorry, we don’t have / can’t do that” is returned.

Legal and Budget Complexities Create Bottlenecks: Budget tracking systems and rules-based automation allows for instantaneous budgetary approvals. Contract negotiation software can automate redlining, compliance checks, etc., but cannot handle a complex negotiation for a complex project where each side has a lot of requirements and multiple parties to satisfy. AI speeds up the technical drudgery, but not the human interaction.

Moreover, if you turn over negotiations to software, you have no idea what the end result will be. If you let it negotiate based on market data, and the cost data is off, you could be committing to a bad deal. If you let it predict timeframes based on how it expects prices to rise/stay high, but it’s off by two years, it could lock you into a three year deal when you only need a one year deal. And so on.

CIOs Need to Upskill Their Teams in AI and Cybersecurity: Just because “AI” can simplify processes with guided intelligence, that doesn’t mean the team is upskilled in the process. The reality is, there is no incentive for users to learn anything if they think the system will guide them in everything they need to do.

Thus, if you over invest in AI, especially the kind that guides users in every task they have to do, and works quite well on the basic tasks they have to do daily, and doesn’t screw up the first half dozen or so moderately complex tasks, the user will believe the system is almost flawless, start to trust it implicitly, stop questioning it as time goes on, start believing there is no need to learn anything else because the system knows it, and, over time, stop thinking. And then, instead of performance improving, it will decline … and that decline might be accompanied by a major financial loss if a bad contract is signed or major risk ignored.

Data Inaccuracy Leads to Poor Procurement Decisions: While it’s true that over three quarters of organizations struggle with unreliable data, AI doesn’t magically fix the problem. It can help with cleansing, validation, and procurement trend analysis, but ask any spend analysis vendor who has tried to apply an LLM to unclassified vendors about the classification accuracy (which tends to top out around 70%) — good data still requires manual cleansing and classification, especially where the system reports good confidence. It can definitely help, but it doesn’t take the onus off of the human.

In other words, if you believe that you can plug in a magic AI black box ad that it will fix your data, you are gravely mistaken. Sure it will tell you that it has cleansed, classified, and validated all of your data, but if it’s only 70% accurate, it’s only made matters worse if you trust the data 100% and don’t know what 30% is inaccurate. When you base your decisions on data, and the data is bad, you are bound to make a bad decision. The question is, how bad. You don’t know. And that’s a big problem!

B2B Software Selection is Increasingly Complex: Moreover, despite the claims, AI-powered vendor analysis doesn’t really help that much — see Pierre Mitchell’s crazy conversations with DeepSeek-Rq. Note how it not only recommends inappropriate vendors, but also recommends vendors that don’t even exist anymore … it can help you discover potential vendors, but you still need human reviews and deep pricing intelligence (from expert SaaS optimizers).

Trusting AI to select your software is worse than trusting an analyst firm map! And we know all of the problems those maps contain. (First of all, they only mention the same 10 to 20 vendors year after year, ignoring the dozens of other vendors that might be more appropriate for you.) AI cannot understand your needs, cannot truly map needs to requirements, cannot truly map requirements to features, and cannot truly assess how relevant a solution is, and definitely can’t assess how well a provider’s culture will match yours.

Come back Thursday for Part II!

We Finally Know the Source of the AI Buzzword Bullsh!t!

The Agentic Software Service Hyper Optimized Learning Engine custom built for drowning the World Wide Web in soundbite and buzzword marketing bullsh!t centered on AI, or the A.S.S.H.O.L.E. for short! (With fervent thanks to the esteemed Arthur Mesher for delving deep into the depths to uncover the source of this madness!)

Technology Project Failure is at an all-time high, boosted by the recent AI failure rates (which are on the rise as almost half of AI initiatives are being scrapped in process, see CIO Dive), and while the hype should be subsiding (and shifting to the next hype cycle), it’s now hitting us harder and faster in what should be its death throes than any hype cycle that has come before.

The AI marketing onslaught is coming so hard and fast that it’s impossible to imagine how so much new soundbite, buzzword, FOMO, and FUD content can be produced so fast and so overwhelming to the point that it seems humanly impossible. And that’s because it is. It’s not coming from humans, it’s coming from the A.S.S.H.O.L.E.. As we have indicated in our previous posts on Gen-AI LLMs, one of the valid uses for Gen-AI is mass content digestion, search, summarization, and generation.

It appears that one of these systems was customized to ingest all of the initial human-generated AI BS and trained to spew out marketing soundbites, social media posts, articles, and other forms of web content ad nauseum and to continually ingest new content on the subject to create even more content, including AI-generated BS content from other AI systems that tried to copy the original A.S.S.H.O.L.E..

And even though it doesn’t matter, since apparently every LLM can be trained to emulate the original, the only question that remains is, who currently owns the source engine, what LLM was it originally built on, and what LLM is it running on now? This is obviously the industry’s best kept secret. I hope someone who has gotten to the bottom of this will let us know the full story of the A.S.S.H.O.L.E.. Considering the intellectual and financial pain and suffering it has caused, we deserve to know the truth!

For those interested, since I’m sure LinkedIn will disappear Art’s post if it hasn’t already, here’s the original. (And the Gartner rant ain’t half bad either!)

CLM is Dead! Long Live CLM!

Last month THE PROPHET ran a RIP post for CLM over on LinkedIn where he heralded the demise of CLM.

Which is coming fast and furious for CLM 1.0 and CLM 2.0 because, as we’ve said before, most current CLM solutions are nothing more than a glorified document repository / barebones CMS with a bit of linguistic rebranding, a few customized meta-data fields, maybe a bit of versioning support, and if you’re super lucky, some integrated e-Signature support.

As for the prophet’s suggestions, most of them won’t happen.

CLM absorbed into I2O?

Considering most I2O (Intake to Orchestrate) players still haven’t absorbed a fleshed out working Source to Pay model … not likely.

CLM goes vertical?

The whole point of CLM is horizontal — to get a grip on all of your contracts, not just a subset of them!

Agentic Solutions?

I like my contracts the way I like my maps: ACCURATE!

The best “AI” can do is enhance the productivity you get from a (very) small legal team … it CAN NOT replace it!

GPOs?

Standard terms around pricing DOES NOT satisfy geographic requirements which vary on levels of regulation, compliance, etc.

Clause based?

Ask Icertis and especially Exari how well that worked out for them …

Every other suggestion

Maybe … but all of this is trickier than THE PROPHET lets on!

The reason that CLM doesn’t work, as we noted above, is that the majority of “CLM” solutions on the market are NOT CLM at all. They are glorified repositories with some authoring and e-Signature support … not at all what an organization needs.

An organization needs “lifecycle” management. That’s a heck of a lot more than just drafting, redlining, signing, and sticking in a repository. That’s because contract “lifecycle” management really starts when the contract is signed (whereas most platforms seem to think it ends when the contract is signed).

It’s about automatically extracting the obligations, indexing them, assigning them, tracking them, and making sure they get done.

It’s about extracting the milestones and deliverables, as well as those obligations, and wrapping them in a project plan, assigning the resources, assigning the supervisory chain, tracking them, making sure they get done, and making sure all requirements are met.

It’s about extracting the SKUS, price tables, rate cards, and pushing them into the Procurement systems to allow those systems to perform the right m-way matches and make sure nothing is paid out that wasn’t agreed to. It’s about pulling in the paid invoices for tracking purposes and allowing the contract/relationship managers to track total contract fulfillment.

It’s about ensuring that the right parties are notified when a contract is coming up for renewal, have all the information necessary to make the decision on termination, renegotiation, or allow an evergreen renewal.

And about a whole lot more where VALUE is concerned. Just check out what The Maverick has to say over on Spend Matters.

Why Are You Still Buying That Fancy New Piece of Software That

  • Could Get You Sued?
  • Increases The Chance You Will Be Hacked!
  • Could Result in a 100 Million Processing Error?
  • Could Shut Down Your Organization’s Systems for Days!
  • Helps Your Employees Commit Fraud?

If someone told you this when evaluating a piece of software, and asked if you wanted to buy it, I’m sure the vast majority of you would say HELL NO!

In which case I want you to please tell me, why are you all still riding the AI Hype Train, Buying, and Using Gen-AI everywhere?

It has already resulted in lawsuits and losses!
The Air Canada lawsuit over the Gen-AI chatbot is just one notable well publicized example.

AI systems are AI coded, and AI code has a much greater security risk
as it generates code using training repositories that contain large amounts of untested, unverified, and high risk code — generating code so full of security holes it’s a hacker’s dream! (See this great piece on the ACM on The Drunken Plagiarists.)

AI systems negotiate on the data they have
and with a single decimal point error and you could be paying 10X what you need to. Not to mention, they don’t always translate right. Remember, the Experimental AI DOGE used claimed an 8 Billion savings on an 8 Million contract!

Bad data generated by an AI system and fed into a legacy system with poor data validity checks can shut it down.
Plus, Gen-AI can also push out bad updates faster than any human can and you can easily have your own Crosslake situation!

Now it’s being used by employees to generate fake receipts
that look so real that, if the employee does a few seconds of research (to get the restaurant info, current menu prices, tax code, etc.), you can’t distinguish the generated image from the real thing. And, before you say “Ramp solves this”, well, it only does if the employee is lazy (which, let’s face it, is human nature, so you’ll catch about 90% of it). But what happens when a user strips the meta data which, FYI, can be as easy as taking a picture of the picture … oops! (And if you’re a hacker, running it through a meta data stripper/replacement routine is even easier as you’re just hotkeying a background task.)

AI is good. Gen-AI has its [limited] uses. But unrestricted and unhinged mass adoption of untested, unverified AI for inappropriate uses is bad. So why do you keep doing it?

Especially since it’s now proven it’s worse for you than some illegal drugs! (Source)