Category Archives: Orchestration

What is Spend Orchestration?

Spend Orchestration is all the rage. But what exactly is it?

Well, as we tried to point out in Demystifying the Marketing Madness for you, where we said it meant we don’t do anything different than all the other orchestration providers, but it sure sounds cool!, Spend Orchestration is essentially:

Clueless for the popular kids.

It’s a coming-of-age comedy where you have a slick looking, popular, over-funded new-age SaaS platform from fresh-out-of-college (dropouts) who want to do “good deeds” for the Procurement space by giving your Procurement department a “makeover” that connects all of your applications together so you can “manage your spend” and match stakeholders with the procurement professionals that can meet their needs (as the platforms try to justify their existence).

Upon implementation of the spend orchestration, there will be one fiasco, hardship, and falling out after another as you realize the platform doesn’t do anything if you don’t have core Procurement platforms for sourcing, supplier management, analytics, contract management, procurement, and invoice management/accounts payable … otherwise, it’s just intake to nowhere and orchestrating faster push and pull from your incomplete, outdated ERP/MRP. Also, without good platforms in place, it will just make it easier for the stakeholders to admonish you on a daily basis when your Procurement process doesn’t actually pick up the pace or perform more preferably. And you will be more jealous of your peers that skipped the orchestration platform and went straight for the S2P or P2P platform that actually solves some of your Procurement problems.

Now, eventually you will acquire the missing pieces (or these orchestration platforms will build basic functionality) and you will kiss and make up at a big fat Procurement Wedding like ISM or DPW, where they invite you on an all expenses paid trip to participate in their prestigious Power Procurement panel, but it will be a very rocky road on the way.

Our suggestion is that if a company comes knocking with “spend orchestration“, you tell them thanks and no thanks and save the comedy hijinks for the big screen. If you do need orchestration — which you won’t know for sure until after you’ve consolidated your applications, determined which are not easy to direct connect (due to a lack of [Open] APIs), which don’t allow easy access across the organization, and where orchestration might actually help — you want to get that orchestration from a company that has grown up, not one just starting it’s teenage high-school journey!

Orchestration Won’t Solve a Reckless Runaway SaaS Proliferation Problem!

In a recent LinkedIn Post, THE REVELATOR asked Why you need an Internal and External Metaprise Strategy for optimal Intake and Orchestration capability? and noted that:

  • Most large enterprises use between 10-25 procurement software platforms, with some complex organizations exceeding 25. Just for Procurement!
  • A 2022 study by Forrester Consulting found that large enterprises use an average of 367 software applications and systems.
  • A 2023 report by Zylo found that large organizations deploy an average of 660 Software as a Service (SaaS) applications.

Moreover, the doctor has seen stats:

  • as high as 87 individual SaaS products in a single department in larger orgs
  • exceeding 40 for Marketing or Sales … when you can’t find more than a half dozen apps that actually do something significantly different

All the doctor can say to this is that if the number of platforms you are using numbers is in the three digits, you don’t need orchestration, you need consolidation!

For example, Marketing and Sales is all lead generation/management and customer prediction/funnel/CRM. With no coherent strategy (beyond maybe SalesForce for CRM), every employee or team will purchase their own set of Apps and the organization will have 5 to 10 apps that more or less do the same thing with 90% overlap. And similar situations abound throughout the organization.

So yes, these organizations need a strategy, and that strategy should be to centralize app decision and management in each department to prevent unnecessary app sprawl. After all, each app you orchestrate costs you even more money than the app subscription cost (as the orchestration app will charge you based on the number of integrations, and how many of those it supports out of the box), which ends up ballooning your overspend to integrate apps you shouldn’t be using in the first place.

Which means that the first thing these organizations need is a SaaS App Optimization platform that can crawl their SaaS purchase and usage data, identify what’s used, identify more-or-less duplicate apps, and identify which app should be consolidated upon based on usage. This will not only reduce costs by over 30% once the unnecessary apps can be dropped (at the end of the current license or payment cycle), but increase productivity (as [cross functional] teams work in the same app ecosystem).

