Category Archives: Procurement Innovation

What’s Your Data Foundation? And is it enough?

A few weeks ago, we asked Do You Have a Data Foundation as a follow up on our post that asked Where’s The Procurement Management Platform because, as has been made clear in our ongoing Source-to-Pay is Extensive Series (which is now at Part 6), even the best platform is useless without data — so what’s your data foundation? And is it enough?

You need a LOT of data for effective Procurement. This includes, but is not limited to:

Catalog Data
which represents commodity goods and packaged services that your buyers can buy in an e-commerce fashion
Contract Data
that encapsulates custom/proprietary goods and services you can buy and the obligations made by both parties as well as standard clauses you use
Supplier Data
that describes suppliers you have done business with, are doing business, and that you are considering doing business with
Product Data
that represents products a potential supplier could provide you with, not in a standard catalog, or product descriptions (and bills of materials) for products you need a supplier to contract manufacture
Purchase (order) Data
that represents what you have bought from suppliers, vendors, and service providers
Invoice & Billing Data
that represents what suppliers bill you for the goods and services you order, regular service/utility/rental payments, and other external payments requested by third parties
AP Data
that represents what Finance actually paid
Inventory Data
that represents what the organization actually received, and what it actually sold
Carrier Data
what carriers are available to bring the organization it’s goods from suppliers and then transport the organization’s products to its end customers, as well as what modes (truck, train, plane, or cargo ship) and types (dry, liquid, frozen, hazardous) of transport they support, the lanes they ship down, and their standard LTL/FTL crate/pallet rates
Risk Data
because you want to understand the inherent risk of a supplier from its operations, finances, regions, and inbound supply chain before you place your survival in their hands
ESG & Carbon/GHG Data
because reporting, and sometimes even reductions, are required in countries where organizations have limits
Supplier Diversity Data
as you need to support goals, and sometimes hit targets to do business with governments or keep existing customers
Supplier Bid Data
from tenders, RFQs, RFBs, and other RFX activities you send out
Market / Benchmark Data
that you can use to analyze your quotes, spend, risk factors, etc.
Document Data
which represent your contracts, product sheets, sales and marketing artifacts, financial reports, etc.
Organizational Data
employees, org structure, office locations, plant locations, etc.
Application Specific Data
created by other applications in the enterprise application ecosystem that power the business and impact what Procurement needs to do

And, moreover, this data takes multiple formats — numeric, fixed value from fixed list, free form text, image, audio file, video file — of various lengths and sizes, and is organized in various ways. Sometimes in a record structure, sometimes in a document structure, sometimes in a spreadsheet structure, and sometimes in a table structure. And it’s stored in various formats (ANSI, UTF8, UTF16, etc.) and communicated in various standards (EDI, c(XML), JSON, etc.)

And you need all of this data to do your job. And, moreover, you need to mangle all of this into a coherent federated schema so that you can do the analysis you need to make the necessary business decisions that Procurement must make to accomplish its task and achieve the business objectives.

But point to one platform that can

  1. Store all this data
  2. Organize all of this data into a federate schema to support holistic analysis
  3. Allow the organizational users to create arbitrary slices (cubes in spend analysis) for analysis
  4. Allow for the creation of arbitrary analysis on those slices
  5. Use the results as baselines for forecasting and predictive analytics
  6. Extract prescription advice based on those results

while integrating with the other modules and applications in the larger ecosystem the organization needs, and do it with a flick-of-the-switch or out-of-the-box configuration (engine).

SAP, Oracle, and other databases and ERPs don’t normally make it past 1 with a baseline implementation. With snowflaking and other advanced offerings (that support warehouses, lakes, and lake houses), maybe you get some of level 2. You then need to buy separate BI tools to get part of level 3 and part of level 4. You then need to turn to external tools and inject the right data to get level 5. And level 6 is still few and far between (and AI ain’t gonna help you here for a while because AI is just very advanced algorithms that can, depending on the problem, do millions, billions, and sometimes trillions of calculations on large, very large, and, if available, extremely large data sets to find likely outcomes — but only if there is enough good data to populate the data set [size] it needs — and where the internet is concerned, that’s usually not the case and the old adage of “Garbage In, Garbage Out” applies here).

