Category Archives: SaaS

Top 10 Ways to be Labelled as a (Procure)Tech Noise / TroubleMaker!

For those of you who want to be a noise maker, trouble maker, Debbie Downer, complainer, etc. etc. etc., the doctor can confidently tell you that these are ten proven ways to accomplish that goal! Enjoy!

10. Point out that Tech Failure Rates have reached an all-time high of 88%! (Bain)

(As it is, in Procurement, We Don’t Get No Respect. We’ll get even less if 9 of every 10 projects fail! They’d fail less if … )

09. State that that RFPs for Tech should be Affordable!
(They are a critical first step in proper vendor selection once your need has been identified, and skipping this step has always proven disastrous. And then, after you select the vendor, the next step is to kick of Project Assurance, so the implementation doesn’t go off the rails.)

08. Go further and suggest that Big X SHOULD NOT be used for analytics and AI!
(The reality is, as we’ve stated again and again, limited tech talent is generally NOT interested in consulting — they want to work with the big powerful mega-corps [Meta, Alphabet, etc.] or join the wild west start-up frontier. Those not good enough get scooped up by the consultancies to try and fill the bench they need to staff the projects they sell. Doesn’t matter how good the outdated playbook is if you’re starting with the B-Team if you’re big, and rich, enough to afford it … or the C-Team if you’re not. Also, as we’ve said before, this doesn’t mean you shouldn’t use Big X for strategy, internationalization advice, etc. or the roots where they started where they have, and attract, the best people — just that, like every business decision, you have to be smart about where, and how, you engage to get your ROI. In fact, there are a whole slew of areas we generally recommend Big X for, and sometimes ONLY recommend Big X for, and these are covered in When Should You Use Big X?)

07. Dare to suggest it may be the end of an era for an early ProcureTech suite!

(Is The Third Act the Final Act?) Let’s ignore the fact that there has been more consolidation and failure in this space over the last two decades than anyone realizes, and that the seven suites appear to be sailing the seven seas without a sextant [foreshadowing?]. See SI’s classic Vendor Day Reprise and count how many of those companies are still around as-is. These were representative of the cream-of-the-crop when they were covered. The rate of disappearance is actually higher across the board!)

06. Note that Gen-AI is way overhyped.

(Unless you want suicidal people committing suicide in suicidal self-driving cars, for example. See valid uses for Gen-AI. And note that one of the big analyst firms pushing it in its hype cycle also noted that that it’s failure rate is 85%! [Source])

05. Remind people that intake & orchestrate is not new!

(With intake in ProcureTech tracing its beginnings back 24 years and orchestrate tracing it’s way back over 50 years as it’s just the fancy new name for middleware, which was a term coined in the 60s and implemented in the late 60s/early 70s with RPC being one of the earliest examples. See Point 11 for more hard truths.)

04. Rail against 2*2 vendor maps, and logo maps, as vendor selection tools!

(They are NOT Appropriate for Tech Selection. At most, they can be used to identify vendors to shortlist — but you still need to create a proper RFP! Remembering that:)

03. FREE RFPS are NOT free!

(How many times do we have to tell you There Are NO Free RFPs? Too many, since vendors will NOT get the message!)

02. State that there is no demonstrable ROI for attendees and vendors at big (Procure)Tech events.

(We need better events. A great experience is not business ROI!)

01. Mathematically argue that no business is worth more than a 10X multiple at investment time.

(‘Nuff said. Deeper dive in linked article.)

Now, I don’t know about you, but if wanting

  • (10) tech project success,
  • (09) affordable RFPs for all Procurement departments that need them,
  • (08) value for your consulting dollar,
  • (07) a true picture of the ProcureTech space and where the best cost/value ratio is for all buying organizations (not just G3000s),
  • (06) real AI powered by real HI that delivers real value,
  • (05) solutions that do what they should with (true) open APIs,
  • (04) real solution guides,
  • (03) valuable RFP advice,
  • (02) valuable events for all (not just organizers and consultants), and
  • (01) fair investments across the board for underfunded ProcureTech companies

