Category Archives: Procurement Innovation

The King is Dead. Long Live the King!

Learn the phrase, because you will soon be living it in every aspect of your life — it’s not only the new fashion in western politics, but the new fashion in enterprise tech tripling down on the AI hype when the big AI vendors are losing money faster than ever before (as compute costs skyrocket, competition heats up, and a lot of people are getting fed up with a total lack of return on their investments)!

However, in the meantime, as the hype wave makes it way though the mass market, a slew of startups emerge building on LLMs and fake AGI offerings, and the marketing mania takes over, expect the e-Procurement is Dead, Sourcing is Dead, and Contract Management is Dead rhetoric to hit all time highs as these new players cr@p their new apps as fast as they can, with new — natural language centric — interfaces, more automation, and instant gratification. (At least when these apps work as desired.)

As these offerings get adopted at a rapid pace in organizations who are just adopting modern solutions (which make up half of the space, or more), replace first generation apps from the noughts in organizations who decided that anti-complex is the way to go, and start to get noticed, the rhetoric picks up the pace and echos.

But that’s all it is — rhetoric amplified through a microphone. Sourcing, Procurement, and Contract Management are not dead, the fundamental requirements are not changing, and these systems are not being adopted en-masse. Not just because they don’t always work very well, but because they don’t fit. (And even when they do, they are just replacing one interface with another.)

First of all, in the public sector, you have to follow rules and frameworks even for tail spend. These systems have no guardrails, and by their very nature can’t guarantee the rules will always be followed. So these systems can’t be adopted.

Secondly, in many large private organizations, very large investments have been made in big suite models (which still have long term subscriptions in place), so unless the new AI solution enables functionality (regardless of interface) that does not exist in the current platform, or allows for a considerable number of seat-based licenses to be dropped on renewal (for a similar or less number in the new, cheaper and more functional, app), it’s not even going to be considered. Even if buyers get blinded by the hype because the CFO is going to say no.

But yes, some organizations will be in a position to adopt these systems, echo that SaaS is dead, hail the new Agents / AI as king, and go back to doing the same old thing through a shiny new interface.

So while THE PROPHET might find it fun to pontificate who killed the e-Procurement king, the reality is that no one killed the king, because the king will die a death by a thousand paper cuts, and then his clone will be put on the throne.

Why? Well, using THE PROPHET‘s examples:

  • most intake/orchestration platforms just put lipstick on the pig you are already using (and the pig isn’t very happy about it), and the king you will get is Merkimer’s clone
  • ERP will do what they always do, acquire what their customers are already using (and this time do it in fire sales as investors who paid 10X for suites get desperate for anything back as the growth in these suite companies stalls), and the king you will get is the next CEO, who will be picked to clone the current CEO in form and function
  • people will see through the BS of “concierge AI employees” when they falter on more complex purchases, over spend on basic items, and allow Sony PlayStations to be charged to the snack budget (because the only AI employees that perform are those based in India), and they’ll keep the king they have until he nominates his successor (whom he expects to be just like him)
  • the viper strikes from fed up merchants being overloaded with RFIs and RFQs to quote items in their public catalogs at non-discount volumes will be laced with poison, and the only way the king will survive is to back down …
  • data aggregators and intermediaries will thrive, and they help to select the next king, but they won’t be king

The King is Dead. Long Live the King!

We Need Exact Purchasing … But It’s NOT a New Matrix!

We all know the Kraljic matrix is broken, and that it has been broken for a while. As Jason Busch starts off in his article on how Supply Management Must Become Exact Purchasing, Kraljic was right at the time, but it’s time to come back to where we started. And, more importantly, recognize that the Kraljic Matrix was designed as a starting point for supply management to think critically — and Supply Management was supposed to evolve from there. But it never really did.

Sure we got the Purchasing Chessboard by Kearney to supplement a host of seven step methodologies, procurement game plans, new techniques for managing indirect spend, lean supply management, and a slew of techniques from every niche consultancy to enhance your supply, and category management, strategies, but almost all of these are based on the classic 2 * 2 Kraljic matrix with refinement.