But you need this in your future “platform” (ecosystem), and you will only get this if you have a good data foundation that captures all of the data elements above as well as providing a data foundation to enable the six (6) levels of capability that an organization will require at a minimum.

Source-to-Pay+ Is Extensive (P6) … But There are Barriers Selecting an e-Procurement Solution!

After sticking through five parts of this series (Part I, Part II,Part III,Part IV, and Part V) you accept that you need to start with e-Procurement, which means getting an e-Procurement foundation in place as soon as possible if you don’t have it or upgrading the e-Procurement foundation if the solution you have now does not meet your baseline requirements. But how do you select the right solution?

After careful consideration, it became quite obvious that e-Procurement was the definitive starting point. It also became quite obvious that no matter how good an argument a vendor gave you for starting elsewhere, it was never the right starting point because all these solutions require data — that the e-Procurement solution collects — and assuming that you could get the full value of their module without that data was a false assumption. (However, if the argument is strong enough, it’s the next module you work on, as soon as possible.) Unfortunately, now that you are ready to select a solution, the answer of what to do next is not so obvious.

Even though we outlined a minimal baseline that is more-or-less an absolute for every organization — small, medium, and large alike — it doesn’t get us anywhere towards selecting a vendor solution, or even identify potential starting vendors, as all the minimal baseline does is allow us to eliminate any solution that doesn’t have core functionality, and, despite vendor claims to the contrary, isn’t yet an enterprise ready e-Procurement solution. So how do you select between what’s left? Especially when this still leaves potentially dozens of solutions that can easily meet your (current) baseline needs.

Well, the answer is a good old-fashioned RFP, but who do you send the RFP too? You don’t want to send it to 20 vendors that seemingly make the baseline based upon their marketing materials and whatever third party write-ups you can find. You want to narrow in to a top 3-5 with the technology to serve your needs as soon as possible, and send the detailed RFPs to them.

If you’re a large company, Spend Matters*1 Solution Map could be a good starting point as that verifies the solutions have certain technical capabilities and you can weight down to the capability level in a detailed assessment project (assuming, of course, you’ve already done a gap analysis and a study to determine the technical foundations that are necessary and relevant to your organization — the must haves and should haves). (And while the Spend Matters Solution Map doesn’t capture every vendor, it captures a majority of those that can serve large multi-nationals.)

If you’re a larger mid-size company, Spend Matters TechMatch may be a good starting point as it is based on Solution Map and allows you to rank vendors by answering questions that encapsulate (related) functional requirements, and you can always verify deep technical requirements where it’s relevant in the RFP. (And while Spend Matters TechMatch doesn’t capture every vendor that can serve a mid-size, primarily regional, organization, it captures more than enough.)

If you’re a smaller company, TechMatch could work, but the reality is that you likely don’t have the budget for it, and/or want to focus in on the smaller, lower-cost, and/or newer solutions to start, of which only a minority are covered at any point in time (due to the baseline capability required for a vendor’s solution to make the maps and the fact that smaller vendors sometimes don’t have anyone to do analyst relations and/or marketing full time). Also, it’s likely that you can’t yet afford half the solutions in the map anyway. (The suites*2 are quite expensive. While the suites are most definitely worth it to a large multinational when you do the ROI calculation, the up front [and even ongoing cost] is sometimes impossible for a smaller organization to justify.)

Moreover, an implicit assumption in SolutionMap is that you’re a typical company in a vertical buying primarily indirect and direct categories that are well covered by the solutions represented in the maps. If this is not the case, or if you need more solutions at the lower end of the market, given that the maps typically only represent around 20 solutions, with the majority of these solutions best suited for the mid-size or large enterprise, the maps may not be for you. (Especially when there are more than twice the number of solutions on the market then are represented on any map.) Moreover, if your company is not a typical company and needs a solution customized for a specific vertical (like Marketing or Legal, etc., where a specific solution would not show well on a general map), the maps won’t work for you in these edge cases.

