Category Archives: AI

“The Suite Was Supposed to Settle Everything.”

This is a requested response to Paul Marty’s inquiry: Is Source-to-Pay Dying.

We’ve heard the “one app to rule them all myth” since the late 60s when IBM said the MRP would control the operations and no other app would be needed. This was rekindled in the mid 80s when Oracle said the ERP would control the organization and no other app would be needed. Then in the late 90s when the web would provide a common interface to everything. Then the late noughts / early tens when the Suite would solve everything. It’s the myth that keeps on giving.

The reality is that any new monolith application model only solves all the problems that came before, not the problems you have now, and not the problems that are coming.

That doesn’t mean suites don’t have value, or that suites won’t provide more value than any other alternative, just that it’s not a panacea. Determining whether it provides more or less value requires understanding the true total value realized (taking all costs and benefits into account) compared to the true total value of the alternatives, many of which are unproven.

“Is The Economic Value Moving Somewhere Else?”

First off, let us note that, fundamentally, the new AI orchestration craze is no different, as it ultimately depends on a protocol that can bind everything together. This isn’t new either. Remember CORBA? Probably not, as most of you probably don’t even know what it is. Look it up. At the dawn of the dot com era, it was going to solve everything. It made all the same promises MCP is making now.

The reality is that the fundamental truths of technology have not changed.

> If it sounds too good to be true, it is.

> Technology can’t advance any faster than discovery (either mathematical computing theory or practical scientific discoveries that allow for new engineering that can build better machines to support better models), and that has, and will, always be slow. How many hundreds of thousands (or millions of years) has it taken us to compute a theoretical warp bubble, and how many decades/centuries more before we can achieve it? (We’ve went from conjecture with the introduction of Star Trek 60 years ago to theoretical possibility 5 years ago … but now we need to create the energy source, the materials that could withstand it, etc. etc. etc.)

> … businesses not only need to make money every year, but are punished by the capitalistic economy if they don’t; so even if all they have is the same old sh!t, they still need to sell it, and the best way to do that is to slap a new coat of paint on the old Mustang and tell you it’s a brand new model (even though the engine hasn’t changed in almost a decade)

This doesn’t mean that AI orchestration doesn’t provide value, just that it’s not the ultimate answer and that you have to truly understand it’s true cost vs its true benefits and, where autonomy is granted, true risks before you can make a decision.

“What if the employee does not need to enter the procurement system at all?”

That doesn’t change the fact you still need a procurement system.

Just because an intake layer can work across applications, and just because an AI agent can complete a routine workflow without ever displaying the myriad of screens suite vendors spent years (if not decades) refining, that doesn’t mean that the core functions go away. Either those have to be part of the intake/orchestration system (in which case it’s really a suite with a new kind of interface) or you still need the underlying best-of-breed / suite systems, which are only accessed through their APIs.

In the latter case, the true economic value remains in the best-of-breed/core systems … and the only value of the intake/orchestration/AI agent is the cost of user time reduction (i.e. 5 FT AP agents to manually process all the invoices vs 1 FT AP agent to manually deal with the exceptions). So if the cost of the software is greater than the manpower saved, it’s negative value.

This assumes that the agent is deterministic and will do all processing according to user defined rules and in user defined bounds. If you are using LLM-powered agents and giving them autonomy, there is no guarantee they will follow all rules and stay without bounds — autonomy means that they can decide only 10K over their approval limit is ok because it appears to be a known supplier, onboard an uncertified supplier, issue a new PO to a supplier who is late on other critical deliveries, etc. which can result in significant losses.

Which brings us to the most important question:

“ONE INTERFACE > MANY SYSTEMS > WHO DECIDES?”

This is a key question for multiple reasons:

1) You can’t cost / benefit a system without knowing.

As above, if the decision is ultimately human, you can accurately cost the system and determine it’s fixed (workforce reduction) benefit as well as it’s expected benefits from (weighted) average results and track true benefits over time.

But if the decision is ultimately the system, you can’t truly estimate the benefits as you don’t know what it will do, how many mistakes it will make, and what the cost to clean them up will be — and if it uses LLM technology, you can’t even cost the system as you don’t know how the token/compute cost is going to increase over time as you don’t know the token growth that will be required or how soon you’re going to have to pay true compute costs (the big AI companies can’t keep losing $4 for every $1 of revenue, and with today’s energy and water costs, the true compute cost is about 5X what most of the players are charging … and this will only increase over time.)

2) You can’t quality control without absolutely knowing who decides what, what the range of options are, where, and how to encode the checks.

Which means that:

“THE CENTRAL QUESTION … IS WHO OWNS THE REASONING THAT DETERMINES WHAT PROCUREMENT SHOULD DO”

Especially when the answer to:

“Are Twenty Agents Really Twenty Opinions?”

is NO!

