Category Archives: RFX

Affordable RFPs – The Real Reason(s) They Are So Rare, Part 2

Three articles ago, we noted that The Key to Procurement Software Selection Success: Affordable RFPs! was critical to getting the right technology to help manage your complex supply chain. This was because a proper RFP required a LOT of understanding to get it right, which we covered in detail in that article and summarized in Part 1. Then, two articles ago, we noted that we know all too well that most of you are asking Affordable RFPs — What Are Those? because you’ve never seen one. So in Part 1, after reviewing the requirements of a good RFP, and pointing out why you weren’t likely to get an affordable RFP from the majority of consultancies, we told you that they were still the answer because

  1. they could be affordable if Niche Consultancies stopped thinking like consultants
    and started thinking like enhanced product-and-data-based SaaS Management Providers,
  2. they only require knowledge management and expert augmentation to get it right, and
  3. if a consultancy understood this and was willing to make the necessary investment, they could quickly become a market leader.

Today we’ll explain what that means. We’ll start with the 10 types of understanding we outlined in our first article on The Key to Procurement Software Selection Success: Affordable RFPs!.

  • Procurement Maturity: the consultancy needs a maturity matrix, along with key capabilities at each level, key questions that need to be asked, and follow on questions (and contextual knowledge) to elicit the right details
  • Process Maturity: the consultancy needs a process progression flow to pinpoint where an organization is in each process, both from a human viewpoint and a technology enablement viewpoint
  • (Critical) Use Cases: not just from a standard “procurement” (“sourcing”, “supply chain”, etc.) point of view, but from an industry point of view; the consultancy needs a large library of standard (critical) use cases to build on
  • Current Technical Maturity: not just from an organizational point of view, but based on the progression of technology in a typical enterprise organization (which, of course, requires a knowledge of the history of tech to the present day along with progression flows along architecture, standards, models, etc. )
  • Missing Capabilities: based on the process and tech maturity, but also based on industry peers and leading solutions; requires all of the above AND all of the below
  • Key Solution Types to Address the Gap(s): knowledge of the standard modular / best of breed offerings in the space and related spaces, as well as knowledge of the standard must have, should have, and nice to have capabilities of each solution type, as well as the progression of technical maturity in each area; a rather extensive knowledge base will be required
  • Key Existing Solutions to Maintain: knowledge of the core, should have, and nice to have requirements of foundational ERP/MRP solutions and companion solutions in inventory, logistics, etc. (to make sure the S2P+ solutions will be enough to go to market for or if other modules / systems [and RFPs] will be needed); a more extensive database
  • Globalization Requirements: knowledge of what the e-procurement requirements are in each country the organization does business in, what languages will be absolutely necessary, what currencies will need to be supported, what government regulations there are for the products/services being sourced/sold, what industry regulations/standards need to be supported etc; internal databases or appropriate database subscriptions will be required
  • Service Requirements: knowledge of what requirements are needed for implementation, data migration, integrations, and maintenance; and how to judge if a vendor / service provider is up to the task
  • Unique Organizational Requirements: knowledge of industries and what differentiates them from a process requirement and solution requirement standpoint; detailed, but yet curtailed, knowledge in an internal database that matrixes this by industry, process, and technology solution

In other words, it means a LOT of detailed models, knowledge bases, and standard progressions as well as a lot of detailed knowledge on:

  • metrics where most organizations lie on the maturity curve(s)
  • vendors, what modules they offer, and how they stack up
  • once all of the above is racked, stacked, and mapped, what the core questions are
  • etc.

And that, of course, requires the consultancy to step up and

  • make some up-front and ongoing investments to build these knowledge bases that will
  • allow their intermediate associates to do the baseline work and
  • enable their experts to come in and finish it up in a fraction of the time compared to if they had to do most of the work themselves (i.e. 1/5 to 1/4).

This will allow most of the work to be done by the intermediate resources at a lower day rate, who will be more efficient with a knowledge base to build on, and then the expert to come in and review the work, identify the areas of weakness, and take it the last mile.