So where do you look? The big analyst firms? Their reports costs thousands of dollars and tend to cover less vendors. Conference exhibitors? That’s typically limited to the bigger companies with larger marketing budgets given the cost of a booth these days and, thus, no better as a starting point. ProcureTech, that puts out a ranking of 100 companies a year? There’s some really good lower end companies there (and the doctor is impressed with the breadth of companies they have identified), but the ProcuremTech 100 is very broad and their organization of this report, and their companies, ranges from ok to confusing to utterly meaningless for a buyer looking for a specific type of solution! (Growth? Innovation? Customer Satisfaction? How do those categories help a company identify who to look at when they need a specific solution type. And sometimes the solutions within a same general category are so different they are barely comparable. This happens a lot in SXM and CLM, as we will discuss in future series.) You could engage with ProcureTech, as they have a good database now, but the doctor feels you shouldn’t have to do an engagement with anyone just to find a starting list of vendors you might want to look at (that the analyst firm could advise you on) or a basic understanding of how the analyst firm can help you before you engage them — especially if all you want is a set of logos in a specific application area when DPW gives you 100+ of those for free with their latest “Sustainable Procurement Technology Landscape“!

How about Spend Matters Almanac? It’s better than most directories out there as it does include over 575 listings across 61 categories, but that’s still only half the vendors in the global extended procurement technology space. (Presumably because most vendors, like most buyers, probably don’t realize it exists and some of those vendors that are aware of it, but not listed, also assume that most buyers aren’t aware of it and thus don’t want to pay for the attention grabbing premium listings and don’t bother with the Almanac at all — often not realizing there is a free listing option.)

The reality is that there’s no good starting point for even getting a near-complete list of relevant vendors to consider, and then when you have that list, putting together a meaningful RFP — which has to get beyond just basic technology and address the core problems your organization needs to solve. (And the answer here is to NEVER take a vendor RFP template and start from it, because all that has ever been since Procuri came up with the concept 15+ years ago is a feature-function list heavily favoured towards the vendor giving the RFP template away for free — and it’s not how many standalone features the product has, including many you don’t need or won’t use, it’s the business functions that support your business, the technical foundations the platform has to be built on to support those functions, the integration capability with other products and platforms you need to work with and support, the support capability of the vendor for implementation, integration, training, and on-going support, etc.)

In other words, it’s difficult to find the right vendor as it’s difficult to even find a meaningful shortlist to send the RFP to. This shouldn’t be the case, but it sadly is. Not a week goes by when the doctor doesn’t talk to a vendor who tells me that a potential client shortlisted them with a second vendor that no one who knows the space would compare to that first vendor and not a month goes by where the doctor doesn’t get an unsolicited request to identify vendors like “X, Y, and Z” where X, Y, and Z are in completely different S2P categories (but the potential buyer thinks they are all interchangeable).

The situation needs to improve, but the reality is that some vendors are profiting too much off of the status quo, the big analyst firms who depend on big cheques from these big firms don’t have a reason to change the status quo, and the smaller analyst firms don’t have the money or the person power to cover all the vendors they want to.

Hopefully now that a few smaller analyst firms are growing they will start to tackle this core problem, but in the interim, the doctor, who used to maintain one of the original resource sites many (many) years ago, still maintains his own database of over 1200 companies in our space, is now working on updating it (which he tends to do biannually or triannually), and will, over the next few months, publish starting lists of vendors in each of the 10 core areas discussed in this series along with an indication of the market-size(s) they are best suited for so you have a starting reference point. It’s not much, but maybe it will help some of you and provide an incentive for the smaller analyst firms to do more. They need to collectively cut through the noise because every Procurement organization who has a bad experience is another Procurement organization we collectively lose for a few years and another voice that’s not spreading the message of how important modern S2P technology is.

And while this wasn’t the post you were hoping for, as the doctor knows you need help breaking down the internal barriers to new solution acquisition (and you assumed the doctor would be talking about that in this post), this is an unspoken reality that, like an elephant in the room, needs to be addressed.

So, onward to Part VII!

*1 At the time of this writing, the doctor is not a Spend Matters analyst, has not been one for seven (7) months, and receives no benefit from you purchasing any Spend Matters solution. However, he cannot deny it is still the ONLY map on the market that is based on tech and hard, well defined, scales. So he cannot overlook the value of these maps and be fair to you, dear reader. (Compare this to the random mish-mash of soft objective factors that the majority of analyst firm maps are based on where the ultimate ranking is utterly the opinion of the analyst who may or may not fully understand the solutions that are being ranked — and the discrepancy in the results that arise if the analyst firm has multiple analysts ranking vendors on the same, soft, objective scale that is open to interpretation.)

