Back to resources

How to Choose Between Different Vendors

Managing Expectations
Product

7 May, 2021

Kapil Gupta
Kapil Gupta

Product Leader at Deloitte

Kapil Gupta, Product Leader at Deloitte, describes why going through a static demo alone is not enough to make the right decision when choosing between different vendors.

Problem

We had to choose a vendor technology partner for our core technology that would be licensed and used. My team started by researching the space and selecting the initial pool of about forty-five potential partners, and eventually narrowed the applicants down to three vendors through a structured process. Only after going through their demos were we to pick the right partner. But, are demos -- and more precisely, what kind of demos -- enough to make the right decision when choosing between different vendors?

Actions taken

At the second stage of our selection process, we asked three vendors to build a demo for us. Not just to do a simple demo but to create a small, one or two weeks time frame with a subset of requirements. We wanted them to provide us with a tailored demo by building some core capabilities that we were looking for; and we also asked for a session where they could walk us through the demo and allow us to run it with their guidance.

The challenge is that it’s easy to be misled by features showcased in a standard demo because it is easy to misunderstand how they may work in your situation, especially if your needs have more nuances that are not covered in the standard demo. Furthermore, vendors often promise things not doablee or replicable in that specific situation. In this particular case, we identified some of the critical gaps only after we were able to review the tailored demo.

One example of this was that to demonstrate a set of actions, the vendor rep switched tabs in a browser to demonstrate how the next set of actions could be done. They were doing it because there was no automatic way to go from one step to another from within the application. I don’t think the vendor was trying to mislead us intentionally -- they just didn’t think it was a critical gap because they were focused on demonstrating the individual features that we had requested. We didn’t notice it during the initial demo done by the reps because the switchover happened quite quickly. It was only when we got the opportunity to run the demo ourselves that we realized how the vendor product worked. Further discussions with the vendor team uncovered the details and we realized it was a significant gap for us.

Lessons learned

It’s important to approach the vendor selection process with a structured process of analysis, but to make the final determination it’s often useful to do a hand-on evaluation of the vendor technology you plan to acquire. This can be effective even when done in a short time frame, by carefully selecting core features you want to evaluate, and having the vendor partner walk you through the demo as you run it yourself, instead of just watching the demo by them.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

The Art of Asking Why: Narrowing the Gap Between Customers and Users

24 May

Jord Sips, Senior Product Manager at Mews, shares his expertise on a common challenge for product managers – finding root causes and solutions.

Customers
Innovation / Experiment
Product
Personal Growth
Leadership
Stakeholders
Users
Jord Sips

Jord Sips

Senior Product Manager at Mews

Streamlining Product Processes After a Reorganization

16 May

Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Acquisition / Integration
Product Team
Product
Building A Team
Leadership
Internal Communication
Collaboration
Reorganization
Strategy
Team Processes
Cross-Functional Collaboration
Snehal Shaha

Snehal Shaha

Senior EPM/TPM at Apple Inc.

Navigating Disagreements When It Comes to Priorities

9 May

Pavel Safarik, Head of Product at ROI Hunter, shares his insights on how to deal with disagreements about prioritization when building a product.

Innovation / Experiment
Product Team
Product
Dev Processes
Conflict Solving
Internal Communication
Collaboration
Convincing
Strategy
Prioritization
Pavel Safarik

Pavel Safarik

Head of Product at ROI Hunter

The Optimization and Organization of Large Scale Demand

4 May

Kamal Qadri, Senior Manager at FICO, drives the importance of setting expectations when optimizing large-scale requirements.

Managing Expectations
Delegate
Team Processes
Prioritization
Kamal Qadri

Kamal Qadri

Head of Software Quality Assurance at FICO

Why You Should Take Technology Risks in Product Development

25 April

Matias Pizarro, CTO and VP of Residents at ComunidadFeliz, recalls a time in his early career when he took a technology risk that had wide-ranging benefits to his product's user experience.

Innovation / Experiment
Product
Scaling Team
Dev Processes
Matias Pizarro

Matias Pizarro

CTO and VP of Residents at ComunidadFeliz

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.