Category Archives: Technology

Suite vs BoB. Which Do You Choose?

Neither!

But you need something. And there is no other option (yet). So are you doomed?

That depends. But first, let’s talk review the Primary Pros and Cons of each.

SUITE
BoB
PRO

  • one vendor relationship to manage
  • modular integration out of the box
  • consistent UX (or it’s not really a suite)
  • pre-implemented with major ERPs
  • the primary module offered by the vendor is truly Best in Class and considerably beyond the average suite capability
  • implementation is typically vendor supported, along with some integration services
  • low (subscription) cost out of the gate, pay as you need
  • today’s BoB comes with full, complete Open APIs to build your own ecosystem
CON

  • likely that only one or two modules are Best-of-Breed (BoB)
  • implementation and integration services are likely third party
  • high cost out of the gate
  • traditionally a closed ecosystem
  • multiple vendor relationships to manage
  • limited integrations out of the box to other modules you will need
  • inconsistent UX across the modules
  • limited to no ERP/MRP support in many modules

In other words, many of the weaknesses of the suites are the strengths of BoB and vice versa. But you want the strengths of both and the weaknesses of neither, even though that doesn’t exist today as no vendor does everything well, nor can they because they would need to be experts in everything. (So unless a vendor hired all the experts, and became a monopoly [and we generally agree monopolies are bad], no vendor could even come close.) Even if a vendor did hire all the experts of today, and build everything out to the best of those experts’ capabilities, they’d soon become an unaffordable mega-suite (and then still not be best in breed in anything because once they built what the experts they hired envisioned, there would be a new generation of experts they still wouldn’t have employed with new, innovative, possibly revolutionary, ideas).

So what do you do? Well, the answer is, as we pointed out in our post that asked where’s the Procurement Management Platform, acquire a platform that is designed to support data-centric end-point integrations for specific processes and organizational needs as this will allow you to select the right module for each task, configure the right procurement workflows, integrate new, even previously unthought of, modules with the Open API, and even support intake and supply chain platform integration.

But, as we noted, there’s no platform. So, unfortunately, you have to assemble your own. But at least today you can. A decade ago there were no options to do this, so either you bought a suite, and lived with it, or you bought best of breed and did extensive work to glue them together in a grit, spit, & a whole lot of duct tape situation (that would take about 69 months).

But today, all of the new best of breed applications are being built from the ground up with complete Open APIs and the newer suites are also offering you APIs to easily get data in and out as well. (Not so much on the workflow configuration / function execution front, but that’s not necessary.) [But please note that an App Store or Marketplace is not an Open API, it’s a closed ecosystem limiting you in what third party add-ons you can select.]

So you can theoretically start with the right instance of a BoB or a Suite as your base and build out the right platform over time, depending on your needs today, and how fast you can digest a new module. If you already have one or more first generation modules, you have the understanding of what these modules do and how to use them and can likely digest new versions of those modules pretty quickly, so you could start with that many modules plus one. If you have no modern S2P modules, then, as we indicated many, many times in our very long Source-to-Pay series, you need to pick a module that represents your most immediate need, start with it, and start to grow your platform from it.

Per Year, How Much Should You Outlay for a Multi-National Enterprise Source to Pay? Good Question! Poor Answer. 500K+

Whereas we were willing and able to put a real, actual, number, or a very tight range, for mid-markets, the situation gets more tricky for a multi-national enterprise with 1 Billion + in Revenue.

Why? Aren’t they using the same advanced tech as a large mid-market, except using advanced capabilities across the board? And, because of this, shouldn’t it max out at 500K? Well, yes, but there are additional considerations you don’t have in the mid-market.

[01] If you are using a lot of decision optimization, semantic analysis, network modelling, etc., then you are using a lot of computing power — that’s driving up the vendors’ hosting costs well beyond the mid-market. Now, at some point, it maxes out at costs on a dedicated machine basis, but it’s still higher.

[02] As a true multi-national enterprise, you are going to need a vendor that has extensive multi-lingual and multi-currency support in the product AND at the help desk when suppliers and third parties have difficulties using the solution to bid, provide information, submit invoices, etc. And while it’s only a one-time cost for a a suite built for true internationalization to add another language pack and currency, an enterprise that offers support in those languages usually has to add more headcount to support that language, and that adds cost.