*2 There are advantages to these suites, especially if you are a larger enterprise that can afford them, as the modules are integrated out of the virtual box and the vendor can turn them on with the flick of a software switch, but there are also disadvantages as well. If the best-of-breed solution you want for a particular module or need to solve a particular problem isn’t already integrated, it could be a while to get it integrated, if you can get it integrated at all (as sometimes only “partners” are supported [and allowed] by these vendors). Plus there’s mapping the data models, API calls, etc. — you’re locking into an ecosystem when you select a suite.

Source-to-Pay+ Is Extensive (P5) … Defining an e-Procurement Baseline

In our series to date, we reviewed the primary modules of S2P (Part I and Part II), argued and counter-argued the merits of sourcing and procurement to clarify why e-Procurement must come first (Part III), and then dispelled some of the better counter-arguments we received (Part IV) as to why another module (specifically, Spend Analytics, Supplier [Relationship] Management, or Contract [Lifecycle] Management) should be first, when in fact, it should always be e-Procurement until a baseline is up and running (at which point the organization can begin implementing/using the next module).

Today, we’re going to outline baseline capabilities you should be looking for in an e-Procurement system, as well as explaining why you need them. This is not meant to be a complete list of capabilities you will need (over time), as every organizations’ needs are different, but a starting list that few organizations can do without.

  • e-Request: any user who does not have access to the system should have the ability to create Procurement requests for Procurement to act on; otherwise, they will attempt to bypass the process and the spend won’t be captured in the system
  • Requisitions: users who have the authority to place orders against contracts or budgets should be able to create a requisition for Procurement to review and flip to the appropriate supplier(s)
  • Purchase Order: the system should generate purchase orders in modern e-Doc standards that are automatically delivered to a supplier in their preferred format (to their preferred system)
  • Catalog support: it doesn’t need to have dozens of catalogs integrated out of the box, but the ability for Procurement to integrate the catalogs it needs as well as build in-house catalogs that represent contractual agreements for goods and services that can be selected by users who have system access (the complexity required will be dependent on the organization and whether it’s just standard CPG or direct parts or packaged services or consulting services with rate cards, etc.)
  • Quick-Quote/Quick-Bid/Request-for-Bid: when the organization needs to spot buy something and needs to get multiple quotes to do so (not a full modern, Strategic Sourcing, RFX solution, but simple functionality for bid collection)
  • PO ACK(nowledgement), A(dvance)S(hipping)N(otification), and standard e-Doc support
  • PO-FLIP: to make it easy for suppliers to create invoices
  • e-Invoice Support: accept the invoices
  • Goods/Service Receipt/ACK: extensive inventory support not required
  • m-way Match: the PO should match the invoice should match the receipt at the minimum (and the PO should match the contract, which it will if the catalog was populated with all the goods/services at contracted rates and the PO built off of the catalog)
  • Approvals and OK-to-Pay: support for (multi-level) (parallel) approvals and ok to pay
  • Complete API for Data Import/Export: catalogs need to get in, ok-to-pay, good receipt notifications, etc. need to be pushed out
  • DIY Organizational Administration: that allows them to define org structure, roles, user, access, catalogs, approval chains, and other core capabilities

This is just a core starting list of capabilities, the average organization will need a bit more, and the goal should be to get a system that will allow the organization, and its users, to grow over time, but anything less than this would likely not provide a baseline.

For a deeper dive into what you should be looking for from a user experience perspective, if you have Spend Matters Pro access, check out this classic series the doctor co-authored with Xavier “The Revolutionary” Olivera:

  • The Procure-to-Pay User Experience Part I
  • The Procure-to-Pay User Experience Part II
  • The Procure-to-Pay User Experience Part III
  • The Procure-to-Pay User Experience Part IV

And for those of you who want an advanced “AI” solution, check out this series which is relevant and realistic:

  • AI in Procurement Today Part I: Definitions and 6 Applications in P2P
  • AI in Procurement Today Part II: 6 Applications in P2P
  • AI in Procurement Tomorrow Part I: Recap and Overspend Prevention Examples
  • AI in Procurement Tomorrow Part II: “Ninjabots” and Augmented Intelligence
  • AI in Procurement Tomorrow Part III: Category Wizards Will Save Time, Add Strategic Muscle
  • AI in Procurement: The Day After Tomorrow