I know Jon W. Hansen might disagree with me here, since he uses multiple systems to arrive at his (starting) algorithmic analysis of the marketplace regularly, but agents reason off of the data they are given.

When you interconnect them, they share “data” and “reasoning” continuously. Also, even though they are ultimately sophisticated probabilistic models no human can fully understand, the core is similar to deep multi-level feedback neural networks. This means that common “data” and “reasoning” increases the weighting on that “data” and “reasoning”, increases similar output, which increases similar input to the minority models, which causes that “data” and “reasoning” to become more heavily weighted in them. Or, in simple terms, a majority of agents will bully the minority of agents into their viewpoint until there is one opinion, not twenty.

Even if all 20 agents start out different, as they share “data” and “reasoning”, there will be some commonality, and as the “data” and “reasoning” flows back and forth, the weighting of the commonality will increase until it snowballs into a majority, given enough exchanges (over time).

While some “experts” will try to tell you this all but certainly guarantees you will get the best results once the agents agree, that is ONLY true if the common “data” and “reasoning” is accurate. Some agents will have bad / fake / hallucinated (wrong) data and others will share faulty “reasoning” because they don’t actually reason. (They predict arguments … think of them as a super powerful fancy version of next word suggestion on your iPhone, except they are predicting answers to questions and sometimes even the steps involved to get there!)

While individual agents sometimes work well if they have enough raw question/answer input/output previous step/next step data top work from (and that’s how they create mathematical “proofs” — they can scan millions of research papers and proofs, build up all the associations as input/output pairs, and then see if there is a way to chain them all together from a question to an answer where the output of one step in one paper is the required input of a step in a paper in another paper, possibly published in an unrelated journal in an unrelated discipline), they sometimes don’t work very well at all!

They’ll tell you to eat one rock a day. Or that strawberry only has 2 rs. Or, because they don’t understand reality, when asked, they will tell you that “the woodchuck could carry 57,600 pounds of wood in a day” when asked “How much wood could a woodchuck chuck if the woodchuck was 10 lbs?” (I didn’t make this up, DeepSeek did!) (And, even worse, it gave some extremely ridiculous “reasoning” to back it up which might fool someone who didn’t think twice because the logic was pretty good, while the data it worked on was ridiculous [and obviously hallucinated]. I should also point out that this was a result “I” totally expected because there shouldn’t be much “data” on “how much wood a wouldchuck could chuck if a woodchuck could chuck wood” on the internet [which is it’s training data], because we all know a woodchuck can’t chuck wood but the AI doesn’t know that.)

Thus, whether you use one agent or twenty, you will get one opinion, and one result, which could be a total hallucination if none of the systems had enough correct “data” and examples to “reason” on.

Given that, as Paul Martyn points out, the best decisions are made when there is

  1. A diversity of experiences and information to draw on
  2. Independent thought by the participants (that can provide truly different views to the ultimate decision owner)
  3. Decentralization of knowledge for risk mitigation

and that today’s AI, which is NOT intelligent, cannot be trusted to always make the best decision as

  1. all agent systems have access to the same data on your network and the web
  2. agents cannot think, only produce “outputs” based on different weightings of “inputs”
  3. agents with minority data/reasoning can, and will, have at least their reasoning, if not their data, overwritten by the majority

This brings us to the following conclusions:

1. Traditional Suite and BoB solutions ARE still needed, even with orchestration and agents (especially since the later should be restricted to either fully deterministic processes or processes where the cost to fix/clean up after an occasional bad decision by software is less than the cost of having a team of people do that process manually)

2. The New Hotness Hype will always take sales away from established players, as the lazy and greedy look for that panacea solution that does not, and cannot exist … but when those solutions fail to achieve the result, some of those sales will return (as the only other option will be to build the missing parts into the acquired system, and why waste money trying to extend a system that’s fundamentally broken?)

3. “The Market is Not Dying”, as Paul Martyn states, but it is shifting. Suites will become the transaction engines and systems of record in organizations that experiment with new interfaces, orchestration, and AI agents. Hybrid suites, which embed orchestration and intake, will take over in organizations that want modern connectivity and interface but want to limit the number of vendors they need to deal with. And traditional suites will gain traction in highly regulated industries and governments where everything has to be 100% predictable and in-line with thousands (if not millions) of pages of policy regulations!

As Jason Busch likes to say, “many things can be true at once” and as long as those things are not mutually exclusive, they will be in the market.

(P.S. Thanks for taking up my day with no warning, Paul!)

If You Can’t Do The Job Without Tech …

Then you can’t do the job with tech.

I’ve said it before and I’ll say it again. If you can’t do the job without tech, then you can’t do the job with tech.

All tech does is automate tasks and workflow processes and allow you to speed them up by a factor of 10 to 1,000,000 plus (depending on the tasks and workflow processes).