[03] You’re not only going to have a larger Procurement team using it, but you’re going to have a decentralized global team with a lot more differentiation in capability, with a lot less people capable of being full DIY. They’re going to need more support on a regular basis, and you’re going to need to contract for this up front.

[04] You’re going to need a lot more data. You’re going to be subject to a lot more regulations and you’re going to need to collect, and verify, a lot of data on your partners and suppliers. A LOT of data. You’re going to need a number of data subscriptions on business identifiers, (beneficial) owners, and credit scores for verification that they aren’t on any embargo lists, involved in any legal suits, and acceptable to your insurance provider. Then you need data on their human/workers’ rights practices, compliance, and third party assessments for those countries with laws enforcing compliance and putting you responsible for your supply chain actions. Then you need Carbon/GHG data for countries with reporting requirements or limits. Then you need other ESG/Risk data for your own internal risk assessments. And so on. These subscriptions add up.

So even though the suite itself should still be within that 250K to 500K per year range, when you add up the additional support needs, additional data needs, and dedicated computing power needs, you’re going to double or triple that cost. That being said, before you sign on the dotted line, especially if the quote gets close to 7 figures (one million), you need to do your expected ROI calculation. If you’re not going to see at least a 5X ROI a year on a conservative estimate, with an expected ROI of 7X to 10X a year by years 2 and 3, you need to step back and decide if you need all the functionality, all of the support, and all of the data subscriptions you’re asking for / being quoted, and if so, if you’ve included the right vendors in your RFX for (a) technology solution(s). The reality is that you should NOT be paying a million plus annually for an extended S2P suite unless you’re getting the ROI.

Also, be sure to build that model in-house or engage a third party that is not a reseller or implementer of the suite you’re considering. First of all, their savings averages are not guaranteed to be applicable to your situation. Secondly, their manpower requirements, and reduction, averages might not be appropriate for your business either. Thirdly, because they often build their savings model as a rollup of savings models across the different modules / functions, many of these suite models often end-up double-counting resource time or savings numbers by way of their design.

(Please note our choice of wording here — “end up“. Usually the provider or consulting organization is not trying to deceive you, and they often don’t realize that their roll-up model is double counting. What we’ve seen happen is they take the best calculators they have access to (through consultant or analyst relationships) in each area they are selling in the suite — sourcing, SXM, CLM, etc. — and then roll them up. But they fail to understand that the attributions of a savings percentage in each model always favours the solution/module being sold, which may also assume some baseline functionality of another module. As a result, especially since the savings opportunity often changes based on what technologies are available and applied together, all the estimates will be “Best Case” for the selected modules, and when you add those up across five/six modules, you will sometimes get a total “Best Case” that is as much as double what is actually reasonable. For example, you can have a category where if you just applied spend analysis on the RFX you could identify 6% savings, if you just applied supplier risk profiling to the RFX and eliminated the high risk suppliers and then took the low bids you could identify 4% savings, and if you just applied strategic sourcing decision optimization you could get 10%, but if you applied all three you only achieved 9% (since optimization finds everything spend analysis finds, but the risk assessment resulted in the manual elimination of a high risk supplier that optimization didn’t catch, lowering the initially identified savings opportunity). Rolling up 3 separate models, it would produce a 20% savings opportunity when it was in fact 9%. Now, in other situations, the rollup could be worse than the actual of combining all three technologies, i.e. the RFX is projected to only identify 3% on it’s own and the negotiation module to save 3% on overheads, but the application of both to a targeted subset of suppliers which are deemed to be most willing to negotiate based on volume could allow for an 8% reduction. But overall, these rollups don’t average out and usually over-count.)

[Also, most vendors feel they have to do it this way since most buyers don’t buy all the modules and they don’t have enough average savings data across the application of all advanced modules to all categories to have reliable numbers. So you really need to do your own models based on your own situation and come up with realistic estimates.]