On to Part VI!

Source-to-Pay+ Is Extensive (P4) … And No Matter How Great The Arguments Are … It’s e-Procurement First!

Every company is different. Every situation is different. And, as a result, for every 10 organizations, the greatest need in S2P will be different, and for the 10 in 100 organizations where it is the same base need, the specific requirements for the solution needed will be different. That cannot be argued.

But that still doesn’t mean you start with any solution other than e-Procurement first (unless, of course, you have “good enough” e-Procurement, in which case you already started with e-Procurement, and can now move on toward fulfilling the greatest organizational need).

the doctor has had some great conversations around this series (Part I) since it started early last week, and some great minds have brought up some great points, and in each case they have managed to convince the doctor of multiple situations where their solution should be the second to be implemented, but none have convinced the doctor that it shouldn’t be e-Procurement first — because in each case he’s been able to find the one assumption, or flaw, in their argument. (But, in fairness, a few great minds have convinced the doctor that the definition of what the “baseline e-Procurement” capability is for an organization can be even murkier than just industry, high-level spend breakdown, and organizational size … but we’re not going to go into that in this post, and possibly even this series, as it’s not an article, but a treatise, and the point here is to get you on your way and educated enough to figure that out with the right expert advisor, not to drown you in confusing hypotheticals that likely aren’t relevant for your business — although we will overview the typical baseline at some point.)

The three best arguments the doctor received were for

  • Spend Analysis
  • Supplier (Relationship) Management
  • Contract (Lifecycle) Management

We’re going to focus in on these one by one, as they came from great experts who had great points (and who were right in that the “baseline” e-Procurement need could sometimes be weakened as it really is different for every organization, although usually just a small +/- to generally agreed upon core capabilities), and because you should not be lead away from pouring the foundation first (because you can’t build an apartment complex without a solid foundation, or at the very least you can’t build an apartment complex that would stand for very long without a solid foundation!).

Spend Analysis

The argument, summarized: If you don’t cleanse, classify, and homogenize the AP information, how do you know what you need the e-Procurement system for — catalogs, 3/m-way match, payment approval (chains), spot-buy quote capability, etc. — and where the opportunities are.

It’s a valid argument, but the counter point came from the admission that sometimes it takes 3-4 months to locate, access, synthesize, and verify all of the data you need to make this decision, and by the time you finish the analysis, design the implementation plan, and get going with e-Procurement, it’s six months. By that time, because you did not have an e-Procurement system in place, when the baseline is finally implemented three months later, you have to repeat the entire spend analysis process to collect, synthesize, verify, and load the next 9 months of data you didn’t process the first time.

the doctor is a very strong proponent of spend analysis, and you should kick off a project (even without getting a system into the hands of everyone) as soon as it is feasible (and it can be congruent with implementing the e-Procurement system if that is feasible), but any delay in getting a system in place that captures all of the spend just leads to repeated effort and incomplete analyses.

Supplier Relationship Management

The argument, summarized: For most big companies, especially in direct, the majority of the spend, and opportunity, is with (at most) the top 20% of suppliers, and management of the relationship is key to achieving the savings as the product/service has to be quality, on time (without expediting), supported, and invoiced at the agreed upon rates or the value never materializes. Furthermore, e-Procurement should be with those suppliers first, so it’s good to identity them.

This is undeniable. And if you don’t have the right relationships, collaboration, interaction, and management of the core supply base, especially in direct or service-driven industries, it’s true that e-Procurement won’t help you. But what’s overlooked is not having e-Procurement will hurt you. Why?

Here are a few reasons:

  • Not a single individual in any large organization will be able to name even the top 10 suppliers by spend, volume, or criticality. In divisions / categories, the experts/leads might get the top 7 or 8 right, but until all the data is captured and properly analyzed, no one will know definitively.
  • Collaboration and management is good, but you still need to send them the PO, get the ack, get the ASN, get the invoice, confirm the receipt, match and confirm the invoice, approve it, pay it, and, if at any point, something is late, detect it and act on it … that’s e-Procurement!
  • Relationship Management should be based on data … SRM systems only track interactions, not spend data, and, at the end of the day, the CFO and CEO only want to know how the relationship improved the bottom line

Contract Lifecycle Management