Moreover, this is just the tip of the overspend iceberg. Once the first round of consolidation is done, these organizations need to tackle SKU sprawl in their enterprise platforms, and their ERP, Cloud Host, and Back-Office Systems in particular where the common vendor strategy is to offer “bigger discounts” when the client purchases packages that contain modules they don’t need or more seats than they will actually use, which, even with the bigger discount percentage off of list price, are still designed to cost the organization more than they should be spending. To do this, they will need to use a vendor, like Green Cabbage that we recently reviewed, that are experts in enterprise software system purchases and know how to unbundle these consolidations and get you insight into market pricing on a SKU basis for hard-nosed fact-based negotiations.

Only once the organization’s platforms have been consolidated and optimized should the organization embark heavily into orchestration, as this is the only way to ensure they don’t do unnecessary work or pay unnecessary costs.

Don’t Zip Through the Zip-sponsored Spend Matters authored Intake and Procurement RFP! [2024] (Collected Links)

Don’t Zip Through the Zip-sponsored Spend Matters authored Intake and Procurement RFP!

Please note this is NOT coverage of Zip. See this post for Zip solution coverage!

BONUS

BONUS 2

2023 was the year of Intake. Will 2024 be the Year of Orchestration?

Orchestrate the feeds
Pave the way for meeting needs
Phase one is initiated,
there’s no more paper chase, eh?
Set the space ablaze
Case closed, we did rephrase
Workflows for phase by phase
Gets you through the hard days

To the tune of “Orchestrate” by Eliozie
(Outtro NSFW)

2023 may have been the year of Intake with Zip raising 100M to do Procurement intake management for the layperson, but 2024 will be the year of Orchestration. The reason is that while it’s great to manage intake and give the organizational end-users and stakeholders insight into where their request is in the process at all times, allowing them to interact with Sourcing and Procurement where needed, it’s even greater to give Sourcing and Procurement the orchestration engine they need to get their job done and fulfill those organizational requests efficiently and effectively – across people, processes, and platforms.

With so many challenges for an average buyer to fulfill a request from an organizational employee or stakeholder:

  • identify potential suppliers
  • identify potential products
  • verify products
  • for suppliers not onboarded, verify supplier eligibility for onboarding
  • onboard the required suppliers for the sourcing event
  • conduct the sourcing event
  • identify the winner
  • conduct negotiations and …
  • collaboratively develop a contract for signature
  • (e-)sign the contract
  • identify and track the performance obligations
  • identify and track the compliance obligations
  • import the pricing into the e-Procurement system
  • send out the (first) PO
  • track the order acknowledgement and the shipment
  • ensure and record delivery
  • etc. etc. etc.

Doing all of this often involves

  • using a third party supplier discovery service to identify potential solutions
  • searching product specs in a third party marketplace that integrates with your catalog management application
  • using a TPRM (third party risk management) to make sure the supplier doesn’t have any obvious red flags
  • onboarding the supplier in your supplier management solution to collect organizational specific data requirements in order for you to potentially transact with the supplier
  • switching to an e-Sourcing tool to do the RFP/RFQ (as appropriate)
  • running a (weighted) analysis on the bids to select a winner …
    possibly in an analytics solution
  • conducting negotiations in a negotiation management tool (that may or may not be integrated with the CLM)
  • managing the contract drafting processing in the CLM
  • … and the signing in the e-Signature tool
  • and then run the the contract through a contract analysis solution to push the performance and compliance obligations into the governance module
  • … and extract and push the pricing into the e-Procurement system(‘s integrated catalog)
  • … where the PO is cut and the Ack received before …
  • they have to manage the invoice in the I2P (Invoice to Pay) / AP (Accounts Payable) system as well as verify the goods receipt
  • etc. etc. etc.