In his post, Jason, who rightfully says that procurement at scale is not one-size-fits-all tells us that answer is Exact Purchasing, or more specifically, The Exact Purchasing Quadrant, where he tries to map cost influence vs contract-and-supply complexity because Kraljic told you what a category is when he mapped profit impact vs. risk / complexity, but he didn’t tell you what to do with it. According to Jason, if you have:

  • low cost influence and low complexity, you transaction capture
  • low cost influence and high complexity, you govern the relationship
  • high cost influence and low complexity, you manage market risk
  • high cost influence and high complexity, you architect the cost

And Jason’s mostly right. Depending on the category in question, you’re generally going to apply one of those approaches.

Jason doesn’t stop there. He tells you that the thread that ties all four of these together is data at the core. And he’s right. Without a data-based (not necessarily database) approach, you’ll never effectively manage, and thus never effectively purchase, a category. Moreover, Jason does a great job at telling you what the core data is, where it resides, and where it could sit in your next generation enterprise Supply Management Solution (SMS). But he falls short when dictates the velocity, because that depends on the criticality. And even worse, the depth of data required depends on the criticality — which can also change the quadrant a category falls in!

For example, while packaging, print & marketing, and NPD are definitely strategic (Kraljic) cost architecture (Busch) categories for some companies (i.e. CPG, Advertising Agencies, and Manufacturers), they are tail-spend for other companies (i.e. Retail Store, Luxury Brands, and a Services Consultancy).

Jason’s improved approach still fails because it suffers from the same fallacy as the original Kraljic matrix — that complexity and risk are a single dimension. They’re not. Complexity is a factor of the product or service that you design and is an internal dimension that you have complete control over. Risk is a factor of the external environment that impacts your ability to create and deliver the product or service and depends on the financial stability of your supplier, the geopolitical situation in which it operates, the trade routes that exist between your supplier and your location, your supplier’s supply chain, and everything else in between — these are all factors you can’t control. Furthermore, it’s not profit impact (Kraljic) [which is short term] or cost influence (Busch) [which depends on spend], but criticality, which is measured in value impact [and what happens if the buy is unprofitable, of poor quality, or unavailable]. A category with zero savings potential can risk a 100M product line if your products can’t be completed without it (and we’ve seen this many times over the last two decades as critical sensors or single-sourced components shut down automotive lines or lack of RAM [from the decennial plant fires] or custom control chips [from trade slow-downs or insufficient production] greatly impacted personal computer / laptop or game system production — costing major brands hundreds of millions of dollars).

The reality is that Supply Management / Exact Purchasing / Get My Stuff (and Git-r-Done) is NOT a 2 * 2 matrix. It’s a(t least a) 2 * 2 * 2 pocket cube (and a 3 * 3 * 3 cube in large Enterprises) that is different for every organization where you take into account:

  1. complexity – low (med) or high
  2. market risk – low (med) or high
  3. criticality – low (med) or high

And as you progress from the lower left of the cube (where all dimensions are low) to the upper right of the cube (where all dimensions are high), you’re simultaneously following a three-dimensional path down a bi-furcating decision tree that takes you from non-critical items where you are simply managing as transactions to highly strategic items that you are cost architecting to the best of your ability, monitoring at least weekly, and alerting the category manager to on every major market event. In the middle, you will deal with your leverage and bottleneck items using well-timed market events to mitigate risk and managed relationships to ensure smooth supply, with the depth, and velocity, of the data correlated to the criticality of the item to your operation.

You do that, and you’ll finally be on the road to Exact Purchasing.

And I’ll leave it to Jason to work out the details of the starting cubic, as he’s so intent on fixing Purchasing (now that he’s semi-retired and can pontificate on the philosophical of purchasing).