the doctor actually received multiple arguments here, which, summarized, were: “It’s an inflationary time, and without contracts with price protection, your costs could be out of control.” “Good contracts are key to ensuring both sides understand their obligations and what is to be delivered when.” “Contracts define what is in the catalogs and/or who the preferred suppliers are.” “Risk is at an all time high, a good contract is the best protection you have.” (And the last one was more extensive, and probably the best, but still not enough. But let’s leave risk to a different series.)

All valid statements, but none override the importance of having an e-Procurement core or address the entire picture. For example:

  • yes, costs are still going up, but they are not going up equally across all spend categories, and if there is sufficient supply available, a simple spot buy in response to a quick bid can keep costs under control, delivering significant value without an extensive (and sometimes expensive) contracting exercise
  • obligations are critical, but you don’t need a CLM to hammer out a good agreement and, in fact, if a solid understanding is key, that education and discussion is going to take place outside of the CLM and the crafting of those responsibilities on (e-)paper done by project leads, not ML-assisted auto-assembly of standard clauses into a contract template
  • you don’t need a contract to integrate a catalog, set preferred suppliers, or set restrictions on who can buy what in an eProcurement system … all of which can be changed as new contracts are negotiated later, and you don’t need a CLM to negotiate the contracts
  • risk is key, but just because you take every contractual step to protect against risk doesn’t mean you won’t have a disruption, that an earthquake won’t destroy the supplier’s plant, that unforeseen embargos will prevent them from fulfilling their responsibilities to you, etc. — you will still need mitigation plans, risk monitoring systems, etc. — and a simple absence of PO acknowledgements, late ASNs, etc. in the e-Procurement system will raise flags of issues that need to be investigated faster than a CLM will

For many companies, one of more of these applications are critical, and they will need to be implemented as soon as possible, but all require a baseline e-Procurement system in place to deliver the full extent of value you want to realize — spend analysis requires the data, SRM requires the data for ongoing monitoring and management, and the e-Pro is what captures the spend-related obligations and can be among the first of the internal systems to provide clues that there might be a problem.

So start with e-Procurement. But whatever you do, don’t stop there … don’t even slow down. As soon as you get a baseline and it’s useable, work on addressing your greatest need from a cost control/value generation perspective. e-Procurement is just the beginning … and the best way to think of it is the forge you use to craft better tools and processes that need the data e-Procurement captures and produces to deliver their full value.

On to Part V!

Source-to-Pay+ is Extensive (P3) … This is Where You Start!!!

In our first post we noted that inflation is back with a vengeance, anticipated savings is leaking faster than a bald spigot, and most organizations are in cash crunch as a result of down sales during the pandemic (and now due to a lack of core inventory to sell), and they need to update their procurement tech stack fast. And they needed to do it yesterday …

We also noted in our first post that no company can do all of Source-to-Pay at once (it’s not as easy as the SaaS vendor just flipping the switch and giving you access to the 10+ modules you need to exhaustively cover Source-to-Pay and related processes) and noted in our second post that, if you ask, everyone will have a different opinion, based on a reasonable (and often valid) argument, as to where you should start, but you need a definitive answer. Not all technologies are created equal, especially when the top four reasons you can’t do it all at once are considered. You need a clear starting point, but it’s not easy to figure it out when every vendor and consultant and analyst has a different opinion, and the right answer only comes with considerable experience.

Then, in our last post, in Part II , we covered eight (8) of the ten (10) upstream, downstream, and cross-stream technologies in detail in an effort to try and understand the right starting point, and started off thinking it might be strategic sourcing. But then we dived into downstream, and after reviewing e-payment and order management, realized that e-Procurement is extremely critical and could be the starting point. So today we dive into both and tell you which one you start with, which will be, for many of you intuitive, counter-intuitive, or both after yesterday’s post.

e-Procurement: makes the order for the good or service you need, it’s certainly critical, but strategic procurement is all about getting costs under control and not just finding a product or service, but securing it at market price and keeping costs under control, which means you need to identify the suppliers, the products and services you’ll accept, based on the price they agree to, which means that …

We need to return to upstream because

