Category Archives: Market Intelligence

Another Reason You Can’t Wait Too Long for the CPO!

In our last post, we reviewed a post by the Great Garry Mansell on the rule of two where he outlined when an organization needs to hire a COO in order to continue to grow. We noted that you can use the same same logic to determine when you should hire the CPO, which should happen earlier than most organizations believe.

In a follow up post on the hidden tax, Garry gave us another great reason to hire a CPO early.

Basically, as organizations grow, they spend money to feel professional. It’s a hidden tax that grows over time that not only (greatly) reduces their EBITDA and profit, but also decreases their resiliency.

As Garry points out, as companies grow, they spend money to feel professional. They add tools because someone recommended them. They add layers because it feels grown-up. They add process because it looks like control. They add roles because it feels safer than making a hard choice about what to stop. And then they end up with three to ten times as many tools as they should (just look at the average number of SaaS tools in an organization), and spend two to three times as much as they should be. And the processes they add are not the right processes because they don’t have the expertise to define best-in-class sales, marketing, procurement, etc. processes because they don’t have a seasoned CRO, CMO, or CPO to define them. They hire people they don’t need to get stuff done that should be automated or simplified by better processes (that could only be defined by the right senior people who should be hired at the right time, and funds saved until they can be).

This is another reason why you need a CPO early. A CPO will vet not only the reason, but the ROI, of every proposed product/platform and prevent unnecessary purchases and, if something is required, find the best product/platform. They will prevent processes that don’t add value. And they can even help determine when hires are really needed or when better platforms and processes can delay the need.

Procurement will focus their spend on the things that improve outcomes. And they will happily cut the things that improve optics because optics don’t carry you through volatility. Cash and speed do. And Procurement will help you conserve cash and act as fast as it is prudent to.

As Garry states A “good company” that has protected margin and kept agility will outlast a “professional company” that has simply become expensive. And a good company is one that puts Procurement front and center. After all, as Coase clarified, Procurement is the reason a company exists!

Don’t Wait too Long for a True #2: The CPO

Garry Mansell recently wrote a great post on the a rule of two that dictates when the founder of a growing start-up needs to hire a COO to help manage the day-to-day to keep the start-up on the growth track. Garry labels the position the second-in-command — a true strong number two! But he should call it number one, because the role of this CEO’s right hand is to create pace without drama … absorb ambiguity and turn it into clarity … make the founder less central … and allow the organization to scale without burnout.

As Garry points out, when it hits the wall where the company struggles to scale, the company is in a state where it looks like the founder being busy, but not effective. It looks like things moving, but not compounding. It looks like decisions being made, but not sticking. It looks like the organization waiting for the founder to be present to progress. As a result founders often try to solve this with many more heads. Another manager. Another lead. Another layer. It can help in the short term … until the founder becomes the bottleneck for alignment across those layers. They don’t admit that the hardest part is not finding talent. It’s letting go of the belief that ‘only I can do it properly’. They don’t realize it becomes the thing that limits growth.

But when the organization has a good COO, she doesn’t just take tasks. She takes load. She takes ownership of outcomes … and they make the founder better by refusing to let everything sit in the founder’s head. And Garry’s right on all accounts.

The same logic more-or-less dictates when the organization needs to hire a CPO. Even if the CPO is the entire team. Once an organization is big enough for the founder to hire a COO, a true #1, one of the hats the COO inherits is the CPO hat — and takes over the Plague of Purchasing. But as the organization continues to grow, more and more divisions/teams need to buy more and more products and services of all shapes and sizes, which requires more and more decisions and analysis, more policy, and more decisions … which get made, not properly codified, forgotten in the heat of the moment, and made again. Just like when the organization reached the point it needed a CEO, we again have the situation where it looks like the COO being busy getting Procurement done, but not effective. It looks like things moving, but not compounding. It looks like decisions being made, but not sticking. It looks like the organization waiting for the COO to be present for Procurement to progress.