Depending on your current state of affairs, current market conditions, and technologies available that your organization is actually capable of utilizing, that could be an overall, estimated, cost reduction of 3% against all spend expected to be put through the platform in the first year, or it could be 5% (or more, or less). Even 3% is good if you’re spending 1 Billion a year, 500 Million is addressable, and you think you can address 20% of that, or 100 Million, the first year. That’s an estimated savings of 3 Million, and if your year 1 cost was 750K, that’s reasonable with an ROI of 4X, especially if you think increased efficiency will come in year 2 with familiarity, that you will address 200 Million in year 2, and increases the estimated savings percentage to 4%, which would be 8 Million savings in year 2, and an 8X multiple even if you needed to add more data subscriptions and support, bringing the total solution cost up to One Million.

Probably not the answer you wanted, since the mid-market looks to be getting off cheap, but they are also spending less as an organization, addressing less of that spend, dealing with fewer volume or consolidation opportunities, fewer resources to tackle the mid-size categories, and losing on the tail since they can’t effectively manage it beyond catalogs, budgets, and hoping the 3-bids and a buy are fair (and not rigged through collusion). They might pay less for their S2P solution suite, but their total savings potential is also (considerably) less and, thus, their typical ROI is limited compared to yours.

But, well chosen, at least you’ll get an open, modern, usable solution for One Million dollars per annum — not something you can say in all areas of enterprise software.

The 39 Steps … err … The 39 Clues … err … The 39 Part Series to Help You Figure Out Where to Start with Source-to-Pay

Figuring out where to start is not easy, and often never where the majority of vendors or consultants say you should start. They’ll have great reasons for their recommendations, which will typically be true, but they will be the subset of reasons that most benefits them (as it will sell their solution), and not necessarily the subset of reasons that most benefits you now. While you will likely need every module there is in the long run, you can often only start with one or two, and you need to focus on what’s the greatest ROI now to prove the investment and help you acquire funds to get more capability later, when you are ready for it. But figuring out how much you can handle, what the greatest needs are, and the necessary starting points aren’t easy, and that’s why SI dove into this topic, with arguments and explanations and module overviews, both broader and deeper than any analyst firm or blogger has done before. Enjoy!

Introductory Posts:
Part 1: Where Do You Start?
Part 2: Where Should You Start?
Part 3: You Start with …
Part 4: e-Procurement, and Here’s Why.

e-Procurement
Part 5: Defining an e-Procurement Baseline
Part 6: There are Barriers to Selecting an e-Procurement Solution (and they are not what you think)
Part 7: Over 70 e-Procurement Companies to Check Out

Interlude 1
Part 8: What Comes Next?

Spend Analysis
Part 9: Time for Spend Analysis
Part 10: What Do You Need for A Spend Analysis Baseline, I
Part 11: What Do You Need for A Spend Analysis Baseline, II
Part 12: Over 40 Spend Analysis Vendors to Check Out

Interlude 2
Part 13: But I Can’t Touch the Sacred Cows!
(including Over 20 SaaS, 10 Legal, and 5 Marketing Spend Management / Analysis Companies to Check Out)
Part 14: Do Not Stop At Spend Analysis!

Supplier Management
Part 15: Supplier Management is a CORNED QUIP Mash
Part 16: Supplier Management A-Side
Part 17: Supplier Management B-Side
Part 18: Supplier Management C-Side
Part 19: Supplier Management D-Side
Part 20: Over 90 Supplier Management Companies to Check Out

Contract Management
Part 21: Time for Contract Management
Part 22: Contract Management is a NAG: Let’s Start with Negotiation
Part 23: Contract Management is a NAG: Let’s Continue with [Contract]Analytics
Part 24: Contract Management is a NAG: Let’s End with [Contract] Governance
Part 25: Over 80 Contract Management Vendors to Check Out

e-Sourcing
Part 26: Time for e-Sourcing
Part 27: Breaking Down the ORA of Sourcing Starting With RFX
Part 28: Breaking Down the ORA of Sourcing Continuing with e-Auctions
Part 29: Breaking Down the ORA of Sourcing Ending with [Strategic Sourcing Decision] Optimization
Part 30: Over 75 e-Sourcing Vendors to Check Out!

Invoice-to-Pay (I2P):
Part 31: Time for Invoice-to-Pay
Part 32: Breaking Down the Invoice-to-Pay Core
Part 33: Over 75 Invoice-to-Pay Companies to Check Out

