But looking closely at the RFP Generator – which has been running with virtually no maintenance for six years – also raised the obvious question of how it should be updated. The current focus of the system is features: users specify their target use cases and the system returns a list of the features those cases require; it then suggests vendors based on how many of those features the vendors provide. That made sense when most systems were largely self-contained bundles of capabilities. Features were the main differentiators and collecting information on each system’s features was the main task of a vendor selection project. Even hands-on evaluation tools like pilot projects and bake-offs, which have to some extent replaced or at least supplemented the traditional Request for Proposal, are still largely aimed at understanding system features more clearly.
But systems today are anything but self-contained. They are components of a larger architecture, more-or-less-fluidly exchanging data and participating in workflows that span different systems, departments and even companies. Any new software has to fit into this larger ecosystem.
This shifts the focus of the purchase process to integration and compatibility. Understanding those is important because different systems are built to play different roles: some are designed to be a company’s primary platform (such as a data warehouse or marketing suite), some are designed to supplement a specific other platform (such as applications on a vendor’s app exchange or an optional module in a platform system), and still others are designed to work with any system that supports the same integration methods.
This means that delivering the right features is no longer enough. Systems must deliver the right features in a way that fits with the company’s larger system architecture. Compatibility with that architecture is the first screen that must be applied to any potential vendor list. In fact, since new tools often make it practical for users to add their own features to a purchased system, finding exactly the right set of features is considerably less important than it used to be.
The CDP Institute’s existing tools already accommodate this change to some extent. We capture whether a particular CDP works with its own database or connects to an external warehouse, which is one of the key architectural differentiators. We also ask whether a system can be installed on-premises, which is an important consideration for some buyers. The vendor selection portion of the new RFP Generator allows users to filter systems on those options. But we could surely do more to understand the different architectural options and the markers that indicate which systems are compatible with which options, and to collect and expose that information.
It's also important to recognize that new architectural options will continue to emerge. The AI-powered transformation of marketing technology is still in that early stage where the industry is trying many alternatives before settling on a standard approach. (Or several standards.) Once the industry coalesces around a few standards, it will be much easier for buyers to identify systems that match their company standard. But it will be at least several years before the winners are clear. This means buyers will struggle for some time to figure out which systems are compatible with their company's chosen approach.
Of course, technology isn’t the only factor that matters when selecting a system. Pricing, industry experience, professional services, typical client size, and local presence are all important considerations. The CDP Institute already captures those in its vendor data and the old RFP Generator already asks the user about them. But it would be helpful to find a way to identify some of the less concrete variables, such as cultural fit, ease of use, and skill requirements.
Ideally, a vendor selection tool would also include a user readiness assessment, to help buyers understand what types of systems are best for them, what kinds of problems they are likely to face, and maybe even what they should do avoid those problems. This is important because -- as I’ve pointed out many times in the past -- by far the most common causes of failure with new systems lie within the purchasing organization, not in the systems themselves.****
In short, finding the right system today is less about finding features and more about architectural and organizational fit. The buying process needs to adjust. Vendor selection tools should – and I’m confident will – adjust along with it.
_______________________________________________________________________
* Lovable also worked very well. Botpress, not so much.
** This was after I spent a day and half prepping the data and writing detailed design instructions. It would have taken much longer if I wasn’t working with materials already assembled for the old system. Still, it would have a taken a conventional developer weeks if not months to deliver a system after they were handed those inputs. Replit cost me $20 in processing credits; conventional developer costs would surely have been in the thousands.
*** You’ll have to trust me that the system is ready to go. There’s no point to releasing it until we make additional changes in the data collected. The same goes for our Vendor Comparison report, which uses the same vendor information as the RFP Generator. Replit built an interactive version of that in just a few minutes. Woot!
****The CDP Institute does have an existing Readiness Assessment tool, although it's limited and not connected with the RFP Generator.