Even though the organization might only be spending a few million, and the savings might only be a few hundred K, which would barely cover the cost of a CPO, making it look like it’s too early to hire the CPO, but it’s the right time. Hiring early allows the CPO to define proper processes and procedures, define platform and automation needs, determine the right time to pull the trigger on platforms and applications, identify when category managers / senior buyers are needed and the team needs to expand, and because processes and platforms were built into the organization as it grew, the CPO will be able to delay hires longer than peers because Procurement will be efficient from the get-go.

All Good Plans Have This in Common!

There’s a number of things all good plans have in common, but one often overlooked aspect is one emphasized by Garry Mansell in his scaling plan is real post.

According to Garry, he can always tell within ten (10) minutes whether or not a scaling plan is real. Not because he’s clever, but because real plans have a particular smell to them … they acknowledge constraints. They name trade-offs. They make it obvious what will be sacrificed, and when.

And he’s right — because if a plan is frictionless, it’s not a plan. It’s a fantasy (and likely even worse than your RFP Fantasy). And many of these fantasies, as Garry points out, are immediately identifiable from their assumptions that everything is possible, nothing has a cost, everything is assumed to be easy, integration is assumed to be smooth, customers are expected to behave, and cash is assumed to cooperate. Anyone who’s been though a real startup knows that NONE of this is the case!

A real plan not only acknowledges constraints, but contains sentences about the harsh reality that are uncomfortable, sometimes very uncomfortable, to say out loud — especially for executives who believe that “leadership” is always maintaining positivity and exuberance. But the reality is that there are always risks, and if you’re trying to start something new, or grow considerably, there will be lots of big risks. And if you don’t acknowledge them, do what you can to mitigate them, and be prepared to work through, or at least around them, you won’t succeed.

This should not be a surprise, because, as Paul Martyn will be quick to point out, and I will be quick to echo, if you don’t acknowledge, and capture, your real constraints in your scenario analysis, you will not succeed. And if the most import constraint is left unspoken, other unspoken constraints will be implicitly captured in the constraints and costs that do get modelled, and the outcome will be determined before the first scenario is run. That’s not success, that’s doing everything possible to protect the status quo.

And you won’t scale anything that way!

Buyers Are Not Process Operators!

In a LinkedIn post from a while back, Garry makes a very important point: many procurement operating models still treat buyers as process operators.

Run the event. Collect the bids. Populate the template. Push it through governance. Negotiate hard. Close the file. Move on.

Tech (which may include AI but doesn’t need to as you can do quite a lot with ARPA and do it better, faster, and cheaper than humans AND Gen-AI can do it) will make the traditional buyer role less central because all of this, except for the finer points of negotiation, can be done by the tech. (The brute force points, collecting all the data to defend your offer can be done by the tech.)

Once you adopt Busch-Lamoureux Exact Purchasing, it becomes easy to not only map your categories to the octants, but identify the processes you should use for sourcing and procuring those categories, as well as monitoring the procurement activities to determine if there is a situation where a human has to intervene.

It also becomes clear what you need to do at each step.

  • Sourcing: identify what needs to be sourced vs procured, what categories and items will be included in an event, what suppliers, what products, what requirements, etc. etc. etc. — all of the decisions you can’t risk automated (which can still only be automated from encoded knowledge from prior decisions)
  • CLM: key contract requirements and acceptance criteria; etc.
  • SXM: key (compliance) requirements, key risk mitigation clauses, need for no vs. internal vs. external review, etc.
  • Analysis: historical spend/volume/prices; current prices/volume requirements; predicted prices/volume requirements; opportunities for demand shaping/control; etc.
  • e-Pro: available channels and under what conditions; what gets in the catalogue; who can buy out-of-catalogue/non-preferred; processes for overrides (to budget limits; cost limits; etc.)
  • I2P: m-way match requirements and tolerances; ok-to-pay / auto-pay requirements; when early-payment discounts can be offered/applied; etc.

As Garry states, a buyer is not a buyer — a buyer is a decision architect and makes the decisions necessary for successful Procurement. A decision architect that designs how a decision should be made. An intelligent human who maps the organization’s categories to the pocket cube of Exact Purchasing, determines what can be automated, what systems will be used to automate, what qualifies as exceptions, how those exceptions will be monitored for, and how they will be alerted.