means being a troublemaker, then make me the leader of the troublemakers! I’ve had enough of platform failures, enough of marketing soundbites, enough of one-way sales, enough of vendor marketing packaged as analysis and advice, and enough BS. Without procurement, there is no business. And, like Rodney Dangerfield, who unfortunately never got it in his lifetime, we deserve a little respect.

Procurement deserves better!

P.S. If you lead a provider organization that wants to do better, please feel free to reach out!

Two and a Half Decades of Project Failure

  • 2024 Bain: 88% of business transformations fail to achieve their original ambitions (Source)
  • 2023 HBR: Some estimates place the failure rate as high as 80%.
  • 2023 Gartner: states that 85% of AI projects fail. As well, 87% of R&D projects never get to the production phase.
  • 2023 EY: 2/3 of senior leaders have experienced at least one underperforming [digital] transformations in the last 5 years (Source)
  • 2020 Standish Group: 66% of technology projects end in partial or total failure (based on the analysis of 50,000 projects globally). 31% of US IT projects were canceled outright and the performance of 53% ‘was so worrying that they were challenged.’ (Source)
  • 2020 McKinsey: 17% of large IT projects go so badly that they threaten the very existence of the company (Source)
  • 2020 BCG: 70% of digital transformation efforts fall short of meeting targets (Source)
  • 2020 KPMG: 70% of organizations have suffered at least one project failure in the prior 12 months (Source)
  • 2019 Everest Research Group: 78% of enterprises fail in their digital transformation initiatives (Source)
  • 2018 PWC: 75% of digital transformations fail to generate returns that exceed the original investment (Source)
  • 2018 Standish Group: only 29% of IT project implementations are successful, and 19 percent are considered utter failures (Source)
  • 2017 Gartner: 75% of all ERP projects fail (Source)
  • 2016 Innotas: 55 percent had a project fail in the last 12 months (Source)
  • 2015 Genpact: more than 66% of digital transformations fail to meet expectations (Source)
  • 2013 Innotas: 50 percent had a project fail in the last 12 months (Source)
  • 2012 McKinsey: large IT projects run 45 percent over budget and 7 percent over time, while delivering 56 percent less value than predicted (Source)
  • 2011 HBR: average project cost overrun is 27%, 1/6 projects is a black swan with a cost overrun of 200% or more Source
  • 2011 Forrester: 70% failure rate of change management initiatives (Source)
  • 2010 Deloitte: only 37% of projects delivered the functionality on time and budget meaning that 63% of projects failed to some degree (if not entirely) (Source)
  • 2009 Standish Group: failure in 68% of projects is probable (because success in 68% of projects is “improbable”) Source
  • 2001 Standish Group: 52.7% of projects will cost 189% of their original estimates and 31.1% of projects will be canceled before they ever get completed (Source)
  • 2001 Robbins-Gioia Survey: 51% viewed their ERP implementations as unsuccessful while 46% did not feel the organization understood how to use the system (Source)
  • 2001 Conference Board Survey: 40% of the projects failed to achieve their business results within one year of going live those that did achieve benefits had to wait (at least) six months longer than expected (Source)
  • 1999 Gartner: 75% of e-business projects will fail to meet the business objectives through 2002 (Source)

Is it just me, or is it the case that:

  • many of the firms who have been chronicling project failures for over two decades are also
  • many of the firms that have been guiding IT projects for over two decades?

Always Start Your Vendor Qualification with a Deep-Dive Demo!

In a recent article, THE REVELATOR asked how many practitioners do a pre-demo discovery call to determine whether seeing a demo is even warranted??

It was a fair question, but for most practitioners, the question is unnecessary because,

  • if you agreed to the demo as a practitioner, then you should have confirmed from the initial sales call that there was enough to actually see (by listening to a rep that sold a solution, not software, and that answered your tough questions);
  • the demo will tell you if it’s worth diving into the vendor’s background, philosophy, and services approach; and, most importantly,
  • if you’re not a senior executive at a large enough company, there’s no way you’re going to get the attention of the right people for that discovery call. (As a [perceived] unqualified lead, you’re not getting a senior person on that pre-demo interview … just a Sales VP who knows what to say to hook you, whether it’s true or not!)