Orchestration:
Part 34: How Do I Orchestrate Everything?
Part 35: Do I Intake, Manage, or Orchestrate?
Part 36: Over 20 Intake, [Procurement] [Project] Management, and/or Orchestration Companies to Check Out
Part 37: Investigating Intake By Diving In to the Details
Part 38: Prettying Up the Project with Procurement Project Management
Part 39: Deobfuscating the Orchestration and Fitting it All Together

Source-to-Pay+ is Extensive (P36) … Here are some Intake/Orchestration Vendors

As promised in our last installment, Part 35, here is a partial, starting list of intake/orchestration vendors that provide one or more of the following capabilities:

  • Intake management (and requester/stakeholder visibility into the process)
  • Project/process management throughout the source-to-pay cycle
  • Orchestration between multiple applications

As with other every list, we must inform you that this list is in no way complete (as no analyst is aware of every company — and sometimes a new company launches its first product, or a new product literally after one of these lists goes up), is only valid as of the date of posting (as companies sometimes go out of business and acquisitions happen all of the time in our space), and does not include vendors which have project management limited to just one (or more) of their internal modules.

As with our lists of e-Procurement Companies (in Part 7), Spend Analysis Companies (in Part 12), Sacred Cow Companies that do, or support, customized “spend” analysis on Marketing, Legal, and SaaS (in Part 13), Supplier Management Companies (in Part 20), Contract Management Companies (in Part 25), and e-Sourcing Companies (in Part 30), and Invoice-to-Pay/Accounts Payable Companies (Part 33), we provide the company name, URL and LinkedIn URL if available, headquarters country, and list other offerings we are aware of.

Remember that if we say Source-to-Pay, it means that vendor offers modules that cover (baseline) Sourcing, Supplier/Vendor Management, Contract Management, Spend Analytics, e-Procurement, and Invoice-to-Pay/Accounts Payable. As to whether or not SI would consider these modules meeting the majority of baseline functional requirements, you will have to check the previously published starting vendor lists in those areas and other prior coverage on SI (if available).

Do your research, and reach out to an expert for help if you need it in compiling a starting list of relevant, comparable, vendors for your organization and your needs. For many of these vendors, good starting points might be the Sourcing Innovation archives, Spend Matters Pro and Gartner Cool Vendor write-ups if any of these sources has a write-up on the vendor.

And while this list is currently (much) smaller than the other lists, as it’s pretty easy to find at least 60 vendors for any core module you want in Source to Pay, and we barely cracked the twenties with this list, we don’t expect it will stay that way for long!

Shout-out to The Revolutionary and The Procurement Dynamo for their thoughts on what vendors might fit into this emerging category!

Finally, a second reminder that inclusion on this list DOES NOT imply Sourcing Innovation is recommending the vendor.

Company LinkedIn
Employees
HQ (State) Country I P O Other Offerings / Notes
Arkestro 98 California, USA O e-Sourcing
Celigo 720 California, USA O Integration Platform, App Marketplace
Cirtuo 40 Austria P Category Management, Supplier Management
Focal Point 26 Georgia, USA I O
Graphite Connect 66 Utah, USA I Supplier Management
Ivalua 912 California, USA I P Source-to-Pay
Kissflow 528 Delaware, USA O e-Procurement, I2P/AP
LevelPath 22 California, USA O
Mercell Negometrix ?? Netherlands I e-Sourcing, Supplier Management, Contract Management, e-Procurement
Omnea 16 United Kingdom O
Opstream 13 New York, USA I New York, USA
Oro 60 California, USA I Supplier Management
Pega 6081 Massachusetts, USA O
Pipefy 580 California O
Qntrl 16 India O
ServiceNow 23,206 California, USA O e-Procurement
Spend HQ Per Angusta 53 France O Spend Analysis, ESG
WorkFridge InGeek 7 India O
ZFlow 8 California, USA O
Zip 351 California, USA I e-Procurement, I2P/AP
Zycus 1607 New Jersey, USA I P Source-to-Pay

We aren’t done yet … we dive deeper into the capabilities required starting in Part 37.

