Category Archives: Technology

Bells and Whistles Lead to Cells and Thistles! Part I

I’ve been hearing and seeing two things lately:

  • smaller vendors telling me they’re struggling to close / losing deals because their potential customers are telling them they are leaning towards the bigger/splashier vendor with more “Bells and Whistles”
  • vendors getting lots of (and possibly too much) funding are focussing heavy on bells and whistles (because they believe it will help them sell fast and meet the significant, and often unrealistic, sales targets of the investment firm[s])

So I have to address this because if you select a solution based on bells and whistles, expect to end up in a cell while your fingers bleed from the thistles that prick you every time you try do something that’s not the primary, simple, use case. This then leads to usage of your purchase declining quickly, causing you to end up with another piece of shelfware before you get even halfway through the initial contract subscription.

Now, to help you understand I’m not making this up for clicks and shares, we’re going to dive into some of the most common bells and whistles and why, in the best case, they’re a complete waste of money and, in the worst case, the thorn prick will end up being so painful that your team will simply stop using the software. We’re going to do this across source-to-pay.

Intake

Everyone’s gotta have it because, apparently, it’s brand new and Zip invented the category a few years ago. This is, of course, complete bullsh!t because

  1. Coupa has had full intake since Procurement Independence Day in 2006. You just didn’t know because when Robbie took over the Coupa factory, licensing switched from enterprise size to per user, and the cost was too much to give non-Procurement users a license so you didn’t see the intake that was there. (And to that effect, if Zip is pricing per user, how is this better?)
  2. Zycus had one of the first modules dedicated to intake, iRequest, over a decade ago

Moreover, everyone has to have Gen-AI intake, because, apparently, using a few drop downs to figure out what a user wants is too difficult for the average iZombie who has been zombified by ChatGPT over-dependence.

While this is useful to parse an initial request from a user — do they have a question, want a report, or want to make a requisition (and if so, is it from a catalog or do you have to go to market) — beyond that initial parsing (which will never achieve an initial parsing accuracy beyond 90%, so at least 1 in every 10 requests will have to be rephrased for the system to get it right), it goes from useful to painful to useless.

Here are a few examples:

  • Policy Question: as we’ve said before, Gen-AI has two strengths: large corpus search and summarization and natural language processing; in this circumstance, if the success rate is 90%, it’s mostly useful, but to be honest, if you know the right terminology, elastic search will work just as well, retrieve the exact clause, and never hallucinate a response. Summary: sometimes useful.
  • Catalog Buy: good luck with this because you’ll spend at least 5 minutes trying to order a box of gloves, and I kid you not — see this post where we illustrate how it will take you five minutes to explain to the Gormless AI what you want when you could place an order in a well-defined catalog in 15 seconds with 3 words, 1 number, and 4 clicks. Nothing will drive your users to maverick purchasing off of Amazon, BestBuy, and even Walmart faster than a Gen-AI intake portal. Summary: painful.
  • Analytics Request: while it’s great for a simple “how much am I spending on supplier S” (especially if that total exists in a spend cube), the fact that Gen-AI is very bad at math (to the point that you can ask the same question twice in a row and get a different answer), and not so great at parsing very specific requests such as how much did we spend with supplier S on steel products last quarter which makes it all but useless — even Gartner, the ring leaders of the Gen-AI lovefest, have predicted that “conversational analytics” will completely leave the ProcureTech vernacular in two years. Summary: useless.

… but this is just the beginning. We’ll continue with the Source to Pay process in Part II.

In ProcureTech, Stop Caring What Gartner, Forrester, or IDC Thinks!

I shouldn’t have to address this again, but every year multiple vendors reach out and ask how to get on these vendors maps because they believe it’s the only way to get more market visibility and/or be selected by certain customers, including you. It’s not the only way to get visibility and if a vendor can’t convince a potential customer from thinking that only map companies are good, I’ll tell them this right now — that’s not a customer they want (because that vendor will be out on the renewal with whatever vendor overtakes them in the map when the CPO changes in 3 years, because companies without vision to look beyond a meaningless map don’t keep real talent, and only real talent will identify and select the best solution and ensure that solution is kept over time).

But I digress — this post is about you, the potential customer, and why you need to STOP caring what Gartner, Forrester, or IDC thinks.