(And once Jason does that, I’ll tell you how execution differs between small, medium, and large enterprises because “strategic” doesn’t mean the same thing at different levels, there is no one-size-fits-all platform, and, after a lack of operational readiness [which THE REVELATOR will happily fill you in on], this is likely the second biggest reason new technology acquisition projects fail in our space.)

Despite what they say, Size Matters! Part II

In Part I, we noted that size really does matter … when you are selecting a ProcureTech or Source to Pay solution, and, in particular, it’s the size of YOUR spend that matters (and not the size of the vendor or even the vendor offering).

We noted that there is no one-size fits all, that the three main tiers of organizations (small, mid-sized, large) have three different needs (which are nuanced, especially in the mid-market as going from small-mid to big-mid can require leaps in complexity), and that you should be paying based upon the tier you need.

But with 3 tiers of solutions out there, the reality is that if you select a bigger solution than you need, you’re going to pay a lot more for a much smaller return. And that’s just NOT good Procurement.

So what should you pay?

It’s all based on your size, maturity, and need. Well, we answered this a bit in the past when we did our series on how much should you outlay for source to pay. (Part 1, Part 2, and Part 3.)

In the series we did in 2023, our answer was 120K to 500K+ (a year), and we were mainly focussed on the mid-mid-market upward. The answer today is similar.

Small Enterprise, < 20M in external spend, 12K to 24K a year. All you need is basic e-Procurement and basic process support. Many shareware suites and low coding platforms will allow you to configure a lot of what you need. At 20M, your full savings potential is 2M or less, and you’re likely to only realize a quarter of that in the first year, or 500K. So spending more than 24K on a license (when you’ll also have implementation and support costs) does not guarantee a worthwhile return.

Medium Enterprise < 500 M in external spend, 60K to 240K a year. You need basic sourcing execution and e-Procurement. A baseline solution does enough at the lower end, and an enhanced solution with deep supplier management, deep P2P+, and some compliance and risk capabilities. Here, the potential savings could be as high as 50M at the high end, or as low as 3M on the low end, with a potential opportunity ranging from 1M to 10M in the first year. At the low end, especially considering the personnel costs, you probably don’t want to pay more than 100K to guarantee a return. At the higher end, you could pay a Million for a small suite and get a return, but considering there’d only be a couple of categories where it would deliver any incremental value, why pay a Million when there are solutions for 250K that deliver the same value for 90%+ of activity. (For the few categories where it’s worth it, just hire a consultant with access to specialized tools!)

Large Enterprise >= 500M in external spend, 480K to 1M+, depending on the particular deep capabilities you need and any specialized modules and support you need. There’ll be more than enough categories to justify the additional spend, and saving an extra 2% on a 50M category will pay for the increased platform cost!

That’s the rule of thumb. Higher or lower depends upon the expected return. This means that before you spend more, you should work out a realistic ROI. If the return isn’t realistically there, you don’t spend more than you need.

Now I know plenty of vendors will disagree with me, but when solutions exist at all tiers that do everything an appropriately sized buying organization will need at the price points above, why pay more? (Even though the ABC suites will tell you that you should!)

Also, please note, these are license costs with basic support only. If you want or need more support or services, expect to pay more. (And do the ROI on the services before you contract them.)

Despite what they say, Size Matters! Part I

Before your mind wanders off in the wrong direction, I’m talking about your manageable external spend size. (Not your company size, or revenue size, but your actual external spend size!)

You see, not every solution fits every company, and it’s not just a matter of company, process, and Procurement Maturity; not just a matter of what is being bought and for what; but a matter of spend size.

Here’s the thing, sourcing strategy depends on three primary factors:

  • the category
  • current market conditions
  • spend size

The third is critical. If you’re only spending 100K, you’re not going to do a multi-stage RFP with multi-objective optimization analyzing multiple factors against multiple award scenarios and spend 10K in personnel time and cloud costs for a 5K savings. If you’re spending 100M, you’re going to do a multi-stage event with deep supplier and product vetting, should and target cost analysis, multi-objective optimization models against multiple potential award scenarios, multi-round negotiation, and so on.