Furthermore, even if the organization has a “suite”, chances are it’s not that “sweet” and many of the core modules aren’t tightly integrated (as most of today’s S2P “suites” were assembled through acquisition and while the UX has been cleaned up to look consistent at first glance and there is some “endpoint” integration, chances are that it’s minimal data push and pull between process endpoints). It’s also often the case that if the required workflow doesn’t exactly match a very specific use case, the integration just doesn’t work seamlessly and it’s a lot of effort. That’s for the modules in the suite. Not all modules are in the suite. Most suites don’t have full TPRM, extensive compliance management, negotiation support, inventory management, etc. and that is through non-integrated third party solutions. A simple process that should take a few hours of effort to check all the boxes can take days of effort as buyers have to switch between multiple systems, check status, re-enter data, switch back to the intake platform to update the requester, make changes, and so on. Just like the introduction of “modern solutions” has taken onboarding from a 2-day fax and email process to a 2-week gated process with multiple, disjointed, approvals, the proliferation of disjoint, specialized, Source-to-Pay-Plus solutions has taken simple processes that take hours of person-work and days in real-time to complex processes that take days of person-work and weeks in real-time.

The solution? Procurement orchestration. Something that integrates, to the extent possible, all of the modules together in the right process with the right steps in the right seamless flow that requires any piece of data to be entered once and only once in a consistent user interface … and works for all parties, the requester, the buyer, and any stakeholder involved in the process.

There are Three Primary Parts to Procurement Orchestration

Procurement Orchestration is the craze, presumably because Procurement shouldn’t operate in a vacuum. There are a number of startups just focussed on orchestration, a number of analyst firms are jumping on the orchestration bandwagon, and a number of enterprise automation platforms are all of a sudden claiming to be procurement orchestration platforms to get in on the buzz. But there’s a lot more to Procurement Orchestration than just application automation. A lot more.

Procurement Orchestration, which we included in our 39 Part Series to Help You Figure Out Where to Start with Source-to-Pay in Parts 34 to 36 and 39, MUST Address, at a minimum, the orchestration of:

  • procurement data
  • procurement process
  • procurement stakeholders

First of all, good Procurement needs to be data-informed. (Not data driven, data informed. Data driven means that all decisions based on the available data, which is never complete. You can accurately capture all bids in an RFP, previous OTD metrics, previous defect metrics, subjective quality ratings, ESG data, etc. but you can’t capture relationship data, innovation support, etc. and these are also factors that are important in Sourcing and Supplier Selection.) This means that all available data needs to available to the Procurement team. It doesn’t have to be centralized in one system or pushed to a data warehouse / lake / lakehouse, but the source system (that holds the golden record of truth) for every piece of data needs to be identified and integrations created to allow the necessary data to be accessed as needed by the Procurement system currently being used.

Secondly, good Procurement needs proper processes. That’s more than just application orchestration as not all Procurement teams will have applications for every step of the process, and even those that have major applications for every major stage (intake / need identification, spend analysis / opportunity / procurement process identification, sourcing, supplier onboarding / management, contract negotiation and governance, e-Procurement/PO Generation and Management, Invoice Management and OK-to-Pay) will still need to orchestrate intermediate process steps such as stakeholder collaboration, external vendor risk/ESG review, etc.

Thirdly, good Procurement needs to involve all of the relevant stakeholders. The category manager, the risk manager, the budget holder / executive, the in house counsel, etc. All of these individuals need to be able to interact with the procurement process and artifacts at the right time, and through their applications if they have special tools to do the risk analysis, budget analysis, contract review, etc. Thus, supporting procurement goes beyond just supporting procurement applications and processes, but peripheral applications and processes as well so that all stakeholders can be part of the process and effectively contribute their expertise and experience.

Remember this the next time a jazzy tool tries to lure you in with pre-built Procurement platform integrations or easy, visual, procurement workflows. That’s just part of the puzzle.