And a consultancy who saw that and made the investments could scale up their operation by allowing their top resources to be four times as productive and support four times as many customers (as well as supporting their customers through the implementation in the project, change management, data migration, and assurance roles. (We only said that they had to be vendor neutral, and not be an implementation provider for the vendor’s software. Everything else is process or organization centric, and as the experts, that’s the work they should be doing, and the most valuable work to be done.)

Again, Affordable RFPs are the answer and maybe someday we’ll see a herd of those mythical unicorns.

Affordable RFPs – The Real Reason(s) They Are So Rare, Part 1

Two articles ago, we noted that The Key to Procurement Software Selection Success: Affordable RFPs! was critical to getting the right technology to help manage your complex supply chain. This was because a proper RFP required a LOT of understanding to get it right, including, but not limited to:

  • Procurement Maturity
  • Process Maturity
  • (Critical) Use Cases
  • Current Technical Maturity
  • Missing Capabilities
  • Key Solution Types to Address the Gap(s)
  • Key Existing Solutions to Maintain
  • Globalization Requirements
  • Service Requirements
  • Unique Organizational Requirements (less than you think, but those that exist are situation critical)

And this required a breadth of understanding across

  • the market
  • process evolution
  • use case specification
  • … including what must be technology backed
  • … and what should be technology or data enhanced
  • common module/solution types that mind the gap
  • internal foundations
  • the unique requirements, regulations, and resignations of each country you do business in
  • the services your team, and current partners, can and can’t do — even service specializations you didn’t know exist
  • what other organizations do

And most of this you won’t have in house. So you need Affordable RFPs. But we know all too well that you are all asking Affordable RFPs — What Are Those? because, as far as you know, they don’t seem to exist. And we hear you, because they rarely exist at mid-sized and larger consultancies  (because only a select few from their talent pool can do it efficiently and relatively cost-effectively and those resources with deep experience are going to be dedicated to any F500/G3000 that can afford to pay the A rates to keep them as a dedicated advisor), and unless you are a larger mid-size buying a mini-suite, they don’t even exist at the Niche Consultancies where they should be common.

We also spent a fair amount of time explaining why they don’t exist, even though one would think that they should be readily available at the niche consultancies (as this could not only make those niche consultancies true leaders in Procurement but also help them grow). In this last case, it was because it was typically only their senior resources that could do these projects, and since these projects aren’t currently quick to complete, it doesn’t take long for a senior resource day rate to add up. And, as we noted before, while this won’t be that much when you are larger mid-sized organization looking for a mini-suite or suite, if you’re just looking for one or two modules to fill a gap, this could add up to quite a bit.

So if this is the case, why are we telling you that Affordable RFPs are the answer if they’re almost impossible to find?

Because:

  1. they are the answer,
  2. they would be affordable at Niche Consultancies if those niche consultancies stopped thinking like consultants and started thinking like enhanced product-and-data-based SaaS Management Providers, and
  3. they only require knowledge management and expert augmentation to get it right.

So what would a Niche Consultancy have to do to get it right?

We’ll outline that in our next part. But it starts with investment. (And how many partners at consultancies want to invest their money? They were brought up on the Wall Street Mantra — Other People’s Money.)

 

Affordable RFPs — What Are Those?

A couple of weeks ago we penned an article on The Key to Procurement Software Selection Success: Affordable RFPs!. This resonated with those of you wanting to improve your Procurement operations who were willing to admit that you could use the help, but it also left you with one big question: where to find these affordable RFPs?

And the doctor hears you on this. You can’t just go to any old consulting firm and get an affordable RFP. Most of you have encountered high price tags, whether you went to a Big X, mid-size consulting company, or even a niche specialist. And you’re probably wondering why. Well, first you need to understand the following.

1. The Big X.

There are a number of reasons you’ll RARELY get an affordable RFP from a Big X.

  • their modus operandi is to get their people embedded on your projects and keep them there for as long as possible at 3X to 5X+ their hourly rate, they are service firms with a large number of people to keep employed (and they need to invest in employing those people, and, to be honest, trying to streamline RFP processes across every type of software imaginable is just unreasonable for any company to do, so why should we expect it)
  • they have agreements with a number of big suite vendors where they are a preferred implementation partner (and not only do they get a big referral check in addition to YOUR implementation fees which makes finance happy, if they don’t bring enough clients, they could lose that partnership and the deep insight it gives them into the partner, which is key to them being able to bring value to the implementation — see when should you use a Big X?
  • they’ll put a senior resource / junior partner as lead, but you’ll hardly ever see that person, instead, most of the work will be done by a team of inexperienced recent hires, usually recent graduates, who will, unfortunately, even with a good playbook, rack up the hours just trying to get the basics right as they get the experience needed to be more effective (mainly because this senior resource / junior partner will also be attached to many other projects so that they can close the deals, leaving the team without a lot of senior guidance)

2. The mid-size consultancies.

While it is sometimes possible to get an affordable RFP from a mid-size consultancy, the reality is that it’s a rare occurrence (and your odds are about the same as achieving success with an average technology project which, as per Gartner, is less than 1 in 5, largely because they are never scoped and planned right, starting with the RFP), and most of you never will. As with the Big X, there are a number of reasons you’ll RARELY get an affordable RFP from a mid-size consultancy.

  • like the Big X, they want to get projects that keep their people busy (usually at more reasonable 3X to 4X resource hourly rates) as they want to grow, and this leaves little time for trying to streamline RFP creation methodologies which is possible if they are sticking to a niche with only a few, and maybe a few dozen, different solution modules that would be relevant (and, in their quest to grow, they can totally miss the big picture that it is delivered value that wins repeat business)
  • while they are willing and able to be more impartial than the Big X (who need to keep their partners happy to get the insight and training they need to deliver unparalleled value), they have a few partners they prefer to direct any RFPs (and awards) to as they know the systems well (and can get the implementation work), those resources get it done fast, and it keeps them front and center with the vendors who need to direct implementation work to a third party
  • they can’t afford benchers, so their recent grads are not only the top of their class who have shown aptitude for their domain, but they are balanced by intermediate personnel on the projects who can guide them and there’s usually always at least one senior person, but only the senior people can do the RFPs well enough on their own, so the day rates are almost as high as a Big X as the RFPs tend to be mostly senior and intermediate personnel

3. The niche consultancies.

The niche consultancies are your best bet of getting an affordable RFP, but the reality is that it’s still, unfortunately, hit and miss and it’s likely that less than 1 in 3 of you will see a decent rate when all is said and done (where we measure RFP spend against total system spend over five years and try to maintain the right ratio).

This is despite the facts that:

  • unlike the Big X and mid-size consultancies, they have lower overheads and can keep their bill rates in the 2.5X to 3X range (enough to cover their resources’ hourly rate, overhead, and a fair profit margin)
  • even if they have partnerships with a vendor or three, they tend not to favoured by the vendors who will never direct work to them (and only allow them to implement deals they bring) due to their small size and inability to rapidly scale up (like a Big X or mid-size), which means their bias towards any vendor, if it exists, is quite limited
  • they don’t have junior people, because they can’t afford benchers and resources that don’t deliver with their cost model, and only hire (high-achieving) intermediate and senior personnel, and focus primarily on those who can do small projects entirely on their own or with limited support

When you look at this, you should be able to get a lot of value for a reasonable amount of money. And, make no mistake, you do get value for money.

However, when you look at the total system cost that you can afford as a (smaller) midsize company, and then you look at the cost of getting that good RFP, the problem is that the cost of the RFP is more than you can afford (and should be spending relative to the annual cost of the specialized system you are likely to buy). This means that you end up having to cut corners on the software (and get less from a preferred vendor or go with a more cost effective runner up) or forego more than a modicum of help from the consultancy (where you just get a few advisory days and hope your team to can capture enough of the brain-dump to put together something reasonable).

Even though this shouldn’t be the case.

So why are most niche consultancy RFPs not affordable (unless you are acquiring a mini-suite or significant advanced functionality that comes with a significant price tag and are a larger mid-size with the budget for it) when they could easily pick a focus area and make it so?   And for that matter, why aren’t the razor focused mid-sized consultancies more affordable when they could do the same?  After all, it’s only the Big X where the investment would be unjustified compared to the return, and, to be honest, you are going to them for enterprise systems that cost nine (9), if not ten (10), figures, so you should be expecting to pay high six figures for a good RFP in that situation!   (See when you should use a Big X!)

We’ll get to that in our next installment.

e-Procurement Implementation Success Goes Well Beyond The Basics

the doctor was quite disappointed with this article over on the WorldBank Blogs on 10 success factors for implementing [an] e-Procurement System because all of these “factors” were generic success factors for the implementation of any technical system. Let’s look at them at a high level (and direct you to the article for a description of what the requirements are if they aren’t immediately clear to you):

Governance Principles
all projects need to be managed and governed, so this is pretty much a “d’uh!”
Transparency on Legal and Regulatory Frameworks
any platform that processes any personal, payment, or classified data HAS to adhere to Legal and Regulatory frameworks of ALL countries the corporation operates in, so this is obvious for any platform that requires it
Strategy Ownership and Sustainability
it’s classic project management, no owner, everything goes to cr@p
Implementation and Integration Challenges
preparing for this is just a given
Technical Infrastructure and SaaS-based Systems
all technology implementations need to integrate with the current infrastructure and SaaS systems that contain the necessary data, so this is pretty much a “d’uh!”
Training & Capacity Building
well, you need the capacity and the training regardless of the system being implemented
Engage Stakeholders Actively
without stakeholder support, it will be hard to get the resources for a timely, successful implementation of any technology
Align with International Standards
technology should always align with any regulatory standards in place
Clear Communication and Change Management
necessary for the success of ANY project, not just a technology project, so this is pretty much a super “D’UH!”
Data Security and Privacy
if the data is personal, payment, classified, trade secret, etc. etc. etc. then security and privacy is of more concern than the tech, so, another ‘d’uh!”

e-Procurement success goes beyond the basics. There are too many six, seven, and, for some multinationals locked into 5-year contracts, eight figure acquisitions that have failed to deliver on the promises made. This is because the selection, implementation, and utilization of such systems goes beyond most back-office tech to get right.

Selection

In our recent article on The Key to Procurement Software Selection Success: Affordable RFPs!, we noted that selecting the right vendor was paramount to success, and a critical requirement in this selection process was a GOOD RFP.

Furthermore, that RFP needed to specify, among a host of requirements:

  • typical use cases
  • target processes
  • globalization requirements
  • data migration requirements
  • integration requirements

Why are we calling these out? Because these define the key factors for implementation success!

Implementation

Key Factors are thus:

Primary Components / Modules
… that are needed to support the critical use cases and target processes, that need to be implemented and demonstrated first
Test Cases
that must be passed, in priority order, to ensure the use cases and target processes can be accomplished
… including multi-lingual use cases
that support not only the customer organization requirements but the supplier requirements
Data Migration Requirements
spelled out in detail, as well as cut-over requirements
Cross-System Bi-Directional Integration Requirements
spelled it in minute detail, not just push to the ERP … and considerably more than just a high level holistic strategy … when it comes to tech, the devil truly is in the details and chaos emerges when you overlook even one

Utilization

A system not utilized is a failed system, even if the implementation and integration goes as well as can be reasonably expected. Utilization is critical, especially early on, or widespread adoption will never be reached. This is why it’s paramount that the functionality required for the critical use cases be implemented and tested first so that utilization of key capabilities can begin as soon as possible, leading to adoption.

In other words, the basic checklist for technology implementation is nowhere near enough for the successful implementation of procurement technology — that success requires going deep.