The reality is that any discovery beyond an initial demo to confirm the vendor actually has a solution and, more importantly, a solution that might actually help you by solving some of your problems, is meaningless. Company history, philosophy, and go-forward don’t matter if they don’t have anything worth working with them.

It’s important to remember that technology cannot overcome a solution provider’s misaligned business values and goals. If the tech is wrong (or just not there), the tech is wrong. Not only do you need real tech (and not vapourware), but you need tech that solves one or more problems you have.

As such, if you dig in on a company before seeing the tech, you could be wasting your time. Especially if you do it for every provider given that you will likely go through half a dozen potential providers before you even find one worth to include in your RFP (when you consider all the overhyped marketing and misleading marketing you need to work your way through).

Moreover, forcing a demo early will quickly cause some vendors (without a solution) to self deselect! If you insist on a demo that shows how they solve the problems they claim and how it’s relevant to you, and they don’t have a deep solution and/or knowledge of your industry, they will likely decide it’s not worth the time trying to bluff you and save you the time and effort of invalidating them as a potential provider. (And, in effect, bypassing the technology-led equation-based providers off the cuff, since they won’t even get the demo if they can’t convince you they are about solving problems first and tech second.)

However, if you get through the demo, put the vendor on your shortlist, and tell them that, you can be sure your follow-up company deep dive call will include the right senior people at the vendor, and not just a say-what-you-want-to-hear Sales VP.

Which Solution Provider Do You Want To Work With? NONE OF THE ABOVE!

In a recent LinkedIn Post, THE REVELATOR asked:

Under which category does your solution provider demo fall?

  1. ? Selectively Stealth With A Reason
  2. ? Smoke And Mirrors
  3. ? Courageous Dreamers

And, more importantly, which one would you, as a practitioner, prefer to work with?

the doctor, who has reviewed over 500 solutions in our space over the last two decades (and interacted with considerably more vendors than that) answered for you:

  • ???? ?? ??? ?????!

a) Selectively Stealth vendors are either

  1. considerably overrating their solution against the market (usually due to lack of homework) or
  2. hiding their solution because they know there is absolutely positively nothing unique about their offering (which is NOT a bad thing if it is easier to use, quicker to implement, better supported, and cheaper than competitors, but if that was the case, why would they be stealth?)

b) Smoke and Mirrors are

  1. greatly overselling a significantly underperforming solution (and usually trying to gouge you with a high price tag while they are at it)

c) Courageous Dreamers are

  1. selling you on a vision they may realize someday, but are usually doing so while trying to sell a woefully inadequate solution (or, a solution with one new great capability but none of the critical baseline functionality)

So what type of vendor do you want?

e. Open, Honest, and Informed

Even if they don’t have anything explicitly unique.

As SI has noted before, a good vendor is one who will be focussed on

  • a particular market size
  • one or more related industries
  • a subset of functionality where the founders / core team have strength

In addition, it will consult with organizations in that niche, analysts and consultants who serve that niche, and third party experts to get feedback during design, development, initial implementation, etc. and take all that into account in order to design a solution that will solve the problems of the aforementioned identified market niche in a manner that will be usable, and used by, the market they are going after.

It’s not about who has the most features, who has the best bells and whistles, who has the coolest sounding tech under the hood, …

IT IS ABOUT WHAT SOLUTION WILL WORK FOR YOU!

It’s the solution that will solve the 80% of your problems, that will contain all the functionality to do the tasks you do every day (not every quarter or every year), that will make those daily tasks more efficient and effective, that will be used in the majority (not the minority), that will be affordable for a business of your size, and generate an ROI.

And, sometimes the best solution is the NO-AI inside solution with nothing new, but the solution that was form fit for companies of your size in your industry, that streamlines your daily processes, that is easier to use than avoid, that solves the problems you wanted solved, and does so at a fraction of the price of the mega-suite that is just complete overkill with respect to what you are looking for.