This is very important. If you’re a small mid-market that only spends 20M a year externally, and your largest category is 200K, your sourcing scenarios are going to be pretty simple. Even though those categories are strategic for you, they are not strategic sourcing in the enterprise sense of the word, which is the sense the big suites try to sell you. All you need is an e-Procurement+ solution with simple RFPs for your big categories and RFQs for the rest.

Now, if you’re a mid-mid-market spending 100M a year with categories 1M plus, that’s not enough. You need sourcing support, but it’s not full fledged strategic sourcing as defined by an enterprise suite. It’s sourcing execution. You need some onboarding, some qualification, some multi-round RFP support with feedback, some basic analytics, and some negotiation support. You don’t need deep optimization or a top-of-the-line analytics solution, an end-to-end third party risk management and compliance solution, or extensive integrated contract creation and redlining support — you just need Word document support as you’re redlining in Word.

In other words e-Procurement isn’t enough. You need some supplier management, sourcing, analytics, and contract document management. And it should all be integrated cohesively. But it’s not a suite.

Now, if you’re a large global organization, spending 500M plus with 10M to 100M categories, that’s different. You need broad and deep. Full multi-stage sourcing with auto-RFX generation, scenario support, and sourcing optimization, which needs to be deeply integrated into the deep supplier and third party management module with extensive onboarding, compliance, risk, and performance support; the analytics module that can analyze offers and compare them against historical, project, should, and target cost scenarios; and the contract lifecycle module that manages the full negotiation, indexing, tracking, and execution of the contract.

This is all very relevant because it determines two things

  1. what type of solution you need
  2. how much you should expect to pay

So how much should you pay? Stay tuned.

There is No One Optimal Team Structure for Procurement …

… not even if you get industry and size specific! But first, let’s backup.

Today I’m going to pick on Tom Mills because he’s well followed, a great practitioner, and gets a lot of stuff right (and I mean a lot of stuff right) … including key functions your “optimal” procurement team needs to support. We’re tackling this now because, in addition to prophetic prediction posts which are full of fantasy, the new year also brings the annual posts that tell you what the Procurement function is, what it’s primary tasks are, and what team you need to address it. And even the most well intentioned ones by the smartest consultants and practitioners don’t always get it right — at least to the extent they think they do.

There’s a couple of reasons for this, and they all relate to their Procurement world view which:

  • boils down to their (limited) experience, which is usually with a few companies in a single industry or related industries
  • typically consisted of sourcing primarily one or two of the six major types of Procurement (which are indirect, direct, services, tail, software, and strategic consulting / commissioning projects — all of which need to be approached differently and often need completely different solutions from different providers to tackle)
  • and usually revolved around a small set of systems and software offerings

Now, I’m not saying I can give you a perfect team model for your company, because I can’t. (In fact, without a deep analysis and evaluation of your company, no one can!) Not even if I created a starting one by industry, size, and geography — because every company is different, and those differences will create minor variations in optimal structure — which sometimes comes down to the talent you can get your hands on.

For example, in most companies product management and product marketing is usually two different functions because it’s rare that one person can do both. But someone who could do both would shift the organizational structure because a person who can do both would bring unique value — being able to design product and communicate the unique value to the market not only ensures all communication is accurate but all design is influenced by market need and reiterated to the market in a meaningful manner.

Now let’s review Tom’s proposal. As per our opening, it’s quite good. In fact, the elements are really good. You need business and category leads. You need sourcing and supplier value. You need operations and governance and someone definitely has to do that. And you need data and digital.
(And if it’s so close, why are we picking on Tom? Because to pick on someone who’s model is bad would require us to write a long multi-part essay or book chapter, and that’s just too much to make a single point.)

So, you need all of the people that are named (or at least the skillsets), but are they leads? Maybe. Maybe not. And is the model appropriate. Somewhat, but not really — not for a lot a of organizations (not being run by Tom or those with his Procurement world view).

