Category Archives: RFX

DEAR ENTERPRISE PROCUREMENT SOFTWARE BUYER: THERE ARE NO FREE RFPs!

This originally published June 29 (2024) and is being reprinted due to how important it is to remember as you enter a new budgetary year and seek out new technology.

This shouldn’t have to be said (again), but apparently it does since Zip has relaunched the FREE RFP madness in Source-to-Pay (that began in 2006 when Procuri first aggressively launched the Sourcing, Supplier Management, Contract Management, and Spend Analysis RFPs) with an RFP that is intake heavy, orchestrate light, process deficient, and, like many RFPs before, completely misses some of the key points when going to market for a technology solution. (Especially since there isn’t a single FREE RFP template from a vendor that isn’t intrinsically weighted towards the vendor’s solution, as it’s always written from the viewpoint of what the vendor believes is important.)

the doctor has extensively written about RFPs and the RFP process here on SI in the past, but, at a high level, a good RFP specifies:

  • your current state,
    it does NOT leave this out leaving the vendor to guess your technical and process maturity
  • what you need the solution to do
    NOT just a list of feature/functions
  • what ecosystem you need the solution to work in
    NOT just a list of protocols or APIs that must be supported
  • where the data will live
    and, if in the solution, how you will access it (for free) for exports and off-(vendor-)site backups, do NOT leave this out
  • what support you need from the vendor
    NOT just whether the vendor offers integration / implementation services and their hourly / project rate
  • any specific services you would like from the vendor
    NOT a list of all services you might want to buy someday
  • what the precise scope of the RFP is if it is part of a larger project
    NOT a blanket request for the vendor to “address what they can”
  • what regulations and laws you are subject to that the vendor must support
    NOT just an extensive list of every standard and protocol you can think of
  • what languages and geographies and time zones you need supported
  • any additional requirements the vendor will need to adhere to based on the regulations you or the vendor would be subject to and additional requirements your organization puts in place
    NOT endless forms of every question you can think of that might never be relevant
  • your goal state,
    it does NOT leave the vendor to guess what you are looking for (note that “goal” defines what you want to achieve, it is up to the vendor to define how they will help you achieve it)
  • what (management) processes you use to work with vendors — and —
  • what collaboration tools you make available to vendors and what your expectations are of them

And it is only created after a current state assessment, goal state specification, and key use-case identification so that it is relatively clear on organization needs and vendors have no excuse to provide a poor response.

Furthermore, a good RFP does NOT contain:

  • requests for features/functions you don’t currently need (but you can ask for a roadmap)
  • specific requests for a certain type of AI/ML/Analytics/Optimization/etc. when you don’t even know what that tech actually does — let the vendor tell you, and then show you, how their tech solves their problem
    (after all, there are almost NO valid uses for Gen-AI in S2P)
  • specific requests on the technology stack, when it doesn’t matter if they use Java or Ruby, host on AWS or Azure, etc.
  • requests for audits (tech, environmental, social welfare, etc.) when you haven’t selected the vendor for an award, pending a successful negotiation
  • requests for service professional resumes when you haven’t selected the vendor for an award that includes professional service, pending a successful negotiation
  • requests for financials, when you haven’t selected the vendor for an award pending a successful negotiation
    (because these last three [3] will scare some vendors off and possibly prevent the best vendor for you from even acknowledging your RFP exists)

And, a good RFP, goes to the right providers! This means that you need to select providers with the right type of solution you need before you issue the RFP, and then only issue to providers that you know offer that type of solution. (You can use analyst reports here if you like to identify potential vendors, but remember these maps cannot be used for solution selection! You will then need to do some basic research to make sure the vendor appears to fit the criteria.)

And if there are a lot of potential providers, you may need to do a RFI — Request for Interest / Intent (to Bid) — where you specify at a high level what the RFP you intend to issue is for, and if you get a lot of positive responses, do an initial call with the providers to confirm not only interest but the solution offered is relevant to your organization. (After all, at the end of the day, as The Revelator is quick to point out, it’s as much about the people behind the technology as the technology itself if you expect to be served by the provider.)

And even if you don’t need to an RFI before the RFP, you should still reach out to the vendors you want to respond, let them know the RFP is coming, and let them know you’ve done your research, believe they are one of the top 5 vendors, and are looking forward to their response. (Otherwise, you might find you don’t get as many responses as you’d hope for as vendors prioritize RFPs that they believe they have a good shot at winning vs. random unexpected RFP requests from unknown companies.)

At the end of the day, if you don’t know:

  • what the main categories of S2P+ solutions are
  • what the typical capabilities of a solution type are, what’s below, average or above
  • who the vendors are
  • how to determine your current state of process maturity (and how that compares to the industry, market, and best-in-class) and what a solution could do for you
  • how to evaluate a vendor’s solution
  • how to evaluate a vendor overall
  • how to write a good RFP that balances core business, tech, and solution requirements to maximize your chances of finding a good vendor for you

and the reality is that you most likely don’t (as less than 10% of Procurement departments are world class, as per Hackett research going back to the 2000s where they also determined the typical journey for an organization to become best-in-class in Procurement was 8 years, and that’s the minimum requirement to write a world-class technology RFP), then you should engage help from an expert to help you craft that RFP, be it an independent consultant or firm that specializes in Procurement transformation.

It is also critically important that the firm you select to help you needs to be neutral (not aligned with one solution provider who refers implementations to them in return for potential customer referrals) and that the firm does not rely on analyst maps either!

If you want help, the doctor has relationships with leading, neutral, firms on both sides of the pond who can help you, and who he will work with to make sure the technology / solution component is precisely what you need to get the right responses from vendors. Simply contact the doctor (at) sourcinginnovation [dot] com if you would like help getting it right.

Simply put, getting help with your technology RFP is the best insurance money you can spend. When you considering that, all in, these solutions will cost seven (7) or eight (8) figures over just a few years, you should be willing to spend 5% to 10% of the initial contract value to make sure you get it right. (Especially when there isn’t a single Private Equity Firm that wouldn’t invest in a technology player without doing a six [6], if not seven [7] figure due diligence first … and sometimes the firm will do this and then walk away! At least in your case, when you work with someone who can identify multiple potential vendors, you’re certain to find one at the end of the day.)

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.