It doesn’t make tasks or processes better or worse (unless you Gen-AI, which typically makes it worse) — just faster (unless, of course, you change the process when you implement the tech and make the task or process better or worse).

Now, you’re probably asking why it’s not enough to design the process and simply install the tech. That’s because there’s a difference between designing a process and executing a process. Anyone can design a process at a high level given a highly set of requirements. Not anyone can execute. Among those, even less can execute it effectively.

Only those who can execute it effectively are fit to do the job, regardless of what tech the organization has or does not have. That’s because, if you don’t know how to do the job without tech (and certainly without AI), you don’t understand what the job really is. Business was conducted for thousands of years without modern tech, and computers only became generally available in big business in the 80s and mid-size businesses in the 90s and small businesses in the 2000s. That means everything you do today with modern tech was once done without modern tech (and, 150 years ago, without any tech that we would consider modern at all).

That understanding means you understand the core of the function. You know what has to be done, how, where the time suck is, what can be automated, how, and why. You also know how to verify correct automations has been implemented, and where the results require human interpretation, review, and decisions — and, if necessary, make those interpretations, review, and decisions.

Without that understanding, you can’t properly make use of tech and you definitely can’t make use of AI. Sure some tasks might be 10 to 1,000,000 times slower (and sourcing optimization will be out of the question, just a few bid comparisons), and you shouldn’t do them by hand unless necessary, but the point is you need to be able to — otherwise, you can never judge what the system does. Iin the age of hyper-fast LLM hallucinations, only good human decisions will allow your organization to succeed.

The Procurement Knowledge Devolution

The internet was supposed to kick off the procurement knowledge revolution, allowing Procurement pros to quickly:

  • find out about best practices
  • get commodity and market pricing for products and services
  • build reasonable (should) cost models
  • find out about new suppliers, carriers, and consulting partners
  • research new products and services
  • hold truly global sourcing and procurement events in real time
  • effectively communicate with, manage, and develop suppliers
  • etc.

For twenty years, that’s what it was. Procurement departments who learned how to use the internet properly for research, deployed the right SaaS to support their processes, and identified the right data for their processes were successful in their endeavours.

But then came Gen-AI LLMs, chatbots were replaced with chat, j’ai pété‘s and clod‘s, and knowledge was replaced with whatever content the LLM generated. Maybe it was correct, maybe it was mostly correct, and maybe it was a 100% fabrication — a hallucination if you please. The problem with LLMs is that they are NOT intelligent. They are essentially super sophisticated multi-level cross-connected deep neural nets that go beyond classification to generation of responses built up from sub-responses built up from deep training on incredibly large data sets.

Therein lies all of the problems. It generates built on random probabilities. Those are dependent on what’s in the training data set, what questions were asked, what results are reinforced, and how it’s used. If the training data is bad and full of bad data and falsehoods, the chances of incorrect, and even dangerous, responses being generated are quite high. If the training was biased, the output is likely to be very biased. And if it’s not “trained to please”, the models are fundamentally designed to “learn to please”, so if computations that are a complete lie will increase utilization of, and faith in the model, that’s what will happen.

Moreover, every vendor is now believing the hype from the big LLM players, treating the technology as real Artificial Intelligence (when it should be called Artificial Idiocy), and trying to plug it in everywhere … promising that it will provide their clients with true natural language interfaces, agentic tech, and even BS AI Employees. Those who are adopting it are literally getting dumber by the day. Not only has the cognitive impairment, atrophy, and potential long-term decline from regular use been well documented, but the failure rate has been well documented as well with MIT and McKinsey studies demonstrating success rates of 5% and 6% successfully. Most pilots are being abandoned, sometimes before they even begin, because the tech isn’t even good enough to put into employee’s hands for the tasks the overpriced Big X consultancies claimed the LLMs would be perfect for.

Furthermore, even when organizations are smart enough to ignore Gen-AI, over-automating using the most advanced last-gen (A)RPA and AI technologies will still give Procurement teams a false sense of security and, due to their very low error rate, as time goes on, the team’s skills will go rusty and their ability to deal with true exceptions quickly disappear, especially as the old Pros (get forced to early) retire and the younglings have never dealt with exceptional situations.

The age of AI hype has ushered in a knowledge devolution faster than any age that has come before.

I hope the profession can survive it!

Why it’s just easier to do your job in the Age of AI

Every year articles make the rounds on how to do nothing at work or look busy to either slack off or keep your annoying cow-orkers away so you don’t end up having to do their work too. Now, a few in 2006 really annoyed me and I decided to point out how stupid they all were by selecting one in particular and pointing out just how stupid it was because it was harder and more work to follow the advice then to just do your job for your 35 hours a week you had to work.

But I’m not here to tackle another inane article about how to slack off or avoid responsibility, because hopefully by now you’re not dumb enough not to fall for it, especially since smart managers (and workforce monitoring solutions) aren’t either.