Source-to-Pay+ is Extensive (P35) … Do I Intake, Manage, or Orchestrate?

In our last installment, Part 34, we noted that, after working through our series, many of you would likely have selected a number of best-of-breed solutions to meet your various need as opposed to a suite (due to unique capabilities that were attractive to you, attractive price points, quick setup times, etc.). And after selecting a few of these, you got to wondering “what’s the best way to integrate these and make sure that, once I have a full set, they support my source-to-pay processes end-to-end in a seamless fashion“. The point of these solutions is to control costs in an efficient, and effective fashion, and this requires effective management of requests, communication, projects, and/or processes.

Plus, even if you selected a suite, even when you finish implementing the last of the six core modules we’ve covered to date in our series, that’s just the beginning … since you will eventually have to enrich your data, deal with ESG/CSR, integrate with services management, asset management, logistics and supply chain management and support other features these core modules won’t have in order to get to the next level of enterprise buying.

In other words, you need to intake requests, manage projects, and/or orchestrate your technology-enabled processes, depending on what the modules/suite you have does and doesn’t do and what your particular situation warrants. Let’s discuss what each of these capabilities are and what a few core features are (especially since you won’t yet find a platform that does it all and does it all well, at least not yet, as intake and orchestration are rather new solutions).

Intake Management

Often known as intake-to-procure or intake-to-pay, this type of solution focusses on allowing anyone in the organization who has a procurement need to make a request which goes to Procurement, get visibility into that request, and know it will get done because the solution allows a buyer to turn a request into a procurement project. Key capabilities:

Configurable Enterprise Procurement Request Portal ANY Employee can Access
In order to make a procurement request for whatever they need, be it resupply of the local office supply closet, special materials and promotional items for an event, short-term services, a restock of materials needed for MRO, or new products for resale to meet (new) client needs. And the interface must be capable of being configured in a way that ensures that whatever information the buyer needs to fulfill the request will be collected before the requester can complete the request (such as high level categories, any budgets [codes] they have, whether or not any of the needs can be met with current contracts / catalog items, etc.).
Request to Project
Once the buyer analyzes the request, they must be able to flip that request into a Sourcing Project, a re-negotiation/Contract Addendum with a current supplier, a catalog buy, or a PO-against a current contract (or whatever else is needed) in order to begin the process of filling that request (or, if the request is not valid, deny it and flip it back with a rejection or a request for modification into a request that would be acceptable).
Process Visibility and Messaging
At all times, the buyer must be able to see where the request is: in queue, approved, being sourced/procured, order placed, goods arrived, invoice paid, process done; etc.

Project Management

The capability to manage a project from beginning to end, no matter how many steps it has, how many modules are required, how many approvals are needed, how many obligations need to be tracked, and how many milestones need to be completed.

Standard Project Management Functionality
The ability to create phases, milestones, tasks, owners, obligations, and track progress throughout the project timeline is a core must. Basically, what you would expect any other project management tool to do.
Links into the appropriate modules from each step of the project.
If all you can do is define and track project steps, you might as well use an open source project management tool. It’s only useful if it allows you to jump into the right screen of the right tool for where you currently are in the process.
Configurable approval flows
The platform should enforce verifications that obligations are met, milestones are completed, and quality is acceptable before projects are allowed to advance.

Orchestration of Processes

The capability to easily integrate as many modules as you need into a configurable workflow that suits your specific organizational processes.

Easy Self-Serve Module Integration
A buyer should be able to select the supported applications that they own, enter their license codes, and it should automatically integrate with the orchestration tool. In addition, they should be able to integrate additional modules easily with
Low-Code Integration
Where a buyer can define the API link, the core data tables/objects, the entry screen links, and that is sufficient for pushing data into the application / extracting processed data out, launching the application, and integrating the new module into process workflows at a high level.
Workflow Automation
The entire idea of process orchestration is to support the right workflows to support the various sourcing, contracting, onboarding, procuring, developing, payment, and other source-to-pay projects the procurement organization needs to undertake.

Of course, these platforms should do more and have more, but these are the core foundational requirements to be classified as an intake, project management, or orchestration solution.

In our next installment [Part 36], we’ll provide you with a list of the solutions available today.