But let’s start with the business and category lead and sourcing and supplier value lead. Maybe these are separate, maybe they are not. It all comes down to your philosophy on how you run Procurement. Are you event-based or category-based? If you are truly category-based, sourcing is part of category management, it’s not a separate function or activity — and your category leads know how to source. They will use analysts to help them understand the current market conditions; break down the cost structures; create should and target costs; identify the most likely suppliers; etc. But they will choose the strategy and own the sourcing event. There will be no “sourcing leads”, just “analyst leads” and “supplier development” leads.

Now let’s tackle the “data and digital lead” category. You’ll have a senior analyst lead who runs the team, which will consist of one or more spend and performance analysts and risk and resilience analysts, but the most critical member will be the Procurement Master Data Manager who will work with IT to ensure the necessary data is captured, maintained, enriched, and applied appropriately. Especially since any AI tool you use will blow up in your face without good data. (And if you’re using an LLM there’s no guarantee that it won’t blow up even with good data, but it’s much less likely to blow up with good data than with bad data.)

As for “digital and enablement specialist”, let’s start by clearly stating that any professional that isn’t digital 31 years after Nicholas Negroponte published Being Digital isn’t going to survive much longer in a world where everyone is chasing the AI Dream and trying to automate everything, even that which can’t be automated. Especially since those departments that lie and say it’s AI and adopt tech that works will be three, five, and even ten times more efficient than those that don’t. Every member will be responsible for digital enablement, not just a lead. The team may use expert consultants to help them pick the right tech and evaluate AI (to identify the hybrid or, better yet, old-school AI that actually works), but it shouldn’t be a separate lead in a modern organization.

Working back through the structure, let’s review the ops. An ops manager is critical — and a lot of departments miss this trying to be lean and mean. Someone has to ensure that all of the operations are aligned to support all of the category manager’s requirements from analysis through sourcing support though supplier development through compliance and risk management. And you probably will need a policy and compliance specialist, but should buying channel leads be separate from category management? And if so, is it a channel manager or a technology manager you need? You’re either buying off of contract, usually through an auto-reorder or catalog; from a marketplace; or through a sourcing event. Are those channels? (We’re not talking sales.) But you probably need an internal catalog manager and a marketplace expert.

Finally, the commercial advisory specialist and the contract and commercial manager should probably be on the same team in many organizations (i.e. the commercial advisory team).

In other words, the presented team structure is a great start for identifying key roles, but might not be the perfect org structure for you … or it might be. As noted above, it depends on whether or not you are category driven or not, tech centric or tech supported, and how much support the different roles need.

But most importantly, it depends on what industry you are in and what you are primarily purchasing. If you are in manufacturing, and are primarily purchasing direct, you will need a category manager for each major category as well as a liaison in the appropriate R&D and Manufacturing production teams for each major category. And since, in some categories, the supply will be limited it will be more about negotiation and target costs than open strategic sourcing, you will need engineering experts for target costs; risk experts to identify potential regional, natural, and economic risks related to a supplier; negotiation experts who understand BATNA who can balance supply assurance, quality, and cost; etc.

But if you are a retailer and just need finished goods, you barely even need a category manager. And you certainly don’t need to have a category expert embedded in another department. You just need to source, source, source. And there’s not a lot of risk analysis that needs to be done. It’s finished goods. If one supplier doesn’t supply, you go to another. Unless the retailer is a luxury retailer, it doesn’t care too much what the brands are as long as it can supply products that will satisfy its customers’ needs. And it will be the one organization that latches onto the digital and AI specialist as it will need tech constantly scouring for new suppliers, distributors, and marketplaces that can enhance supply certainty, quality, and/or cost effectiveness — because achievine any two of its three desires ain’t bad!

In other words, the optimal team depends on what the organization actually needs to succeed based on its industry, size, and maturity. It can start with a great template, but it will need to customize based upon its specific circumstances, processes, and maturity. And it might need help to define what that is.