First of all, we’ve said it before, and we’ll say it again: It’s NOT the Analyst Firm. It’s the Analyst!.

In addition to all of the skillsets and education that an analyst needs to have to get it right, which we covered in detail in that post, the analyst needs a lot of relevant experience, and history in the ProcureTech space, to make sense of the ProcureTech world today. Ask yourself: how many of the analysts with the right education have at least 10 years in our space? The answer is very few. How many have 20 years in (independent) analyst roles? You can count them on your fingers. I know of myself, Jon Hansen, Pierre Mitchell, and Chris Sawchuk with 20 years of (independent) analyst experience in our space and a deep technical (STEM) education. Everyone else who started covering this space day in, day out two decades ago has moved on or retired. Now, of these analysts, how many have also built actual solutions in the ProcureTech space, connecting the dots between the education, theory, and practice? Two of us — myself and Jon Hansen. (But we should note that Pierre and Chris spent part of their careers on solution advisory consulting and implementation guidance, and have deep knowledge about the implementation and integration requirements, which is also very unique and useful in technology selection.)

Now remember the second point: Vendors Have Lured Big Analyst Firms Astray and that you’re not getting a map of the best solutions, but the best solutions from the analyst firm’s pool of vendor sponsors and research subscribers, where the reality is that only the big, established, cash-rich companies can afford the high-priced subscriptions that keep them in front of the overworked analysts who have to spend over half of their time taking inquiries or keeping high paying subscription customers happy. (Whereas analysts at smaller firms or independents get to focus on studying and understanding the solutions, not general inquiries or whether or not the contract [or pricing model] is good.)

This means that these big firm analysts are not spending a lot of time, if any, looking at the up-and-coming mid-sized companies that have not only been around long enough to develop mature enterprise solutions, but solutions that are more modern, more powerful, more usable, and more intelligent (with embedded analytics, RPA, and the right AI for the task at hand), and possibly (much) better for you. Moreover, if the enterprise is a mid-market company, or able to go with a best-of-breed as a bolt-on to their enterprise ProcureTech platform, they’ll never know about the majority of these solutions (as only the overfunded startups will have the money to get the big analyst firm attention, and these vendors often have more financial stability problems than the smaller vendors who are bootstrapping or taking minimal funding and actually have stable, happy, paying customers keeping them afloat).

Third, and most important, it’s not the best rated solution, it’s the best solution for your organization. Not only is it the case that this solution is very likely not on a map of only 20 companies (when there might be 100 companies that offer that solution), but it might also be the case that it is the lowest ranked solution on those maps — especially when these maps tend to rate solutions on a lot of subjective factors that match what the analyst thinks are the most relevant for an average organization, whereas you are a specific organization which has a specific set of relevant factors that you care about, with specific requirements for those factors. The more divergence between your factors and the analysts’, and your scale and theirs, the worse the map is for your needs, and the worse the solution you select will be.

The only maps you should care about are those that rank solutions solely on the tech capabilities and/or the customer rankings. But only so far as potential solution identification, not selection. Maps that concentrate on pure tech (like Spend Matters Solution Map) allow you to identify vendors that have the tech foundations, giving you a starting pool, but don’t allow you to identify vendors that have a solution — because a solution is tech and appropriate process support and integration capability and support and culture and whatever else transforms another piece of potential shelfware into a solution that will be used daily by your employees.

Note that we used the word “potential” for a reason. No map (including Spend Matters) is complete, so you will need to look at multiple sources (like ProcurementSoftware.site and the upcoming Art of Procurement ProcureTech 100) to put together a complete list of vendors to consider. Then you will have to cross reference with real analyst vendor write-ups (which can include the hundreds of write-ups here on this site if one or more of your potential finalists are included) to whittle down that list to the best starting set for your best practice technology RFP (of which we have a lot of advice on how to write that on this site as well).

At the end of the day, it’s about what solution will work for you, not about which solution is on which map!

Best Practice Vendor Selection for True Multi-Nationals 2025 Reprise Part V: Stuck with an ERP or outdated S2P suite? You do have options!

This is a repost and reprise of a series that last ran (for the second time) in 2015. It’s as relevant, and important, today as it was then, if not more so, thanks to the I2O Hype and AI BS!