Strategic Sourcing is obviously the answer to where you start after looking at each application and realizing it is what you use to identify what you need, from who, where it will come from, at what price, and allow you to start without much data (just get the requirements and bid in, satisfying requirement #1), or training (as it’s a process a senior buyer will understand, it’s just learning the tool, satisfying requirement #2), while identifying value within weeks (satisfying requirement #3), in a manner that allow users to see the value they are getting (satisfying requirement #4). So we have our answer, right? Wrong!

Even though many experts will say this is the right starting point, especially all of the strategic sourcing / upstream providers that started building their solutions with this belief, and the consultancies that use them, it’s only the second best starting point.

The best starting point is plain old e-Procurement.

Why? The goal is not identified value, but realized value, across all spend, not just some of your spend. When you dive into the situation in detail,

1) Strategic sourcing does not realize value out of the gate, if it does at all. First of all, there can be a long time delay between award, contract, order, receipt, and payment — which is where the value is realized or not. Secondly, the value is only realized if the organization orders against the contract at the contracted value, only accepts the invoice if it is for the contracted rate, and only pays at the contracted rate when the goods are received. Sourcing applications don’t ensure any of this, but e-Procurement applications can be populated with the contracted products and services at the contracted rates, be referenced when the invoice comes in for invoice verification, and will allow goods to be marked as received (even though it won’t manage the physical location of the inventory or what happens to the goods after they are initial received).

2) Strategic sourcing only address high-dollar or strategic categories, but the organization needs to realize value on ALL its spend categories. e-Procurement can be used for all product and services being purchased, not just those sourced (or under contract). The organization can typically integrate allowed catalogs/vendors, force approvals for products/services not pre-approved or above a threshold, and make sure the spend going out the door is, where there are contracted/approved rates, at those rates (and eliminate the considerable overspend from lack of management).

e-Procurement gets all of your out of control spend under control the day it’s implemented, prevents overspend on existing agreements, and allows your buyers to focus on ensuring high-dollar orders are not only for approved products / services at approved rates, but also for products and services that are actually needed. While it may not identify any new savings opportunities, when you consider the fact that organizations without e-Procurement only ever realize 60% to 70% of potential savings identified in a sourcing project, that’s an immediate 30% to 40% improvement on savings realization. If the average savings identified was 6%, that’s 2% straight to the bottom line before a single new sourcing project is executed.

When it takes most large organizations three years to do spend projects on the majority of their high-dollar / strategic spend categories, that’s three years to address 80% of the opportunity, with “savings” going down the drain every day there isn’t an e-Procurement system in place. So start with e-Procurement, and then do (optimization backed) strategic sourcing (with advanced analytic capabilities) next. The day e-procurement is up and running with the majority of organizational spend is the day you start getting the strategic sourcing platform up and running. No exceptions, no delays. That’s the one-two punch you start with, and how you realize the greatest value potential as soon as possible.

(Spend Analysis, one of the only two advanced technologies that has consistently delivered savings and cost avoidance of 10%+ for two decades [and a specialty of the doctor‘s], sadly, comes third because most senior buyers who know their spend categories can identify 8 of their top 10 spend categories, 6 to 8 of their initial top opportunities, and 4 to 6 of their top categories not under contract that should be analyzed to determine if they should be analyzed, or the organization should continue to spot buy. They’re not very good at identifying wave 2 opportunities, and even worse at identifying wave 3, and, as we just pointed out, will miss some biggies, but they generally know where to start so until they are going [and efficient with the sourcing application], they can hold off on spend analysis for a bit [but not too long]. And this really should be the third module/technology that you implement, because the longer you wait, the less likely the buyers are going to select the next best opportunity.)

So that’s it. And if you need help identifying the right e-Procurement vendor for you, feel free to reach out to the doctor for a list of vendors you can look at and some insight into them, and if you need deep expertise, these are the analysts that focus heavy just on e-Pro/P2P/Procurement that the doctor recommended in his recent post on who he recommends when asked:

 

Pete Loughlin Purchase to Pay / Procurement / Coupa & Ariba Independent
Xavier Olivera Procure-to-Pay/LATAM Market Spend Matters

 

And then, when you’re ready for advanced sourcing (which should immediately follow), remember that’s one of the doctor‘s particular areas of expertise (as an expert in optimization, modelling, analytics, RPA, ML, and Advanced Tech in general, including “AI” to the extent it actually exists and is not BS).

On to Part IV!