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.