Despite claims to the contrary, you are not stuck being a sap or following prophecies from an ethylene-gas inhaling delphi. You do have options. Acquisitions might have some analysts in a tizzy, but you only need to remember one thing. Don’t Panic.

It’s been over a decade since the acquisitions of Ariba & Emptoris, which kicked the M&A mania in our space into super high gear for the first time.
They were not the only best-of-breed suite game in town then, and they certainly aren’t the only best-of-breed game in town now, especially since the latter was retired by IBM a mere five years after acquisition. In fact, for many companies that have been acquired in our space over the years, SI would argue that they are not even in the best-of-breed category as the lengthy integration cycles required to integrate them into their acquirer’s platforms slowed down development and now there are only a few module or functions left that, in SI’s opinion, are still best-of-breed. However, there are lots of other options, and these options exist on both sides of what the Brits call the pond. (For you Americans, that’s the Atlantic Ocean.)

Best of Breed vendors eat, sleep, and drink sourcing, procurement, and supply management
Unlike do-it-all suites or ERP vendors, best-of-breed supply management vendors are focused entirely on a critical supply management process and, as a result, they tend to be much better at it than do-it-all or ERP vendors, especially supplier enablement, which we all know fuels the e-procurement benefits engine. (And whatever you do, don’t confuse supplier enablement with supplier experience or confuse vendor marketing with actual supplier experience — some vendors who market supplier experience actually excel at the working with the supplier experience which means the platform makes buyers happy, but suppliers [much] less so.)

Best of Breed on an ERP backbone can offer significant advantages

  • Best of Breed providers often know the strengths and weaknesses of ERP systems they are replacing (or augmenting) better than the consulting implementation partners, who care more about if they can weasel their way into long-term strategy consulting than a successful implementation. (For example, there are now a number of vendors with over 100 customer SAP implementations who know the system way better than a Big 5 consultant on his second implementation project ever will.)
  • Best of Breed providers have enabled hundreds of thousand of suppliers, maybe more, over the years … in all regions of the world … your 13,470 suppliers aren’t going to make them flinch (and they will be faster and cost less, because once again, they, or their carefully selected and trained integration partners, have been there, done that … a few hundred or thousand times.)
  • Best of Breed provider’s customers are all former ERP e-procurement / consulting implementation customers … that’s right, most of whom have already failed using the ERP/consultant approach, spent the millions, got 7 punch-outs and 11 catalogs implemented … now they spend hundreds of thousands and get … well, you already know … actual results and benefits. And the Best of Breed learns from those customers!
  • Best of Breed providers have to be better than the ERP or broad portfolio providers, because they can’t fall back on their CRM sales or app server license revenue if they don’t deliver.
  • And because of all of this, Best of Breed providers have way more references than the ERP providers. Those big ERP guys based in Germany have a handful of significant e-procurement references at best … because they’ve already lost most to specialist providers with better systems.
  • Best of Breed providers’ SaaS-type offerings and supplier networks minimize or eliminate the need for your IT department or external consultants to be involved, so they implement faster and less expensively
  • The most successful Best of Breed providers have service organizations or carefully selected service partners around the globe to assist with implementations and provide stability.
  • Best of Breed providers fill in the gaps where ERP falls short. ERP may try, but it is not all-in-one and they are usually years or more (and sometimes a decade) behind the Best-of-Breeds functionality-wise.
  • Best of Breed works and they have the client stories to prove it. Follow SI’s advice, verify their offerings, check their references, and find the right one for you.
  • Best of Breed will help your SUM (Spend Under Management) soar.

Consider your options carefully. A Best of Breed solution on your ERP backbone might be the best decision you can make.

Best Practice Technology Vendor Selection for True Multi-Nationals 2025 Reprise Part IV: Open the Doors for a Truly Successful RFX

This is a repost and reprise of a series that last ran (for the second time) in 2015. It’s as relevant, and important, today as it was then, if not more so, thanks to the I2O Hype and AI BS!