Some of the vendors that received the best coverage here on SI are those that didn’t contain a single capability the doctor hadn’t seen ten (to one hundred) times before, but came from vendors who designed a solution for an underserved market niche, made it valuable for that market niche, and were completely honest about what they had and who they were selling to. That’s what the market needs.

AND THAT IS WHAT YOU NEED!

Want A Good Solution, Ask Vendors The Hardest Questions Off The Bat!

Even though they don’t always do so with their slimy sales and misleading marketing practices, be sure to keep it above the waist as you repeatedly hit them as hard and fast as you can. (You don’t want to dance around with a vendor unless you know they can take a few hits and are in it to win it, because once you start to dance they’ll duck and dodge until the end of time).

This post was inspired by THE REVELATOR who asked us What are the most important questions to ask a potential solution provider partner?

1) Can, and will, you show me (not tell me) live … preferably on use cases or data I give you on the spot?

I’ve said it before, and I’ll say it again: Dear Procurement Practitioner, when it comes to solution selection from today’s vendor, your mantra is Show Me, Don’t Tell Me! There’s too much hogwash out there today, buzzwords don’t solve problems, and when you dive into the marketing madness, you see there’s absolutely no value, or even core capability, in what’s being sold by many vendors.

You need solid solutions with substance, not glitzy fake-take UX, broken Gen-AI, or slack-like conversations that don’t do anything. You also need solutions that digitize and automate the 80% of Procurement / Sourcing / Supplier (Data) Management / etc. that you do day-in and day-out, week-in and week-out, month-in and month-out, and year-in and year-out and not the odd special case that comes up once a week, month, or year. And you definitely don’t need solutions that don’t fit your domain.

Moreover, you want relevant demos. If you’re buying janitorial and building maintenance supplies, you don’t want a demo on how the catalog makes it easy to buy sneakers and shoes. (FYI: I’m not being unnecessarily ridiculous here. I have been in demos where a primarily MRO buyer was demoing the top three platforms, and one showed them how to buy sneakers and shoes!) If you get such a ridiculous demo, you want to show that vendor the door as fast as possible because you have one of two situations: they didn’t do their homework on you (and don’t have a clue if their solution is appropriate), or their solution was built, and over customized, for one niche industry and will not easily support yours.

2) Once you show me the core use cases, can, and will, you explain the breadth of use cases you developed your solution for and how they are specific to my business?

You want someone who both understands what they are selling and how it might help your business. Any less and you might as well just roll the bones to select your solution provider. At the end of the day you need to understand the following:

  • there may be 666 logos on the mega map but there is no perfect solution; and nothing that will meet all of the requirements in your RFP
  • the best solution will meet the majority, and, more specifically, the requirements related to the tasks you do all the time, not the ones that you do once a quarter or once a year
  • the best solution for you will be one that comes close and comes from a vendor who both understands this and makes an effort to customize their solution for you in a manner that will achieve maximum results … from the first demo
  • the best solution provider will take the time to explain that which they don’t have time to demo, or can’t demo without your data; even the sales person will attempt it at a high level, and then bring in a product specialist for where more depth is needed

3) Once we tell you the extent of your solution we feel is appropriate, can you talk us through what the implementation and integration to our environment would require without bringing in a paid third party “expert” consultant? And how long will that take?

A great solution provider for you will be one that understands your needs, their platform, and what will need to be done in order to implement it for you, integrate it into your stack, and prepare it for you to extract the value they promise. They won’t need third party help to figure all this out and walk you through it. If a lot of integrations or data migrations are required, they, or you, may need to partner to get it done, but they should still know what’s required.

And, as we said in the introduction, while you should keep your rapid, one-two-three punch, above the belt until the vendor sales rep goes below in their tactics, you should also endeavour to hit ’em as hard as you can with that 1-2-3 combo. If they can’t take it, you want them knocked out before you waste any time on them, because any good vendor will be able to take them and come back with the best damn demo, details, and arguments as to why they are sure their solution will work for your problems, with concrete examples, in a very short timeframe. (And yes, odds are you could be unlucky and have to knock out the first 6 before you find that first 1/7 that is still there so solve problems. But the wait will be worth it.)