But a buyer is more than that — it’s a decision architect and relationship management. Procurement is about managing stakeholders and suppliers. Dumb systems cannot do that. Only HUMAN INTELLIGENCE can.

In an AI-Hype world, Procurement will be measured on its success, and that success will require Human Intelligence leading Procurement to glory. So acquire real pros if you want to not only survive, but thrive in, the Age of Retardation the AI-Hype is ushering in!

Are they 2026? Or 2016? Or 2006? Procurement Trends? Part II

Tom Mills recently posted a Top 10 Procurement Trends in 2026 post on LinkedIn that made me ask Really? Basically, I’ve been reading, and writing, about the majority of the “trends” for two decades. As per my recent 34-part series on you don’t need to read another state of procurement report for five years!, nothing has really changed in the last five years. In fact, not much has changed in the last ten, if not twenty, years. All that ever changes is the tech-du-jour, which particular risk is the most prominent, which particular process is the most recommended, and whether the trend is in-sourcing solutions, out-sourcing solutions, or hybrid models.

To make this oh-so-clear, we’re going to conclude Tom’s list and provide some colour commentary!

6️⃣ AI Becomes Core but our Readiness Lags

This is the only “sort of new” trend, except it has been the “sort of new” trend for three years now, but when you realize “AI” is the “tech-du-jour”, you realize that, again, nothing has changed for the past two-plus decades because the “tech-du-jour” is always the 10th trend. And for every
tech-du-jour that becomes core, our readiness lags. Over the past 25 years we’ve had these five tech-du-jours (that tend to last for around 5 years).

  • WWW
  • SaaS
  • The Fluffy Magic Cloud
  • Predictive Analytics
  • AI

7️⃣ Data Quality and Governance as a Prerequisite

For all advanced tech, data quality has ALWAYS been central and paramount. Ever since the introduction of optimization, and in our space, strategic sourcing decision optimization (SSDO), data quality was key. With traditional (MILP) optimization, one value in one million can tank an entire model (because if a decimal point error makes one product 50X cheaper, then the allocation will obviously go to the wrong supplier). Moreover, if there are capacity constraints, minimum allocations, maximum supplier counts, etc., this will result in cascading incorrect assignments and allotments across the entire model. Then came should cost modelling, and again, without good data quality and governance, it didn’t work. Then spend analysis, which needed proper market baselines. And now AI, which is garbage in, hazardous waste out. Even with perfect data you can still get hallucinations, so you definitely don’t want even the slightest error!

8️⃣ Orchestrated Procurement Ecosystems

In Procurement, which has NOT fundamentally changed since the first manual was written 139 years ago, the story remains the same — only the names have changed! AI may be the tech-du-jour, but orchestration is the term-du-jour. But it’s not new. The automated coordination, management, and sequencing of multiple distinct processes, systems, or components to achieve a unified, higher-level goal has been a goal of Procurement for decades — except back in the 2000s the term-du-jour was “metaprise”. (And Jon W. Hansen can also fill you in on the history here.)

9️⃣ Talent as the Transformation Multiplier

We’ve been talking about this for decades. I wrote a 7-part series 20 years ago when I first started SI. Talent is not only necessary, but it’s the way you truly succeed. Talent that designs better processes, selects better technologies, and, most importantly, makes better decisions that allows the organization to be more strategic and more effective is not only transformation, but a transformation multiplier.

🔟 Procurement as an Enterprise Value Driver

Ever since AMR first started covering the space in the early 2000s, we’ve been told that Procurement is the Enterprise Value Driver. That strategic sourcing, when utilizing the right technology (namely optimization and analytics) would consistently identify year-over-year savings of 12%. That m-way matching, which ensured the payment matched the invoice matched the PO matched the contract would prevent (often unrecoverable) overspend. That spend analysis can identify real value drivers. The whole space was defined as a value driver. Nothing has changed.

The GruntMaster 6000 was engineered for longevity and has a long memory. And his long memory tells him that the more things (are purported to) change, the more they stay the same!