I’m here to tell you why it’s just easier to do your job in the age of AI than to try to use AI to do it for you.

1. You’ll have to tell the AI what you want at least 3 times. Maybe 10. Or More.

Gen-AI LLMs should be called Artificial Idiocy. There’s nothing intelligent about them. They don’t understand anything. It’s all a Grand Illusion. Automated puppet-theatre … and we’re the suckers born every minute for using it.

As a result, they produce a lot of good sounding text that sounds close to what you need, but upon further review, always misses one or more key points of your request … until you repeat it and rephrase it ten times ten different ways and your strive to perfection slowly reduces to anything acceptable whatsoever.

2. You’ll still have to edit the final outputs and execute the work in the tools it can’t drive because they don’t have the APIs for the LLM to execute.

So, after spending hours trying to get it to output the perfect report and process, you have to go edit, finish, and execute that process. Spending as much time as if you just skipped the AI in the first place.

3. You have to deal with the consequences of the errors you miss.

If you’re using a modern Procurement system which is AI-first and allows external AI to drive it, a request to “restock the supply room at the lowest cost” can result in ten times the amount of printer ink, paper, pens, and cleaning solvent you go through in a year because it hit a volume break at the production plant and skipped the intermediate supplier, ignoring the fact that you have to rent a warehouse for the truckloads of cleaning solvent you just ordered for your office building (even though you only use one floor — it assumed you wanted enough for the twenty story office building).

You’ve spent too much, have no room for the inventory, and have to explain to your boss why ordering years worth of office supplies was a good idea.

4. You have to explain the AI bill that was five fold what you planned.

While also explaining that it was your idea, not the AI’s, to screw everything up.

It’s always easier, and less risky, to use your Human Intelligence, and not the AI, to get your job done.

… so What’s the Real Future for Procurement Tech?

Yesterday we pointed out that SOFIA Killed BOB and Replaced POE with a Black Box Agent, which forces us to ask what’s the real future for Procurement Tech?

As we noted in our last post, twenty (20) years ago the debate was BOB (Best-of-Breed) vs POE (Platform Oriented Enterprise — a [mini] Suite solution).

It was a real debate — best-of-breed modules gave you what you wanted and delivered value, but a slew of disconnected modules is not very productive. (Mini) Suites solved the dis-connectivity problem, but came with their own problems. Given that most were quickly built out on top of one or two core modules, and modules beyond those were barely MVP (that even startups would be shy releasing), you were sometimes lucky to get the 60% to 80% functionality the vendor promised.

SOFIA ((Solution Orchestration Framework Integration Architecture) was supposed to end the debate. Real orchestration solutions that would allow organizations to BYO-BOB (bring-your-own-best-of-breed) for any and all modules they wanted to construct their ProcureTech (and, hopefully, SupplyTech) platforms, but fell short. Part of the reason is that they started as intake to make the big suites usable, and didn’t start building a true, native, orchestration architecture — making it difficult for them to quickly and easily orchestrate the plethora of platforms that customers throw at them. The other part of the problem is that the majority of (classic) SaaS platforms weren’t built to be orchestrated, and, frankly, can’t be.

And using AI-first tools to quickly vibe-code the most common MVP modules customers want that can be “orchestrated out of the box”, doesn’t solve the problem. It just devolves the solution into a classic POE solution (but with less security — one of the big flaws of vibe coding). So SOFIA isn’t solving anything either.

Now, if you ask GAIN, the future is “AI Employees” (which aren’t real). Like any LLM-based solution, they will work great until a Grade A Hallucination results in buying millions of dollars of the wrong product, selecting a sanctioned supplier, or sending money to a dark-web criminal organization. Then it won’t. (At first, it will just order 3,000 pairs of gloves for an automated cafe for a lone worker, because it’s cheaper. LLM-based AI has already done that. Look it up.)

Probabilistic AI (where hallucinations are a core function that CANNOT be trained out) is not the answer and should never be used for more than suggestions.

So what is?

An enterprise SaaS platform rebuilt on a proper intake and orchestration platform (that supports rules-based agentic automation, i.e. [A]RPA) that was originally built to be domain independent and just solve the data and workflow integration challenges. In other words, if Coupa rebuilt on Tonkean (which won’t happen for so many reasons), that could be close to the answer. Zip and Oro were built too quick or too focussed to be the answer. It will be true orchestration platforms you don’t yet know that get acquired by tier-2 suite players with a lot of tech debt that rebuild on those orchestration platforms (that also built native intake) which can seamlessly integrate with next-gen SaaS platforms with secure, full, open APIs that allow for full data push and pull and programmatic function and workflow execution.

In other words, it will be domain specific SOFIAs. Not POE (which is too limited) and not Fake AI Employees.

The question is, who will create theirs first?