In the first three parts of this series we discussed the proper RFX process to follow when attempting to select a technology(-based) solution provider (for e-Procurement, e-Sourcing, and Supply Management solutions in particular) as a true multi-national. We noted that while most companies more-or-less understand the high level process, most get the implementation wrong, focussing too heavy on feature-function checklists (that are usually put together by vendors, even if they are obtained from third parties), technology buzzwords (like AI, Intake, and Orchestration) and too little on the core processes that need to be effectively supported and a vendor’s global implementation and support capabilities.

If your organization follows the advice presented, starts with the customer references, and only spends time and energy conducting a detailed review of those vendors with a track record that suggests that the vendor has a solution that will support your core processes and could meet your global implementation and support needs, then your organization is off to a great start. But this isn’t the only best practice that your organization should be following in the selection of a vendor for your global technology needs. In this post we’ll cover five more.

The Core Solution Litmus Test
Once the vendor has passed the core process and customer litmus test, the next litmus test is the core solution requirement litmus test. After dividing all of the stakeholder problems into must solves, should solves, and nice-to-solves, re-validate that the vendor has solutions (technology, services, or a combination thereof) that address each of the must-solve problems and most of the should-be-solved problems. The vendor is not right for you unless it is a global, cultural fit that brings the right solutions. (Remember, there’s no checking feature/function boxes at this step!)

Third-Party Claim Verification
Most vendors will make big claims in terms of their platform capabilities. Just like a vendor’s ability to serve your organization globally should be challenged and verified with customer references, so should its ability to fill your technology gaps. Not only should you talk to their partners, but talk to analysts, bloggers, and other third-parties they have interacted with and whom have seen (part of) their solution.

Open Book Negotiations
In addition to third-party claim verification, don’t be afraid to force a vendor to prove every claim, statement, and assumption. This should not stop at current, successful, customer references. The vendor should let you speak to analysts it has relationships with, consultants who have implemented their solutions, auditors to verify their financial stability, and even ex-customers if asked.

End-To-End Total Cost of Ownership Elucidation
What is the true cost of the solution to your organization AND your supply chain? This goes beyond the end-to-end platform cost, as discussed in this classic post on Cost Model Calculations in SI’s “Enterprise Software Buying Guide” series, but also includes any costs that will be borne by your supply base. It’s often the case with e-Sourcing/e-Procurement/Supply Management solutions with Supplier Information Management, Supplier Portal, or Supplier Network functionality that a vendor will charge your suppliers an access fee, which can sometimes be hefty. An access fee that is just going to hit your organization with interest in a year when your suppliers raise their prices to cover the fees you caused them to incur. In Procurement, a penny saved today at your supplier’s expense often translates into a dime spent tomorrow. (And if you don’t believe me, then you need to work on understanding the cost of capital throughout your supply chain. Remember that sound, conventional financial management is NOT good for supply chains.)

Open Finals*
Typically, the final negotiations in this space are more secret than what goes on beyond closed doors at Area 51, scientology headquarters, and the back room of the club where Wall Street mega deals really happen. This is dumb. Really, really dumb! Blind auctions may be okay when buying commodities, but it’s the last thing an organization should do when buying a critical piece of functionality where a failed implementation will cost (tens of) millions of dollars or more in overspend and opportunity costs. Not only should each vendor be aware of whom it is up against, but vendors should be asked to promote their strengths and counter their opponents weaknesses. They should be instructed to tell the truth, even when asked tough questions (about customer retention and defection to a competitor), and (severely) penalized for false answers (and if they try to bypass you by going straight to the CFO or CEO, they should immediately be disqualified from the competition).

Remember, good vendors are honest, especially about the occasional (big) mistake that they made in the past, learned from, and put measures in place to prevent ever repeating it. And the best vendors will get up and walk away as soon as they realize they are not the solution for you (because they thought you needed primarily e-Sourcing functionality and they are mainly e-Procurement for example) and that it would take too long or cost to much to tailor it to your needs. (And these are the first vendors you should go back to as soon as you have needs that they can fulfill. As we said in a prior post, there is no perfect solution, or even anything close, but a vendor who is completely honest about what they do and willing to work with you to solve your problems is the best vendor for you, not the vendor with the most extensive system today [who may have stopped new development entirely and is just selling what they have].)

If your organization implements the best practices covered in this series, then chances are that it will have no choice but to prepare for success!

* Nothing to do with tennis, folks!